Strange LE / link list behaviour

>We're in the process of upgrading to Enterprise COBOL 5.1 and one of our=20 >development groups has decided to re-compile all their COBOL modules even=20 >though it is not deemed necessary - that's their prerogative.=20 I think it is an excellent idea to recompile all of an application and test

Re: Strange LE / link list behaviour

blin 4, Ireland. From: Ken MacKenzie To: IBM-MAIN@LISTSERV.UA.EDU, Date: 27/02/2015 09:28 Subject: Strange LE / link list behaviour Sent by:IBM Mainframe Discussion List Hi all, We're in the process of upgrading to Enterprise COBOL 5.1 and one of our developmen

Re: Strange LE / link list behaviour

At 09:07 -0800 on 02/27/2015, Sri h Kolusu wrote about Re: Strange LE / link list behaviour: Ken, My guess would be that your Linklist might have LE modules from an older release where as your JOBLIB/STEPLIB libraries might have the latest LE modules. Something similar to this scenario

Re: Strange LE / link list behaviour

In , on 03/01/2015 at 10:40 AM, Peter Relson said: >My guess is that >-- the module claims to be reentrant, but isn't (and yes I know that >it is conceivable to have a reentrant module that stores into >itself, but the rules don't care about that) Are you talking about the Linkage Editor

Re: Strange LE / link list behaviour

The rules about which subpool to place a reentrant module depend on APF authorization. My guess is that -- the module claims to be reentrant, but isn't (and yes I know that it is conceivable to have a reentrant module that stores into itself, but the rules don't care about that) -- when run o

Re: Strange LE / link list behaviour

Are they concatenation with non-apf Libs in the step lib? On Friday, February 27, 2015, Ken MacKenzie wrote: > 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 deeme

Re: Strange LE / link list behaviour

:Re: Strange LE / link list behaviour Sent by:IBM Mainframe Discussion List Ken, My guess would be that your Linklist might have LE modules from an older release where as your JOBLIB/STEPLIB libraries might have the latest LE modules. Something similar to this scenario. http

Re: Strange LE / link list behaviour

In , on 02/27/2015 at 09:27 AM, Ken MacKenzie said: >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 - S0C4 - what? The

Re: Strange LE / link list behaviour

List wrote on 02/27/2015 01:27:54 AM: > From: Ken MacKenzie > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 02/27/2015 01:29 AM > Subject: Strange LE / link list behaviour > Sent by: IBM Mainframe Discussion List > > Hi all, > > We're in the process of upgrading to Ent

Re: Strange LE / link list behaviour

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Friday, February 27, 2015 5:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Strange LE / link list behaviour > > I would open an SR wit

Re: Strange LE / link list behaviour

n List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Ken MacKenzie > Sent: Friday, February 27, 2015 2:28 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Strange LE / link list behaviour > > Hi all, > > We're in the process of upgrading to Enterprise COBOL 5.1 and

Re: Strange LE / link list behaviour

My best guess is that the LE module when loaded into storage from an APF authorized library is loaded into a store protected subpool, and the program is attempting to alter the LE load module in error. What flavor of 0C4 are you getting? Mark Jacobs Ken MacKenzie

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 LPA