Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Moving file systems to a back-level system z/OS UNIX System Services Planning GA32-0884-00 |
|
If you move a file system to a back-level system, existing NFS client connections to the files in that file system might be broken if Share Reservations are used. With Share Reservations, remote NFS clients can open files on z/OS® in such a way that no one else can open that file until the first program finishes and closes the file. For more information about Share Reservations, see the BPX1VOP callable service in z/OS UNIX System Services File System Interface Reference. Share Reservations that attempt to deny reading or writing for files in a read-only file system are accepted but will not be enforced. File systems cannot be remounted from read/write to read-only or from read-only to read/write while there are Share Reservations established on any file in that file system. Restrictions: A file system cannot be moved to a back-level system while there are active Share Reservations on any file in the file system. You will have to move the file system to a sysplex member at the z/OS V1R7 release level or later. Alternatively, you can stop the applications at the NFS clients who have put reservations on the files, or wait for them to finish. If an NFS client is going to open a file that has Share Reservations
set:
If the system goes down and there are Share Reservations on a file
owned by a remote system:
|
Copyright IBM Corporation 1990, 2014
|