The AUTOCONNECT attribute of the SESSIONS resource

The AUTOCONNECT attribute specifies which sessions are to be bound when the associated LU services manager sessions have been bound. No user sessions can be bound before this time.

The option can have the following values:

AUTOCONNECT(NO)
specifies that no sessions are to be bound.
AUTOCONNECT(YES)
specifies that the contention-winning sessions are to be bound.
AUTOCONNECT(ALL)
specifies that the contention-winning and the contention-losing sessions are to be bound.

AUTOCONNECT(ALL) allows CICS to bind contention-losing sessions with remote systems that cannot send bind requests. By specifying AUTOCONNECT(ALL), you can cause CICS to bind a number of contention winners other than the number originally specified in the local system. The number of contention winners that CICS binds depends on the reply that the partner system gives to the request to initiate sessions (CNOS exchange). CICS tries to bind as contention winners all sessions that are not designated as contention losers in the CNOS reply.

For example, suppose that you specify MAXIMUM(10,4) in the local system and MAXIMUM(10,2) in the remote system. If the sessions are acquired from the local system, and the contention-losing sessions bind successfully, the result is 8 primary contention-winning sessions.

Important: Never specify AUTOCONNECT(ALL) for sessions to another CICS system, or to any system that can send a bind request. This could lead to bind-race conditions that CICS cannot resolve.

If AUTOCONNECT(NO) is specified, the sessions can be bound and made available by setting the modename into ACQUIRED AVAILABLE command. If this is not done, sessions are bound individually according to the demands of your application program.

For a single-session APPC terminal, the value specified for the AUTOCONNECT attribute of the SESSIONS or TYPETERM resources determines whether CICS tries to bind the single session or not.



dfht1c00121.html | Timestamp icon Last updated: Sunday, 4 June 2017