Hello Donald, Just adding some more to your discussion. Always mount the root as READ (yeah, easy to say... I don't have root mounted as READ where I work). Applications/users should NOT update root, they have their own directories for that (/usr/lpp/xxxxx , /u , etc).
I very often apply maintenance to the root. Where I work, all OMVS files are allocated on OMVSxx volumes - so outside the SYSRES - including the SMPE-updated ones, and I use &SYSR1. var in the middle of the root filesystem name, so it changes every IPL where SYSRES changes (I have 2 SYSRESs volumes to garantee the backout). I never IPL from the SMPE volumes and use ADRDSSU COPY to clone the ROOT. If you plan to IPL a lot with root maintenance (as a outsourcer worker, I know it varies A LOT from company to company), you should consider cataloging your OMVS files with &SYSR2 variable (considering you have a 2-vol SYSRES). This way you would always garantee that when system is IPLed from a certain SYSRES, the OMVS root - and any other filesystem that would also be carried over - are the ones with the same "maintenance level" as the z/OS loadlibs (LINKLIB, MACLIB, etc). Just another way to accomplish the same thing... we almost never see that in z/OS, right?! Take care, *Lucas Rosalen* 2013/11/25 Donald Likens <[email protected]> > I did not read about File System in a Sysplex because we are not running a > Sysplex but now that you pointed it out I will. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
