On Mon, 8 Feb 2021 03:12:25 +, CM Poncelet wrote:
>
>Never heard of REFRPROT or how it differs from REFR. Perhaps it's after I
>retired (7+ years ago)
>
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieae200/progref.htm
-- gil
>From Michael Stein's excellent summary of REFR:
refreshable:
all or part of the module can be replaced at any time without notice
by the operating system. *therefore* must not modify itself in
any way.
Never heard of REFRPROT or how it differs from REFR. Perhaps it's after I
This is refreshable, and even runs on S/360
L R15,PTR
LTR R15,R15
BNZ CALLIT
......Code that always
leaves the same value in R15
STR15,PTR
CALLIT BALR R14,R15
...
PTR DCA(0)
If it were me I'd ask IBM to set what they considered the most reasonable
precedence and document it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin
If REFRPROT is not specified then a refreshable module can modify itself. Don't
do it at home.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of CM
Poncelet
W dniu 07.02.2021 o 19:34, Arye Shemer pisze:
Installation I work with is going to move Coupling Facilities and z/OS
LPARs to new hardware.
To best of my recollections after defining the IODFs for the new systems
(z15)
which should (could) include definitions for old and new systems.system
Of course. I have never suggested that it was *reasonable* to ENQ/DEQ or
otherwise serialize code in a RENT module, but only that it was
*possible* to do so without compromising an LMOD's RENT attribute.
Likewise, when I said a REFR LMOD could be "swapped out", I meant its
page(s) could be
doesn’t matter, by the time the code reaches the branch to address, address is
a value that will work.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Paul Gilmartin
> Sent: Sunday, February 07, 2021 2:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LINK vs
On Sun, 7 Feb 2021 17:53:28 +, Seymour J Metz wrote:
>... IMHO a warn option would be highly desirable.
>Why JOB instead of EXEC?
>
Good suggestion. How about both; but which dominates?
>
>From: Paul Gilmartin
>Sent: Sunday, February 7, 2021 12:46
On Sun, 7 Feb 2021 21:32:36 +0200, Binyamin Dissen wrote:
>On Sun, 7 Feb 2021 19:04:16 + "Gibney, Dave" wrote:
>...
>:>Classic "bad" code
>:>IF address = 0
>:>Determine and store address
>:>End-if
>:>Branch to address
>
Beware TOCTTOU!
>I guess you can add the case where the value
On Sun, 7 Feb 2021 19:04:16 + "Gibney, Dave" wrote:
:>REFR means reloadable without changing function or behavior
:>RENT means multiple users without changing function or behavior,
:>Classic "bad" code
:>IF address = 0
:>Determine and store address
:>End-if
:>Branch to address
:>When
Dear Folks,
I just put up an old tape mapping program named PRECIS from "UNC",
which I presume is the University of North Carolina. The load module
was linkedited in 1986, so it is old. But it works beautifully, the
report is concise, and it displays the beginning of each data block,
You will need to define new cf's along with the existing ones in the cfrm
policy and activate it before you move.
From: IBM Mainframe Discussion List on behalf of
Arye Shemer
Sent: Sunday, February 7, 2021 1:34:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
REFR means reloadable without changing function or behavior
RENT means multiple users without changing function or behavior,
Classic "bad" code
IF address = 0
Determine and store address
End-if
Branch to address
When refreshed, the address has to be redetermined, but program still works
And,
Assuming that your active CFRM policy allows structure movement from the old CF
LPAR(s) to the new, then yes.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Sun, 7 Feb 2021 16:52:55 + Seymour J Metz wrote:
:>Second, you can write code that is reentrant and refreshable, modifies itself
...
Only possible if it modifies itself but pays no attention to the modified
area.
Not really relevant.
--
Binyamin Dissen
Installation I work with is going to move Coupling Facilities and z/OS
LPARs to new hardware.
To best of my recollections after defining the IODFs for the new systems
(z15)
which should (could) include definitions for old and new systems.system
programmers can rely on system commands to remove CF
No, but IMHO a warn option would be highly desirable.
Why JOB instead of EXEC?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin
On Sun, 7 Feb 2021 16:52:55 +, Seymour J Metz wrote:
>..., I suspect that at some point REFRPR"OT will be mandatory.
>
The effect of REFRPROT has long been enforced for modules loaded
from APF libraries. IBM suspects that there are so many dusty-deck
modules incorrectly marked REFR in
It's a bit more complicated. First, you can decouple REFR from RENT by using
the linkage editor. Second, you can write code that is reentrant and
refreshable, modifies itself and does not use ENQ/DEQ. However, I suspect that
at some point REFRPR"OT will be mandatory.
BTW, just because it is
It is possible to write a module that is refreshable but not read only.
However, it will fail once you turn on REFRPROT, and is bad form even if you
don't.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
21 matches
Mail list logo
