On Mon, 8 Jul 2013 07:55:46 -0500, Kenneth Wilkerson <[email protected]> wrote:
>And it doesn't >matter what the AC= is for a LPA program. MVS is going to treat it as >authorized simply because it's in the LPA. I discovered that the hard way. > That's not true, Kenneth. MVS will certainly consider any LPA-resident module to have been loaded from (i.e., resident in) an APF-authorized library, but that is not related to the AC=0/1 setting. Being resident in an APF-authorized library simply means that the system will allow another program that is already running authorized (APF, system key, or supervisor state) to load the module, and this is true for both AC=0 and AC=1 modules. If the module is not in an APF-authorized library and an authorized program tries to load it in the normal way, the load will fail. If the module does have AC=1, and it's resident in an APF-authorized library, then IF the module in invoked as the jobstep program by the initiator (or in a small handful of other ways) then the new jobstep will gain APF-authorization and run APF-authorized. If you have an LPA-resident module that is AC=0, and you run it via EXEC PGM= it will NOT run APF-authorized. It needs AC=1 for that. Many people (including some IBMers, and some writers of documentation) seem confused by the distinctions between APF-authorized libraries, AC=1, and running APF-authorized. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
