On Wed, Jun 10, 2009 at 5:42 PM, Rick Fochtman <[email protected]> wrote:
> ------------------------------------<snip>--------------------------- > > > > > -------------------------------------<unsnip>------------------------------------------ > Frank, I understand your frustration, but there are some limitations that > need to be kept in mind. > > 1. To place your library(s) in the LINKLIST, they must be cataloged in the > Master Catalog. But unless the name starts with a SYS1. qualifier, it can't > appear in multiple catalogs. This could be a real problem in a > multiple-image environment. Do you want to maintain multiple copies of each > dataset? I seriously doubt it. Maintenance headache. Much better to have it > in a USERCAT, which can itself be shared across multiple images, but this > precludes LINKLIST presence. (Master Catalog integrity is absolutely CRUCIAL > to system availability. You can't even IPL with a corrupted MCAT, in most > cases. That's why system guys get really nervous about any access other than > READ to the MCAT.) > Wow, I'm surprised no one caught this one. Supported levels of z/OS no longer require linklisted libs to be in the master catalog! Just use the VOLSER option. None of my non-SYS1 libs are in the master cat including the IBM supplied ones, like TCPIP.*, CEE.*, etc. They are in a user cat but still cataloged indirectly - no rule that says indirect cataloging can only be done in the master cat. For production application libraries in lnk list, I'm failing to see the problem of simply issuing a F LLA,UPDATE=xx command when new versions are available. Guy Gardoit z/OS Systems Programming > > 2. There's no reason that some system libraries can't be in LINKLIST. > Language Environment and TCP/IP come to mind. Depending on the names, > perhaps your compiler(s) as well. > > 3. Even in a single-image environment, it can create a hassle when your > systems guys start testing a new level of the Operating System, if they've > had to create a new Master Catalog. Not to mention maintenance and upgrades > to OEM products. > > Consider this: even if you can't get all the libraries you want into > LINKLIST, and thus into LLA, you can probably get them under the VLF > "umbrella", improving performance. Check with your systems guys about this > possibility. > > For the foreseeable future, JOBLIB/STEPLIB are going to be a fact of life. > No getting around it. > > -- > Rick > -- > Remember that if you’re not the lead dog, the view never changes. > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
