Configuration
These statements and parameters specify your HCL Workload Automation for Z configuration. They identify HCL Workload Automation for Z subsystems and the connections between them.
| Statement | Keywords | Description |
|---|---|---|
| OPCOPTS | OPCHOST | Specifies the subsystem type (tracker, controller, or standby controller). |
| NCFTASK | Starts NCF for communication through VTAM®. | |
| EWTRTASK | Starts an event writer to collect events from the z/OS system. | |
| ERDRTASK | Starts an event reader to transfer events to the event. | |
| SERVERS | Starts one or more server queues at the controller. | |
| TPLGYSRV | Not applicable. | |
| EWTROPTS | EWSEQNO | Event writer also performs event reader function. Separate event reader is not required. |
| SUREL | Specifies if the event writer reads a submit/release data set. | |
| ERDROPTS | ERSEQNO | Specifies the event reader and defines the ddname of the input event data set. |
| RELDDNAME | Specifies the submit/release data set that release commands are written to in a shared DASD environment. | |
| ROUTOPTS | Identifies routes from the controller to tracker destinations. | |
| TRROPTS | Identifies the route from a tracker to the controller. | |
| XCFOPTS | Identifies XCF connections and specifies when a standby controller performs take over. | |
| SERVOPTS | SUBSYS | Identifies the controller with which the server communicates. |