I do 3 LPARs much as you describe. Currently, I don't believe IBM maintenance will target /var. There should be HOLDDATA when /etc is targeted because you need to change the links before and after. I usually keep the /etc from release to release and update it if a change requires it. It Is mostly tailoring. Up until z/OS 1.13 (I skipped 1.12) I had /var as a TFS, but I learned of some products expecting data there from ipl to ipl. It is now a ZFS file, but not routinely copied when implementing SMP/E maintenance.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Donald Likens > Sent: Wednesday, March 12, 2014 7:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Handing /etc and /var filesystems > > We have 4 different non-sysplex LPARs all maintained by a sand box LPAR. We > install on the sand box LPAR and then copy volumes and files to the other > systems to roll out the maintenance. I recently installed a serverpac and > decided to make the /etc and /var filesystems SYS1 residing on the SYSRES. In > this way, whenever IBM updates these directories with maintenance it will > automatically be implemented on the other systems with the SYSRES volume > copy. My concern is that any changes to these directories will be lost as new > SYSRES copies are rolled out. So far looking at what is on these directories > it is > either static or updated all the time (like a pid number). > > My question is how do you handle these file systems in your shop. Note: > Sharing them is not an option, so if you share these directories across LPARs > please do not respond. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
