If that is your scenario then you should be using 'unmount' for the automove parameter. Noautomove can still leave entries in the global mount table for these filesystems even though the system is down. That is usually not a big issue unless you have the need to mount them on another system for some reason (maintenance or problem determination, etc).
Jon L. Veilleux [email protected] (860) 636-2683 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, February 17, 2009 6:45 PM To: [email protected] Subject: Re: Automove vs Noautomove in BPXPRMxx 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 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- 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
