Choosing the appropriate statements

|The statements that you define determine the Tivoli Workload Scheduler for z/OS functions |that you can use. Table 1 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.

To use the end-to-end scheduling with fault tolerance capabilities, you must also define the job definition statements for fault-tolerant workstations in the SCRPTLIB library as described in Table 2.

Table 1. Defining the appropriate initialization statements
Name Tracker Controller Server Data Store Batch PIF Specifies options for
ALERTS X X Generating NetView®, IBM® Tivoli® Monitoring, message log, and WTO alerts.
AROPTS X Automatic job recovery.
AUDIT X Creating audit information for changes to Tivoli Workload Scheduler for z/OS data.
AUDITCP X Creating audit information for automatic status changes of an operation condition in the current plan.
AUTHDEF X X Security checking.
BATCHOPT X Specifying options for all batch jobs.
CPUREC X Specifying the configuration options for a fault-tolerant workstation.
DBCSOPTS X Japanese language feature.
DBOPT X X Dynamic Workload Console reporting.
DOMREC X Defining a domain for distributed agents network.
DSTOPTS X Specifying options for the data store.
DSTUTIL X Specifying options for data store batch utilities and the CleanUp subtask.
ERDROPTS X X Event reader task.
EWTROPTS X Event writer task.
EXITS X X Calling Tivoli Workload Scheduler for z/OS exits.
FLOPTS X Communicating with data store (allowing job log retrieval and restart and cleanup functions).
HTTPOPTS X Tracking jobs running on z-centric agents and for retrieving their job execution logs.
INCLUDE X NOERROR table definition members.
INIT X X Run-time options for processing requests from a PIF application and a server.
INTFOPTS X Requests from programming interfaces (required).
JCCOPTS X Job completion checker task.
JTOPTS X Determining how operations behave at workstations and how they are submitted and tracked.
MONOPTS X Enabling monitoring by an external agent. Used by IBM Tivoli Monitoring.
MONPOL X Defining the monitoring policy to be used by external monitors.
NOERROR X Treating job-tracking error codes as normal completion codes.
OPCOPTS X X Starting Tivoli Workload Scheduler for z/OS subtasks.
RCLDDP X Listing protected DDnames
RCLDSNP X Listing protected data set name.
RCLOPTS X Defining the options used during the restart and cleanup functions.
RCLSKIP X Listing the INCLUDEs to keep at the beginning of a JCL when it is tailored by the Restart and Cleanup function.
RESOPTS X Controlling special resources
RESOURCE X Defining for which special resources daily planning should produce reports.
RODMOPTS X Monitoring special resources through RODM.
ROUTOPTS X |Communication routes |to tracker, z-centric agent and remote engine destinations.
SERVOPTS X Defining options for a server.
TCPOPTS X X X X X Local TCP/IP communication task. You can define it also in an EQQYPARM file referenced in the user logon procedure.
TOPOLOGY X X Specifying configuration options for end-to-end scheduling with fault tolerance capabilities.
TRGOPT X Event-driven workload automation support. Used by the Java program that creates configuration files for data set triggering.
TRROPTS X The communication route to the controller.
USRREC X Defining the user id and password to be used for the operations running on fault-tolerant workstations.
XCFOPTS X X XCF communications.

Table 2 shows the statements you must define for the jobs running on fault-tolerant workstations. For detailed information, see Tivoli Workload Scheduler for z/OS: Scheduling End-to-end with Fault Tolerance Capabilities.

Table 2. Defining the initialization statements for end-to-end scheduling with fault tolerance capabilities
Name Description
JOBREC Fault-tolerant workstation job properties
VARSUB Variable substitution options
RECOVERY Recovery for a job whose status is in error and the error code is not FAIL

Refer to the following sections for a detailed syntax and description of each initialization statement, listed in alphabetical order.