IBM Mainframe Forum

A jobs daily runs fine in prodution.
But for last two days ...its abending with S0c4 error. Sysdump is pasted below.
Job failed . No problems .... we know that its S0c4 and we were working on it.
now just to know for which record job is failing, we moved each record to spool(using sysout) and to our surprise the job ran fine. Couldn't believe.
We could understand what happened ...!!!! we thought a simple re-run whould have solved the problem.
Now on the next day ... the job failed again ... this time we decided to re-run(expected to run fine) .. but the job again abended with S0C4.
To resolve the issue we again used the previous method i.e moving all the records to spool using sysout.
And the job ran fine.

Has any body any idea ..what has happend ???????
Please let me know if you need any more information.

This is what i found in the sysdump
OB22989 IEA995I SYMPTOM DUMP OUTPUT 367
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011
TIME=05.53.22 SEQ=50343 CPU=0000 ASID=0313
PSW AT TIME OF ERROR 078D1800 00036966 ILC 6 INTC 11
ACTIVE LOAD MODULE ADDRESS=0001D000 OFFSET=000
NAME=SELCOPY
DATA AT PSW 00036960 - 30144780 D4D4D502 30703071
AR/GR 0: 80C9F890/00000005 1: 00000000/00000000
2: 00000000/8803692E 3: 00000000/60071FA0
4: 00000000/00039940 5: 00000000/00037500
6: 00000000/00038C14 7: 00000000/00000000
8: 00000000/40D5D6D7 9: 00000000/00037668
A: 00000000/00038DA0 B: 00000000/0000005A
C: 00000000/0001D000 D: 00000000/00036500
E: 00000000/580376BA F: 00000000/00033400
END OF SYMPTOM DUMP

For intermittent abends, the problem may be storage alignment. One possibility is a work area, table or DSECT definition shorter than the data being accessed. Depending on the program's mapping into storage, the bytes beyond the work area are sometimes still within the boundary and sometimes not (S0C4).

Thanks Bill.
I have the same understanding of a S0C4 error.
My programs( its a selcopy ) splits the input file in to 5 files doing some formatting and nothing more.
When the job failed , we ran the job again by changing the job to split into 6 parts by adding one more fileout6(//FILE6OUT DD SYSOUT=* ) in the JCL and changed the selcopy to copy every record to write in sixth partion.

After this job ran fine.
I am not able to relate the S0C4 defination given by you to my problem.
Thanks anyways.

Can some one help ...!!!

Hello ashu,

Can some one help ...!!!

Probably not from the info posted so far - we have nothing to work with.

I do not understand this:

we moved each record to spool(using sysout)

If you are using some 3rd-part utility (selcopy?), you might contact their support and ask if this is a known problem.

Do you have a SYSUDUMP? Post the next few lines starting at address 00071FE0

Selcopy is a batch language ? If the problem is in SELCOPY then why the job is running fine after sometime. ?
I think this is a evvironment related problem !!!
If anyone has any idea about the relation between S0c4 and environment , please reply . Thank you .

Sysdump from the lastest failue.
IEA995I SYMPTOM DUMP OUTPUT 909
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011
TIME=03.03.48 SEQ=16374 CPU=0000 ASID=00F2
PSW AT TIME OF ERROR 078D1800 00036966 ILC 6 INTC 11
ACTIVE LOAD MODULE ADDRESS=0001D000 OFFSET=00019966
NAME=SELCOPY
DATA AT PSW 00036960 - 30144780 D4D4D502 30703071
AR/GR 0: 80C9F890/00000005 1: 00000000/00000000
2: 00000000/8803692E 3: 00000000/60071FA0
4: 00000000/00039940 5: 00000000/00037500
6: 00000000/00038C14 7: 00000000/00000000
8: 00000000/40D5D6D7 9: 00000000/00037668
A: 00000000/00038DA0 B: 00000000/0000005A
C: 00000000/0001D000 D: 00000000/00036500
E: 00000000/580376BA F: 00000000/00033400
END OF SYMPTOM DUMP

IEF450I SM205DLP STEP0010 - ABEND=S0C4 U0000 REASON=00000011 910
TIME=03.04.03
IEF234E K 5567,W30801,PVT,SM205DLP,STEP0010
-SM205DLP STEP0010 *S0C4 1683 .02 .00 .33 238K 0 0
-SM205DLP STEP0015 FLUSH 0 .00 .00 .00 0 0 0
IEF404I SM205DLP - ENDED - TIME=03.04.04

Bill Dennis wrote:Do you have a SYSUDUMP? Post the next few lines starting at address 00071FE0

Help me to help you!

Hello,

Sysdump from the lastest failue.

Sorry, but that is not the requested SYSUDUMP.

Please post any messages of any kind in any of the sysout= datasets from an abended run. Also, please post the jeslog info (the first dataset in the spooled output).

You mention that it fails one day and runs correctly another. Once it fails, will it fail repeatedly with the exact same input data and jcl?

Is this selcopy from some vendor or is it something written at your organization?

Hi,

I have some experience working on SELCOPY. If you can provide the selcopy code, i can help you...