Control operator option sets

VTAM® supports the following control operator option sets:

CHANGE_SESSION_LIMIT verb (501): Enables a program at the source LU to request a change in the mode name group session limit from one nonzero value to another or to request a change in the minimum number of contention-winner sessions for the source LU or target LU. This is implemented through APPCCMD CONTROL=OPRCNTL, QUALIFY=CNOS.
LU-definition verbs (505): Enables a program or an operator to specify the operating parameters of its LU. These parameters include the LU's network-qualified name, session limit information, and security information such as passwords and profiles. See Managing sessions for information on controlling session limits. Security information can be maintained by the application program independently of VTAM.
MIN_CONTENTION_WINNERS_TARGET parameter (601): Enables a program at the source LU to request a nonzero value for the target LU's minimum number of contention-winner sessions. This is implemented through APPCCMD CONTROL=OPRCNTL, QUALIFY=CNOS.
RESPONSIBLE(TARGET) parameter (602): Enables a program at the source LU to request that the target LU deactivate sessions when a CNOS verb requires a decrease in the number of active sessions. This is implemented through the RESP field in the CNOS session limits control block.
DRAIN_TARGET(NO) parameter (603): Enables a transaction program to prevent its partner from honoring queued conversation requests for a mode name group when the group's session limit is being set to 0. This is implemented with the DRAINR field in the CNOS session limits data structure.
Locally known LU names (606): Enables a program or an operator to specify the locally known names of remote LUs. The 1- through 8-byte LU name that is used on all of VTAM's APIs is considered by architecture to be the locally known name for the network-qualified LU name.
Uninterpreted LU names (inbound only) (607): Enables a program to specify the uninterpreted names of partner LUs. VTAM provides this function as part of its services to all of its application programs. It is not unique to LU 6.2 support.
Single-session reinitiation (608): Enables a program to specify the responsibility for reinitiating single sessions to partner LUs. VTAM does this by ensuring that the BIND image used to establish a single session specifies that either side of the session can reinitiate.
Maximum RU size bounds (610): Enables a program to specify the upper bounds for the maximum RU sizes on sessions within a mode name group. The application program can control maximum RU sizes by setting fields in the BIND when issuing APPCCMD CONTROL=OPRCNTL, QUALIFY=ACTSESS.
Session-level mandatory cryptography (611): Enables a program or an operator to specify that session-level mandatory cryptography is to be used on sessions within an LU-mode group.
Contention winner automatic activation limit (612): Enables a program to specify the limit for automatically activating contention-winner sessions within a mode name group. This option set can be implemented through the use of the AUTOSES parameter on the APPL definition statement.
Session-level selective cryptography (617): Enables data that is both encrypted and not encrypted to be sent on the same session.