05 es2j common abend routine
ES2J - Common ABEND Routine
| Program ID: | ES2JP01 |
|---|---|
| Mapset: | None |
| Files: | None |
All error exceptions that are not handled within a CICS transaction will be sent to this program. It displays a standardized error message line which includes the last-referenced file’s Data Definition (DD) name associated with the problem (if, in fact, it is file-related), and the CICS ABEND code. A subsequent line gives a verbal description of that error code. This can more quickly and easily point both the QCEW analyst and the data processing staff toward the resolution of the problem.
Note: When a data exception occurs (such as an “ASRA” condition for non-numeric data in a PIC 9 (i.e., strictly numeric) field), the displayed file name may not be the source of the problem. For instance, a micro record might contain a blank tax rate. When the record is read into a program, the Lookup File could be accessed to validate the county and industry codes for the account. If a later computation uses the tax rate, it would cause the ASRA error, identifying the last file accessed (the Lookup File) as the culprit, when it is actually attributable to bad Micro File data. These conditions can be misleading as to cause and effect. It is generally best not to be too hasty in making conclusions on ASRA’s. Contact the EXPO support line when ABEND conditions occur.
The most common type of system ABEND is caused because one of the VSAM files used by the system has been disabled (closed to CICS access). Generally, this occurs when a currently-executing batch job requires a VSAM file to be disabled for a batch update or file rebuild. The error could require the intervention of a CICS system programmer.
There may be a non-Service Center State that has established their own error-handling routines to trap and describe CICS errors. When this is the case, the EXPO CICS programs should be adapted to reference this State-specific error trapper.
Related Links
