Setting alerts or actions if an operation does not start or complete

In the JTOPTS statement, specify NOTSTARTCOMP(Y) to have an alert issued or an action taken when an operation does not complete or start within its deadline or by the time that you specify.

In the TIME SPECIFICATIONS panel you set how you want to be notified about the operation completion or start, when it does not occur at expected time.
Deadline and Action
Deadline day and time for the operation to complete, related to the application start time. If the operation does not complete within this time setting, an alert is issued and, optionally, an action taken.
Not Started Alert
Day offset and time, related to the application start day, used to check if the operation has not yet started. If, by the time specified, the operation has not started, an alert is issued.
Not Started Action
Day offset and time, related to the application start day, used to check if the operation has not yet started. If, by the time specified, the operation has not started, an alert is issued and an action taken.
For detailed information about how to set alerts and actions through ISPF panels, see Specifying times, actions, and alerts for operations. You can set a Deadline Action, Not Started Alert, and Not Started Action also through the following interfaces:
Program interface (PIF) and Batch Command Interface (BCIT)
The following segments and requests have been added or updated (see Driving HCL Workload Automation for Z):
  • ADLAT
  • ADOP
  • ADVDD
  • CPLAT, Insert CPLAT, Delete CPLAT
  • CPOP, Insert CPOP, Modify CPOP
  • List CPOPCOM
Workload Automation Programming Language (WAPL)
The following statements and requests have been added or updated (see Workload Automation Programming Language for z/OS User's Guide and Reference):
  • ADLAT
  • ADOP
  • ADVDD
  • Insert CPLAT, Delete CPLAT
  • CPOP, Insert CPOP, Modify CPOP
  • List CPOPCOM
Batch loader
The following statements have been added or updated (see Managing the Workload):
  • ADLAT
  • ADOP
  • ADVDD
REST APIs
SELECT 
GET --> /{engine}/model/jobstream/{jobstreamId} 
INSERT
POST --> /{engine}/model/jobstream/ 
REPLACE 
PUT --> /{engine}/model/jobstream/{jobstreamId}
Note: The object ID has now a new layout, Base64-encoded, that enables you to use the Swagger button Try it out!