The other option is to change TERMTHDACT to a more robust process.  If you
have MSG you may wish to change it to UATRACE, DUMP and UADUMP or similar
function.  You can do that for just the one job by coding CEEOPTS in the
JCL.

Example:
//CEEOPTS DD *
ALL31(OFF),STACK(,,BELOW)



Lizette
 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Lizette Koehler
> Sent: Friday, February 27, 2015 5:57 AM
> To: [email protected]
> Subject: Re: Strange LE / link list behaviour
> 
> I would open an SR with IBM on this issue.  LE Typically captures abends
and
> then reproduces them later.  There might be a different abend occurring
that
> you might only see in an SVC Dump with IPCS and LEDATA analysis.
> 
> Lizette
> 
> 
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:IBM-
> [email protected]]
> > On Behalf Of Ken MacKenzie
> > Sent: Friday, February 27, 2015 2:28 AM
> > To: [email protected]
> > Subject: Strange LE / link list behaviour
> >
> > Hi all,
> >
> > We're in the process of upgrading to Enterprise COBOL 5.1 and one of
> > our development groups has decided to re-compile all their COBOL
> > modules even though it is not deemed necessary - that's their
prerogative.
> >
> > One of their programs is exhibiting strange behaviour on the
> > development LPAR that I have been unable to replicate on our sandbox
> system.
> >
> > If they code the LE libraries SCEERUN and SCEERUN2 in their JOBLIB
> > statement, their program runs OK.  However, if they allow the LE
> > libraries
> to
> > come from link list (as they should) their program abends with S0C4 -
> > the address of the offending instruction is way outside of the module
> > reported
> in
> > the dump - probably a wild branch, I guess.
> >
> > Has anyone encountered anything similar?  Why should coding LE
> > libraries
> in
> > your JOBLIB (the same with STEPLIB, incidentally) cause a module to
> > work when it doesn't work from link list?
> >
> > Any helpful suggestions welcomed.
> >
> >
> > Ken MacKenzie
> 

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

Reply via email to