System Administration Guide

Using control commands

You use control commands to perform operations on queue managers, command servers, and channels. Control commands can be divided into three categories, as shown in Table 2.

Table 2. Categories of control commands

Category	Description
Queue manager commands	Queue manager control commands include commands for creating, starting, stopping, and deleting queue managers and command servers
Channel commands	Channel commands include commands for starting and ending channels and channel initiators
Utility commands	Utility commands include commands associated with: Running MQSC commands Conversion exits Authority management Recording and recovering media images of queue manager resources Displaying and resolving transactions Trigger monitors Displaying the file names of WebSphere MQ objects

For information about administration tasks for channels, see WebSphere MQ Intercommunication.

Using control commands on Windows systems

In WebSphere MQ for Windows, you enter control commands at a command prompt. In these environments, control commands and their flags are not case sensitive, but arguments to those commands (such as queue names and queue-manager names) are case sensitive.

For example, in the command:

crtmqm /u SYSTEM.DEAD.LETTER.QUEUE jupiter.queue.manager

The command name can be entered in uppercase or lowercase, or a mixture of the two. These are all valid: crtmqm, CRTMQM, and CRTmqm.
The flag can be entered as -u, -U, /u, or /U.
SYSTEM.DEAD.LETTER.QUEUE and jupiter.queue.manager must be entered exactly as shown.

For more information, see Chapter 16, How to use WebSphere MQ control commands.

Using the WebSphere MQ Explorer on Windows systems

On WebSphere MQ for Windows, you can use the WebSphere MQ Explorer to perform the operations described in this chapter, except for:

Making an existing queue manager the default
Preemptive shutdown

The tables in Appendix E, "Comparing command sets" summarize which control commands have an equivalent WebSphere MQ Explorer implementation.

Using control commands on UNIX systems

In WebSphere MQ for UNIX systems, you enter control commands in a shell window. In these environments, control commands, including the command name itself, the flags, and any arguments, are case sensitive. For example, in the command:

crtmqm -u SYSTEM.DEAD.LETTER.QUEUE jupiter.queue.manager

The command name must be crtmqm, not CRTMQM.
The flag must be -u, not -U.
The dead-letter queue is called SYSTEM.DEAD.LETTER.QUEUE.
The argument is specified as jupiter.queue.manager, which is different from JUPITER.queue.manager.

Take care to type the commands exactly as you see them in the examples.

For more information about the crtmqm command, see crtmqm (create queue manager).