MVSFORUMS.com

radair · Beginner Joined: 05 Oct 2006 Posts: 1 Topics: 1

I am receiving an OC4, reason 11 at program termination - the active load module name is IGZCPCO. I have displays in the application that show that I have finished all application processing. I believe it is running in an LE/370 runtime environment - it's Cobol/DB2 and has a dynamic call.
Any ideas?
Thanks
Newbie

kolusu · Posted: Thu Oct 05, 2006 5:09 pm Post subject:

radair,

Add the following line as the first line in your pgm (before ID division)

coolman · Posted: Mon Oct 16, 2006 11:41 am Post subject:

Kolusu,

How did you find out it was an array overflow?

The manual says this ...

coolman · Posted: Wed Oct 18, 2006 2:35 pm Post subject:

Kolusu,

Can you please let us know. Thanks.
________
head shop

kolusu · Posted: Wed Oct 18, 2006 2:53 pm Post subject:

Coolman,

It is a known error. A pgm compiled with NOSSRANGE will have this problem. Check this link

http://www.mvsforums.com/helpboards/viewtopic.php?t=4417&highlight=ssrange

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

coolman · Posted: Wed Oct 18, 2006 4:38 pm Post subject:

True - I agree that NOSSR is a known problem - But as you might know, there might be other problems too. I was wondering how your directly zeroed in on this one w/o getting any details.

Maybe, the below line helped you reach the conclusion

dtf · Posted: Thu Oct 19, 2006 12:06 pm Post subject:

In my opinion, this is an educated guess, and as such a good thing to try. It is quite possible that there is another issue causing your S0C4 abend. Perhaps though, from the information you provided, Kolusa was able to research the problem, and provide the correct answer.

The fact that the you appear to have run all the way through your program and are abending on termination, is a clue that an address needed to properly shut the program down has been destroyed. This could be in the chain called the SAVE AREA, or perhaps in some file area.

A subscript out of bounds can cause various types of abends, and even worse, and be intermitant. It is quite possible that you could have a progam get a S0C4 on one run, a S0C7 on another run, and appear to run clean on yet another run.

This is because a subscript/index out of bounds leads to data and or program instructions being overlaid. If the data overlaid is an address, that is later used, this could cause a S0C4, or if you run way out of bounds on a table so much so that you run into storage that is not yours, you could get a S0C4. If you overlay numeric data and then reference it, you could get a S0C7. If you whack instructions and then try to execute them, you could get a S0C1, or another abend that I can't remeber right now, where the system things you are trying to execute a privialged instruction.
________
Suzuki MR Wagon history