Event manager (EM)

The event manager (EM) subtask processes job-tracking, and user-created events, and updates the current plan accordingly. Event records are passed from a number of event writers via event reader subtasks, the network communication function, and XCF, and are passed to the EM queue via the data router subtask. The EM subtask calls a queue handler routine to retrieve events from the queue.HCL Workload Automation for Z produces tracking, submission, and synch events. Tracking events are preceded by the letter A (for JES2 complexes) or by the letter B (for JES3 complexes).

Note: HCL Workload Automation for Z does not track jobs with TYPRUN=SCAN.

The z/OS® tracking events are:

1
Reader event
2
Start event
3S
Step-end events
3J
Job or started-task end event
3P
Job or started-task termination event
4
Print-end event
5
Purge event.
The submit events are:
IJ0
Submit synch event
IJ1
Submit job JCL
IJ2
Submit started-task JCL
IJ3
Submit standalone cleanup job
IWTO
Submit WTO message
IREL
Submit a release command

User-created events (created with the EQQUSINx subroutines or the corresponding TSO commands) are sorted between jobs in event-creation order.

Events started by distributed agents are 0-type event records.

Most events processed by the queue handler subroutine are automatically created job-tracking events. To process the event, the subroutine:
  • Updates the event reader position of the event data set that this event was read from.
  • Checks if the event is for an operation defined in the current plan.
    • If the event is for an operation that can be matched with an operation in the current plan, the event manager processes the event by updating the current plan.
    • If the event is not for an operation that is controlled by HCL Workload Automation for Z but is a reader event, a start event, or a user event with status Q, the EM checks if the event matches an event-triggered tracking (ETT) trigger, if ETT is active.
    • If the event is not for an operation that is controlled by HCL Workload Automation for Z and the job is held by the HCL Workload Automation for Z subsystem (via the HOLDJOB parameter of the EWTROPTS initialization statement), EM releases the job from hold.
  • Writes a record to the current job-tracking log if the event is for an HCL Workload Automation for Z operation and was successfully processed.
  • If the event is for an HCL Workload Automation for Z submit synchronization response, the operations for the corresponding workstation are analyzed; if the submit requests are lost, the operations are flagged as requiring the submit requests to be resent, and the workstation analyzer is posted.
  • If the event is for an HCL Workload Automation for Z job but cannot be processed immediately, the EM updates the job-tracking log and places the event on a suspend chain. Suspended events are examined by the EM every time the subtask gets control. If the event cannot be successfully matched against an operation in the current plan within 5 minutes, the event is discarded. If the event can be matched but is received out of sequence and is still out of sequence after 5 minutes, the event is processed and the operation might be set to ended in error status.

Subtask initialization consists of building the EM environment and opening all logical VSAM files that are required.

Subtask mainline logic consists of providing service for the following events:
  • Timer expiration. Retry processing of suspended events.
  • Subtask stop request.
  • Add an event record to the event manager queue.

Subtask termination consists of closing all open files.