ASPO

Explanation

An intersystem session failed while a syncpoint was being taken. The intersystem session that failed was the link to the coordinator system. The failure occurred during the indoubt period of syncpoint processing. As a result this CICS system is in doubt as to the outcome of the unit of work for the transaction.

The unit of work is not shunted to await the return of the coordinator system, but is instead unilaterally committed. The unit of work is not shunted for one of the following reasons:

• The transaction definition specifies WAIT(NO).

• The unit of work includes an MRO session to a back-level CICS system which does not support the WAIT(YES) option, and the role of the session in the unit of work is such that it cannot await the return of the coordinator system.

• The unit of work includes an LU6.1 session, and the role of the session in the unit of work is such that it cannot await the return of the coordinator system.

• The unit of work involves a task related user exit which is not enabled with the INDOUBTWAIT option.

• The unit of work has updated a recoverable transient data destination, which is defined with WAIT(NO).

• The unit of work involves the installation of CICS resource definitions from the CSD (CICS system definition) file.

The unit of work is committed, rather than backed out, because the transaction definition specifies ACTION(COMMIT).

The fact that the unit of work is committed is remembered by the recovery manager (RM) domain until the unit of work is resynchronized with the coordinator system. At this time, according to whether the coordinator system committed or backed out, the recovery manager domain issues resynchronization messages reporting whether or not the resolution of the unit of work in the subordinate system was consistent with the coordinator system.