Initialization statements used for XCF
Tivoli Workload Scheduler for z/OS started tasks use these initialization statements for XCF for controller/tracker connections:
- XCFOPTS
- Identifies the XCF group and member name for the started task. Include XCFOPTS for each started task that should join an XCF group.
- ROUTOPTS
- Identifies all XCF destinations to the controller or standby controller. Specify ROUTOPTS for each controller and standby controller.
- TRROPTS
- Identifies the controller for a tracker. TRROPTS is required for each tracker on a controlled system. On a controlling system, TRROPTS is not required if the tracker and the controller are started in the same address space, or if they use shared DASD for event communication. Otherwise, specify TRROPTS.
Tivoli Workload Scheduler for z/OS started tasks use these initialization statements for XCF for controller/Data Store connections:
- CTLMEM
- Defines the XCF member name identifying the controller in the XCF connection between controller and Data Store.
- DSTGROUP
- It defines the XCF group name identifying the Data Store in the XCF connection with the controller.
- DSTMEM
- XCF member name, identifying the Data Store in the XCF connection between controller and Data Store.
- DSTOPTS
- Defines the runtime options for the Data Store.
- FLOPTS
- Defines the options for Fetch Job Log (FL) task.
- XCFDEST
- It is used by the FL (Fetch Job Log) task to decide from which Data Store the Job Log will be retrieved.
If you did not include these runtime options when you defined the initialization statements, do this now. Step 11. Defining the initialization statements and Tivoli® Workload Scheduler for z/OS®: Customization and Tuning describe the initialization statements.