On Wed, 25 Jun 2014 15:52:35 +0000, Rob Scott <[email protected]> wrote:
>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. When I was a RACF developer we hit that situation quite often. Debugging cross-memory programs is made more complex, imho, by the fact that usually the addresses of the address space ACEE and the jobstep TCB are the same from address space to address space. For some of our testing we specifically attached additional tasks, and created additional ACEEs, all with different user IDs (with different authorities to the resources in question), simply so that if we were grabbing an ACEE from the wrong address space, or wrong task, it would be obvious because the check would fail. And the failure messages would tell us exactly what part of the code was wrong. > >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. I recall reading a long time ago that passing an ALET of (I think) 1 to a system service was risky, and discouraged. The problem is that you don't necessarily kinow how the service is implemented, and if it does another space-switching PC then the meaning of ALET 1 changes. I don't think that would be a problem with RACROUTE, but I still wouldn't recognize. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
