When your *IX client allows you to read files, but you are unable to
write or create files:
Are you sure you have done a R/W mount? From a VM user ID
issue smsg vmnfs m q resource user ALL to make sure the
VMNFS server agrees.
Are you sure you have authority to write to an SFS file? Remember
that in SFS the authority levels are different for a file and its
owning directory.
From the VM user ID used for the mount, issue
Query Auth filename filetype dirid
to see your authority for the file.
Issue Query Auth dirid
to see your authority for the directory.
(The VM user ID must be running CMS to issue these commands.)
If mounting a BFS directory,
are your UIDs consistent across systems? You may have problems
if the UID/GIDs for
the mount point on the *IX system are different from those assigned
to the VM user ID used on the mount.
Look for the POSIXINFO statement in its VM directory entry. (A default
of -1 is assigned if there is no UID specification for a user.)
What version of NFS is in use? Some *IX NFS Clients
quietly default to the highest supported version, but don't complain
that the NFS server does not support it. The
z/VM VM NFS server supports
only NFS version 2 and NFS version 3, so you
may need to specify
nfsvers=2 or nfsvers=3 on your mount.
