On 21 August 2018 at 10:49, Seymour J Metz <[email protected]> wrote:
> If you only want to test problem state callers, look at the JSCB.

Sure... But then why is there a TESTAUTH macro with both SVC and
branch entry at all? Everyone could just check JSCBAUTH on their own.
And that single bit is even a Programming Interface! Checking key or
state is slightly fiddlier from, say, an SVC routine, but still not
rocket science. And in a PC routine it's trivial.

But I was just wondering why IBM seems to have provided the necessary
few lines of code, conveniently located in Common so it can run in
home space mode, to do exactly and only this one (JSCBAUTH) test, but
not documented it. Providing a PC routine that can handle APF and
non-APF callers differently seems like a common enough thing to want
to do.

Tony H.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to