OPCOPTS

Purpose

The OPCOPTS statement defines run-time options to Tivoli Workload Scheduler for z/OS. This statement is used by a tracker, controller, or standby controller.

OPCOPTS is defined in the member of the EQQPARM library as specified by the PARM parameter on the JCL EXEC statement.

Format

>>-OPCOPTS--+---------------------+--+----------------+--------->
            |           .-NO--.   |  |      .-NO--.   |
            '-APPCTASK(-+-YES-+-)-'  '-ARM(-+-YES-+-)-'
 
>--+---------------------------+-------------------------------->
   |         .-STDAR-------.   |
   '-ARPARM(-+-member name-+-)-'
 
>--+-----------------------------+------------------------------>
   |                .-MLOG---.   |
   '-AUTOMATIONMSG(-+-SYSLOG-+-)-'
                    +-BOTH---+
                    '-NONE---'
 
>--+-------------------------+---------------------------------->
   '-BUILDSSX(-+-MERGE---+-)-'
               '-REBUILD-'
 
>--+--------------------------------------+--------------------->
   |           .-IBM-037--------------.   |
   '-CODEPAGE(-+-host system codepage-+-)-'
 
>--+---------------------------------------+-------------------->
   |                  .-this subsystem-.   |
   '-CONTROLLERTOKEN(-+-subsystem name-+-)-'
 
>--+------------------------------------+----------------------->
   |          .-40------------------.   |
   '-CPBPLIM(-+-CP buffer pool size-+-)-'
 
>--+--------------------------------------------+--------------->
   |          .-50--------------------------.   |
   '-CPDTLIM(-+-CP data set size percentage-+-)-'
 
>--+--------------------------------+--------------------------->
   '-DB2SYSTEM(---DB2 subsystem---)-'
 
>--+---------------------------------+-------------------------->
   |           .-STDERDR---------.   |
   |           | .-,-----------. |   |
   |           | V             | |   |
   '-ERDRPARM(-+---member name-+-+-)-'
 
>--+-----------------------------------------+------------------>
   |           .-1-----------------------.   |
   '-ERDRTASK(-+-number of event readers-+-)-'
 
>--+-------------------------------------+---------------------->
   |           .-0-------------------.   |
   '-EXIT01SZ(-+-number of JCL lines-+-)-'
 
>--+-------------------+--+-----------------------------+------->
   |         .-NO--.   |  |           .-STDEWTR-----.   |
   '-EXTMON(-+-YES-+-)-'  '-EWTRPARM(-+-member name-+-)-'
 
>--+---------------------+--+---------------------+------------->
   |           .-NO--.   |  |           .-|YES-.   |
   '-EWTRTASK(-+-YES-+-)-'  '-|GDGNONST|(-+-|NO--+-|)-'
 
>--+-------------------------------+---------------------------->
   |            .-0------------.   |
   '-GMTOFFSET(-+-offset value-+-)-'
 
>--+-------------------------------------------+---------------->
   |         .-5---------------------------.   |
   '-GSTASK(-+-number of parallel requests-+-)-'
 
>--+------------------------+--+----------------------------+--->
   |         .-GLOBAL---.   |  |          .-STDJCC------.   |
   '-GTABLE(-+-table ID-+-)-'  '-JCCPARM(-+-member name-+-)-'
 
>--+--------------------+--+----------------------------+------->
   |          .-NO--.   |  |          .-,-----------.   |
   '-JCCTASK(-+-YES-+-)-'  '-JESPLEX(-+-System Name-+-)-'
 
>--+--------------------------------------+--------------------->
   |                 .-5000-----------.   |
   '-MAXHISTORYROWS(-+-number of rows-+-)-'
 
>--+-----------------------------+--+--------------------+------>
   '-NCFAPPL(---VTAM LU name---)-'  |          .-NO--.   |
                                    '-NCFTASK(-+-YES-+-)-'
 
>--+--------------------------+--+------------------------+----->
   |                .-YES-.   |  |          .-YES-----.   |
   '-NOERRCONCHECK(-+-NO--+-)-'  '-OPCHOST(-+-NO------+-)-'
                    '-MSG-'                 +-STANDBY-+
                                            '-PLEX----'
 
>--+------------------------+--+-------------------------+------>
   |              .-NO--.   |  |              .-NO--.    |
   '-OPERHISTORY(-+-YES-+-)-'  '-RCLEANUP--(--+-YES-+--)-'
 
