FLOPTS

Purpose

The FLOPTS statement defines the options for Fetch Job Log (FL) task.

A controller uses this statement when OPCOPTS RCLEANUP (YES) is specified.

Parameters

CTLLUNAM(LU Name)

Defines the VTAM® application LU name identifying the controller in the SNA connection between the controller and data store. It is required if the SNA connection is used between the controller and data store, and must be the same specified in the data store DSTOPTS CTLLUNAM statement.

You must specify at least the keyword CTLLUNAM, or the keywords DSTGROUP and CTLMEM.

CTLMEM(XCFMemName)

Defines the XCF member name identifying the controller in the XCF connection between the controller and data store. It must be specified together with the DSTGROUP keyword. It is required if the XCF connection is used between the controller and data store and must be the same specified in the data store DSTOPTS CTLMEM statement.

DSTGROUP(XCFGroupName)

Defines the XCF group name identifying the controller in the XCF connection between the controller and data store. It must be specified together with the CTLMEM keyword. It is required if the XCF connection is used between the controller and data store.

The XCF group defined to connect the controller to the data store must be different from the one defined in the XCFOPTS group to connect the controller to the z/OS® tracker.

SNADEST(TrackerDest.DSTdest)

Defines a table of pairs of tracker destinations and data store destinations, each pair separated by a period, when the data store destinations are LU names. SNADEST is used by the FL (Fetch Job Log) task to decide from which data store the job log will be retrieved. Several tracker destinations can be associated to the same data store only in a system where the spool is shared (for example, JES2 MAS). The tracker destination of 8 asterisks (********) identifies the data store associated with a tracker running in the same address space as the controller. You can connect the controller to SNA and XCF data stores at the same time, that is, you can specify SNADEST and XCFDEST together, but you cannot specify the same tracker or data store destinations in SNADEST and XCFDEST. You must specify at least SNADEST or XCFDEST.

When using a shared DASD connection, you must specify the DDname of the submit/release dataset. When using a SNA connection, you must specify the tracker LU name.

TCPDEST(TrackerDest.DSTdest)

Defines a table of pairs of tracker destinations and data store destinations, each pair separated by a period, when the destinations are TCP/IP destinations. The following rules apply to the destination sub-values:

• The TrackerDest name can be up to 8 alphanumeric characters. In association with the host name or IP address, it is used to identify the communication partners. This sub-value is required.
• The DSTdest consists of a host name or IP address and optionally a port number:
  • The host name or IP address can be up to 52 alphanumeric characters. It can contain a host name or IP address in IPv4 or IPv6 format. Enclose this value in single quotation marks. This sub-value is required.
  • The port number can be up to 5 numeric characters. Valid values are from 0 to 65535. This sub-value is optional. The default is 0, meaning that any port number is accepted.
• The TrackerDest name and the DSTdest name must be separate by a period.
• The required values and the port number must be separated by a slash.

TCPDEST is used by the Fetch Job Log (FL) task to decide from which data store the job log is to be retrieved. Several tracker destinations can be associated with the same data store only in a system where the spool is shared (for example, JES2 MAS). In this case, you must use the same address format for the different destinations. The tracker destination marked with 8 asterisks (********) identifies the data store associated with a tracker running in the same address space as the controller. You can connect the controller to SNA, XCF, and TCPIP data stores at the same time, that is, you can specify SNADEST, XCFDEST, and TCPDEST together, but you cannot specify the same tracker or data store destinations in SNADEST, TCPDEST, or XCFDEST. You must specify at least one of the following destinations: SNADEST, XCFDEST, or TCPDEST.

XCFDEST(TrackerDest.DSTdest)

Defines a table of pairs of tracker destinations and data store destinations, each pair separated by a period, when the data store destinations are XCF member names. XCFDEST is used by the FL task to decide from which data store the job log will be retrieved. Several tracker destinations can be associated to the same data store only in a system where the spool is shared (for example, JES2 MAS). Because the restart and cleanup function adds a job card to the procedures for scheduled STC workstation operations at the same time it adds the //TIVDSTxx output JCL statements, there are some exceptions to the previous instructions if you want to use the restart and Cleanup function. The JCL for a started task can contain a job card only if the JCL is in a data set in the IEFPDSI or IEFJOBS concatenations of MSTJCLxx when the start command is issued. The XCFDEST value (********.DSTdest) identifies the data store associated with a tracker running in the same address space or in the same LPAR as the controller. You can connect the controller to SNA and XCF data stores at the same time, that is, you can specify XCFDEST and SNADEST together, but you cannot specify the same tracker or data store destinations in XCFDEST and SNADEST. You must specify at least XCFDEST or SNADEST.