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