Biggest reason to use Dynamic Proclibs is your end users cannot reallocate/compress it and cause JES2 to fail.
The other process I like my end users to use is JCLLIB dd statement. Then they have complete control and do not need me to handle their proclib datasets. They are responsible for backup and recovery of their proclibs at least for their test ones. I still do dfdss dumps of all prod datasets so that would include their production proclibs.. I have my JES2 proc down to mostly SYSTEM proclibs and only one production proclib dataset. Lizette > I know that using dynamic proclibs gives you the ability to change the proclib > concatenations dynamically and also the ability to rebuild pointers if a library has gone > into extents or been compressed. > > My shop uses static concatenations. We haven't needed to change the proclib > concatenations in several years and JCL can be used to rebuild JES2's pointers if > needed. I'd like to convert to dynamic proclibs because it seems more modern and > cooler. But I wonder if it's really necessary for my installation and maybe I'd just be > doing work for work's sake. > > Any opinions? Am I missing some benefits? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