>--+------------------------+--+---------------------+---------->
   |             .-NO--.    |  |           .-NO--.   |
   '-RCLPASS--(--+-YES-+--)-'  '-RECOVERY(-+-YES-+-)-'
 
>--+-----------------------------+------------------------------>
   |                   .-NO--.   |
   '-REMJCLDIRECTIVES(-+-YES-+-)-'
 
>--+-----------------------------+--+---------------------+----->
   |           .-STDRODM-----.   |  |           .-NO--.   |
   '-RODMPARM(-+-member name-+-)-'  '-RODMTASK(-+-YES-+-)-'
 
>--+-----------------------+--+-------------------------+------->
   '-SAVARFAIL(---&, %---)-'  |          .-NO-------.   |
                              '-SECHECK(-+-ALL------+-)-'
                                         '-OPERONLY-'
 
>--+--------------------------------------+--------------------->
   |          .-,---------------------.   |
   |          V                       |   |
   '-SERVERS(-----Started task name---+-)-'
 
>--+-----------------+------------------------------------------>
   |       .-NO--.   |
   '-SPIN(-+-YES-+-)-'
 
>--+---------------------------------------------+-------------->
   |                             .-TEMPORARY-.   |
   '-SSCMNAME(---module name---,-+-PERMANENT-+-)-'
 
>--+------------------------+----------------------------------->
   |              .-NO--.   |
   '-SUPPRESSENF(-+-YES-+-)-'
 
>--+-----------------------------+--+--------------------+------>
   |            .-1----------.   |  |          .-|YES-.   |
   '-SYSPLEXID(-+-Sysplex Id-+-)-'  '-|TASKUSR|(-+-|NO--+-|)-'
 
>--+-----------------------------+--+--------------------+------>
   '-TPLGYSRV(---server name---)-'  |         .-SCAN-.   |
                                    '-VARSUB(-+-YES--+-)-'
                                              '-NO---'
 
>--+----------------------+--+--------------------+------------->
   '-VARFAIL(---& % ?---)-'  |          .-NO--.   |
                             '-VARPROC(-+-YES-+-)-'
 
>--+---------------------------------------------------------------------+-><
   |                                                   .-20------.       |
   |      .-WLMJOBPR---.                .-CONDITIONAL(-+-percent-+-)-.   |
   '-WLM(-+-class name-+-,-policy name--+----------------------------+-)-'
                                        +-DURATION-------------------+
                                        +-DEADLINE-------------------+
                                        '-LATESTSTARTTIME------------'

Parameters

APPCTASK(YES|NO)

Specify YES if an AS400 tracker is used or there are programs using the API interface. The appctask is not required for the Tivoli Workload Scheduler for z/OS Server communication. You can specify APPCTASK for a tracker and a controller.

ARPARM(member name|STDAR)

Defines the name of the member in the EQQPARM data set that contains an AROPTS statement for the automatic job-recovery task.

ARM(YES|NO)

The z/OS Automatic Restart Manager (ARM) can reduce the impact of an unexpected error to Tivoli Workload Scheduler for z/OS because z/OS can restart it automatically, without operator intervention.

Specify YES if automatic restart of the failed Tivoli Workload Scheduler for z/OS component should be activated, and define the component in the ARM policy. The element name comprises the string "OPC" , the SYSTEMID, and the SUBSYSTEM name. ARM recovery of the failed Tivoli Workload Scheduler for z/OS component is possible in the same image (restart-in-place). This feature allows the recovery of the tracker and a fast restart of the controller and the server. In addition, restart-in-place does not reduce the number of standby controllers when there is a controller failure. You can customize the number of restarts and the period of a restart by setting the parameters for each Tivoli Workload Scheduler for z/OS component in the z/OS ARM policy.

AUTOMATIONMSG(MLOG|SYSLOG|BOTH|NONE)

Defines where the messages issued by System Automation are to be logged. You can specify one of the following:

MLOG: Tivoli Workload Scheduler for z/OS message log, this is the default.
SYSLOG: System log.
BOTH: Tivoli Workload Scheduler for z/OS message log and system log.
NONE: None of the messages issued by the System Automation are logged.

Note that message EQQE123I is logged into MLOG, regardless of the value you set for this keyword. This option is valid only if you run System Automation version 3.1 (with the appropriate maintenance level installed), or later.

BUILDSSX(MERGE|REBUILD)

