AZCR
Explanation
A logic or protocol error has been detected during processing of an APPC SYNCPOINT ROLLBACK request. An attempt has been made to restore the conversation state to what it was after completion of the last successful unit of work. This saved state does not match flows received from the partner.
The problem arises during rollback in one of the following situations:
-
The saved state is receive, and the partner sent change direction on the last flow, indicating that the partner expects CICS to be in send state
-
The saved state is send, and the partner did not send the change-direction indicator on the last flow, indicating that the partner expects CICS to be in receive state.
System action
The task is abnormally terminated with a CICS transaction dump. Other processing continues.
User response
The problem can arise because of a failure in CICS, or a failure in the partner. To determine which is failing, analyze the flows at the last successful syncpoint. Try to determine the states the two LUs were in at this point. Look at the last syncpoint flow into CICS from the partner, before the abend. From this flow, calculate whether the change-direction indicator on the SPCMOD modifier byte is on. ( See the manual for further information on the SPCMOD modifier byte.) The indicator must only be set when the saved CICS conversation state is send. If the last CICS state was send, and the indicator is on, CICS is at fault. Similarly, if the last CICS state was receive, and the indicator is off, CICS is at fault.
If the last CICS state was send and the indicator is off, or the last CICS state was receive, and the indicator is on, CICS has received a change-direction indicator when it was not expecting one. In this case, examine the partner for a logic error.