SERVOPTS

Purpose

The SERVOPTS statement is for a server which handles transactions directed to the controller subsystem name on the same z/OS® system as the server.

Format

Read syntax diagramSkip visual syntax diagram>>-SERVOPTS--+----------------+--------------------------------->
             |      .-NO--.   |
             '-ARM(-+-YES-+-)-'
 
>--+--------------------------------------+--------------------->
   |           .-IBM – 037------------.   |
   '-CODEPAGE(-+-host system codepage-+-)-'
 
>--+-----------------------------+------------------------------>
   |           .-DBOPT-------.   |
   '-DBOPTPRM(-+-member name-+-)-'
 
>--+-----------------------------------+------------------------>
   |              .-local hostname-.   |
   '-JSCHOSTNAME(-+-hostname-------+-)-'
                  '-IP address-----'
 
>--+-------------------------+---------------------------------->
   |             .-425---.   |
   '-PORTNUMBER(-+-value-+-)-'
 
>--+------------------------------+----------------------------->
   |             .-,--------.     |
   |             V .-APPC-. |     |
   '-PROTOCOL(-----+-E2E--+-+---)-'
                   '-TCP--'
 
>--+---------------------------------+-------------------------->
   |            .-,--------------.   |
   |            V                |   |
   '-SCHEDULER(---Scheduler name-+-)-'
 
>--SUBSYS(---Controller Subsystem name---)---------------------->
 
>--+--------------------+--+-----------------------------+------>
   |          .-|YES-.   |  |           .-TPLGPARM----.   |
   '-|TASKUSR|(-+-|NO--+-|)-'  '-TPLGYPRM(-+-member name-+-)-'
 
>--+--------------------------------------+--------------------><
   '-USERMAP(-parameters library member-)-'

Parameters

This section describes parameters that apply to all connection types. Parameters that are specific to a connection type are described separately in the sections that follow.

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. 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. The number of restarts and the period of a restart are parameters that can be customized for each Tivoli Workload Scheduler for z/OS component in the z/OS ARM policy.

CODEPAGE (host system codepage|IBM–037)
|The name of the host code page. 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. |If you specify a codepage value different from the default value, |a check has been implemented to use the default codepage if the first |four characters of the codepage you specify are different from "IBM-". |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 |
|
DBOPTPRM(member name|DBOPT)
Indicates the member of the PARMLIB that contains the parameters to connect to the database and manage the historical data archiving process.
JSCHOSTNAME (JSChostname|IP address| local hostname)
Specifies the host name or IP address that are used by a remote application to connect to the server, when PROTOCOL=TCP. The default is the host name returned by the operating system.

You can define a virtual IP address for each server of the active controller and the standby controllers. If you use a dynamic virtual IP address in a SYSPLEX environment, when the active controller fails and the standby controller takes over the communication, the remote application automatically switches the communication to the server of the standby controller.

If you specify the TCPOPTS statement for the server, the HOSTNAME parameter overrides the JSCHOSTNAME parameter in the SERVOPTS statement. It applies also if the HOSTNAME parameter is not explicitly defined: in this case, the default value overrides any different value specified in the SERVOPTS statement.

PORTNUMBER (value|425)
The port number used by the server when PROTOCOL=TCP. Valid values are from 0 to 65535. The default is 425. This port number is used by the server to connect to the remote application. Select different values for this parameter and the one specified in the TOPOLOGY statement.

If you specify the TCPOPTS statement for the server, the SRVPORTNUMBER parameter overrides the PORTNUMBER parameter in the SERVOPTS statement. It applies also if the SRVPORTNUMBER parameter is not explicitly defined: in this case, the default value overrides any different value specified in the SERVOPTS statement.

PROTOCOL (APPC,E2E,TCP)
Identifies the types of communication used by the server. You can specify any combination of the following values separated by a comma:
APPC
For communication with ISPF dialog and PIF, through the APPC protocol.
TCP
For communication with ISPF dialog, PIF, Job Scheduling Console, and Tivoli® Dynamic Workload Console, through the TCP/IP protocol.
E2E
For communication with a distributed environment, through the TCP/IP protocol.

For example, PROTOCOL(E2E,TCP) activates all the communication with the server through the TCP/IP protocol.

If you do not specify this keyword, APPC is used as the default value.

Note:
Although you can configure one server task to handle multiple protocols, for example PROTOCOL(E2E,APPC,TCP), consider having multiple server tasks, each one with one PROTOCOL function. By using separate server tasks, you can:
  • maximize the time the server is up and running; in fact you do not need to shut down the server to configure another PROTOCOL value.
  • minimize the occurrence of storage handling problems.
SCHEDULER (scheduler name)
Identifies the name of the server as an APPC scheduler. This parameter is used only if PROTOCOL is set to APPC. If you omit this parameter, the started task name is used as scheduler name.
SUBSYS (controller subsystem name)
Identifies the controller for which this server is started.
USERMAP (parameters library member)
Defines a member in the file identified by the EQQPARM DD statement in the server startup job. This member contains all the associations between a z/OS connector user and a RACF® user ID. If the USERMAP exists, the TMEADMIN security class is ignored.

The member of the initialization parameters data set should contain, for example: 

USER 'SCOT@HOST' RACFUSER(SCOT) RACFGROUP(TIVOLI)
USER 'PAOLO@HOST1' RACFUSER(FALSI) RACFGROUP(TIVOLI)
USER 'MOSSOTT@HOST' RACFUSER(FMOSSOTT) RACFGROUP(TIVOLI)

Parameters

USER "Tivoli_Administrator_ID"
The Tivoli administrator trying to log on to Tivoli Workload Scheduler for z/OS using the Java GUI Interface (mandatory field). The user_ID format received from the Job Scheduling Console is Administrator-at-TMR_region. For more information about Administrator-at-TMR_region, see User IDs involved with Dynamic Workload Console, in Chapter 3.
RACFUSER(RACF_user_ID)
The RACF user related to the Tivoli administrator (specified in the USER keyword). This field is mandatory and can be up to 8 characters in length (see RACF user definitions).
RACFGROUP(RACF_group)
The RACF group related to the RACF user. This field is optional and can be up to 8 characters in length (see RACF group definitions). It is used to set a group different from the default one associated with the specified RACF_user_ID of the RACFUSER.
|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. |
|
TPLGYPRM(member name|TPLGPARM)
Specify this parameter to activate the end-to-end scheduling with fault tolerance capabilities feature, when you set PROTOCOL to E2E.

The specified member name is a member of the PARMLIB in which the fault-tolerant end-to-end options are defined by the TOPOLOGY statement.

Examples

 SERVOPTS SUBSYS(OPCA)       1 
          SCHEDULER(OSCA)    2 

In this example of a SERVOPTS statement:

 1 
The server handles APPC transactions directed to controller OPCA on the same z/OS system as the server.
 2 
The name of the server as an APPC scheduler.