Previous Topic: Message Queue Manager: OPVMQMNext Topic: Queue Manager Console Messages


Execution Considerations

The utility OPVMQM is included in data set &hlq.CCLXEXEC, and must be made resident in a library containing REXX members which will be concatenated into filename SYSEXEC. SYSEXEC can then be allocated to an individual TSO User ID, or contained in the JCL containing the OPSIMEX command. The global variable queue manager is a REXX program, designed to be executed using the command.

OPS OPSIMEX (OI)

As with any OI command, it can be directly executed as a command, or submitted with surrounding JCL. A batch submission allows introducing a different SYSEXEC DD definition and target CA OPS/MVS SSID specification, but command execution requires that both be predefined. OPVMQM utilizes CA OPS/MVS services, so CA OPS/MVS must be active.

Each execution will append the text string in its ARG parameter as one message to the queue. Tailoring is limited to the global variable name which must correspond to the server's definition. The default name, as packaged, is a REXX label MSGQUE, with the value 'GLVTEMP0.MSG.OPVMSV.

The execution syntax is that of OPSIMEX:

oi  opvmqm  ARG('text'){,SUBSYS=ssid}
'text'

Contains the text string of either a local command, or a message to a client. Text cannot be omitted.

ssid

An optional CA OPS/MVS subsystem designator if the default is not desired.

IMPORTANT: This is not the SSID where OPVMQM begins execution, but the designator of another CA OPS/MVS system where the message queue is updated.