> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
>
> >>> On 7/30/2009 at 9:55 AM, in message
> "Chase, John" wrote:
> >> -----Original Message-----
> >> From: IBM Mainframe Discussion List On Behalf Of Frank Swarbrick
> >>
> >> If necessary, is there a way to inhibit unauthorized individuals
from
> > linking with AC=1, even when
> >> linking in to an authorized library?
> >
> > Why would an unauthorized individual be able to link anything into
an
> > authorized library?
>
> The issue was putting an "unauthorized library" in the LNKLST with
LNKAUTH=LNKLST treats that library
> as authorized when accessed through the LNKLST concatenation. I was
thinking perhaps we could keep
> LNKAUTH=LNKLST (instead of APFTAB) but make sure that nothing going in
to that library could be
> authorized.
>
> LNKAUTH=APFTAB seems to me to be the answer, but I just want to know
all of the options.
I'd argue that LNKAUTH=APFTAB is "better" because it "forces" you to
explicitly authorize every library that needs to be authorized.
Libraries not explicitly authorized are then treated as unauthorized
even if they are link-listed. "Automatic authorization" then occurs
only if the library is in the LPA.
-jc-
----------------------------------------------------------------------
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
