Choosing a queue manager

While you are viewing the initial panel, you are not connected to any queue manager. However, as soon as you press Enter, you are connected to the queue manager, or a queue manager in the queue-sharing group named in the Connect name field. We can leave this field blank; this means you are using the default queue manager for batch applications. This is defined in CSQBDEFV (see the WebSphere MQ for z/OS System Setup Guide for information about this).

Use the Target queue manager field to specify the queue manager where the actions you request are to be performed. If you leave this field blank, it defaults to the queue manager specified in the Connect name field. We can specify a target queue manager that is not the one you connect to. In this case, you would normally specify the name of a remote queue manager object that provides a queue manager alias definition (the name is used as the ObjectQMgrName when opening the command input queue). To do this, have suitable queues and channels set up to access the remote queue manager.

The Action queue manager allows you to specify a queue manager that is in the same queue-sharing group as the queue manager specified in the Target queue manager field to be the queue manager where the actions you request are to be performed. If you specify * in this field, the actions you request are performed on all queue managers in the queue-sharing group. If you leave this field blank, it defaults to the value specified in the Target queue manager field. The Action queue manager field corresponds to using the CMDSCOPE command modifier described in the WebSphere MQ Script (MQSC) Command Reference.

 

Queue manager defaults

If you leave any queue manager fields blank, or choose to connect to a queue-sharing group, a secondary window appears when you press Enter. This window confirms the names of the queue managers you will be using. Press Enter to continue. When you return to the initial panel after having made some requests, you find fields filled in with the actual names.

 

Queue manager levels

The Operations and Control panels work satisfactorily only with queue managers that are running on z/OS, and whose command level matches that of the panels, currently 530, 531, or 600.

If these conditions are not met, it is likely that actions work only partially, incorrectly, or not at all, and that the replies from the queue manager are not recognized.

If the action queue manager is not at command level 600, some fields are not displayed, and some values cannot be entered. A few objects and actions are disallowed. In such cases, a secondary window appears asking for you to confirm that you want to proceed.