A mount for server text was dropped. At z/OS NFS server shutdown, the message is issued and the mount path is written into the MHDB along with the reason string rsnstr. At next z/OS NFS startup, the reason string in the MHDB is detected and the message issued. By contrast, at resource timeout the message is issued, but no MHDB record will be written in the swapped MHDB data set. In the message text:

text

"current" or "prior". The text "prior" will only be seen at z/OS NFS server startup from MHDB diagnostic records. All other instances of this message will see "current".

rsnstr

The reason for the mount to be dropped is one of the following:

• "Mount Block current count is 0"
• "No MVS File Block found"
• "No Mount Usage Block found"
• "NFS version 4 non-recorded mount"
• "Mount Usage Block marked for deletion"
• "Mount Usage Block has usage count of 0"
• "Mount timed out"
• "Mount has no hostname"
• "Mount record has no hostname"
• "Mount MVS File Block locate reasoncode=fbrc"

  where fbrc is an internal reason code

host

the hostname of the mount being dropped

mpath

the pathname of the mount being dropped

fsname

the USS filesystem name for the mount pathname, or "MVS" for an MVS mount

fhandle

hex representation of the mount filehandle, so the mount keys can be correlated to dependent filehandles getting dropped errors