Home

 

Performing local administration tasks using MQSC commands

 

This section introduces you to MQSC commands and tells you how to use them for some common tasks. If you use WebSphere MQ for Windows or WebSphere MQ for Linux (x86 platform), we can also perform the operations described in this section using the WebSphere MQ Explorer. See Administration using the WebSphere MQ Explorer for more information.

We can use MQSC commands to manage queue manager objects, including the queue manager itself, queues, process definitions, channels, client connection channels, listeners, services, namelists, clusters, and authentication information objects. This section deals with queue managers, queues, and process definitions; for information about administering channel, client connection channel, and listener objects, see WebSphere MQ Intercommunications. For information about all the MQSC commands for managing queue manager objects, see WebSphere MQ Script (MQSC) Command Reference.

You issue MQSC commands to a queue manager using the runmqsc command. (For details of this command, see runmqsc (run MQSC commands).) We can do this interactively, issuing commands from a keyboard, or we can redirect the standard input device (stdin) to run a sequence of commands from an ASCII text file. In both cases, the format of the commands is the same. (For information about running the commands from a text file, see Running MQSC commands from text files.)

We can run the runmqsc command in three ways, depending on the flags set on the command:

• Verify a command without running it, where the MQSC commands are verified on a local queue manager, but are not actually run.

• Run a command on a local queue manager, where the MQSC commands are run on a local queue manager.

• Run a command on a remote queue manager, where the MQSC commands are run on a remote queue manager.

We can also run the command followed by a question mark to display the syntax.

Object attributes specified in MQSC commands are shown in this book in uppercase (for example, RQMNAME), although they are not case sensitive. MQSC command attribute names are limited to eight characters. MQSC commands are available on other platforms, including i5/OS and z/OS.

MQSC commands are summarized in Comparing command sets.The WebSphere MQ Script (MQSC) Command Reference contains a description of each MQSC command and its syntax.

• WebSphere MQ object names
  

• Standard input and output
  

• Using MQSC commands interactively
  

• Running MQSC commands from text files
  

• Running MQSC commands from batch files
  

• Resolving problems with MQSC commands
  

 

Parent topic:

Administering local WebSphere MQ objects

fa11050_

 

Home