Cobol Error Codes In Mainframes
Contents |
or worth reading for someone please like mainframegeek facebook page. Abend Codes Abend happens during the execution of a program in a step(JCL). Generally it can be categorized into system abend and user abend. System Abend - sql error codes in mainframes It will occurs when the system is not able to execute a statement which how to pass return code from cobol to jcl is coded in a program. This abend code will be thrown by OS. User Abend - This is due to unexpected condition
Java Mainframes
occurs in data passed; this abend will be thrown by application based on the requirement. Condition Code Abends CC=0001 - (1016) PIE JOBS - BAD PART NUMBER - FOLLOW PACBOOK VERY CAREFULLY CC=001 - I/O ERROR CC=002
Cics Mainframes
- I/O INVALID RECORD CC=0004 - DATASET NOT FOUND, TABLESPACE IN COPY PENDING, ETC MAY BE OK(CHECK COND STATEMENTS OR CALL ADM TO VERIFY) CC=0008 - EQUIP CHECK, UNABLE TO DBR DB RLAO00, RC-08 SQL ERROR, EMPTY DATASET CC=0010 - (CC=0016 IN HEX) BAD DATA CC=0012 - I/O ERROR TAPE, VSAM DATASETS CLOSED, INVALID DATA, EMPTY TABLE, COULD BE ANYTHING CC=0014 - CC=0016 - COULD BE ANYTHING, CONTENTION ,INVALID DATA, EMPTY TABLE, # db2 mainframes OF FILES EXPECTED NOT EQUAL TO # OF FILES RECEIVED CC=0020 - COULD BE ANYTHING (CATCHALL) CC=0030 - DB2 TABLES WRONG DATES CC=0152 - ERROR ATTEMPTING TO TRANSLATE NEXT TRANSACTION CC=0696 - FTP LINE DOWN CC=804 OR 80A - REGION SIZE TOO SMALL - SPECIFY REGION=0M CC=1000 - BAD DATA, CONTENTION(-911) CC=1008 - TOTALS OUT OF BALANCE CC=1016 - NUMBER OF FILES EXPECTED DOES NOT EQUAL NUMBER RECEIVED, BAD DATA, CONTENTION CC=1999 - DATA EXCEPTION, BAD DATA CC=2000 - RESOURCE NOT FOUND (07D0), PROGRAMMING ERROR WAITING FOR FILE, RACF (-922), REBIND (-805) CC=2004 - CYCLE OUT OF SEQUENCE CC=2016 - TOO MUCH DATA FOR ARRAY SIZE, TABLE UPDATE INCORRECT, NULL DATA CC=2444 - INVALID RECORD LENGTH CC=8000 DATASET ALREADY IN USE, I/O ERROR, FILES NOT SENT RESOURCE NOT AVAILABLE CC=FFF - FATAL INTER ADDRESS COMMUNICATION ERROR User Abends U046 - NOT ENOUGH OR NO SORT WORK SPACE ALLOCATED. U048 - USER DOES NOT HAVE ACCESS AUTHORIZATION FOR THE DATASET U061 - REORDER DATASETS, CHECK BLOCKSIZES. LARGEST BLOCKSIZE FIRST U063 - CHECK SPELLING OF DD STATEMENTS U099 - DATASET NOT FOUND U0000 - DB2 STOPPED UTILID, TABLESPACE U0007/U0240 - VSAM I/O ERROR ON ACKS DATASET(WIDEBAND PROBLEM) U0100 - USER ERROR U0102 - PROBLEM WITH CHECKPOINT - MAY NOT HAVE BEEN ANY CHECKPOINTS U0103 - ENTRY NOT FOUND
otherwise specified, each file status code can be received for operations on any file organizations in any access mode. The ANSI'74, ANSI'85 and Extended File Status codes are given in your Error Messages. The following sections contain
Cobol Compiler Jcl
the RM/COBOL file status codes and the Microsoft V2 file status codes. In addition to the cobol vsam above file status conventions you can produce more detailed extended file status codes. Extended file status codes have the following format: 9/nnn where cobol jcl jobs nnn is a binary (COMP-X) number, equivalent to a run-time error number. Run-time errors are documented in the chapter Run-time System Messages in your Error Messages. For example, if you are writing a file to disk and the disk http://mainframegeek.me/abend-codes-and-explanation/ runs out of space, the ANSI'74 file status would be "30", which translates into a "Permanent error - no other information is available" error message. That error message is very general; a "permanent error" could mean that the disk has failed, or that the disk drive door is open. So, rather than return a generic file status, this COBOL system returns an extended file status of 9/007. When using ANSI'74 or ANSI'85 file status codes, the run-time https://supportline.microfocus.com/documentation/books/sx20books/fhscod.htm system returns extended status codes if the extended file status is more specific than what would normally be returned. Unless otherwise specified, each file status code can be received for operations on any file organizations in any access mode. 15.1 List of Messages '74 '85 Meaning 00 00 Successful completion 02 02 Indexed files only. One of two possibilities: For a READ statement, the key value for the current key is equal to the value of that same key in the next record in the current key of reference. For a WRITE or REWRITE statement, the record just written created a duplicate key value for at least one alternate record key for which duplicates are allowed. 00 04 The length of the record being processed does not conform to the fixed file attributes for that file. 00 05 The referenced optional file is not present at the time the OPEN statement is executed. 00 07 Sequential files only. For an OPEN or CLOSE statement with the REEL/UNIT phrase the referenced file is a non-reel/unit medium. 10 10 No next logical record exists. You have reached the end of the file. 14 Relative files only. The number of significant digits in the relative record number is larger than the size of the relative key data item described for that file. 21 21 Sequentially accessed files only. Indicates a sequence error. The
Disk space problem Below is a summary of the common messages that could occur. Each message is identified by a message number, and is formatted as: NNNNNNN ccc-rr jjj sss ddname where NNNNNNN is the error message http://faculty.madisoncollege.edu/schmidt/mainframe/abendcodes.html number ccc is the system completion code associated with the message rr is the return code associated with the message jjj is the job name sss is the step name ddname is the file associated with the problem Message Number Parameters/Description IEA702I 80A-1 There is not enough storage to run the request program IEA703I 806-x x=4 The requested program could not be found. Check the JCL STEPLIB or JOBLIB statements to be sure error codes they define the library containing the requested program. x=8 An uncorrectable input-output error has occurred. Try to run the job again. If the error reoccurs, consult your technical support staff IEC015I A34-04 An attempt was made to read an unopened file. IEC020I 001-x x=1, 3, or 4 The dataset characteristics don't match the specified file. Check your FD, JCL and data set information x=2 An error occurred when the program tried to close the file error codes in x=5 The program tried to read the file after end of file had been reached. IEC030I B37-04 There is no space left on the disk volume The data set has reached it's limit of space The disk volume table of contents is full IEC031I D37-04 The file has used up all of its space IEC032I E37-x x=04 All available disk space is used up IEC141I 013-x x=10, 34 The block size and record length are both 0 or the block size is not a multiple of the record length. x=20 The record format indicates that the file is a blocked file, but the block size is not a multiple of the record size. x=60 The record format indicates that the file is an unblocked file, but the block size does not equal the record length x=68 The block size exceeds the maximum allowable IEC143I 213-x x=04 1) An incorrect volume or data set name parameter 2) Data set not found on disk 3) The data set has been deleted x=08 Password violation x=18, 1C I/O error Common Completion Codes - Details Code Probable Cause 001 I/O Error Attempt to read after AT END Referring to an I/O area before opening and reading a record Reading a wrong length record 002 I/O Error DD statement doesn't match FD 013 Something doesn't mat