Invoking the monitor DSP *CALL,MONITOR

Function

JES3 examines monitoring parameters to see if any resources or queues are being monitored. The monitoring parameters are specified either on the MNTRDEF macro or the *START,MONITOR command. (For more information on the MNTRDEF macro, see z/OS JES3 Customization.) If a non-zero value is specified for the interval, a resource or queue is to be monitored. The monitor DSP sets a timer. At the end of each interval, the monitor examines the resource or queue and reports exceptions.

The *CALL,MONITOR command is issued automatically by JES3 on every global restart if the MONITOR DSP is not already active. Therefore you will not need to issue this command unless you have previously issued the *CANCEL,MONITOR command.

Syntax


>>-+-*CALL-+--,--MONITOR---------------------------------------><
   '-*X----'

Parameters

The monitor DSP receives control and issues the following message to indicate the monitor is active:

*X,MONITOR  IAT6306 JOB (JOB33580) IS MONITOR , CALLED BY 01 IAT6394 MONITOR
FUNCTION ACTIVE

Rules

The MONITOR DSP is shipped with all resources and queues being monitored except for ALLOCQ and VERIFYQ.
If you want to monitor either or both of these, or change parameters of existing queues and resources, either:
- Modify the interval value on the INTERV keyword using the *START,MONITOR,ID= command. See Modifying or displaying the monitoring parameters *START,MONITOR.
- Update the INTERVAL parameter on the MNTRDEF macro.
Only one copy of the monitor DSP can be active at a time.
If a warm or hot start is performed while the monitor DSP is active, the monitor DSP is automatically reactivated after the operator enters the *S,JSS command. However, any changes made to the monitoring parameters since the monitor DSP was originally called are lost.