Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Viewing the Abend-AID for CICS diagnostics_COBOL guide

Related Topics

Quick Reference

Installation and Configuration Guide

Advanced Configuration Guide

Getting Started

The Abend-AID for CICS interface provides additional diagnostics to help solve abends.

  1. To return to the Abend-AID for CICS Interface Menu (7), press PF3. The menu appears, and you are now back in Code Debug CICS.
  2. To view the diagnostic messages, type 3 in the COMMAND field.

  3. Press Enter to display the following screen.
    Abend-AID for CICS Diagnostic Information Screen

      Compuware Abend-AID ----- Diagnostic Information ------ Row 000001 of 000009
     COMMAND ===>                                                SCROLL ===> PAGE

     The transaction was terminated with the AEIM abend because the exceptional
     condition NOTFND occurred for which there was no 'EXEC CICS HANDLE
     CONDITION' request active.

     Either change the application program to prevent the condition recurring, or
     to handle the condition using the "EXEC CICS HANDLE CONDITION' command.  If
     necessary, use the contents of the EIBRCODE field in the EIB or information
     from the CICS trace table to assist in determining the cause of the
     exception condition.

    Since an AEIM abend was the last abend to occur, this screen automatically displays the diagnostics for an AEIM. The diagnostics for all CICS abend codes can be displayed from this screen.

  4. To display more information for an AEIM abend, tab to the highlighted AEIM abend code and press Enter. The IBM Message Text screen shown in following figure will be displayed.
    Abend-AID for CICS IBM Message Text Screen

      Compuware Abend-AID -------- IBM Message Text --------- Row 000001 of 000011
     COMMAND ===>                                                SCROLL ===> PAGE

     AEIM

     Explanation:

            NOTFND condition not handled.

            This is one of a number of abends issued by the EXEC interface
            program. Because of their similar characteristics these abends are
            described as a group.

            See the description of abend AEIA for further details.









                                             CF450QCV    AssistMenu=PF24

  5. Press PF3 twice to return to Code Debug CICS. The Abend-AID for CICS Diagnostics screen (7) will be displayed as shown in following figure.
    Abend-AID for CICS Diagnostics Screen (7)

     ---------------------- ABEND-AID FOR CICS DIAGNOSTICS (7) ----------------C123
    COMMAND ===>                                                   SCROLL ===> CSR
    MODULE: CWDEMCB2 CSECT: CWDEMCB2 ***Abend-AID for CICS processing completed***
    ABEND CODE: AEIM       "NOTFND" RECORD NOT FOUND
  6. To see another diagnostic message, type ASRA in the ABEND CODE field.
  7. Press Enter. The Abend-AID for CICS Diagnostic Information screen appears as shown in following figure, with the explanation of an ASRA abend.

Remember to end the session as described in Exiting Code Debug CICS and Ending a Debugging Session.

Abend-AID for CICS Diagnostic Information Screen for an ASRA Abend

 Compuware Abend-AID ----- Diagnostic Information ------ Row 000001 of 000059
 COMMAND ===>                                                SCROLL ===> PAGE
 FDBRC2100I User MYUSRID successfully logged on
 The transaction was terminated with the ASRA abend because the CICS system
 recovery detected a program check.  This may occur for any of the following
 reasons.

 The invalid operation code exception occurs when the operation code of the
 instruction to be executed is not a valid code or not available on the CPU
 that the program is running on.

 The priviledged operation exception normally occurs by executing a
 priviledged instruction while the program is executing in problem state.
 This is usually a symptom of another error.

 The execute exception normally occurs by executing an "EXECUTE" instruction
 by means of another "EXECUTE" instruction.  This is usually a symptom of
 another error.

 The protection exception occurs when the storage protect key of an operand,
 instruction, or data does not match the program's protection key.  This
 normally occurs by executing an instruction that either references or
 resides at an illegal storage location.  See also the notes on the
                                         CF450QCV    AssistMenu=PF24   More...

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*