Subtasks
An HCL Workload Automation for Z address space (subsystem) consists of many z/OS subtasks. Some of these subtasks are always attached when the subsystem is started, others are conditionally attached according to initialization parameters specified for the scheduler options (OPCOPTS) statement in the HCL Workload Automation for Z parameter library.
HCL Workload Automation for Z subtasks describes the subtasks.
| Subtask ID | Component code | Description | Activated by OPCOPTS parameter | Function |
|---|---|---|---|---|
| APPC | PP | APPC functions | APPCTASK(YES) | Starts APPC support |
| AR | AR | Automatic recovery | RECOVERY(YES) | Manages failing operations |
| CPH | CPH | Critical path handler | Always activated | Updates the critical job table |
| DRT | DX | Data router | Always activated | Routes data to other subtasks or HCL Workload Automation for Z subsystems |
| EMGR | EM | Event manager | OPCHOST(YES) | Processes job-tracking events |
| ERDR | ER | Event reader | ERDRTASK(n) | Reads events from an event data set |
| EWTR | EW | Event writer | EWTRTASK(YES) | Writes events to an event data set |
| EXA | EX | External router | OPCHOST(YES) | Calls EQQUX009 to route submit requests to a user-defined destination ID |
| FL | FL | Fetch joblog | RCLEANUP(YES) | Retrieves JOBLOG information |
| GEN | GS | General service | OPCHOST(YES) | Processes HCL Workload Automation for Z dialog requests |
| HTC | HTC | HTTP client | HTTP keyword of ROUTOPTS | Manages communications with z-centric agents through the HTTP or HTTPS protocol |
| HTS | HTS | HTTP client | HTTP keyword of ROUTOPTS | Listens for inbound requests from the z-centric agent |
| ID | ID | TCP/IP Data Store | TCPDEST keyword of FLOPTS | Manages communications with TCP/IP-connected Data Stores |
| IP | IP | TCP/IP tracker | TCPIP keyword of ROUTOPTS | Manages communications with TCP/IP-connected standard trackers |
| JCC | JC | Job completion checker | JCCTASK(YES) | Scans SYSOUT data sets |
| JLA | JL | JT and DB logs archiver | OPCHOST(YES) | Copies JT and DB logs to the archive data set (EQQJTARC and EQQDBARC, respectively) |
| NMM | NM | Normal mode manager | OPCHOST(YES) | Maintains the current plan |
| PSU | PS | Pre-SUBMIT tailoring | RCLEANUP(YES) | Tailors the JCL before submitting it by adding the EQQCLEAN pre-step |
| RODM | RM | RODM support | RODMTASK (YES) | Starts RODM support |
| SUB | SU | Submit task | Always activated | Initiates work (job submit, job release, and WTO and STC operations) |
| VTAM® | CB | Network communication function (NCF) | NCFTASK(YES) | Transmits and receives HCL Workload Automation for Z data through a VTAM® link |
| WSA | WA | Workstation analyzer | OPCHOST(YES) | Schedules work for processing |
|
Note: The subtask ID is the same identifier used to control the subtask using the z/OS MODIFY command.
|
||||
When a controller is started in standby mode, only the HCL Workload Automation for Z main task (EQQMAJOR) is started. The subtasks that comprise an active controller are attached when a takeover is performed.