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
