LST parameters for OCF

OCF_APPLID

vtamapplid

The VTAM application ID of this OCF node. The application name must be defined in the SYS1.VTAMLST dataset with parameter APPC=YES.

Note: The SSID used must be unique.

required

Depends on the Beta product serving as the OCF node.

OCF_CONVERSE

remapplid, sessions, retries, interval, maxdata

Details of the five positional parameters of this keyword are provided below;
remapplid is required;
the other parameters are optional

remapplid

The VTAM application IDs of the OCF nodes with which the OCF node specified by OCF_APPLID is connected. The number of remote OCF nodes with which this node can converse is mainly limited by the amount of VTAM resources available to the installation. As with the keyword OCF_APPLID, these application names must be defined in the SYS1.VTAMLST dataset with parameter APPC=YES. This keyword also sets some limits on how the node-to-node conversations can take place (see five optional parameters below).

Note: The SSID used must be unique.

required

none

sessions

The maximum number of concurrent LU-LU sessions that can take place at one time with this remote OCF node. The value specified here is limited by the session limits set in the application definition in SYS1.VTAMLST. If the value specified there is lower than this one, the value specified in SYS1.VTAMLST will be used.

optional

4

retries

The number of times a BIND attempt is retried before OCF determines that a physical connection to the remote node is not possible. After this, OCF waits for a BIND request from the partner (specified in 'remapplid').

optional

5

interval

The minimum number of seconds that OCF is to wait before retrying a failed BIND attempt.

optional

10

maxdata

The maximum size of a Path Information Unit (PIU) that can be transferred between OCF nodes. The maximum permitted size depends on the VTAM connection, e.g. CTC attached, VTAM-NCP attached, etc.
If the value specified here exceeds the permitted size, it will not be possible to correctly establish a connection between the OCF nodes. Message 9241E or 9243E will come up. See the explanation of message 9204E in BSA Messages and Codes to find out how to determine the size used for MAXDATA.
If a value for MAXDATA is not entered here, or if the value is 0 (default), the RU size from the LOGMODE APPC01 of the MODETAB definition will be used instead (see "Calculating the values for RU sizes").

optional

0

OCF_ACTSESS_ MOD

YES | NO

Activates the MAXDATA or RU size values as entered in the keyword OCF_CONVERSE.

YES: The value entered for MAXDATA in the keyword OCF_CONVERSE or the RUSIZE value entered in the LOGMODE APPC01 of the MODETAB definition will be activated. Message 9231I informs you which parameter is active.

NO: The value entered for MAXDATA in the keyword OCF_CONVERSE or the RUSIZE value entered in the LOGMODE APPC01 of the MODETAB definition will not be used. Message 9231I informs you which parameter is active.

optional

NO

OCF_LOCAL_ SYSTEM

ssid, product

Both positional parameters are required.

ssid

The subsystem ID of the Beta product started task which is addressable via this OCF node.

required

none

product

The Beta product running under the started task.

required

none

The subsystem IDs and Beta product types of the Beta product subsystems that are executing on the same operating system as this OCF node.
The subsystems specified here are the target subsystems for communications and data transfer from other subsystems connected to this OCF network. Furthermore the subsystems specified here can send requests to remote subsystems connected to the remote OCF nodes which are specified in the OCF_CONVERSE parameter.
The number of local subsystems that can be connected to this OCF node is mainly limited by the amount of Common Service Area (CSA) available to the installation.

OCF_LOGMODE_ NAME

name

Name of the LOGMODE used in the VTAM MODETAB.

optional

APPC01