JCL

S0CB

Attempting to divide by 0 and not using ON SIZE ERROR

S002

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 The job was cancelled (by subsystem or operator)
because it violated
some restriction
S522

OR

JOB or TSO session exceeded

maximum job wait time

operator did not mount the require tape within

allowed time limit

S806

Load module not found

S837

Space problem, Alloted space is not enough for data set

S913 You are trying to access a dataset which you are not
authorized to use.
SOC7

1. Moving non-numeric value to numeric field

2. Not initilizing the numeric variables before first use

SOC4

1. Index exceeds the size of table

2. Trying to use File Section variables without opening the

file
S0C1 Operation Exception. Check for subscript errors, missing DD
card, file not opened.
SE37

Insufficient disk space.

U1026 -

COBOL sort failed.

U1056 -

Program didn't close a file before ending

DB2

+100

->

End of cursor

-180

->

String representation of DATE, TTIME, TIMESTAMP is invalid

-204

->

Object not defined to DB2

-205

->

Column name not in specified DB2 table

-206

->

Column does not exist in any tabble in the SELECT

-551

->

Not authorized to access DB2

-803

->

Unquie index voilation. Try to insert duplicate record.

-805

->

DBRM or PACKAGE not found in PLAAN

-811 ->
result

Cursor should be used , when morre than one row returned as an

of an singleton SELECT query

-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

FOR SQL STATE CODES (VERSION 7) CLICK HERE

FOR SQL TUTORIAL CLICK HERE

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

they are not handled in the cics program.

RESP
VALUE

CONDITION

00
01
02
03
04
05
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

NORMAL
ERROR
RDATT
WRBRK
EOF
EODS
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

ABEND

AEIK
AEIL
AEIM
AEIN
AEIP
AEIQ
AEIR

AEIU
AEIV

AEIO
AEI1

34
35
36
37
38
39
40
41
42
43
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

RTESOME
TSIOERR
MAPFAIL
INVERRTERM
INVMPSZ
IGREQID
OVERFLOW
INVLDC
NOSTG
JIDERR
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

AEYG
AEYH

AEYQ

AEYX
AEY7
AEXV

76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
255

NOSPOOL
TERMERR
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

SUCCESSFUL COMPLETION

02

DUPLICATE KEY, NON UNIQUE ALT INDEX

04

READ, WRONG LENGTH RECORD

05

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
with key)

35

RECORD NOT FOUND - (when we are trying to access a record

or
FILE NOT FOUND
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

OPEN, FILE IS OPEN

42

CLOSE, FILE IS CLOSED

43

DELETE OR REWRITE & NO GOOD READ FIRST

46

SEQUENTIAL READ WITHOUT POSITIONING

47

READING FILE NOT OPEN AS INPUT/IO/EXTEND

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 REC POINTER FOR SEQ

96

MISSING DD STATEMENT IN JCL

97

00 or 97
routine.

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

IMS
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)

WHAT WE SHOULD DO ?
START PSB FROM THE REGION IN WHICH YOU ARE RUNNING 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
GB

End Of Segment
End of Database

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 )

COBOL:
1
1
2
4
8

NibbleByte Bytes
Bytes
Bytes

4 bits
8 bites
Half word
Full word
Double word

PL/1 Errors