1. The document provides explanations for various abend codes encountered in JCL, DB2, VSAM, CICS, IMS, and other environments.
2. Common causes for abends include subscript errors, missing or incorrect DD statements, authorization issues, invalid data values, program logic errors, and resource limitations like insufficient disk space.
3. Specific abend codes are provided for different errors in each system along with short descriptions of likely causes.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as ODT, PDF, TXT or read online from Scribd
1. The document provides explanations for various abend codes encountered in JCL, DB2, VSAM, CICS, IMS, and other environments.
2. Common causes for abends include subscript errors, missing or incorrect DD statements, authorization issues, invalid data values, program logic errors, and resource limitations like insufficient disk space.
3. Specific abend codes are provided for different errors in each system along with short descriptions of likely causes.
1. The document provides explanations for various abend codes encountered in JCL, DB2, VSAM, CICS, IMS, and other environments.
2. Common causes for abends include subscript errors, missing or incorrect DD statements, authorization issues, invalid data values, program logic errors, and resource limitations like insufficient disk space.
3. Specific abend codes are provided for different errors in each system along with short descriptions of likely causes.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as ODT, PDF, TXT or read online from Scribd
1. The document provides explanations for various abend codes encountered in JCL, DB2, VSAM, CICS, IMS, and other environments.
2. Common causes for abends include subscript errors, missing or incorrect DD statements, authorization issues, invalid data values, program logic errors, and resource limitations like insufficient disk space.
3. Specific abend codes are provided for different errors in each system along with short descriptions of likely causes.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as ODT, PDF, TXT or read online from Scribd
Download as odt, pdf, or txt
You are on page 1/ 8
Abend Codes
Jcl:
S0C1 - Operation Exception. Check for subscript errors, missing DD card, file not opened. SOC4 - 1. Index exceeds the size of table 2.Trying to use File Section variables without opening the file SOC5 - 1. Bad subscript/Index 2. Close an un-opened dataset. 3. Bad exit from a perform statement. SOC7 - 1. Moving non-numeric value to numeric field 2.Not initilizing the numeric variables before first use S0CB - Attempting to divide by 0 and not using ON SIZE ERROR SB37 - Insufficient disk space (End of volume and no volume specified) SD37 - Insufficient disk space (No secondary allocation was specified SE37 - Insufficient disk space. (Max. of 16 extents already allocated) Sx22 - Job has been cancelled. The value of x will vary depending on the way the job was cancelled. S222 - The job was cancelled (by subsystem or operator) because it violated some restriction S522 - JOB or TSO session exceeded maximum job wait time OR operator did not mount the require tape within allowed time limit S322 - The job used more CPU time than it should have.Either the estimate is wrong OR the program is in an uncontrolled loop. S002 - Very large record length/ wrong record length. S806 - Load module not found S913 - You are trying to access a dataset which you are not authorized to use. U1026 - COBOL sort failed. U1056 - Program didn't close a file before ending. DB2
+100 - Row not found OR End of cursor
-102 - String constant is too long. -117 - The number of values you are trying to INSERT doesnot match the number of columns -180 - String representation of DATE, TTIME, TIMESTAMP is invalid -181 - Value for DATE, TTIME, TIMESTAMP is invalid -199 - Illegal use of the specified keyword -204 - Object not defined to DB2 -205 - Column name not in specified DB22 table -206 - Column does not exist in any tabble in the SELECT +222 - Trying to fetch a row that fell through a DELETE hole +223 - Trying to fetch a row that fell through a UPDATE hole +304 - Value cannot be assigned to this host variable, because it is out of range -305 - Null indicator needed -311 - Varchar, INSERT or UPDATE, you didn't set the -LEN field with the right data length -501 - Cursor not open on FETCH -502 - Opening cursor that is already open -503 - Updating column, which needs to be specified in FOR UPDATE OF -530 - Referential integrity prevents the INSERT/UPDATE -532 - Referential integrity prevents the DELETE -545 - Check consttaint prevents the INSERT/UPDATE -551 - Not authorized to access DB2 -747 - The table specified is not available because table and/or indexes need to be created +802 - The null indicator was set to +2, because an arthmetic statement didn't work -803 - Unquie index voilation. Duplicate key on insert or update -805 - DBRM or PACKAGE not found in PLAAN -811 - Cursor should be used , when more than one row returned as an result of an singleton SELECT query -818 - Timestamp mismatch between plan and load module -904 - Unavailable resource. Someone is locking the data you need. You may choose to termonate the program. -911 - Deadlock or Timeout. Rollback has been done -913 - Deadlock or Timeout. No Rollback has been done -922 - Authorization needed. -927 - The language interface was called, but no connection had been issued.
VSAM
02 - Duplicate key found
04 - Wrong Length Record 05/35 - Open, File not present 10 - End Of File 20 - Invalid key VSAM KSDS or RRDS 21 - Sequence Error, On Write OR Changing Key on Rewrite 22 - Duplicate Key 23 - Record Not Found - (when we are trying to access a record with key) or File Not Found 41 - OPEN, File is already Opened 42 - CLOSE, File is already Closed 43 - No Good Read First 46 - Sequential Read Without Positioning 47 - Reading file, which is not opened 48 - Write without open in IO mode 49 - Delete OR Rewrite without open in IO mode 92 - Logic Error/Opening an open file OR Reading Output file OR Write Input file OR Del/Rew but No Prior Read 94 - Sequential Read after End Of File OR No Current RC Pointer for SEQ 96 - Missing DD Statement in JCL CICS ASRA - This abend occured beacuse of invalid non numeric data
AICA - A looping task has been terminated with this abend
code by CICS because it was executing without giving up control longer than the time period specified by the ICVR keyword in the CICS SIT.
AEY9 - Invalid EXEC CICS command issued
AE** - Most of the abends starts with AE, occures because
U0778 - A ROLL call was issued by a user application program, or a failure during the Database Backout utility in another region resulted in all regions being terminated as a result of an internally issued ROLL call.
U0456 - If PSB is not available. (Not Running/Somebody is Using)
Solution:
Start PSB from the region in which you are running.
COMMAND - /start PGM <PSB>
NOTE - Before issuing command , please check PSB is running or not by using following command /dis PGM <PSB>
If psb is not running then only issue above /start command.
If some body using the PSB and you want to stop that transaction. use following command to stop command /stop PGB <PSB>
------------ Status Codes ------------
GE - End Of Segment
AC - Invalid SSA
* Invalid Segment name specified in SSA
* The segment name is in the DB PCB, but the SSA specifying that segment name is not in its correct hierarchic sequence.
AD - Problem in PCB listing in program ( linkage section )
AK - Invalid SSA
* Invalid field name in SSA ( Key given in SSA is wrong )
