Critical Path Monitor (CPM) monitors critical job streams and issues alerts if the job streams do not complete within the service level agreement time. Previous releases of Scheduler did not load the job flow until the first job in the stream is submitted.
By default Scheduler informs Critical Path Monitor (CPM) when the first job in the job flow is submitted. An option is available to inform CPM when the first job in the job flow enters the active workload. The option is CAS9 CAIJGEN CPMLOAD=ENTRY.
This installation option, CAS9 CAIJGEN CPMLOAD adds a feature where the event is loaded when the first job in the stream is added to the active workload. This normally happens during Autoscan.
The usage of the CPMLOAD option is described below.
CAS9 CAIJGEN CPMLOAD=ENTRY
Option 'ENTRY' allows the load event to occur when the first job in the flow enters the active workload. Therefore after Autoscan, the flows will be seen in CPM.
Because CPMLOAD=ENTRY causes CPM to build the flow when the first job is in the active workload, changes to the jobs in the flow can cause the flow to be incomplete. This can happen if jobs in the flow are added by using the RUN SCHEDULE, RUN JOB, or ADD JOB commands. Even the ADD PRED command can change a flow. When this happens, use the REFRESH CPMLOAD command to force CPM to rebuild a flow.
CAS9 CAIJGEN CPMLOAD=START
This is the default option. The load event occurs when the first job is submitted and the flow is seen in CPM at this time. This is how previous versions of Scheduler worked.
-
The CPMLOAD option is documented in the CA Scheduler Job Management Systems Programmer Guide, Chapter 2 Initialization.