| System Completion Codes (Abends) | ||
| OS/390 Abend codes are sometimes difficult to decipher; some of the explanations offered by the IBM OS/390 MVS Messages manual can be cryptic and difficult to understand. The Abend Helper offers you an additional source of information which may help you to figure out what's going on by providing a brief explanation of some of the common MVS system completion codes. | ||
| Note: Although I have tried to include some of the more common Abend codes, Not all Abends are included. As always, the IBM manuals are the definitive source for looking up messages. Adding explanatory text to the Abend Helper is an ongoing project, so if you have any "pet" abend codes you would like explained, drop me an email at the address below. | ||
| When a program abends, a system message and/or system completion (ABEND) code is included in the job's JCL output. The system abend code is either displayed as part of the system message that begins with IECxxxI, or is located in the JES2 job log and in the JCL expansion at the step where the abend occurred. | ||
| The general format system messages related to Abend codes is: | ||
IECxxxI AAA-RC,MOD,JJJ,SSS,DDN(x),DDD,SER,DSN |
||
| xxx | 3 character system message number. | |
| AAA | 3 digit system completion (ABEND) code. | |
| RC | 2 digit return code. | |
| MOD | Name of the module (program) that was running when the Abend occurred. | |
| JJJ | Job Name. | |
| SSS | Step name. | |
| DDN(x) | DDNAME associated with the Abend. If a number is included, indicates the position in the concatenation. | |
| DDD | Hardware Device address associated with the Abend. | |
| SER | Volume Serial number. | |
| DSN | Dataset Name. | |
Comments or questions can be directed to: John Miller 