Defines if the subsystem communication vector table (CVT) extension for Tivoli Workload Scheduler for z/OS, the SSX, should be rebuilt at a new level when the address space is started. The SSX is created at subsystem initialization by the EQQINITJ module. If the EQQINITJ module has since been updated, by maintenance or because you are installing a new release or modification level of Tivoli Workload Scheduler for z/OS, use the BUILDSSX keyword to avoid a z/OS IPL.

Specify MERGE when operational data, such as the event-writer queue, should be copied to the new SSX. This ensures that the new event-writer queue is primed with events queued to the old SSX block. Use this option when starting a Tivoli Workload Scheduler for z/OS address space after installing maintenance updates.

Specify REBUILD when you are migrating to, or falling back from, a new release or modification level of Tivoli Workload Scheduler for z/OS. The event-writer queue from the old SSX will not be referenced in the new SSX. Ensure you also identify the new subsystem communication module name using the SSCMNAME keyword.

Notes:

The PTF coverletter ++HOLD section identifies the service updates that require the SSX be rebuilt.
MERGE cannot be used when the old and new SSX blocks are built for different FMIDs. Do not use MERGE when migrating to, or falling back from, a new release or modification level of Tivoli Workload Scheduler for z/OS.
If you specify BUILDSSX(REBUILD) to migrate to, or fallback from, a new release or modification level of Tivoli Workload Scheduler for z/OS, ensure you also specify the SSCMNAME keyword.
The BUILDSSX parameter should be removed after the next IPL of the z/OS system as it is no longer required.

CODEPAGE(host system codepage|IBM – 037)

The name of the host code page. This value is used by the monitoring task to convert the monitoring data to be sent to the monitoring agent. You can provide the IBM®–nnn value, where nnn is the EBCDIC code page. The default value, IBM–037, defines the EBCDIC code page for US English, Portuguese, and Canadian French. The following is a list of the EBCDIC code pages:

IBM–939: Japan Extended
IBM-937: Taiwan
IBM–935: China
IBM–933: Korea
IBM–975: Greece
IBM–971: Iceland
IBM–970: Latin 2
IBM–838: Thai
IBM-500: International
IBM–424: Israel
IBM–297: France
IBM–285: UK
IBM–284: Spain - Latin America
IBM-280: Italy
IBM–278: Sweden - Finland
IBM–277: Denmark - Norway
IBM–274: Belgium
IBM–273: Germany
IBM–1388: China
IBM–1122: Estonia
IBM–1112: Baltic
IBM–1047: Open Systems
IBM–1026: Latin 5 (Turkey)
IBM–1025: Cyrillic

The following is a list of the EBCDIC code pages for EURO support:

IBM-1140: Finland, Sweden
IBM-1141: Austria, Germany
IBM-1142: Denmark, Norway
IBM-1143: USA
IBM-1144: Italy
IBM-1145: Spain, spanish-speaking Latin America
IBM-1146: UK
IBM-1147: France
IBM-1148: Belgium, Switzerland
IBM-1149: Iceland

CONTROLLERTOKEN(subsystem name|this subsystem)

This keyword is used for the history function. The subsystem name is a key for the history information. When the current plan is extended, the BATCHOPT CONTROLLERTOKEN value is used to write the information. When the information is retrieved from the database, the OPCOPTS CONTROLLERTOKEN value is used, so you can rerun jobs initiated from another subsystem current plan (for example, when a standby system takes over) by specifying the correct token after takeover.

If you specify OPERHISTORY(NO) or omit the OPERHISTORY keyword, the CONTROLLERTOKEN keyword is ignored.

CPBPLIM (CP buffer pool size |40)

The CP buffer pool size is set to half the size of the current plan, but it is limited to a certain percentage of the amount of storage available; this percentage is given by the CPBPLIM keyword.

Values allowed are 0-99. Values 1-99 are considered as a percentage; value 0 causes the old restriction, 400 blocks. The default is a percentage of 40.

CPDTLIM (CP data set size percentage|50)

This keyword determines the percentage of size of the current plan used as maximum for buffer pool size. If CPDTLIM is omitted, the default 50 is used.

Values allowed are 0-100. Values 1-100 are considered as a percentage; value 0 causes the default of 50 to be used. Recommended values are between 50 and 100.

DB2SYSTEM(DB2 subsystem)

This keyword is required for the history function. It specifies the DB2® subsystem, as in the IEFSSNxx member of SYS1.PARMLIB.

If you specify OPERHISTORY(YES) but omit the DB2SYSTEM keyword, an error message is issued.

