Day1 ProblemSolving-AbendsHandling v1[1].0

7/31/2019 Day1 ProblemSolving-AbendsHandling v1[1].0

1/18

Problem Solving -

Abend Handling

Basic

Problem SolvingProblem Solving --

Abend HandlingAbend Handling

BasicBasic

C3: ProtectedC3: Protected


2/18

Copyright 2004, Cognizant Academy, All Rights Reserved 2

About the Author

More than 4 years of experience in mainframe

technologies.

Credential

Information:

ABEND/PPT/0406/1.0Version and Date:

Alagumalai Punitha, 123830Created By:


3/18


Questions

A Welcome Break

Coding Standards

Demo Key Contacts

Reference

Test Your Understanding

Hands-on Exercise

Icons Used


4/18


Problem Solving - Abend Handling:

OverviewIntroduction:

ABENDS are abnormal termination of a job:

The job may encounter an unsuccessful completion which may be an

ABEND.

Abend means ABnormal END of the job.

Abend code preceding with S denotes a system abend

Abend code preceding with U denotes a user abend


5/18



Objective

Objective:

After completing this topic, you will be able to:

Locate system ABEND

Resolve system ABEND

Locate JCL errors

Resolve JCL errors

Locate user ABEND

Resolve user ABEND


6/18


Problem Solving Abend HandlingS0C1 - Operation Exception

When does it come?

When the subscript is out of boundary for a COBOL table size Trying to read a file that is not open

Error in PARM passed to subroutine (Related to addressing mode and data

mode)

Missing DD card Recording mode was wrong

Bad load module (Subroutine program ID and program name not the same)

Same name for array and subroutine.

How to solve it? Check for subscript errors Refer to the DD cards specified

Check the file open status.


7/18


Problem Solving Abend Handling

(Contd.)

S0C4 Protection Exception/Storage Violation

S0C4 - Page translation error

When does it come?

Trying to access memory that is not allocated to it

Tried to read or write a file that is not open

When subscript of out range

How to solve it?

Check the length of receiving variable record (AMODE, RMODE)

Check whether the program is compiled with SSRANGE option


8/18


S0C7 - Program Check Exception Data

S0C7 - Data Exception error

When does it come?

Sign is invalid for packed variable

When tried to move a non numeric value in to packed decimal


(Contd.)


9/18



(Contd.)S0C7 - Program Check Exception Data

How to solve it? Find out the next sequential instruction to be executed from SYSUDUMP

Go to compile listing and find the instruction where the abend occurred

(HEXLOC - OFFSET)

Check for initialization of packed variables in the statement

Check for correct data present is moved to packed fields

Otherwise, go to Diagnostic Section of DUMP and find out the offset anddisplacement. This helps to locate the field in problem.

Check for spaces in a packed decimal or numeric field.

Check to see if record layouts or file layouts have been changed.


10/18



(Contd.)S122 Abend:

The job was canceled because it violated some restriction.

A dump was requested

S222 Abend:

The job was cancelled because it violated some restriction.

No dump was requested.

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.


11/18



(Contd.)S422 Abend:

Too many job steps.

S522 Abend:

Job was waiting too long.

S0CB Abend:

Attempting to divide by 0 and not using ON SIZE ERROR

S013-18 Abend:

A library member was specified in the JCL but was not found


12/18



(Contd.)S806 - Load module not found

When does it come?

When the load module not present in the joblib concatenation.

How to solve it?

Goto JOBLOG and find out the module name which is not found

Search the joblib concatenation

Check whether the load module of the called program is present in the loadlib

Check for the correctness of the load module name


13/18


Demo: Example for S806

000100 //TCHN001A JOB NOTIFY=&SYSUID,CLASS=A,MSGLEVEL=(1,1)

000300 //JOBLIB DD DSN=TCHN001.GENERAL.LOAD,DISP=SHR

000400 //STEP1 EXEC PGM=XYZ

000410 //SYSOUT DD SYSOUT=*

000420 //SYSIN DD DUMMY

000500 //

Note: REQUESTED MODULE XYZ NOT FOUND


14/18


SB37 Abend:

Insufficient disk space.

SD37 Abend:


SE37 Abend:


The maximum number of extents would be exceeded.

For instance, when exceeding 16 extents of a PDS.

An E37 on tape datasets is most often caused when the number of requested

volumes is exceeded.

The default is 5, therefore a request for the sixth volume will fail with a E37.


(Contd.)


15/18


Allow time for questions from participants


16/18



Summary S0C1 - Operation Exception.

S0C4 - Protection Exception/Storage Violation.

S0C7 - Program Check Exception Data.

S122 - The job was canceled because it violated some restriction and dump was

requested.

S222 - The job was cancelled because it violated some restriction and No dump

was requested.

S322 - The job used more CPU time than it should have.

Either the estimate is wrong or the program is in an uncontrollable loop.

S806 - Load module not found.

SB37 - Insufficient disk space.


17/18



Source http://publib.boulder.ibm.com/infocenter

Disclaimer: Parts of the content of this course is based on the materials available from the

Web sites and books listed above. The materials that can be accessed from linked sites are

not maintained by Cognizant Academy and we are not responsible for the contents thereof.

All trademarks, service marks, and trade names in this course are the marks of the

respective owner(s).


18/18

You have successfully

completedProblem Solving- Abend

Handling

You have successfullyYou have successfully

completedcompletedProblem SolvingProblem Solving--AbendAbend

HandlingHandling

Documents

Day1 ProblemSolving-AbendsHandling v1[1].0