On Wed, 25 Jun 2014 08:32:38 -0700 Phil Smith <[email protected]> wrote:
:>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!
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.
:>>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?
Note that
LA R1,2 Secondary space address number
really is using the ALET for HOME. In a simple PC-SS SASID=HOME.
--
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: INFO IBM-MAIN
