Vous êtes sur la page 1sur 6

JCL

S0CB S002 Attempting to divide by 0 and not using ON SIZE ERROR Very large record length/ wrong record length

Sx22 Job has been cancelled. The value of x will vary depending on the way the job was cancelled. S222 means job was cancelled by a user or operator without a dump. If a TSO session times out you will probably get an S522 abend code. S222 it violated The job was cancelled (by subsystem or operator) because some restriction S522 time limit S806 S837 S913 use. SOC7 Load module not found Space problem, Alloted space is not enough for data set You are trying to access a dataset which you are not authorized to JOB or TSO session exceeded maximum job wait time OR operator did not mount the require tape within allowed

1. Moving non-numeric value to numeric field 2. Not initilizing the numeric variables before first use 1. Index exceeds the size of table 2. Trying to use File Section variables without opening the file

SOC4

S0C1 Operation Exception. Check for subscript errors, missing DD card, file not opened. SE37 Insufficient disk space. COBOL sort failed. Program didn't close a file before ending

U1026 U1056 -

DB2
+100 -180 -204 -205 -206 -> -> -> -> -> End of cursor String representation of DATE, TTIME, TIMESTAMP is invalid Object not defined to DB2 Column name not in specified DB22 table Column does not exist in any tabble in the SELECT

-551 -803 -805

-> -> ->

Not authorized to access DB2 Unquie index voilation. Try to iinsert duplicate record. DBRM or PACKAGE not found in PLAAN Cursor should be used , when morre than one row returned as an of an singleton SELECT query

-811 -> result -818 ->

Timestamp mismatch between plan

and load module

IMP QUESTIONS ON ERROR CODES Q. What is error code for end of record/record not found in DB2? A. 100 Q. Then How you will find that, Error is for end of record or record not found? A. If we are using select statement, sql error code 100 represents record not found If we are using cursor , in that situation, sql error code 100 represents end of records

CICS
ASRA AICA - This abend occured beacuse of invalid non numeric data - 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. - Invalid EXEC CICS command issued - Most of the abends starts with AE, occures because they are not handled in the cics program.

AEY9 AE**

RESP VALUE 00 01 02 03 04 05

CONDITION NORMAL ERROR RDATT WRBRK EOF EODS

ABEND

06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

EOC INBFMH ENDINPT NONVAL NOSTART TERMIDERR FILENOTFOUND NOTFND DUPREC DUPKEY INVREQ IOERR NOSPACE NOTOPEN ENDFILE ILLOGIC LENGERR QZERO SIGNAL QBUSY ITEMERR PGMIDERR TRANSIDERR ENDDATA INVTSREQ EXPIRED RETPAGE RTEFAIL RTESOME TSIOERR MAPFAIL INVERRTERM INVMPSZ IGREQID OVERFLOW INVLDC NOSTG JIDERR

AEIK AEIL AEIM AEIN AEIP AEIQ AEIR

AEIU AEIV

AEIO AEI1

AEYG

44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81

QIDERR NOJBUFSP DSSTAT SELNERR FUNCERR UNEXPIN NOPASSBKRD NOPASSBKWR SYSIDERR ISCINVREQ ENQBUSY ENVDEFERR IGREQCD SESSIONERR SYSBUSY SESSBUSY NOTALLOC CBIDERR INVEXITREQ INVPARTNSET INVPARTN PARTNFAIL USERIDERR NOTAUTH VOLIDERR SUPPRESSED RESIDERR NOSPOOL TERMERR

AEYH

AEYQ

AEYX AEY7 AEXV

82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 255

ROLLEDBACK END DISABLED ALLOCERR STRELERR OPENERR SPOLBUSY SPOLERR NODEIDERR TASKIDERR TCIDERR DSNNOTFOUND LOADING MODELIDERR OUTDESCRERR PARTNERIDERR PROFILEIDERR NETNAMEIDERR NOTPOSS

AEXK

AEXX AEXO AEX1 AEX3 AEX5 AEX6

VSAM
00 02 04 05 10 20 21 22 23 key) SUCCESSFUL COMPLETION DUPLICATE KEY, NON UNIQUE ALT INDEX READ, WRONG LENGTH RECORD OPEN, FILE NOT PRESENT END OF FILE INVALID KEY VSAM KSDS OR RRDS SEQUENCE ERROR, ON WRITE OR CHANGING KEY ON REWRITE DUPLICATE KEY RECORD NOT FOUND - (when we are trying to access a record with or FILE NOT FOUND 35 OPEN, FILE NOT PRESENT

When we will use this code in our program? There are situations where file should be read if exists, write if it does not when you dont know whether file exists are not , first you will open file in I-O mode and check status code. if it is 35 then open that file for output file. other wise you will continue with your logic

41 42 43 46 47 48 49 92

OPEN, FILE IS OPEN CLOSE, FILE IS CLOSED DELETE OR REWRITE & NO GOOD READ FIRST SEQUENTIAL READ WITHOUT POSITIONING READING FILE NOT OPEN AS INPUT/IO/EXTEND WRITE WITHOUT OPEN IN IO MODE DELETE OR REWRITE WITHOUT OPEN IN IO MODE LOGIC ERROR/OPENING AN OPEN FILE OR READING OUTPUT FILE OR WRITE INPUT FILE OR DEL/REW BUT NO PRIOR READ SEQUENTIAL READ AFTER END OF FILE OR NO CURRENT REC POINTER FOR SEQ MISSING DD STATEMENT IN JCL OPEN OK, FILE INTEGRITY VERIFIED When we will use this in our programs? We use this code whenever we open the file, if status code is 00 or

94 96 97

97 we will proceed with our logic, other wise, call error routine. Usaully, it may come when file was not closed. for example IF WS-FILE-STATUS NOT = '00' AND '97' PERFORM ERROR-ROUTINE END-IF.

Vous aimerez peut-être aussi