ERDRPARM(member name|STDERDR)

Defines the names of the members in the EQQPARM data set that contain an ERDROPTS statement for an event-reader task. The number of member names in this list must equal the number of event-reader tasks as defined by the ERDRTASK keyword. This keyword is required if more than one event reader is started.

ERDRTASK(number of event readers|1)

Defines the number of event-reader tasks to be started by Tivoli Workload Scheduler for z/OS. The maximum number is 16.

Notes:

If no event-reader tasks should be started, you must specify ERDRTASK(0).
On controller side, separate event-reader tasks must be started when there are trackers connected via shared DASD.
On tracker side, it is recommended (for performance reasons) not to start a separate event-reader task by setting ERDRTASK(0). The event reader function should be activated in an event-writer task by specifying EWSEQNO on the EWTROPTS statement.

EWTRPARM(member name|STDEWTR)

Defines the name of the member in the EQQPARM data set that contains an EWTROPTS statement for the event-writer task.

EWTRTASK(YES|NO)

Specify YES if the Tivoli Workload Scheduler for z/OS subsystem should start an event-writer task to create events in an event data set.

|GDGNONST(YES|NO)

|If you set this keyword to No, Tivoli Workload Scheduler for z/OS tests |the JCFGDG section to recognize if a data set is a GDG member. This |means that the dataset triggering function does recognize as GDG the |dataset referenced in the JCL in expanded format. |

Note:

The |restart and cleanup function might not work properly wih GDG.

If you set this keyword to Yes, Tivoli Workload Scheduler for z/OS assumes that a dataset |having its last qualifier syntax compatible with a GDG member, is |a GDG member.

EXIT01SZ(number of JCL lines|0)

This keyword, if specified with a nonzero value, tells Tivoli Workload Scheduler for z/OS that the JCL size can be changes using user exit 01, and that the new JCL size cannot be greater than the value specified.

For example, a value of 5000 will set the limit to 5000 JCL lines. Each JCL line is considered to be 80 characters in length.

EXTMON (YES|NO)

Specify YES to enable Tivoli Workload Scheduler for z/OS to communicate with Tivoli Business System Manager. Tivoli Business System Manager is notified of any alerts or changes in status related to monitored jobs. Specify NO if no monitoring is wanted.

GMTOFFSET(offset value|0)

This keyword is used to request Tivoli Workload Scheduler for z/OS to correct the GMT clock which is recognized as incorrect. The keyword parameter value defines how much the clock must be corrected. The value must be a number, positive or negative, less than 1440 (24 hours), that defines the number of minutes that must be added to the GMT clock value, on this system (where the keyword is used), to get the true GMT time.

