Ok - we are assuming that this is an LE problem. Let's not do that. If we 
assume we are looking at a plain old application program bug, we'd be right 
99.9% of the time, so let's do that.   

So, what is the most common causes of an 0C4? Storage overlay is at the top of 
my list. Take a look at any array processing and make sure that there are 
overrun stoppers. 

Also, take a hard look at all of the files. Did each open ok? Do the DCB's fit 
what the program is expecting (that is, is the program trying to read a 32k 
record into an 80 byte buffer?).  Did the program attempt to write to or read 
from closed file? Or perhaps read past the end of file?  

Back on the mixed version suspicion, try relinking the program and take a close 
look at the csect map. LE generally dynamically loads most all of the runtimes 
at runtime (vs static linking in olden days) so there shouldn't be much in the 
map.    

HTH and good luck
 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Charles Mills
Sent: Tuesday, January 31, 2012 4:17 PM
To: [email protected]
Subject: Re: S0C4 in CEE3DMP

Thanks. No change.

//STEPLIB  DD  DSN=my.load.library,DISP=SHR 
//         DD  DSN=CEE.SCEERUN,DISP=SHR              
//         DD  DSN=CEE.SCEERUN2,DISP=SHR             

Is there a way to tell the version of CEE.SCEERUN & RUN2?

BTW, I *should* be able to test on two other LPARs (which might reveal that the 
problem was somewhere outside my code) but an unrelated problem is stopping me 
for now. I have asked the powers that be to resolve it.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Staller, Allan
Sent: Tuesday, January 31, 2012 1:54 PM
To: [email protected]
Subject: Re: S0C4 in CEE3DMP

I would add the datasets CEE.SCEERUN and CEE.SCEERUN2 via steplib and see if 
your S0C4  goes away

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to