<snip> When an AC(1) module is loaded, the decision to honor the authorization is made (in part) by searching the **current** APF list for the DSN and volume for an entry that matches where the module was found. </snip>
Aside from the LNKLST, this is not correct. And for the LNKLST, it is correct only when LNKAUTH=APFTAB is in effect. It is at open time that a concatenation (or individual data set) is evaluated for "APF-ness". If all data sets in the concatenation are APF-authorized then the concatenation is considered APF authorized. This is remembered/represented in the DEB (bit DEBAPFIN). Fetch processing pays attention to DEBAPFIN. This is why a concatenation of 9 APF-authorized data sets and 1 non-APF-authorized data sets is not considered APF-authorized and why AC(1) would not be honored upon a fetch from such a concatenation. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
