Mainframe230

HomeFree Questions
Showing posts with label Abend Codes. Show all posts
File Status Codes (or) COBOL Abend Codes
ERROR
REASON
CODE
00
Operation completed successfully
02
Duplicate Key was found
04
Invalid fixed length record
05
The file was created when opened - Successful Completion
07
CLOSE with REEL or NO REWIND executed for non tape dataset
.
10
End of File encountered
14
Attempted to READ a relative record outside file boundary
21
Invalid Key - Sequence error
22
Invalid Key - Duplicate Key found
23
Invalid key - No record found
24
Invalid Key - key outside boundary of file.
30
Permanent I/O Error
34
Permanent I/O Error - Record outside file boundary
35
OPEN, but file not found
37
OPEN with wrong mode
38
Tried to OPEN a Locked file
39
OPEN failed, conflicting file attributes
41
Tried to OPEN a file that is already open
42
Tried to CLOSE a file that is not OPEN
43
Tried to REWRITE without READing a record first
44
Tried to REWRITE a record of a different length
46
Tried to READ beyond End-of-file
47
Tried to READ from a file that was not opened I-O or INPUT
48
Tried to WRITE to a file that was not opened I-O or OUTPUT
49
Tried to DELETE or REWRITE to a file that was not opened I
-O
91
Password or authorization failed
92
Logic Error
93
Resource was not available (may be allocated to CICS or ano
ther user)
94
Sequential record unavailable or concurrent OPEN error
95
File Information invalid or incomplete
96
No DD statement for the file
97
OPEN successful and file integrity verified
98
File is Locked - OPEN failed
99
Record Locked - record access failed.
Get FREE Mainframe Interview Question & Answers - Click Here
Posted by M siva raman at Friday, April 08, 2011 1 comments
Labels: Abend Codes, Entire Mainframe Materials, Mainframe, Mainframe Tips, MF I
nterview Question Answers
Important COBOL ABENDS in COBOL
1.
What are the causes for S0C1, S0C4, S0C5, S0C7, and S0CB ABENDs?
S0C1 - May be due to
1.Missing or misspelled DD name
2.Read/Write to unopened DataSet
3.Read to DataSet opened output
4.Write to DataSet opened input
5.Called subprogram not found

S0C4 - Mmay be due to

1.Missing Select statement (during compile)
2.Bad Subscript/index
3.Protection Exception
4.Missing parameters on called subprogram
5.Read/Write to unopened file
6.Move data from/to unopened file
S0C5 - May be due to
1.Bad Subscript/index
2.Close an unopenunopened DataSet
3.Bad exit from a perform
4.Access to I/O area (FD) before read
S0C7 - Mmay be due to
1.Numeric operation
on non-numeric data
2.Un-initialize working-storage
3.Coding past the maximum allowed sub script
S0CB - Mmay be due to
1.Division by Zero
2.
What do you do to resolve SOC-7 error? Basically you need to correct the offending data.
Many times the reason for SOC7 is an uninitialized numeric item. Examine that po
ssibility first.
Many installations provide you a dump for run time ABENDs ( it can be generated
also by calling some subroutines or OS services thru assembly language). Thes
e dumps provide the offset of the last instruction at which the ABEND occurred.
Examine the compilation
output XREF listing to get the verb and the line number of the source code at t
his offset. Then you can look at the source code to find the bug. To get capt
ure the runtime dumps, you will have to define some Data Sets (SYSABOUT etc )
in the JCL.
If none of these are helpful, use judgement and DISPLAY to localise the source
of error.
Some installation might have batch program debugging tools. Use them.
3.
What is SOC1 and SOC4?
A S0C1 occurs if the CPU attempts to execute binary code that isn't a valid mac
hine instruction; e.g. if you attempt to execute data. A S0C4 is a memory protec
tion violation. This occurs if a program attempts to access storage beyond the a
reas assigned to it.
Get FREE Mainframe Interview Question & Answers - Click Here
Posted by M siva raman at Thursday, October 28, 2010 0 comments
Labels: Abend Codes, COBOL, COBOL Tutorial, Entire Mainframe Materials, Mainfram
e Tips, Mainframe Tutorials
JCL Abend Codes
S001-4 ABEND
Input file record length is not equal to the length stated in the DD or the FD.
Wrong length record.
IO error, damaged tape, device malfunction.
With disk, reading a dataset that was allocated but never written to.
Writing to input file
Concatenation of files with different record lengths or record formats.
S001-5 ABEND

Reading after the end of the file by non-COBOL program.

COBOL intercepts this and displays "QSAM error, status 92".
Out of space on output disk file.
S002 ABEND
With variable format files used for output.
The record is larger than the track size.
The record length is greater than allowed maximum 32,768.
The wrong record length is being used on output.
The 4-byte record length indicator is wrong.
Record greater than 32,768 bytes
S013-10 ABEND
A dummy file with no blocksize.
S013-14 ABEND
A library has run out of space in its directory.
You have to backup, delete, and restore the library with IEBCOPY.
A dataset is sequential, but the JCL indicates that it is a library/PDS.
S013-18 ABEND
A library member was specified in the JCL but was not found.
S013-20 ABEND
The block size is not a multiple of record length.
Check record length in program, compare to actual record length of file
S013-34 ABEND
The block size was found to be 0.
A new file is being created but block size was not in the JCL.
S013-40 ABEND
Reading a file whose JCL has SYSOUT=
S106 ABEND
The program on the program library was unreadable. Recompile and link.
S122 ABEND
The job was canceled because it violated some restriction.
A dump was requested
S137 ABEND
A tape has a bad trailer label.
Copy the file with IEBGENER, ignoring the error. The copy will be good.
Using LABEL=2 when there's only one dataset on the tape.
S213 ABEND
A disk dataset was not actually on the volume stated in the VOL=SER=.
A disk dataset was not actually on the volume indicated in the catalog.
S222 ABEND
The job was cancelled because it violated some restriction.
No dump was requested.
S237 ABEND
The block count on
Probably caused by
Copy the file with
A problem with the
S313, 314 ABEND

