Got it. Missed that explicit distinction ("all the libraries in LNKLST just
happen to be authorized" as opposed to LNKAUTH=LNKLST) until @Jim emphasized
it here.

Thanks all.

Charles


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Peter Relson
Sent: Saturday, May 27, 2017 7:58 AM
To: [email protected]
Subject: Re: Setting of LNKAUTH available to a program?

<snip>
But isn't LNKAUTH= an IPL option that would therefore necessarily be
consistent and stable across A/S's? Or am I missing some consideration?
</snip>

The LNKAUTH option is of course consistent and stable across address spaces.
But my comment was about the DlcbAPF bit which, as I said, does not
correlate to the LNKAUTH option.
Different LNKLSTs could have different values for this bit.

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

Reply via email to