CPFs in a sysplex environment

If you are in a sysplex environment, WebSphere MQ registers your CPFs to enable you to enter a command from any console in the sysplex and route that command to the appropriate system for execution. The command responses are returned to the originating console.

 

Defining the scope for sysplex operation

Scope is used to determine the type of CPF registration performed by the WebSphere MQ subsystem when you are running WebSphere MQ in a sysplex environment.

Possible values for scope are as follows:

M

System scope.

The CPF is registered with z/OS at system IPL time by WebSphere MQ and remains registered for the entire time that the z/OS system is active.

WebSphere MQ commands must be entered at a console connected to the z/OS image running the target subsystem, or use ROUTE commands to direct the command to that image.

You should use this option if you are not running in a sysplex.

S

Sysplex started scope.

The CPF is registered with z/OS when the WebSphere MQ subsystem is started, and remains active until the WebSphere MQ subsystem terminates.

You must use ROUTE commands to direct the original START QMGR command to the target system, but all further WebSphere MQ commands can be entered at any console connected to the sysplex, and are routed to the target system automatically.

After WebSphere MQ termination, use the ROUTE commands to direct subsequent START commands to the target WebSphere MQ subsystem.

X

Sysplex IPL scope.

The CPF is registered with z/OS at system IPL time by WebSphere MQ and remains registered for the entire time that the z/OS system is active.

WebSphere MQ commands can be entered at any console connected to the sysplex, and are routed to the image that is executing the target system automatically.

A WebSphere MQ subsystem with a CPF with scope of S can be defined on one or more z/OS images within a sysplex, so these images can share a single subsystem name table. However, ensure that the initial START command is issued on (or routed to) the z/OS image on which you want the WebSphere MQ subsystem to run. If you use this option, we can stop the WebSphere MQ subsystem and restart it on a different z/OS image within the sysplex without having to change the subsystem name table or re-IPL a z/OS system.

A WebSphere MQ subsystem with a CPF with scope of X can only be defined on one z/OS image within a sysplex. If you use this option, define a unique subsystem name table for each z/OS image requiring WebSphere MQ subsystems with CPFs of scope X.

If you want to use the z/OS automatic restart manager (ARM) to restart queue managers in different z/OS images automatically, every queue manager must be defined in each z/OS image on which that queue manager might be restarted. Every queue manager must be defined with a sysplex-wide, unique 4-character subsystem name with a CPF scope of S.