We keep local /etc directories, but most of the entries are either symbolic links to /SAXX/etc entries (with etc members common across each plex) or symbolic links to /usr/etc entries (with etc members common across all systems). /usr/etc is on our sysres. The contents is not IBM or SMP maintained.
At the /etc level (ignoring subdirectories), we have 6 entries that are local, 5 entries that are symlinks to /SAXX/etc and 24 entries that are symlinks to /usr/etc. (those numbers aren't quite correct, for a number of the entries we concluded that a symlink in /etc isn't needed as the app in question can just be updated to point to the real location). Bart -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Donald Likens Sent: Wednesday, March 12, 2014 10:12 AM To: [email protected] 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 [email protected] with the message: INFO IBM-MAIN
