SSWITCH=NO means you put your system LX PC routine into common storage? LPA or LOAD GLOBAL=YES? Having the system LX validate the client and set up the non-system LX makes sense.
You also implied the answer to my question about not having an AXRES/ATSET for a system LX. David Logan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rob Scott Sent: Monday, December 17, 2007 7:02 AM To: [email protected] Subject: Re: Basic Cross Memory questions David, Believe me this is possible as I use it for my products : (o) APF-auth server code issues LXRES, ETDEF, ETCRE and ETCON for a System-LX (o) APF-auth server code also builds one or more non-system LXs for other PC routines (o) The system-LX PC routine's only function is to validate client authority to the product (RACROUTE) and connect/disconnect the client (ATSET and ETCON/ETDIS) to the non-system LX (the code that is the "meat" of the product). Here is the definition for the system-LX : ETDEF TYPE=SET,ETEADR=ETTBSYS1, ROUTINE=(R7), ARR=(R9), PC=STACKING, ASCMODE=PRIMARY, SSWITCH=NO, SASN=OLD, STATE=SUPERVISOR, RAMODE=31, AKM=(0:15), EK=(0) ETCRE ENTRIES=ETTBSYS Create the Entry Table STCM R0,B'1111',TKVALUE MVC TKCOUNT,=F'1' Set # ET tokens ETCON LXLIST=LXL, Connect LX to Entry Table TKLIST=TKL, MF=(E,ETCONL) Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Logan, David Sent: 17 December 2007 13:19 To: [email protected] Subject: Re: Basic Cross Memory questions I believe I understand the ETDEF options. Took me a bit, because the authorization and execution key parameters are a bit complicated. 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. If there is a better way than an SVC, I would love to hear about it. 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. David Logan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Binyamin Dissen Sent: Monday, December 17, 2007 6:10 AM To: [email protected] Subject: Re: Basic Cross Memory questions On Mon, 17 Dec 2007 07:51:56 -0500 "Logan, David" <[EMAIL PROTECTED]> wrote: :>Apologies, you are right...I was writing from memory, and :>mis-remembered. The client needs an AXSET and an ETCON. The only way to :>issues AXSET and ETCON seems to be in supervisor state. The only way for :>a problem program to gain access to supervisor state code seems to be :>via an SVC. The client only needs to issue an ATSET, which does require authorization. :>I tried using a system LX, and removed the above setup. I get a S0C2 in :>the client. This indicates to me that even WITH a system LX, I still :>need an SVC to issue the ATSET and the ETCON. Depends on how you define the PC. It can be defined as requiring supervisor state/system key, or acceptable in problem state. It can be defined as switching to supervisor state, or staying in problem state. Look carefully at the ETDEF operands. -- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
