User exit and task relationships

User exits in HCL Workload Automation for Z and User exit and task relationships show the subsystems in which each user exit of HCL Workload Automation for Z is run. User exits in HCL Workload Automation for Z lists the user exits and assigns them a key heading that you can match in User exit and task relationships to find the corresponding subsystem and task.
Table 1. User exits in HCL Workload Automation for Z
Exit Name Exit Type Heading in User exit and task relationships
EQQUX000 Start/Stop 0
EQQUX001 Job-Submit 1
EQQUX002 Job-Library-Read 2
EQQUX003 Application-Description-Feedback 3
EQQUX004 Event-Filtering 4
EQQUX005 SYSOUT Archiving 5
EQQUX006 Incident-Record-Create 6
EQQUX007 Operation-Status-Change 7
EQQUX009 Operation-Initiation 9
EQQUX011 Job-Tracking Log Write 11
EQQUX013 Job-Tailoring Prevention 1
EQQUXPIF Application-Description-Validation AV
EQQUXSAZ System Automation command SAZ
User defined JCL-Imbed (FETCH Directive) JCL
User defined JCL-Variable-Substitution JVAR
User defined Automatic-Job-Recovery AR
User defined Daily-Planning-Report DP
User exit and task relationships shows whether each exit is executed in the Controller, the Tracker, or in a batch program. Tracker exits are run also in the Controller if the Controller has an Event Writer task; that is, if EWTRTASK(YES) is specified in OPCOPTS.
Table 2. User exit and task relationships
Subsystem Task 0 1 2 3 4 5 6 7 9 11 JCL JVAR AR DP AV SAZ
All System Task Dispatcher X
Controller Automatic Recovery S S S S
Controller Event Manager S S S
Controller External Router X
Controller General Service S S S S S S
Controller Normal Mode Manager S S S
Controller Workstation Analyzer S S S S S S S S
Trackers/ Controller Event Writer X
Trackers/ Controller Job Completion Checker X X
Batch Daily Planning X
PIF AD Validation X
Notes:
  1. The S mark means that the execution in the part of the task where the exit is run is subject to serialization. The X mark implies that there is no serialization.
  2. When a task operates on a resource, it holds it exclusively. Normally the resource is the current plan. While the task is updating the current plan, no other task can reference the current plan at the same time.
  3. An exit should avoid processing, such as I/O operations, that may result in system waits and must not perform requests to the HCL Workload Automation for Z program interface.
  4. Termination of the Job Completion Checker exits (EQQUX005 and EQQUX006) precludes the ending of the connected job.