Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-20 Thread Shmuel Metz (Seymour J.)
In , on 01/20/2015 at 08:29 AM, Peter Relson said: >I don't know of any reentrant code in the BCP in assembler or >(internal) PL/X for which static does not happen to equate to >constant-after-load. While some nonreshaable reentrant code ib OS/360 survived into MVS, my understanding is that

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-20 Thread Peter Relson
>If now with new releases of the >OpSys, all modules linked as RENT will be read only, I'm not sure where that thought came from. The operating system rule has been in place for way longer than I have. In general, reentrant modules from APF-authorized concatenations are placed into key 0 storage

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread Paul Gilmartin
On Mon, 19 Jan 2015 16:18:37 +0100, Bernd Oppolzer wrote: > >even a program that is linked as RENT may in certain circumstances >need to store some information in static storage. Think of a routine >that is >establishing a cache memory for a table access that is valid for ALL >parallel >running thr

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread John McKown
On Mon, Jan 19, 2015 at 9:18 AM, Bernd Oppolzer wrote: > Am 19.01.2015 um 13:32 schrieb Peter Relson: > >> Even a non-authorized program which is linked RENT >>> can write into its STATIC CSECT. >>> >> But only if the program is not fetched from an APF-authorized >> concatenation (and maybe that'

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread Bernd Oppolzer
Am 19.01.2015 um 13:32 schrieb Peter Relson: Even a non-authorized program which is linked RENT can write into its STATIC CSECT. But only if the program is not fetched from an APF-authorized concatenation (and maybe that's a requirement for PL/I programs with this characteristic). In that case,

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread John McKown
On Mon, Jan 19, 2015 at 6:58 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 19 Jan 2015 06:40:30 -0600, John McKown wrote: > > >On Mon, Jan 19, 2015 at 6:32 AM, Peter Relson wrote: > > > >> >Even a non-authorized program which is linked RENT > >> >can write i

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread Paul Gilmartin
On Mon, 19 Jan 2015 06:40:30 -0600, John McKown wrote: >On Mon, Jan 19, 2015 at 6:32 AM, Peter Relson wrote: > >> >Even a non-authorized program which is linked RENT >> >can write into its STATIC CSECT. >> >> But only if the program is not fetched from an APF-authorized >> concatenation ... >> >​A

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread John McKown
On Mon, Jan 19, 2015 at 6:32 AM, Peter Relson wrote: > >Even a non-authorized program which is linked RENT > >can write into its STATIC CSECT. > > But only if the program is not fetched from an APF-authorized > concatenation (and maybe that's a requirement for PL/I programs with this > characteri

Re: PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-19 Thread Peter Relson
>Even a non-authorized program which is linked RENT >can write into its STATIC CSECT. But only if the program is not fetched from an APF-authorized concatenation (and maybe that's a requirement for PL/I programs with this characteristic). In that case, the program can write into the program it

PL/1 modules linked RENT, compiled NORENT (was: Re: abend S602-0 when in AMODE 64)

2015-01-18 Thread Bernd Oppolzer
Am 18.01.2015 um 17:19 schrieb Peter Relson: Storage for static variables, i.e. variables declared with the STATIC keyword, is "allocated" in the so called static CSECT that becomes part of the object module. Note that this *is* read/write storage, so in PL/I STATIC does not mean constant. If it