Effects of the AUTOCONNECT option

The AUTOCONNECT attribute of the SESSIONS resource controls the acquisition of sessions in modegroups associated with the connection.

The meanings of the AUTOCONNECT attribute for APPC connections are described in The AUTOCONNECT attribute. Each modegroup has its own AUTOCONNECT option and the setting of this attribute affects the sessions in the modegroup:
Table 1. Effect of AUTOCONNECT on the SESSIONS resource
Setting Effect
YES CNOS negotiation with the partner system is performed for the modegroup, and all negotiated contention-winner sessions are acquired when the connection is acquired.
NO CNOS negotiation with the partner system is performed, but no sessions are acquired. Contention-winner sessions can be bound individually according to the demands of application programs (for example, when a program issues an ALLOCATE command), or the SET MODENAME ACQUIRED command can be used to bind contention-winner sessions.
ALL CNOS negotiation with the partner system is performed for the modegroup, and all negotiated sessions, contention winners, and contention losers are acquired when the connection is acquired. This setting should be necessary only on connections to non-CICS systems.

When the connection is in ACQUIRED status, the INQUIRE MODENAME command can be used to determine whether the user sessions have been made available and activated as required. The binding of user sessions is not completed instantaneously, and you may have to repeat the command to see the final results of the process.

CICS can bind contention-winner sessions to satisfy an application request, but not contention losers. However, it can assign contention-loser sessions to application requests if they are already bound. Considerations for binding contention losers are described in the next section.



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