LS:
Cross post from MVS-OE Currently I am in discussion with IBM about the design changes made, in z/OS V1R6 and later, with the behavior of the USS MOUNT options UNMOUNT, AUTOMOVE etc. The new design, described in APAR OA12251, introduces problems in the area of "Dead System Recovery" during an IPL in the two system SYSPLEX in our shop. IBM states that they understand the problems but will not change the behavior until a "future release". The problems are encountered because USS MOUNT option UNMOUNT is ignored for SYSPLEX-AWARE Read-Only file systems when a system is removed from SYSPLEX without correct OMVS termination. This behavior introduces as an example the next problem at our site: * SYSPLEX with 2 systems SYSM and SYSI and USS sharing active. * File System SYSIHFS.EXAMPLE.OLD mounted R/O on system SYSI with UNMOUNT option on /SYSI_VER/usr/lpp/example * SYSI working normally but IPL needed, due to updated software, SYSI has to leave the SYSPLEX. * When SYSI was brought down OMVS most likely did not terminate properly because SYSIHFS.EXAMPLE.OLD mounted on system SYSM with UNMOUNT indication after message BPXN001I UNIX SYSTEM SERVICES PARTITION CLEANUP IN PROGRESS FOR SYSTEM SYSI * IPL system SYSI with changed BPXPRM member saying SYSIHFS.EXAMPLE.NEW (software update) should be used during IPL did not mount the new SYSIHFS.EXAMPLE.NEW because SYSIHFS.EXAMPLE.OLD already mounted on the mountpoint /SYSI_VER/usr/lpp/example * System SYSI continues using WRONG OUTDATED FILESYSTEMS Main reason of this problem is the UNMOUNT behavior not honored in all cases. If files where unmounted as requested by the UNMOUNT option as with z/OS V1R4 we did not had these problems. Or the IBM behavior and design is wrong or the way we are working with, in this case, the version file systems is not as other shops are doing. Note: Bypass build to automatically unmount all unwanted file systems on remaining system MVSM before IPL system MVSI. In our opinion this should not be needed in the first place. SYSNAME used in $VERSION because we do not want to use this type files on more than one system in the sysplex to keep all SMP maintained files HFS/ZFS and others always in synch on every system. Only application data files are really shared. We had the idea $VERSION definition should only change with a new z/OS release. We now changing the $Version definition every IPL to make sure the correct files are used after the IPL. Question; did other shops have seen these problems or is this never the case because this cannot happen due to the way they are using file systems? Regards and thank for your reactions Ron van der Zande ---------------------------------------------------------------------- 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