a tape trailer label is wrong.

hardware error.
IEBGENER, ignoring the error. The copy will be good.
second volume of tape or disk.

An Input/output error in the VTOC of a disk volume. Inform support staff.

S322 ABEND
The job used more CPU time than it should have.
Either the estimate is wrong or the program is in an uncontrollable loop.
S413 ABEND
A volume was needed that could not be mounted.
S422 ABEND
Too many job steps.
S513 ABEND
Two jobs or DDNAMES wanting same tape at same time.
S522 ABEND
Job was waiting too long.
S613 ABEND
A bad tape label.
S637 ABEND
A bad concatenation, different types of devices were used.
An unreadable tape mark or label.
S706 ABEND
The program on the library was not executable.
See linkage editor report that put the program on library.
S713 ABEND
The tape was unexpired and the operator terminated the job.
S714 ABEND
Labels on the tape were bad.
S722 ABEND
Too many lines of print.
S804 ABEND
Region too small for the program.
S806 ABEND
Program not on the library. May need a JOBLIB or STEPLIB.
S80A ABEND
Region too small for the program.
S813 ABEND
Right tape volume, wrong dataset name.
Right dataset name, wrong tape volume.
S913 ABEND
Security violation.
SA13 ABEND
Label=n states the wrong number.
SB14 ABEND
No space in a library directory for this member's name.

SB37 ABEND
Insufficient disk space.
SD37 ABEND
Insufficient disk space.
SE37 ABEND
Insufficient disk space.
An E37 on tape datasets is most often caused when the number of requested volume
s is exceeded. The default is 5,
therefore a request for the sixth volume will fail with a E37.
S0C1 ABEND
Executing a program with an unresolved external reference.
Calling a program and the program was not included during link edit.
An uncontrolled loop moved data on top of instructions.
Reading a file that is not open
Your SORTIN DCB was not correct
Mixing compile options RES and NORES in different modules
S042PRIVILEGED OPERATION ABEND
Read/write to unopened file
An uncontrolled loop moved data on top of instructions.
S0C4 PROTECTION ABEND
An uncontrolled loop moved data on top of instructions.
referencing a field in a record of a closed file
referencing an item in Linkage-Section when there was no PARM= in the JCL.
Calling/called programs have different length for items passed in Linkage Sectio
n
with COBOL Sort, doing a STOP RUN or GOBACK while
an input or output procedure is still running
S0C5 ADDRESSING ABEND
See reasons as for 0C4.
Falling through into an ENTRY statement
Transferring control into the middle of a SORT procedure.
S0C6 SPECIFICATION ABEND
Bad boundary alignment for binary data.
See reasons for 0C4
S0C7 ABEND
Program attempting to do math on illegal data.
Data is not numeric, but should be.
Moving ZEROS to group item whose subordinate items
are packed-decimal
Uninitialized packed-decimal fields.
Record description is wrong. Field starts or ends in the wrong place in the reco
rd.
Find record description of creating program.
S0CB ABEND
Attempting to divide by 0 and not using ON SIZE ERROR
U1002 ABEND
Conflicting file attributes. See S013.
U1005 ABEND

Executing with modules compiled both with RES and NORES

U1006 ABEND
Subscript out of range
U1017 ABEND
Missing DD statement in JCL for DISPLAY or ACCEPT verb
U1020 ABEND
Problem opening or processing a file.
Check the file status.
U1026 ABEND
COBOL sort failed.
U1034 ABEND
Same as SB37 Abend
U1035 ABEND
Conflicting DCB parameters. Same as S013.
U1037 ABEND
Program control falls through the last physical statement in program,
which is not GOBACK/STOP RUN.
U1056 ABEND
Program didn't close a file before ending
U1066, U1075 ABEND
Conflicting DCB information for file defined as EXTERNAL
U1072, U1073, U1074 ABEND
Illegal numbers in reference modification
U3000 ABEND
COBOL LE intercepted the Abend. Messages in SYSDBOUT.
U4038 ABEND
COBOL LE intercepted the Abend. Messages in CEEDUMP.
Get FREE Mainframe Interview Question & Answers - Click Here
Posted by M siva raman at Monday, August 23, 2010 0 comments
Labels: Abend Codes, JCL, Mainframe
Older Posts Home
Subscribe to: Posts (Atom)
? Grab this Headline Animator
CONTENT
Abend Codes
CICS
CICS Program's
CICS Tutorial
COBOL
COBOL Program's
COBOL Tutorial
DB2
DB2 Tutorial
Download
Entire Mainframe Materials
JCL

JCL Program's
JCL Tutorials
Mainframe
Mainframe Case Study
Mainframe Tips
Mainframe Tools
Mainframe Tutorials
MF Interview Question Answers
PL/I Program's
Progrrams
Sample Mainframe Program's
SQL Codes
TSO/ISPF
VSAM
VSAM Program's
VSAM Tutorials
MAINFRAME PROGRAM'S
JCL Sample Program's
VSAM Sample Program's
DB2 Sample Program's
COBOL Sample Program's
CICS Sample Program's
SUBSCRIBE TO
Posts
All Comments
TOTAL PAGEVIEWS
SUBSCRIBE VIA EMAIL

Enter your email address:

Subscribe
Delivered by FeedBurner
ABOUT ME
My photo
M siva raman
Gingee, Tamilnadu, India
View my complete profile