In a recent note, Ed Rabara said: > Date: Fri, 9 Mar 2007 18:52:06 -0600 > > Has anyone run across a situation where the MVS NFS Server retains its > exclusive enqueue against an MVS data set (not a HFS file) created by one of > its clients even after the client no longer use the file? > Yes, yes, yes!
> NFS clients run on AIX. > Ours run on Solaris. > Because MVS NFS Server holds an exclusive enqueue, MVS batch jobs are not > able to use the data sets. F MVSNFS,RELEASE=data_set_name works but is not > practical when there are tens of them. > Sometimes (but, not, IIRC, always) I can delete the data set from the NFS client side. But sometimes the ENQ comes right back when I re-create it. > Appreciate any input, Ed R. > I've deferred reporting this because all the data sets I use in this fashion are expendable. I can just choose a different data set name and proceed. Problem finally clears up at NFS recycle or IPL (the server is a lab system, IPLed weekly), but it has persisted longer than any plausible time out value. If I could re-create the problem at will, I'd report it. Misery loves company. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
