Mounting an SFS directory on *IX
Examples
- To work with text files that can be used from both CMS and
*IX:
mountpw hostname:fpcool:jake.mission,userid=elwood,password=mypass
mount -o soft,rw hostname:fpcool:jake.mission,lines=nl,trans=yes< /home/jake/miss1 - To use an SFS directory as a repository for binary files:
mountpw hostname:fpcool:jake.mission,userid=elwood,password=mypass
mount -o soft,rw hostname:fpcool:jake.mission,lines=none,trans=no /home/jake/miss1
Hints and Tips
- See a "security flavor not supported" message? Try using mountvers=1
on your mount request.
-
See MOUNT command,
MOUNTPW command, and
UMOUNT command,
for complete syntax descriptions.
Still having trouble? Try
Diagnosing Mount Problems.
- Your NFS administrator can define export entries to make it
easier to mount a VM file system. Use
showmount -e hostname to determine
which file systems are exported for that server.
Export is supported for VM NFS servers at TCP/IP level 320 for VM/ESA Version 2, Release 4.0 and higher. Do you need help determining the release level running on your server?
- You can use any LOGON BY privileges defined
for your VM user ID. See the userid= and
by= parameters on the MOUNT
command for more information.
- The MOUNTPW command can be used to enter authentication information
such as user ID and password separately from the MOUNT command.
This is useful on multi-user NFS client systems, where the
MOUNT commands are saved and can be displayed later.
- MOUNT must be issued from a super-user.
-
Access to SFS files and directories is based on the authorities
granted to the VM user ID specified on the userid
parameter, and not UIDs. On multi-user NFS client systems, all
users have the same access to objects in the mounted SFS directory if
they have permission to use the mount point. Thus the super-user who
performs the mount must make sure that appropriate controls are in
place for the mount point.
- Be careful about submitting too many MOUNT requests with an invalid
password. The VM system may disable a user ID if too many attempts
are made to verify a userid/password combination.
- For hostname:, use the system on which the file pool
server resides to avoid unnecessary overhead.
-
If you want EBCDIC-ASCII translation and bytestream-to-record
translation to be done based on the value of the
file extension,
use the
lines=ext and
trans=ext
parameters.
- See SFS link processing
for more information about hard and symbolic links.
-
Use the
SMSG command to obtain more information
if you receive an error
but don't understand what went wrong when using an SFS directory.
- NFS server support for SFS is available only on NFS servers running at least TCP/IP level 310 for VM/ESA Version 2 Release 3.
Return to the main z/VM TCP/IP NFS Server Support page.