MONPOL
Purpose
The MONPOL statement defines the monitoring policy based on which IBM Tivoli Workload Scheduler for z/OS operations are automatically monitored. The operations satisfying the specified policy, together with all operations manually flagged using EXTERNAL MONITOR=YES, constitute the current set of monitored operations. One or more values can be specified for the MONPOL statement.
This statement is only used in conjunction with the MONOPTS statement (used by IBM® Tivoli® Monitoring) or when EXTMON = YES has been specified in the OPCOPTS statement (used by Tivoli Business Systems Manager).
Format
.-ERROR----. >>-MONPOL--OPERATION(-+-CRITICAL-+-)--------------------------->< +-LATE-----+ +-DURATION-+ '-MANUAL---'
Parameters
- (OPERATION CRITICAL||ERROR|LATE|DURATION|MANUAL)
- Defines the criteria used to select operations to be monitored
by IBM Tivoli Monitoring or by Tivoli Business Systems Manager
- CRITICAL
- The scheduler will monitor operations that
are:
- Eligible for WLM assistance.
- Included in a critical network. In particular, when the scheduler recalculates a critical path or changes the risk level of an operation, it sends an event to the Tivoli Universal Agent.
- Added to the hot list.
- ERROR
- All operations that ended in error will be monitored. This is the default value.
- LATE
- All late operations will be monitored. An operation is considered late if it reaches its latest start time and is not started, complete, or deleted.
- DURATION
- All operations that run beyond their estimated duration time will be monitored.
- MANUAL
- Only those jobs explicitly flagged by the user as "monitored" will be selected. This value excludes all other values specified.
Notes:- The MONPOL statement is not retroactive. Based on the specified policy, operations will be selected for monitoring only when their next change of status matching the MONPOL criteria occurs. If an operation is in one of the specified states before MONPOL is in effect, it will not be monitored.
- When an operation has been promoted to "monitored" for a LATE or DURATION condition, it will continue to be monitored even if the EXTERNAL MONITOR flag for the operation is subsequently changed to NO.
Examples
MONPOL OPERATION (CRITICAL 1
LATE
DURATION)
In this example of MONPOL statement:
- 1
- Operations eligible for WLM assistance, included in a critical network, and added to the hot list will be automatically selected for monitoring.