Consider the following : CLIENT ASID = 00A0 SERVER ASID = 00A1 OTHER SERVER ASID = 00A2 (ISV or IBM software)
When PC-ss called by normal HOME ASID from H=P=S environment, the contents afterwards will be : HASN= 00A0 PASN = 00A1 SASN = 00A0 H=S<>P More complicated environment when your client has already PC-ss to the other server ASID and *it* invokes your PC-ss : Stage 1 : Connect to other server : HASN = 00A0 PASN = 00A2 SASB = 00A0 H=S<>P Stage 2 : And then server invokes your PC-ss : HASN = 00A0 PASN= 00A1 SASN = 00A2 (notice !) H<>S<>P I am not a DB2 person, so I cannot confirm that when you are called from DB2 then your HASN is the client ASID that you require - you need to verify this as stated earlier. Rob Scott Lead Developer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Phil Smith Sent: 25 June 2014 16:59 To: [email protected] Subject: Re: Address space puzzle Binyamin Dissen wrote: >The ASID of Home is found via PSAAOLD. But MVS creates an ALET 2 on the >PASN DU-AL to refer to home. No need to build another. >Note that > LA R1,2 Secondary space address number >really is using the ALET for HOME. In a simple PC-SS SASID=HOME. OK, is this a "simple" PC-SS? With DB2 involved? What does "simple" mean in this context? Not challenging you, just trying to grok! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
