LU6.1 connections

This section describes the ways in which LU6.1 connections differ from APPC parallel-session connections and MRO connections to CICS® TS for z/OS® systems.

Recovery functions and interfaces

Some recovery functions are not available to LU6.1 connections:
  • Shunting is not always supported.
  • Some recovery-related commands and options are not supported.
  • Resynchronization takes place on a session-by-session basis.
Restriction on shunting support
There is no LU6.1 protocol by which one system can notify another system that a unit of work has been shunted. The only time when a UOW that includes an LU6.1 session can be shunted is when all the following are true:
  • There is only one LU6.1 session in the local UOW.
  • The LU6.1 session is the coordinator.
  • The LU6.1 session has failed during the indoubt period.
  • The LU6.1 session is to the last agent.

Under these conditions, the UOW can be shunted, because there is no need for the LU6.1 partner to be notified of the shunt.

Under other conditions, a UOW that fails in the indoubt period, and that involves an LU6.1 session, takes a unilateral decision. If WAIT(YES) is specified on the transaction definition, it has no effect—WAIT(NO) is forced.

Unsupported commands
The following commands are not supported on LU6.1 connections:
  • INQUIRE CONNECTION PENDSTATUS
  • INQUIRE CONNECTION RECOVSTATUS
  • INQUIRE CONNECTION XLNSTATUS.
Lack of SYNCPOINT ROLLBACK support
There is no LU6.1 protocol by which one system can notify another that a UOW has been backed out, without terminating the conversation. An attempt to issue an EXEC CICS SYNCPOINT ROLLBACK command in a UOW that includes an LU6.1 session results in an ASP8 abend. This abend cannot be handled by the application program.

Any resources in the UOW are backed out, but the transaction is not able to continue.

Session-by-session resynchronization
Unlike APPC parallel-session connections and CICS TS for z/OS-CICS TS for z/OS MRO connections, LU6.1 sessions are resynchronized one by one, as they are bound. Therefore, any UOW that requires resynchronization is not resynchronized until the session that failed is reconnected.

Initial and cold starts

The LU6.1 connection definition contains sequence numbers used for recovery. If you perform an initial or cold start of CICS when there are LU6.1 connections on which recovery is outstanding, the sequence numbers are lost, and it becomes impossible for the partner systems to resynchronize their outstanding units of work.

Lognames are not used. Therefore, the XLNACTION attribute of the CONNECTION resource is meaningless for LU6.1 connections.

Managing connection definitions

Recovery information for a remote system is not stored independently from the connection definition for the system—the LU6.1 connection definition contains sequence numbers used for recovery. Therefore you should not modify or discard connections for which recovery information may be outstanding.



dfht1c00246.html | Timestamp icon Last updated: Monday, 5 June 2017