TRROPTS

Purpose

The TRROPTS statement defines routing options from:

A z/OS tracker that is connected to a primary or standby controller through shared DASD, SNA (VTAM®), XCF, or TCP/IP.
A z/OS tracker that is connected to a backup controller through TCP/IP. In this case, the only connections supported between the tracker and the primary controller are XCF and TCP/IP.
If the tracker is connected to the primary controller through XCF, ensure that you also set TCPOPTS HOSTNAME and TCPOPTS TRKPORTNUMBER on the tracker.

Include TRROPTS in the statements for each z/OS tracker in your HCL Workload Automation for Z configuration, except where the tracker and controller are started in the same address space. Use TRROPTS where OPCOPTS OPCHOST(NO) is specified.

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

Format

Parameters

BKPHOSTNAME (backup controller hostname|backup controller IP address)

The host name, or IP address in IPv4 or IPv6 format, of the remote backup controller. Valid values are fully-qualified names up to 52 alphanumeric characters. This parameter is required only if you want to connect to a backup controller; in this case the HOSTCON parameter, which is used to connect to the primary controller, must be set to TCP or XCF.

BKPPORTNUMBER (value|424)

The TCP/IP port number used to communicate with the remote backup controller. Valid values are from 0 to 65535. If not specified, the default value of 424 is used. This parameter is required only if you want to connect to a backup controller; in this case the HOSTCON parameter, which is used to connect to the primary controller, must be set to TCP or XCF.

HOSTCON(DASD|SNA|TCP|XCF)

The HOSTCON keyword identifies the connection that is used when transmitting events to the controller.

If you specify HOSTCON(DASD), you cannot specify EWSEQNO on the EWTROPTS statement.

If you specify HOSTCON(SNA), the SNAHOST keyword must contain the NCF LU name of the controller. This tracker must also have the NCFAPPL keyword specified in the OPCOPTS statement.

If you specify HOSTCON(XCF), the XCFOPTS statement must also be present.

If you specify HOSTCON(TCP), set also TCPHOSTNAME to identify the remote controller.

SNAHOST(VTAM LU name,...,VTAM LU name)

The SNAHOST keyword is required for trackers connected to the controller through an SNA link. This keyword defines the VTAM® LU name of the controller and any standby controllers. In a hot standby configuration, you can specify several LU names. At initialization, the tracker logs on to the LU at the SNAHOST that becomes active first. That is, the tracker attempts to communicate with the first HCL Workload Automation for Z started task that is identified as the controller. If you specify the SNAHOST keyword, the HOSTCON keyword must be SNA.

TCPHOSTNAME (hostname|IP address)

The host name or IP address in IPV4 or IPV6 format of the remote controller. Valid values are fully-qualified names up to 52 alphanumeric characters. This parameter is required.

TCPPORTNUMBER (value|424)

The TCP/IP port number used to communicate with the remote controller. Valid values are from 0 to 65535. If not specified, the default value of 424 is used.

 TRROPTS HOSTCON(SNA)       1
         SNAHOST(NCFAPPL1)  2

In this example:

1: The tracker is connected to the controller through a VTAM® link.
2: The name of the NCF LU used by the controller is NCFAPPL1.

 TRROPTS HOSTCON(XCF)                 1
         BKPHOSTNAME('9.168.119.53')  2
         BKPPORTNUMBER(924)           3

In this example:

1: The tracker is connected to the primarycontroller through an XCF link.
2: The host name of the backup controller to which the tracker is connected.
3: The TCP/IP port number used by the tracker to communicate with the remote backup controller.