If the server creates a system LX, how does the client locate it? Of those 
ways, which is easiest?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Peter Relson [rel...@us.ibm.com]
Sent: Monday, July 20, 2020 7:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Using AN EAX value of PC Routineto index into the Authority Table

<snip>
If the AS2 has the capability of switching to supervisor state; why can't
it (AS2) create
its own Cross Memory environment allowing Address Space (AS1) the ability
to issue a PC to AS2 and the PC Service Routine use AR Mode to transfer
data from the Target Address Space (AS2) to the Accessing Address Space
(AS1) ?
</snip>

That's exactly what it can do and does do. For a space-switch PC when the
new SASN is set to the old PASN, the target routine can use MVCS or a move
with ALET=1 to move data to the secondary space.

What in the book contradicts this?

By the way, I disagree with Shmuel about "The easy way is to be a
subsystem".   The client needs to know what PC to issue. This does not
require a subsystem in order to "know". When the LX is not a system LX,
the client will need to connect to the server's LX.  That in and of itself
requires authorization, sometimes/often provided by the server having
defined a system LX for that purpose.

<snip>
Are You saying that each accessing address space would provide a unique
EAX.
<snip>
Definitely not. An "accessing address space" does not "provide" an EAX.
That is not how EAX's are used.

Peter Relson
z/OS Core Technology Design


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to