How true!
For whatever reason, it reminded me of a time I wrote the LLGT instruction on a
coworker's grease board. He apparently thought I was making some sort of
political/social statement and abruptly terminated the conversation!?
From: IBM Mainframe
.you're reading some British crime fiction that includes a Detective Sergeant
named O'Halloran, and every time there's a reference to
DS O'Halloran
you find yourself looking for the quote to close the literal!
Seems like LDAEPVTS Starting Extended boundary and Adding LDAESIZA (size)
encompasses bot USER and System Private Area
While it seems like the 24 bit User and System Private Area are Segregated
LDASTRTS Is the beginning of User 24 bit private area LDASIZS is the size Of
user 24 bit area
I want to identify an Address I know ultimately I can do a VSMLIST (that would
give me allocated and unallocated as well ) But it seems like Every other type
of Address type Nucleus, CSA. SQA, Private, LPA is identified besides LSQA
thanks
-Original Message-
From: IBM Mainframe
On 2019-05-27 08:26, Joseph Reichman wrote:
Hi
From the CVT I can get M,F,L Extended LPA Start and Ending Storage Ranges
and I can also get Nucleus Extended Read Only and Read Write Starting and
ending Ranges
From the LDA I can get Private / Extended Starting and Ending Private
Hi
>From the CVT I can get M,F,L Extended LPA Start and Ending Storage Ranges
and I can also get Nucleus Extended Read Only and Read Write Starting and
ending Ranges
>From the LDA I can get Private / Extended Starting and Ending Private Ranges
>From the GDA I can get SQA and CSA /
