In a PC-ss environment, you can access data in the following address spaces 
using special ALET values :

PRIMARY (PASN/PASID):   Binary fullword value 0 (as normal)
SECONDARY (SASN/SASID):         Binary fullword value 1 
HOME (HASN/HASID):              Binary fullword value 2 

To access data in the HOME address space, you need to load x'00000002' into 
your access register(s) that you are using to traverse control blocks in the 
HOME address space.

Be careful to ensure that you always use correctly primed AR when accessing 
storage in either HOME or SECONDARY - it is *VERY* easy to overlook and end up 
with misleading address pointers or bad data.

For example, you cannot use TCBSENV pointers in the SASN to access the ACEE in 
the HASN.

I would be surprised if RACROUTE did not support x'00000001' or x'00000002' as 
valid values in ACEEALET - therefore I am guessing that the ACEE pointer that 
you have is incorrect.

There is nothing like a SVCDUMP or SNAP at the time prior to RACROUTE to help 
know for sure - I assume this is a development/test LPAR. 

Rob Scott
Lead Developer
Rocket Software
77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA
Tel: +1.781.684.2305
Email: rsc...@rs.com
Web: www.rocketsoftware.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Phil Smith
Sent: 25 June 2014 16:33
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Address space puzzle

Rob Scott wrote:
>I am guessing that this is down to the difference between HASID and SASID in 
>your two quoted environments.

That's been my suspicion too, though it hasn't gotten me very far!

>When your PC-ss code is working OK, HASID  and SASID both are the same value 
>(with PASID being your server address space - ie H=S<>P), however if your 
>PC-ss can be invoked from an environment where there has already been a PC-ss 
>issued by another software product, the HASID and SASID could be different 
>(H<>S<>P).

>Your client ACEE will be the in HASID storage - so you will have to retrieve 
>it from there instead of the SASID.

So how do I get the HASID? That's what I've been unable to figure out!

>One further point, as you already have a valid cross-memory bind between your 
>client and your server by the nature of the PC-ss, why are you attempting to 
>perform an extra ALESERV add for the client address space? Have you tried 
>using the special ALET value of "2" (for HOME) in the RACROUTE FASTAUTH 
>ACEEALET parameter?

I had not, but I just did, and it did not work--same results.

Thanks for the hints--got more? 

----------------------------------------------------------------------
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