On Fri, 24 Jul 2009 17:30:23 -0600, Frank Swarbrick
<[email protected]> wrote:

<snip>

>
>From my perspective this works exactly as I, an applications developer,
desire.  It has neither the advantages nor the disadvantages of LLA
controlled libraries.  I am fine with this.
>
>Systems is concerned about system integrity.  Rightly so.  LNKLST has
>historically been for systems libraries only.  But since there is no
similar >facility for business applications libraries this seems to be the
only way I can >get what I want.  In any case, does anyone see any obvious
issues with this? 
> One concern is that the APPL libraries would automatically become APF
>authorized, which of course is a no-no. 


 That does not *appear* to have occured:
>
>/D PROG,LNKLIST
>RESPONSE=ZOSD
> CSV470I 17.22.12 LNKLST DISPLAY 224
> LNKLST SET LNKLSTAP   LNKAUTH=LNKLST
> ENTRY  APF  VOLUME  DSNAME
>    1    A   DEVR80  SYS1.LINKLIB
>    2    A   DEVR80  SYS1.MIGLIB
>    3    A   DEVR80  SYS1.CSSLIB
>    4    A   DEVR80  SYS1.SIEALNKE
>   etc.
>   60    A   DB2001  SYS3.DSN910.SDSNEXIT
>   61    A   DB2001  SYS3.DSN910.SDSNLINK
>   62        DB2001  SYS3.DSN910.SDSNLOD2
>   63    A   DB2001  SYS3.DSN910.SDSNLOAD
>   64        *SMS*   PROD.APPL.DFSRESL
>   65        *SMS*   EMER.APPL.LOADLIB
>   66        *SMS*   PROD.APPL.LOADLIB
>
>/D PROG,APF does not show the APPL libraries.
>
>/D LLA does not show the APPL libraries.
>
>All of the above are as I would expect.
>
>The only concern I have at this point, and it's a very very minor one, is
that if you add an application library to the LNKLST you also have to
remember to REMOVE it from the LLA.  But since I don't anticipate there
being changes often or at all (after implentation) to these I'm not too worried.
>
>Thanks!
>Frank
>

Maybe, maybe not....

If LNKAUTH=LNKLST is used, your libraries will be APF authorized.  I can't
tell that from the display above, but something like my IPLINFO will show
you what is in IEASYSxx.  Also, the LNKLST display in my IPLINFO and
LPROG execs show APF=Y for all LNKLST libs in the LNKLST display
when LNKAUTH=LNKLST.

Other than that, I guess you have what you wanted - which is fine - assuming
LNKAUTH=APFTAB (which BTW, is the setting auditors prefer).  Even if not
set that way, your system staff can do a little work, change IEASYSxx 
and add the libraries to APF that really need to be added.  

If I were you or an application programmer, I would still rather use INCLUDE
or some other method where I had control of what I wanted to change and 
when instead of having to rely on the system programming staff.   Yes, it's
a one time change to existing JCL, but assuming you have STEPLIBs or 
JOBLIBs in there now and you want to move to LNKLST execution, you have
to make changes anyway or what you are doing now doesn't matter.


Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[email protected]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
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