Error handling and failure of the mirror transaction
If the mirror task in the remote region encounters an error or abend, and the mirror program can handle the error or abend, the error, or abend is returned to the application program that issued the function-shipped request.
The remote mirror (server) task, and the task running the program that issued the request (client task), share a common transaction scope unless the request was one of the following requests:
- A function-shipped EXEC CICS® START NOCHECK command
- A distributed program link (DPL) request with SYNCONRETURN
- A non update request; for example, a file control read only
If the server task performs recoverable work as part of such a common transaction scope, that work is committed or backed out under the control of the sync point processing of the client task even though an error or abend was encountered. The default action is for the error or abend to cause abnormal termination of the client task and to back out all recoverable updates made by both the client and server programs.
However, in common with local execution (that is, when not using function shipping or distributed program link), the application program that issued the request that was function-shipped might attempt to handle the error or abend. The handle logic then issues an EXEC CICS SYNCPOINT, SYNCPOINT ROLLBACK, RETURN, or ABEND command. Attempting a SYNCPOINT or RETURN, (rather than a SYNCPOINT ROLLBACK or ABEND) despite being informed of the error or abend, results in an attempt to commit the client program's local resource updates and those performed by the server transaction before the error or abend was encountered.
If the mirror program cannot handle the error or abend encountered by the mirror transaction and this causes the termination and backout of the mirror transaction without sending a response to the client application, CICS forces the client program's transaction to back out. Any explicit sync point attempt fails and the local updates are backed out. This response also occurs if a problem is encountered with the communications link between the client and server tasks.
If the client and server tasks do not share a common transaction scope, as described previously, errors or abends that result in the stopping of the server task, and problems with the communications link, do not force the client's transaction to back out.