On 7/24/2006 3:52 PM, Chase, John wrote:
-----Original Message-----
From: IBM Mainframe Discussion List On Behalf Of McKown, John

Any chance that ISPLLIB (and maybe STEPLIB?) could contain an non-APF authorized library? IIRC, that will remove the APF authorization from all modules loaded via ISPLLIB regardless of the AC value.

No //STEPLIB in the logon proc, and about half of //ISPLLIB is
unauthorized (and it's always been that way, AFAIK).

Besides, if it were an authorization problem I'd expect a different
diagnostic than "program not found".  Of course, this is TSO and
ISPF....

And you also wrote earlier:
There are unauthorized libraries in the //ISPLLIB concatenation.  But if
it's an authorization issue, why does the reason code translate to
"program not found" (reason code 40 (x'28')) instead of something like
"program not authorized"  (reason code 56 (x'38'))?

First, the flavor of IKJEFTSR that can run code authorized can not find things in ISPLLIB, and has never had the ability to find things there. A form of invocation for IKJEFTSR that would search ISPLLIB exists, but it can not invoke authorized code.

Therefore, if this worked previously via IKJEFTSR you must have had another copy of the module somewhere in LINKLIST or LPA, or you must have had a STEPLIB or TSOLIB.

As for "program not found" vs "program not authorized" I believe you'll find that "program not found" means exactly that: no copy of the program was found.

"Program not authorized" means, as far as I know, that a copy was found, but not in an authorized library. If IKJEFTSR could search ISPLLIB, and if ISPLLIB contained unauthorized libraries, then I agree that you should have seen a 56 reason code. But as IKJEFTSR can not see ISPLLIB, the 40 was correct.

        Walt Farrell, CISSP
        z/OS Security Design, IBM

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to