Previous Topic: Abend HandlingNext Topic: Using a CEMT Force-Purge Transaction


Using an Abend Handler

Using an abend handling routine causes CICS to reset the abend condition and, at termination, CA Datacom CICS Services does not use its special abend processing to issue a ROLBK command. If you want to use CA Datacom/DB's transaction backout processing, your abend handling routine must issue one of the following (shown in their preferred order):

CICS SYNCPOINT ROLLBACK and CICS ABEND allows CA Datacom CICS Services to handle the backout. However, any allowable CA Datacom/DB command is honored.

When processing a CA Datacom/DB request from an abend handling routine, CA Datacom CICS Services treats it as a new request and has no indication that it has been issued by an abend handler. Therefore, CA Datacom CICS Services processes a request from an abend handler like any other CA Datacom/DB request:

  1. CA Datacom CICS Services checks for the completion of any previous CA Datacom/DB request. If it finds a previous request that has not been completed, it abends the transaction (active request) with an abend code of DC16.
  2. The DC16 abend causes abend processing to occur. CA Datacom CICS Services is called by CICS and:
    1. Releases any attached facility (terminal).
    2. Waits on the original request.
    3. Is followed by a ROLBK (backout).

If the application and the abend handler have used different Request Areas, the results of both commands are available to your application.