Starting a local queue manager

You must:

1. Create a local queue manager by issuing the CRTMQM command from an OS/400 command line.

   When you create a queue manager, you have the option of making that queue manager the default queue manager.

   The default queue manager (of which there can only be one) is the queue manager to which a CL command applies, if the queue manager name (MQMNAME) parameter is omitted.

   Note:

   One queue manager must be selected as the default queue manager.

2. Start a local queue manager by issuing the STRMQM command from an OS/400 command line.

   If the queue manager start up takes more than a few seconds WebSphere MQ will show status messages intermittently detailing the start up progress. For more information on these messages see WebSphere MQ Messages.

We can stop a queue manager by issuing the ENDMQM command from the OS/400 command line, and control a queue manager by issuing other WebSphere MQ commands from an OS/400 command line.

The principal commands are described later in this chapter.

Remote queue managers cannot be started remotely but must be created and started in their systems by local operators. An exception to this is where remote operating facilities (outside WebSphere MQ for iSeries) exist to enable such operations.

The local queue administrator cannot stop a remote queue manager.

Note:

As part of quiescing a WebSphere MQ (or MQSeries) system, you have to quiesce the active queue managers. This is described in Appendix D. Quiescing WebSphere MQ and MQSeries systems.