How / why is LPAR2 trying to mount LPAR1's files? Do you have them defined in BPXPRMxx? That is allowed if they are mounted read only on both LPARs (which would create a SHR ENQ in SYSZDSN and not EXCL). Or is someone manually trying to mount them?
If they are "cross defined" as R/W, then it's a good thing the SYSZDSN ENQ is there to protect you, otherwise you would end up with a sync error and the HFS would be unusable until it was unmounted / remounted (not to mention possible corruption). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[email protected] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html On Tue, 17 Feb 2009 18:45:06 -0500, Lizette Koehler <[email protected]> wrote: >I have th 5 lpars. Each one has its own set of OMVS datasets. > >For example Lpar1 has SYS1.OMVS.ROOT.LPAR1, SYS1.OMVS.JV390.LPAR1, >SYS1.OMVS.SGIYROOT.LPAR1 and so on. >Lpar2 has a duplicate set of files that end with LPAR2 rather LPAR1 >And so forth. > >I see in syslog that the LPAR2 gets an IGW026I message trying to mount the >LPAR1 dataset. This is not needed nor required. Each system has its own >set. > >I was thinking that setting the files to NOAUTOMOVE would prevent another >system from trying to mount them. > >Lizette > >> >> On Tue, 17 Feb 2009 11:20:11 -0500, Lizette Koehler >> <[email protected]> wrote: >> >> >I have read the manuals but I am still not clear on the use of automove >vs. >> noautomove. >> > >> >My Unix envrionment on z/OS V1.9 is one system/one set of UNIX files. >So, >> yes, I have a lot of duplicated files. >> > >> >However, from time to time I notice I will see the following message in >SYSLOG >> > >> >IGW026I HFS FILE SYSTEM: SYS1.SPG7.OMVS.DB2V91.SDSNAHFS 202 >> >MOUNT REQUEST FAILED, RESOURCE HELD EXCLUSIVE ON: SPG7 >> >RESOURCE HOLDER: OMVS ASID: X000E TCB: X009DB360 >> > >> >I am thinking that I should add NOAUTOMOVE to the MOUNT statement in >> BPXPRMxx for these files - because they truely cannot move. >> > >> >Am I correct in this thought? >> > >> >If I could get to a SYSPLEX ROOT, then I would be using a different >> approach. However, it is not there yet. >> > >> >> Since you are not using a shared file system, automove is not relevant. >> >> Are you saying you have the same data set name but 2 physically different >file >> systems mounted, but they are in the same sysplex / grsplex? That would >> be a problem - unless you excluded SYSZDSN - which is there to protect >> you from mounting the same file system R/W on 2 LPARs in the plex when >> you aren't using a shared file system. >> >> Or do I not understand the issue? >> > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
