NFS creates a unique UID and GID for each client, and the UIDs and GIDs are consistent within a session. For example, the server might return the UID and GID set (100,100) for one user, and (101,100) for the next user.

If the client maintains the UID and GID for the mount point base, you should use the PCNFSD requests rather than the mvslogin client enabling command. However, if the client does not maintain the UID and GID for the mount point base, you should use the mvslogin client enabling commands rather than PCNFSD requests.

If you issue the mount command, which issues a PCNFSD request (as it is implemented on some platforms), to do the authentication, you should not use the mvslogin client enabling command.

If the client's z/OS user ID, which was authenticated by a PCNFSD request issued by a mount command, is logged off by the server due to timeout or server restart, then the client needs to issue the umount and mount commands to log on again.

See Using z/OS Network File System for information about how clients use PCNFSD.