I did not mean to imply I thought there was any hardship, it's just a
curiosity. Virtually everything I write is non-modifying reentrant (and
therefore refreshable). But the system does load APF-authorized modules
marked RENT into key zero storage, making them at least more difficult
to modif
The system has not attempted to make RENT programs non-writeable. It has
only, in certain cases, attempted to make them non-writeable unless key 0.
I do not know about CICS' RENTPGM=PROTECT option, but I'd guess that it
does something similar, expanding which cases. But it could go further,
con
I have the same understanding. I've sometimes wondered why there was
never an explicit non-modifiable attribute. Especially since the system
tries in more than one way to take RENT or REFR to mean that.
RENT, REFR, and self-modification are completely independent attributes
(although some per
I have always understood that refreshable always meant that the
executable could be replaced by the copy from a load library at anytime,
which probably could be interpreted as between the execution of any two
instructions. I thought of reentrant as a considerably looser
definition, and presu
On 2016-02-17 10:38, Jim Mulder wrote:
>
> The administrator should be specifying REFRPROT in PROGxx.
> The only reason we made it an option was concern that an installation
> might have self-modifying programs which were incorrectly had the
> REFR attribute, and we didn't want that to be a mig
> > REFRPROT in PROGxx causes REFR load modules and program objects
> > to be loaded into key 0 storage, and the full 4K pages are page
> > protected. RSECT is not involved. I would expect that the
> > individual unprivileged programmer has control over whether he
> > specifies REFR when he bin
On 2016-02-16, at 22:38, Jim Mulder wrote:
>
> REFRPROT in PROGxx causes REFR load modules and program objects
> to be loaded into key 0 storage, and the full 4K pages are page
> protected. RSECT is not involved. I would expect that the
> individual unprivileged programmer has control over whe
> > Perhaps I'm forgetting something, but IIRC, as far as the binder and
z/OS
> > itself is concerned, RSECT matters only for CSECTs in IEANUCxx where
they
> > are put into the read-only nucleus. It is ignored for all other
> > situations.
> >
> Isn't there for several releases a REFRPROT opt
On 2016-02-16, at 07:17, Peter Relson wrote:
>
> Perhaps I'm forgetting something, but IIRC, as far as the binder and z/OS
> itself is concerned, RSECT matters only for CSECTs in IEANUCxx where they
> are put into the read-only nucleus. It is ignored for all other
> situations.
>
Isn't there
Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Peter Relson
Sent: Tuesday, February 16, 2016 16:18
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Using macro to set assembler option
>if the option is RENT, I define an RSECT, else CSECT.
I'm curious. Why? I
>if the option is RENT, I define an RSECT, else CSECT.
I'm curious. Why? If you're assembling with RENT, then what does RSECT
additionally buy you? RSECT can protect you against not assembling with
RENT, but that seems to be the flip side of what was stated.
Perhaps I'm forgetting something, bu
nd "SETOPT PARM(LET=4)" as the first
output, causing them to become input to the binder.
*PROCESS RENT
LNKREUS REFR
TEST1CSECT ,
Will punch " SETOPT PARM(REUS=REFR)".
*PROCESS NORENT
LNKREUS
TEST1CSECT ,
Will punch " SETOPT PARM(REUS=NONE)".
Subject: Using macro to set assembler option
I don't see how this might be possible, but no harm in asking. I am writing
a simple macro which can be used to insert an appropriate SETOPT line to set
the link/bind REUS attribute:
MACRO ,
&LABEL REUS &REUSOPT
AIF (
I'm afraid you're snookered as far as specifying the RENT option
dynamically. The ACONTROL statement, which can modify some of the
assembler options, does not include a way to set RENT on or off.
I see not reason why this should be so, particularly since the RSECT
instruction does just that,
I don't see how this might be possible, but no harm in asking. I am writing a
simple macro which can be used to insert an appropriate SETOPT line to set the
link/bind REUS attribute:
MACRO ,
&LABEL REUS &REUSOPT
AIF ('&REUSOPT' EQ 'RENT').OPTRENT
AIF ('&REUSOPT
15 matches
Mail list logo
