Got S0C4, but program runnning successfully, Why?

kalyanp_80 · New User Joined: 03 Feb 2006 Posts: 41 Location: Hyderabad

Hi,

Job is abending with S0C4 in the production. I tried to replicate the issue in test and could replicate the same error.
But when I retrived the program causing S0C4 into test and recompile it (no changes made) and run the job its running successfully.
My question is why is that job running successfully when I recompile the program?

Thanks
Amith

akbar_mohammed · New User Joined: 16 May 2007 Posts: 1 Location: Hyd

WERE THE FILES USED IN BOTH THE CASES I.E., PRODUCTION AND TESTING THE SAME AND ALSO DOES THIS PROGRAM USES ANY DATA BASE.

William Thompson · Posted: Mon May 21, 2007 7:10 pm

Look at the failing program's link map....you may find a called module missing.....

dick scherrer · Posted: Tue May 22, 2007 4:01 am

Hello,

Does the program have an internal sort?

If it does, a possible cause is that the production run is issuing a "goback" or "stop run" before the sort is finished.

shagnwrx · Posted: Wed May 23, 2007 1:06 am

So program was executed, and you got a S0C4. You re-compiled program and all worked fine?

If this is the case, my guess is that somebody goofed on the first compile regarding AMODE and RMODE.

When you recompiled, did you happen to catch those attributes? Sounds like a 24 bit program got linked to above the line for the first run.