The default value is zero (GMTOFFSET(0), that is, the GMT clock shows the true GMT time.

Note:

This parameter only enables Tivoli Workload Scheduler for z/OS to bypass GMT synchronization processing, and does not enable the correct interpretation of the timestamp in events received from the tracker when the connection is established. So the actual start time and end time of related operations will be deviated by the amount of the specified offset.

GSTASK(number of parallel requests|5)

Defines the number of dialog requests that can be handled simultaneously by the general-service subtask to a maximum of 5. So GSTASK(1) will not permit parallel processing of requests, but GSTASK(5), the default value, will allow maximum parallel processing.

GTABLE(table ID|GLOBAL)

Defines the name of the global JCL-variable table for the Tivoli Workload Scheduler for z/OS complex. This table contains JCL variable definitions that can be used for any operation within the Tivoli Workload Scheduler for z/OS complex. The global variable table is searched when a table (or variable within a table) that is referenced by an operation cannot be found.

If you schedule end-to-end with fault tolerance capabilities, set this keyword to the same value as the value of the GTABLE keyword in the BATCHOPT statement

You can specify only one table ID for the Tivoli Workload Scheduler for z/OS complex. Tivoli Workload Scheduler for z/OS uses the default name GLOBAL if you do not specify a table ID.

JCCPARM(member name|STDJCC)

Defines the name of the member in the EQQPARM data set that contains a JCCOPTS statement for the job-completion-checker task.

JCCTASK(YES|NO|)

Specify JCCTASK (YES) if the job-completion checker function is to be used.

Specify JCCTASK (NO) if the job-completion checker function is not to be used.

JESPLEX(list of system names)

Provides a list of the system names within the JESplex where the tracker belongs. Each system name can be up to 8 characters.

MAXHISTORYROWS(number of rows|5000

This keyword, if specified with a nonzero value, tells Tivoli Workload Scheduler for z/OS the maximum number of rows that can be retrieved from DB2 by using the HIST command. The default value is 5000. the maximum value is 999999. If you specify 0, all the rows are retrieved without limitations.

For example, by specifying 1000 you set 1000 as the maximum number of rows that can be retrieved by the HIST command processing. If less than 1000 rows are retrieved, the rows are shown in the requesting panel. If more that 1000 rows are retrieved, the HIST command processing is interrupted, an error message is issued, and no data is shown in the requesting panel. To reduce the amount of data to retrieve, set the appropriate filtering criteria.

NCFAPPL(VTAM LU name)

Specify the VTAM® LU name associated with the subsystem. This keyword is required if NCSK(YES) is specified.

NCFTASK(YES|NO)

Specify YES if the subsystem should start a network communication function (NCF) task. That is, communication is through VTAM.

NOERRCONCHECK(YES|NO|MSG)

Defines which level of check the scheduler performs when adding entries to the NOERROR table. You can specify one of the following:

YES: A consistency check is active. The scheduler does not add inconsistent entries to the NOERROR table and issues EQQN069W messages in the controller message log to indicate the inconsistencies. It is the default setting.
NO: To force the scheduler to update the NOERROR table even after detecting inconsistent entries. Related EQQN069W messages are not issued. EQQN098I message (informing that the table has been updated anyway, based on NOERRCONCHECK setting) is not issued either. Setting this keyword to NO prevents any consistency check from being performed.
MSG: Like the NO setting, it forces the scheduler to update the NOERROR table even after detecting inconsistent entries. Unlike the NO setting, related EQQN069W messages are issued. EQQN098I message is issued informing that the table has been updated anyway, based on NOERRCONCHECK setting.

OPCHOST(NO|STANDBY|YES|PLEX)

Specify YES if this subsystem supports dialog users and contains the databases and plans. Specify NO if this subsystem is not the controlling system. Specify STANDBY if this subsystem should be prepared to change from running in non-host mode to host mode. OPCHOST(STANDBY) is valid only in an XCF environment. You cannot specify OPCHOST(STANDBY) and EWTRTASK(YES) on the same OPCOPTS statement. Specify PLEX if this subsystem has to start as the controlling system. If there already is an active controller in the XCF group, the start up continues as standby controller. OPCHOST(PLEX) is valid only when XCF GROUP and MEMBER have been specified. Also, this selection requires that IBM Tivoli Workload Scheduler for z/OS is running on a z/OS/ESA Version 4 Release 1 or later system. If IBM Tivoli Workload Scheduler for z/OS is started with OPCHOST(YES), NMM initializes the CKPT data set with FMID and level corresponding to SSX.

OPERHISTORY(YES|NO)

This keyword is required for the history function. It specifies that Tivoli Workload Scheduler for z/OS will store completed operation information in the DB2 database. If you specify YES, you must also specify the DB2SYSTEM keyword.

If you specify YES but omit the DB2SYSTEM keyword, an error message is issued.

If you specify NO or omit the OPERHISTORY keyword, but specify related keywords (such as DB2SYSTEM or CONTROLLERTOKEN) a warning message is issued to inform you that the history function is not active.

RCLEANUP (YES/NO)

Default is NO. Specify YES to use the restart and cleanup function: The value of RCLEANUP must match the value in the BATCHOPT for RCLEANUP. If RCLEANUP(YES) is coded, the CP16 records created by the batch job (if the BATCHOPT has RCLEANUP(YES) specified) are deleted as part of "catch up" processing. The FL task and the PSU task are started, the local data store is activated, and the scheduler changes the jobs to duplicate the output to OPC DEST ID.

When YES is specified, OUTPUTNODE(FINAL) is forced in the JTOPTS statement.

RCLPASS (YES|NO)

Default is NO. Specify YES to use the restart and cleanup function for JCLs with DISP=(,PASS) in the last step.

RECOVERY(YES|NO)

Specify YES if the controller should start an automatic-job-recovery task to manage automatically operations that end in error.

Note:

If you specify RECOVERY(NO), you cannot use the Service Functions dialog to activate the automatic-job-recovery task.

REMJCLDIRECTIVES(YES|NO)

Defines if JCL directives are to be removed from the JCL at submission time.

Specify YES to remove the directives from the JCL at submission time. In this case, the scheduler removes the directives before submitting the JCL, therefore the job output does not contain the directives.

Specify NO to keep the directives in the JCL at submission time. In this case the job output contains the directives.

RODMPARM(member name|STDRODM)

Specifies the member in the EQQPARM data set that contains RODMOPTS statements for the RODM (resource object data manager) subtask. RODMPARM is not used by a tracker.

RODMTASK(YES|NO)

IBM Tivoli Workload Scheduler for z/OS support for RODM (resource object data manager) lets you associate fields of special resources in the current plan with fields of RODM classes or RODM objects. Support for RODM requires that:

A tracker is started on the same z/OS image as the RODM subsystem that requests are sent to, and RODMTASK(YES) is specified for both the tracker and the controller.
An event writer is started in the Tivoli Workload Scheduler for z/OS address space that communicates with RODM. This address space creates resource events (type S) from RODM notifications, which Tivoli Workload Scheduler for z/OS uses to update the current plan.
The controller is connected to the tracker through XCF, NCF, TCP/IPor a submit/release data set.
Each address space has a unique RACF® user ID if more than 1 Tivoli Workload Scheduler for z/OS address space communicates with a RODM subsystem, such as when you start production and test systems that subscribe to the same RODM subsystem.

Tivoli Workload Scheduler for z/OS can communicate with several RODM subsystems.

SAVARFAIL(&, %)

This keyword tells Tivoli Workload Scheduler for z/OS not to consider unresolved variables in the System Automation command as an error, preventing the operation from completing with error code OJCV. The allowed variable types are the ampersand (&) and percent sign (%). You can use one or both of them, in any order, to bypass the substitution failure. For example if you set SAVARFAIL(&), Tivoli Workload Scheduler for z/OS does not consider as error the failing substitution of variables beginning with &.

Any combination of the two variables types is allowed, for example SAVARFAIL(&, %) or SAVARFAIL(%, &), but you must specify at least one type. If SAVARFAIL is not set, the failing substitution of a variable is considered as an operation error.

SECHECK(ALL|OPERONLY|NO)

This keyword applies to trackers and controllers where the Submit function is active (a blank destination is used to submit jobs locally). To activate WLM scheduling environments, you must specify a value other than NO.

When you activate this function, you must do so for all the trackers and for the controller within the same sysplex. This is needed to correctly implement the ENF listener mechanism, because each tracker activates the listener exits only in the MVS™ system where it is located.

The possible values are:

ALL

All the submitted JCLs are to be checked for an associated scheduling environment name. The check is the following:

If it is defined, the scheduling environment name associated to the operation is used. In this case, the JCL is tailored by adding or replacing the SCHENV keyword of the JOB card statement. Any pre-existing value in the JCL is overwritten.
If the above condition is not true, the scheduling environment name specified in the SCHENV keyword of the JOB card statement is used, if it is present.
If the above condition is not true, no scheduling environment name is used (WLM is not queried).

When a scheduling environment is found, WLM is queried to find if the environment is available. If it is, the job is submitted, otherwise:

If the environment is not available, the operation is set to READY, WAITING FOR SE
If the environment is not defined, the operation is set to error (SEUN error code)

OPERONLY

Only the JCLs of operations with a scheduling environment defined in the Tivoli® Workload Scheduler for z/OS® data base are to be checked. The check is the following:

The scheduling environment name associated to the operation is used to insert or update in the JCL the SCHENV keyword of the JOB card statement. When this happens, the existing value in the JCL is overwritten.
WLM is queried to find if the environment is available. If it is, the job is submitted, otherwise:
- If the environment is not available, the operation is set to READY, WAITING FOR SE
- If the environment is not defined, the operation is set to error (SEUN error code)

NO

No checks are performed. This is the default setting.

Note:

When the JOB card is tailored to insert or replace the SCHENV=new value keyword, any comments on the right might be ignored and could show truncated in the submitted JCL.

SERVERS(Started task name, Started task name,...)

Identifies one or more servers to be started, and stopped, by this controller. Use this parameter in a sysplex environment to enable a standby controller to automatically take over the communication.

SPIN(YES|NO)

This keyword enables or disables the usage of the JESLOG SPIN functionality available with z/OS 1.2 or later. If you specify YES, the usage of the JESLOG SPIN functionality is enabled. Because the Restart and Cleanup or Job Completion Checker functions do not support this functionality, when you use them a warning message is issued.

If you specify NO, the usage of the JESLOG SPIN functionality is disabled by adding JESLOG=NOSPIN to the JOB card of every submitted job. SPIN(NO) is effective only if RCLEANUP(YES) or JCCTASK(YES) is specified. If you use the Restart and Cleanup function, a JOB card is added automatically to each submitted JCL when missing. If you do not use the Restart and Cleanup function (RCLEANUP(NO)), a warning message is issued for each submitted JCL that does not have a job card. The default is NO.

Note:

When the JOB card is tailored to insert or replace the JESLOG=NOSPIN keyword, any comments on the right might be ignored and could show truncated in the submitted JCL.

SSCMNAME(module name,PERMANENT|TEMPORARY)

The first keyword value defines the name of the subsystem communication module to be used instead of EQQSSCMJ that was loaded at IPL. The second keyword value specifies if the module should replace the one loaded at IPL. Use this keyword to load an updated version of the module before a scheduled IPL. The module you specify must reside in an APF-authorized library defined by either the STEPLIB ddname or LNKLSTnn concatenation. If SSCMNAME is not specified or specifies a module that cannot be located in an authorized library, Tivoli Workload Scheduler for z/OS events will continue to be generated by the EQQSSCMJ loaded at IPL.

Specify PERMANENT as the second keyword value to replace the subsystem communication module loaded at IPL with the module identified in the first keyword value. In this case the module specified must reside in an APF-authorized library defined by the STEPLIB ddname.

When TEMPORARY is specified or defaulted as the second keyword value, the module you specify will generate Tivoli Workload Scheduler for z/OS job-tracking events only while the Tivoli Workload Scheduler for z/OS address space is active. When the address space is stopped, events will continue to be generated by the EQQSSCMJ module loaded at IPL.

Notes:

The PTF cover letter ++HOLD section identifies service updates that require a new subsystem communication module to be loaded.
Ensure you specify this keyword when BUILDSSX(REBUILD) option is used to migrate to, or fallback from, a new release or modification level of Tivoli Workload Scheduler for z/OS.
The SSCMNAME keyword should be removed after the next IPL as it is no longer required.

SUPPRESSENF(YES|NO)

Specifies if activation of the ENF 57 and ENF 41 listener exits must be recalled.

YES: Exits ENF 57 and ENF 41 are not to be activated although it is marked for activation (because a value other than NO was specified for SECHECK).
NO: Activation of the exits is not to be recalled. This is the default.
You should not set this parameter to YES on trackers located in a sysplex that is not the one where the controller is. You can suppress activation of the exits on trackers that belong to the same sysplex as the controller only if there is a tracker in the same MVS image as the controller and the ENF exits are active (SECHECK is not set to NO).

SYSPLEXID (nnn)

Identifies the sysplex where the controller or tracker is located. nn is an integer ranging from 1 to 9999. The default is 1.

|TASKUSR(NO|YES)

|Specifies if a started task is to be run with the user ID associated |with the task, instead of the user ID associated with the job name. |

YES: The task is run with the user ID associated with the started |task name. This is the default. |
NO: The task is run with the user ID associated with the job name. |

TPLGYSRV (server_name)

Activates the end-to-end scheduling with fault tolerance capabilities feature in the controller. If you specify this keyword the IBM Tivoli Workload Scheduler Enabler task is started. Defining this parameter requires the definition of an OMVS segment for the controller user ID.

The specified server_name is that of the server that handles the events to and from the distributed agents. Only one server can handle events to and from the distributed agents.

VARSUB(YES|NO|SCAN)

This keyword tells Tivoli Workload Scheduler for z/OS whether JCL variable substitution should be performed. YES means that variable scanning will be performed for all computer operations. NO means that variable scanning will not occur. SCAN tells Tivoli Workload Scheduler for z/OS to search JCL for variables only if the //*%OPC SCAN directive has been found in the JCL.

This keyword applies also to variable substitution in the System Automation command text. YES and SCAN mean that the command text is scanned for variable substitution. NO means that variable scanning is not performed.

VARFAIL(&, %, ?)

This keyword tells Tivoli Workload Scheduler for z/OS whether or not unresolved variables in the JCL would cause a JCL error (OJCV). You can use from one to three of the following characters, in any order, to bypass substitution failure (&, %, ?).

If, for example, VARFAIL(&) is specified, Tivoli Workload Scheduler for z/OS will not consider the failure of a substitution of variables beginning with an & to be an error. Any combination of the three types is allowed, for example, VARFAIL(&, %) or VARFAIL(?), but at least one value must be specified while any repetition of characters will be rejected.

If VARFAIL is not specified, then all the lack of substitution of variables will be treated as errors, as previously.

Note that the error bypass is not applicable to Tivoli Workload Scheduler for z/OS Directive and Dependent variables.

VARPROC(YES|NO)

This keyword tells Tivoli Workload Scheduler for z/OS whether or not online procedures should consider variable substitution. If VARPROC(YES) is specified, variables in online procedures will be resolved.

The default is NO.

WLM(class name|WLMJOBPR, policy name, CONDITIONAL(20))

The WLM keyword defines the options that are to be applied for workload manager intervention. The WLM function can be used to assign extra resource to critical jobs that are running late. Tivoli Workload Scheduler for z/OS does this by promoting a late critical job to a higher performance WLM service class. WLM is defined in the member of the EQQPARM library as specified by the PARM parameter on the JCL EXEC statement.

Class Name: The name of the WLM service class to which late critical jobs are promoted. It can be an existing service class or a new service class created for this purpose.

Policy Name

The means by which Tivoli Workload Scheduler for z/OS decides whether a critical job is running late. One of the four possible policies should be specified here, and that is the default policy that Tivoli Workload Scheduler for z/OS will apply. This default can be overwritten at the individual job level. The following is a list of the valid policy names:

DURATION

When a critical job exceeds the expected duration (as specified in the current plan), Tivoli Workload Scheduler for z/OS moves it to the higher-performance service class, according also to the ALEACTION or LIMFDBK value set in the JTOPTS statement. (For details about the ALEACTION and LIMFDBK keywords, refer to JTOPTS.)

Note:

The fact that a job exceeds its expected duration does not necessarily imply that it is running late or that it will negatively impact the plan as a whole. Specifying this policy could mean that extra resource is dedicated to a job when not strictly necessary.

DEADLINE

When a critical job runs beyond its deadline time (calculated as Latest Start Time + Duration), Tivoli Workload Scheduler for z/OS moves it to a higher-performance service class.

Note:

If this policy is used, then extra resources are dedicated to a job only when it really needs it. The extra resources help to reduce the delay.

LATESTSTARTTIME

When a critical job starts after its latest start time, Tivoli Workload Scheduler for z/OS promotes it to a higher-performance service class.

Note:

Using this policy the gains are greater, as extra resources are dedicated to the job for its entire execution time. However, with this policy, it is possible to over-compensate, dedicating extra resources to a job for longer than necessary. For example, a long running job might start only a few minutes late, but get enough extra resources that let it finish early.

CONDITIONAL (NN)

This policy uses a simple test that decides whether the deadline or the lateststarttime policy is applied when a critical job starts after its latest start time.

The numeric value (NN) specified in this policy defines a threshold, which is used as follows:

If(Delay÷Time to Deadline)×100 > NN

then Tivoli Workload Scheduler for z/OS moves the job immediately to the higher-performance service class. This effectively applies the lateststarttime policy.

If (Delay÷Time to Deadline)×100 <= NN

then Tivoli Workload Scheduler for z/OS takes no action until the job runs beyond its deadline time. This is to avoid over-compensation.

Note:

If you use the default member name for ARPARM, ERDRPARM, EWTRPARM, JCCPARM, or RODMPARM, you must define the member.

Examples

 OPCOPTS OPCHOST(YES)                    1 
         NCFTASK(YES)                    2 
         NCFAPPL(NCFAPPL1)               3 
         ERDRTASK(2)                     4 
         ERDRPARM(ERDR1,ERDR2)           5 
         GMTOFFSET(60)                   6 
         GTABLE(GVARTAB)                 7 
         SERVERS(OPCBCOM1,OPCBCOM2)...   8

In this example of an OPCOPTS statement:

1: Tivoli Workload Scheduler for z/OS is started as a controller. This system supports dialog users.
2: The network communication function (NCF) is started.
3: The controller has the VTAM LU name NCFAPPL1.
4: Two event-reader tasks are started.
5: Run-time options for the event-reader tasks are specified in the ERDR1 and ERDR2 members of the parameter library.
6: Tivoli Workload Scheduler for z/OS adds one hour to GMT clock values retrieved from the running system.
7: A global JCL-variable table, called GVARTAB, is used by this Tivoli Workload Scheduler for z/OS complex.
8: A server is started for handling the communication to a certain controller. The server verifies that the inbound transactions are requests to the controller for which the server is started.