Directing commands to different queue managers on z/OS®

We can use the command scope to control on which queue manager the command runs.

We can choose to execute a command on the queue manager where it is entered, or on a different queue manager in the queue sharing group. We can also choose to issue a particular command in parallel on all the queue managers in a queue sharing group. This is possible for both MQSC commands and PCF commands.

This is determined by the command scope. The command scope is used with the object disposition to determine which version of an object you want to work with.

For example, you might want to alter some of the attributes of an object, the definition of which is held in the shared repository.

• You might want to change the version on one queue manager only, and not make any changes to the version on the repository or those in use by other queue managers.
• You might want to change the version in the shared repository for future users, but leave existing copies unchanged.
• You might want to change the version in the shared repository, but also want your changes to be reflected immediately on all the queue managers in the queue sharing group that hold a copy of the object on their page set zero.

Use the command scope to specify whether the command is executed on this queue manager, another queue manager, or all queue managers. Use the object disposition to specify whether the object you are manipulating is in the shared repository (a group object), or is a local copy on page set zero (a queue manager object).

You do not have to specify the command scope and object disposition to work with a shared queue because every queue manager in the queue sharing group handles the shared queue as a single queue.