OK, if I don't need an ATSET for a non-system LX, why did my PC crash
with a S0C2? Do I not want to AXRES/AXSET in my server if I use a system
LX?
Here is my XMS setup from the service:
----------------------------------------------------
GETAX AXRES AXLIST=AXL,RELATED=FREEAX
GETAXV AXSET AX=AXVALUE,RELATED=(GETAX,SETAX)
MVC LXCOUNT,=F'1'
GETLX LXRES LXLIST=LXL,RELATED=FREELX
L 5,PCRTNADR
LH 6,AXVALUE
ETDEF TYPE=SET,ETEADR=ETD1,ROUTINE=(5),EAX=(6),AKM=(0:15), X
SSWITCH=YES,STATE=SUPERVISOR,EKM=(0:15),PKM=OR, X
ASCMODE=AR
CET1 ETCRE ENTRIES=ETDESC
ST 0,TKVALUE
MODESET MODE=PROB
EDCEPIL
ETDESC ETDEF TYPE=INITIAL,RELATED=(CET1)
ETD1 ETDEF TYPE=ENTRY,ROUTINE=0,SSWITCH=YES,STATE=SUPERVISOR, X
EKM=(0:15),PKM=OR,AKM=(0:15),ASCMODE=AR
ETDEF TYPE=FINAL
LTORG
----------------------------------------------------
To run my system LX test, I added SYSTEM=YES on my LXRES, then removed
the call to my SVC routine in my client. My client would then simply
pick up the LX value and PC to it in problem state.
David Logan
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Binyamin Dissen
Sent: Monday, December 17, 2007 6:26 AM
To: [email protected]
Subject: Re: Basic Cross Memory questions
On Mon, 17 Dec 2007 08:19:07 -0500 "Logan, David" <[EMAIL PROTECTED]>
wrote:
:>I believe I understand the ETDEF options. Took me a bit, because the
:>authorization and execution key parameters are a bit complicated.
Why not show what you specified?
:>But this fact remains: " The client only needs to issue an ATSET,
which
:>does require authorization." -- and as long as this is true, I need an
:>SVC, since this seems to be the best way to get my client connected to
:>my server.
The ATSET only has to be issued for a non-system LX.
:>If there is a better way than an SVC, I would love to hear about it.
No need for one.
:>Also, this means that there is no reason whatsoever to use a system
LX,
:>since I need to be in supervisor state anyway for the ATSET. I might
as
:>well go ahead after that and connect my LX/entry table at the same
time.
:>There is no way to get around the supervisor state requirement for
:>client (i.e. problem program) setup.
You do not have to issue a ATSET for a system linkage index.
--
Binyamin Dissen <[EMAIL PROTECTED]>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.
I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
