Choosing the appropriate statements
The statements that you define determine the HCL Workload Automation for Z functions that you can use. Defining the appropriate initialization statements shows which statements you can define for a tracker, a controller, a server, a data store, a batch, or a PIF application. For a standby controller, you specify the controller statements.
| Name | Tracker | Controller | Server | Data Store | Batch | PIF | Specifies options for |
|---|---|---|---|---|---|---|---|
| ALERTS | ✓ | ✓ | Generating NetView®, IBM® Tivoli® Monitoring, message log, and WTO alerts. | ||||
| AROPTS | ✓ | Automatic job recovery. | |||||
| AUDIT | ✓ | Creating audit information for changes to HCL Workload Automation for Z data. | |||||
| AUDITCP | ✓ | Creating audit information for automatic status changes of an operation condition in the current plan. | |||||
| AUTHDEF | ✓ | ✓ | Security checking. | ||||
| BATCHOPT | ✓ | Specifying options for all batch jobs. | |||||
| DBCSOPTS | ✓ | Japanese language feature. | |||||
| DBOPT | ✓ | ✓ | Dynamic Workload Console reporting. | ||||
| DSTOPTS | ✓ | Specifying options for the data store. | |||||
| DSTUTIL | ✓ | Specifying options for data store batch utilities and the CleanUp subtask. | |||||
| ERDROPTS | ✓ | ✓ | Event reader task. | ||||
| EWTROPTS | ✓ | Event writer task. | |||||
| EXITS | ✓ | ✓ | Calling HCL Workload Automation for Z exits. | ||||
| FLOPTS | ✓ | Communicating with data store (allowing job log retrieval and restart and cleanup functions). | |||||
| HTTPOPTS | ✓ | Options for the HTTP communications. | |||||
| INCLUDE | ✓ | NOERROR table definition members. | |||||
| Purpose | ✓ | ✓ | Run-time options for processing requests from a PIF application and a server. | ||||
| INTFOPTS | ✓ | Requests from programming interfaces (required). | |||||
| JCCOPTS | ✓ | Job completion checker task. | |||||
| JTOPTS | ✓ | Determining how operations behave at workstations and how they are submitted and tracked. | |||||
| MONOPTS | ✓ | Enabling monitoring by an external agent. Used by IBM® Tivoli® Monitoring. | |||||
| MONPOL | ✓ | Defining the monitoring policy to be used by external monitors. | |||||
| NOERROR | ✓ | Treating job-tracking error codes as normal completion codes. | |||||
| OPCOPTS | ✓ | ✓ | Starting HCL Workload Automation for Z subtasks. | ||||
| RCLDDP | ✓ | Listing protected DDnames | |||||
| RCLDSNP | ✓ | Listing protected data set name. | |||||
| RCLOPTS | ✓ | Defining the options used during the restart and cleanup functions. | |||||
| RCLSKIP | ✓ | Listing the INCLUDEs to keep at the beginning of a JCL when it is tailored by the Restart and Cleanup function. | |||||
| RESOPTS | ✓ | Controlling special resources | |||||
| RESOURCE | ✓ | Defining for which special resources daily planning should produce reports. | |||||
| RODMOPTS | ✓ | Monitoring special resources through RODM. | |||||
| ROUTOPTS | ✓ | Communication routes to tracker, z-centric agent, and remote engine destinations. | |||||
| TCPOPTS | ✓ | ✓ | ✓ | ✓ | ✓ | Local TCP/IP communication task. You can define it also in an EQQYPARM file referenced in the user logon procedure. | |
| TRGOPT | ✓ | Event-driven workload automation support. Used by the Java™ program that creates configuration files for data set triggering. | |||||
| TRROPTS | ✓ | The communication route to the controller. | |||||
| XCFOPTS | ✓ | ✓ | XCF communications. |
For a detailed syntax and description of each initialization statement, listed in alphabetical order, see the following sections.