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.

Overview of Abend-AID


Abend-AID intercepts and analyzes application program failures to provide comprehensive fault diagnostics reacting specifically to the type of error, the language of the failing program, and the types of files or databases in use. A concise, easy-to-read report, available online or in printed form, presents the most important information first and includes only the data necessary to solve the problem. Abend-AID provides diagnostics for Db2, IMS, and IDMS databases as well as COBOL, PL/I, Assembler, C, and VS FORTRAN languages. This support includes those versions of COBOL and PL/I that can be run with Language Environment. For COBOL, PL/I, and Assembler errors, Abend-AID merges actual source code and diagnostic data into a single report. Online, menu-driven access enables quick and accurate problem resolution. The specialized diagnostics for Db2, IMS, and IDMS environments enable programmers to resolve errors independently of the DBA staff.

Abend-AID utilizes both Report and Source Listing shared directories. The source listings can also be utilized by Strobe and Code Debug TSO and/or Code Debug CICS. Users can view reports either in Job/STC output or online in the Abend-AID Viewer.

Product architecture

Abend-AID is comprised of the following three main components, as described in the figure:

  • Batch Dump Capture Address Space (BDCAS): This component is required and must be active to capture and process dump information for batch Abend-AID.
  • Transaction Dump Capture Address Space (TDCAS): This component is required and must be active to capture and process dump information for Abend-AID for CICS.
  • Viewing Server: This component is an MVS address space that is required and must be active to view Abend-AID reports and/or dump information via the Abend-AID Viewer or via the Abend-AID Web Browser Interface plug-in within the BMC AMI DevX Workbench for Eclipse. This component does not have to be active to capture dump information.

Abend-AID Product Architecture

architecture.png


The 

Abend-AID

 product architecture is described here in the context of an application abend event:

  1. An application abend occurs.
  2. The application abend event data is processed by one of Abend-AID's dump capture components and is written as reports in the BMC Report Shared Directory. Batch applications are processed by Abend-AID’s Batch Dump Capture Address Space (BDCAS). CICS applications are processed by Abend-AID's Transaction Dump Capture Address Space (TDCAS).
  3. The Abend-AID viewing server, running as a started task, formats the abend analysis from the generated reports and displays the information in the context of the program's source via BMC source listings. The abend analysis can be viewed in a 3270 session, a web browser, or BMC AMI DevX Workbench​ Eclipse-based IDE.

Note

BMC AMI DevX Workbench for Eclipse integration requires that you follow the instructions in Configure Workbench for Eclipse integration.

The Abend-AID viewing server uses the following required files:

  • BMC report database VSAM files that contain Abend-AID reports.
  • BMC report shared directory VSAM files to which Abend-AID reports are attached for viewing in the Abend-AID viewing server
  • BMC source listings that contain source listing files that have been processed by the BMC AMI Common Shared Services (CSS) language processors for COBOL, PL/I, and/or Assembler.
  • A BMC source shared directory to which source listing files are attached for viewing in the Abend-AID viewing server
  • Viewing server VSAM work file
  • Persistent data VSAM file that contains end-user customization of Abend-AID panels

The Abend-AID viewing server also uses the following optional files:

  • IPCS directory
  • User DSECT
  • Dump information file

Related topic



 

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