+

Search Tips | Advanced Search

Operations and control panels for IBM MQ for z/OS

We can use the IBM MQ operations and control panels to perform administration tasks on IBM MQ objects. Use this topic as an introduction to the commands, and control panels.

We use these panels for defining, displaying, altering, or deleting IBM MQ objects. Use the panels for day-to-day administration and for making small changes to objects. If you are setting up or changing many objects, use the COMMAND function of the CSQUTIL utility program.

The operations and control panels support the controls for the channel initiator (for example, to start a channel or a TCP/IP listener), for clustering, and for security. They also enable you to display information about threads and page set usage.

The panels work by sending MQSC type IBM MQ commands to a queue manager, through the system command input queue.

Note:
  1. The z/OS® IBM MQ operations and controls panels (CSQOREXX) might not support all new function and parameters added from version 7 onwards. For example, there are no panels for the direct manipulation of topic objects or subscriptions.Using one of the following supported mechanisms allows you to administer publish/subscribe definitions and other system controls that are not directly available from other panels:
    1. IBM MQ Explorer
    2. z/OS console
    3. Programmable Command Format (PCF) messages
    4. COMMAND function of CSQUTIL

    Note that the generic Command action in the CSQOREXX panels allows you to issue any valid MQSC command, including SMDS related commands. We can use all the commands that the COMMAND function of CSQUTIL issues.

  2. We cannot issue the IBM MQ commands directly from the command line in the panels.
  3. To use the operations and control panels, you must have the correct security authorization; this is described in the User IDs for command security and command resource security.
  4. We cannot provide a user ID and password using CSQUTIL, or the CSQOREXX panels. Instead, if you user ID has UPDATE authority to the BATCH profile in MQCONN, we can bypass the CHCKLOCL(REQUIRED setting. See Use CHCKLOCL on locally bound applications for more information.