Establishing intersystem sessions
Before traffic can flow on an intersystem session, the session must be established, or bound.
CICS® can be either the primary (BIND sender) or secondary (BIND receiver) in an intersystem session, and can be either the contention winner or the contention loser. The contention winner in an LU-LU session is the LU that is permitted to begin a conversation at any time. The contention loser is the LU that must use an SNA BID command (LUTYPE6.1) or LUSTATUS command (APPC) to request permission to begin a conversation.
You can specify the number of contention-winning and contention-losing sessions required on a link to a particular remote system.
For LUTYPE6.1 sessions, CICS always binds as a contention loser.
For APPC links, the number of contention-winning sessions is specified when the link is defined. See Defining APPC links. The contention-winning sessions are normally bound by CICS, but CICS also accepts bind requests from the remote system for these sessions.
Normally, the contention-losing sessions are bound by the remote system. However, CICS can also bind contention-losing sessions if the remote system is cannot send bind requests.
A single session to an APPC terminal is normally defined as the contention winner, and is bound by CICS, but CICS can accept a negotiated bind in which the contention winner is changed to the loser.
- By CICS during CICS initialization for sessions for which AUTOCONNECT(YES) or AUTOCONNECT(ALL) has been specified. See Defining connections to remote systems.
- By a request from the CICS master terminal operator.
- By the remote system with which CICS is to communicate.
- By CICS when an application explicitly or implicitly requests the use of an intersystem session and the request can be satisfied only by binding a previously unbound session.