Examples

• When the minidisk is protected by link passwords, mdiskpw= specifies the minidisk's read-write password. (If the ro parameter is used, use the read-only password.)
  • To work with text files that can be used from both CMS and *IX:
    mountpw hostname:jake.191,mdiskpw=mypass
    mount -o soft,rw hostname:jake.191,rw,lines=nl,trans=yes /home/jake/m191

  • To use a minidisk as a repository for binary files:
    mountpw hostname:jake.191,mdiskpw=mypass
    mount -o soft,rw hostname:jake.191,rw,lines=none,trans=no /home/jake/m191

• When the disk is protected by an External Security Manager (ESM) such as RACF/VM, password= specifies the logon password for the VM user ID specified on userid=.
  • To work with text files that can be used from both CMS and *IX:
    mountpw hostname:jake.191,userid=elwood,password=mypass
    mount -o soft,rw hostname:jake.191,rw,lines=nl,trans=yes /home/jake/m191

  • To use a minidisk as a repository for binary files:
    mountpw hostname:jake.191,userid=elwood,password=mypass
    mount -o soft,rw hostname:jake.191,rw,lines=none,trans=no /home/jake/m191

Hints and Tips

• See a "security flavor not supported" message? Try using mountvers=1 on your mount request.

• Starting in TCP/IP level 320 for VM/ESA Version 2, Release 4.0, your NFS administrator can configure the VM NFS server so that no anonymous mounts are allowed, even for minidisks protected by passwords. In this case, identify yourself by specifying userid= and password= on the mount string (where password= is userid's logon password), and specify the minidisk link password using mdiskpw=.

• 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 CMS minidisks is based on the ability of the NFS server to link the disk. On multi-user NFS client systems, all users have the same access to objects in the mounted minidisk 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.

• 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.

• When a minidisk is mounted, the VM NFS server machine LINKs to the target minidisk. If the minidisk is linked by other CMS users, the NFS server must sometimes be told to refresh or detach the disk. Use the SMSG command to refresh or detach a link to a CMS minidisk.

• 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.

• The lines and trans parameters are supported only on NFS servers running at least TCP/IP level 310 for VM/ESA Version 2 Release 3.

Please write to Mary Ellen Carollo, maryelln@us.ibm.com, if you have comments on these instructions.

Return to the main z/VM TCP/IP NFS Server Support page.