> We are beginning to customize our z./OS 1.7 (to > replace 1.4). We have several folks who will be > updating parmib and proclib. There is a possibility > that we might step on each other's changes. Say, > for instance, two people are making changes to COMMNDxx.
At my last job, I was the "parmlib nazi". All changes to parmlib went to me (except off hours to fix a problem). IMHO, there should only be one person updating the parmlib. You always want the system to IPL. For example for Audits, there was only one person making changes to the APF list. Regardless of if it's one person or many updating the parmlib, I would recommend using a parmlib concatenation. See what I did here: http://www.planetmvs.com/userexperiences/os390r6.html#parmlib Put the new parmlib dataset that contains all changes just for the new operating system in front of your current concatenation. All of the changes go there instead of your production libraries so you never cause a problem to your current system. I don't know if its on that web page but I also create a system symbol like "&OSLEVEL" with the value like "ZOS17". There would be a LNKLST library with a name like SYS2.&OSLEVEL..LINKLIB for modules that are needed just for the new operating system. One place I worked had a third SYSRES, &SYSR3, which was for program products and had the updated libraries to match that level of the operating system. That makes it nice to bring in everything needed for that level of the OS. ---------------------------------------------------------------------- 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
