On Fri, 27 Aug 2021 01:05:18 +0100, CM Poncelet wrote:
>According to my OS/390 Collection March 1999 Version 2 Release 7.0:
>
>RENT: MVS *protects your module's virtual storage so that your module
>cannot be modified* - and REFR implies RENT.
>
Feels like a doc error. Submit an RCF.
Which
According to my OS/390 Collection March 1999 Version 2 Release 7.0:
RENT: MVS *protects your module's virtual storage so that your module
cannot be modified* - and REFR implies RENT.
See attached (this time without Unicode formatting .)
Cheers, Chris Poncelet (retired sysprog consultant)
According to my OS/390 Collection March 1999 Version 2 Release 7.0:
RENT: MVS *protects your module's virtual storage so that your module
cannot be modified* - and REFR implies RENT.
See attached.
Cheers, Chris Poncelet (retired sysprog consultant)
On 26/08/2021 04:54, Jim Mulder wrote:
>
And both solve the RLD problem, which MVCL does not.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent: Thursday, August 26, 2021 9:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LOAD with ADDR
On 8/26/2021
REFR precedes OS/VS. In OS/360 MVS with MCH, the REFR bit affected the handling
of machine checks. As I recall, the MCH could refresh transient SVC routines
and refreshable nucleus CSECTs. With OS/VS2 R1 (SVS), there were no more SVC
transient areas, but the MCH could still reload refreshable
Hi All,
Should one pursue AI and ML training keeping in mind that it might help MF
sysprogs/admins in future or will it just be a waste of time?Intention is
that it should help on the job like troubleshooting,smf analysis etc.
Are there any use cases or red papers or articles around it.
Thanks
On 8/26/2021 9:05 AM, Charles Mills wrote:
EXACTLY what CSVDYLPA does flawlessly.
LOAD with GLOBAL=YES also performs the same function flawlessly -- and
comes with the additional feature of automatic cleanup at termination
time (assuming that's the behavior you want).
--
Phoenix Software
On 8/26/2021 7:03 AM, Peter Relson wrote:
Regardless, if you are doing a LOAD with ADDR you don't typically do a
LOAD to get the length to obtain (or a CSVQUERY after a LOAD). That is
very inefficient. You use the information in the directory entry returned
by BLDL or DESERV.
I discovered some
EXACTLY what CSVDYLPA does flawlessly.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Joseph Reichman
Sent: Wednesday, August 25, 2021 7:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LOAD with ADDR
I need these programs
I figured someone would mention pre-LOAD vs. BLDL :) In my case the
efficiency didn't really matter. It was a one-time load as the STC
initialized things soon after IPL. Most likely I looked at LOAD vs.
BLDL where I had to code a build list and said "why bother when I can
LOAD to get the
Shmuel you are correct. If you code RENT the linkage editor also sets REUS, and
if you set REFR it does not set the others. However you can also independently
turn on or off REUS in the linkage editor. The binder enforces that only one
reusability attribute is set. (Interestingly the linkage
>LPA load modules are or should always be marked RF (REFR).
LPA modules are considered refreshable. There is no reason to mark them
so, but it will do no harm if you do.
IIRC The page(s) of an LMOD marked REFR can be stolen without having
first to back it up to cache, because it can be
Since the OP's goal was to have a copy available to all address spaces,
the best option is to use dynamic LPA (CSVDYLPA).
There are few, if any, reasons still to use LOAD with ADDR for common
storage. In neither CSVDYLPA nor LOAD with ADDR is it generally safe ever
to free the storage. And LOAD
On Wed, 25 Aug 2021 16:39:24 -0500, Bill Giannelli
wrote:
>how might I display or report how an alias is defined?
>I am trying to determine is a system symbol was used to create the alias and
>"resolve" the name i.e.
>
>ALIAS "*.RTE.LINK" points to "*.RTE2104.LINK"
>but I want to make sure it
Even the linkage editor had a hierarchy: nonreusable, serially reusable and
reentrant. The difference is that in the binder REFR is part of the hierarchy,
while in the linkage editor it is independent.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
REUS and REFR would give you the serialization if the binder treated it the
same as the linkage editor, but IMHO there are much better ways to serialize.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
On 8/26/2021 1:54 PM, Jim Mulder wrote:
The only exception to that is the PLPA and EPLPA
virtual storage ranges, for which the frame steal code does
steal without paging out, effectively treating everything in
those ranges as conceptually REFR for stealing purposes,
regardless of the load module
It’s was a PDSE I got the abend under TESTAUTH
I can get the source and the target address
Since I was at the starting points of my program and was loading my programs
One of them was my general recovery routine meaning I had not established
An recovery routine as yet, I just saw the message
To answer myself and Attila:
I don't fully understand the requirement for unique sysid, however I
found it in clear text in SCRT v18.1 manual. And I remember big
discussion with IBM about it. They even provided a tool to change sysid
before the records are read by SCRT reporting program.
19 matches
Mail list logo
