s0c4 abend

2
Solving a S0C4 Abend STEP1. First Check the SYSOUT of CA-VIEW whether any thing regarding the bad record is dis!aying" #$ost cases it wi!! dis!ay the %ecord &ey 'a!(e in the Syso If this infor)ation is not fo(nd we can roceed as er STE*+ If the key 'a!(e is dis!aying go to the artic(!ar fi!e an this artic(!ar record" Check a!! the 'a!(es of that artic(!ar records whether a!! 'a!(es are as er 'ariab!es defined in fi!e str(ct(re" Take a backup of the Original file. Stri of the record fro) the fi!e and res(b)it the .C/ as e )odification !og" STEP2. /ook at the 0U$* and trace o(t the state)ent dis!ace)ent wh Abend is occ(rring"#A00%ESS122332C24 OFFSET1222225E6, %eco)i!e the *rogra) and check the dis!ace)ent in the rogra) there we can find o(t the e7act !ocation of the ro Search for these 'a!(es in the co)i!e /istings There we ca the osition where the abend has occ(rred" Check the 'a!(es there for the fi!e 'ariab!es fro) the rogr where it is abending and trace o(t the record fro) the fi!e E"F"3" Stri off the records fro) the fi!e (sing E"F"+ " by se!ecti artic(!ar records by gi'ing Se!ection criteria (sage 1118 T *ress 9E:TE%8

Upload: rammurthy

Post on 05-Nov-2015

10 views

Category:

Documents


0 download

DESCRIPTION

S0C4 Abend Resolution Easy steps to resolve it

TRANSCRIPT

Solving a S0C4 Abend

Solving a S0C4 Abend

STEP1.

First Check the SYSOUT of CA-VIEW whether any thing regarding the bad record is displaying.

(Most cases it will display the Record Key value in the Sysout.

If this information is not found we can proceed as per STEP2)If the key value is displaying, go to the particular file and check this particular record.

Check all the values of that particular records whether all the values are as per variables defined in file structure.

Take a backup of the Original file.

Strip of the record from the file and resubmit the JCL as per the modification log.

STEP2.

Look at the DUMP and trace out the statement displacement where Abend is occurring.(ADDRESS=00110C08 OFFSET=00000BE6)

Recompile the Program and check the displacement in the program, there we can find out the exact location of the problem.

Search for these values in the compile Listings, There we can find the position where the abend has occurred.

Check the values there for the file variables from the program logic where it is abending and trace out the record from the file using E.F.1.

Strip off the records from the file using E.F.2 . by selecting these particular records by giving

Selection criteria usage ===> TPress

Now select 1 and give the key value in

Starting record key ===> key value Strip off the record from the file.

STEP3.

Recompile the program again with display statements for the record count after reading the file.

Display Count = working-storage Counter.

Resubmit the JCL in test region and check the number of records read.

Locate that particular record using File-Aid.

Check this particular record, check the variables whether it is as per the variables defined in the file-structure.

Take a backup of the file containing bad record(s).

Strip off the records that are creating the problem.

(If all the records with record type 2 are bad records then Strip off all the TYPE 2 records and the corresponding TYPE 1 record

also.

If only one Type 2 is bad record then Strip that particular record with Type 2.)

Resubmit the job as per the modification log.

Note: Before stripping you have to take a backup of the particular file.