Mounting an SFS directory on Microsoft Windows®
- Optionally create an alias.
- Go to NFS Servers I Have Configured, as you did when you configured the NFS server.
- Select the host, and click on the right mouse button to obtain a list.
- Select Create Alias.
- Fill in the alias name that you want to use.
- Fill in the Path, specifying the mount operands, as shown in the examples below.
- Select OK to create the alias.
Once created, aliases are not easy to change on some NFS clients. Make a note of the alias name and parameters you have specified. Sometimes changes are necessary, such as when your alias contains a password and you change your password. - Issue the "mount".
- Go to Windows Explorer.
- On the menu bar, select Tools.
- Select Map Network Drive.
- Select or fill in hostname\alias.
(Note the backslash following hostname.)
(If you did NOT create an alias, the information shown in the examples below can be entered following hostname\ in place of the alias.) - Select Ok.
Path Examples
- When PCNFSD is available and
you have specified a VM user ID
for the host username under the security tab.
- To work with text files that can be used from both CMS and
Windows:
fpcool:jake.mission,lines=nl,nlvalue=0D0A,trans=yes - To use an SFS directory as a repository for binary files:
fpcool:jake.mission,lines=none,trans=no
- To work with text files that can be used from both CMS and
Windows:
- When PCNFSD
is not available and you must define a username of
NOBODY for your host.
Note that different NFS clients may have other ways of saying that PCNFSD should be bypassed. Consult your NFS client documentation for the correct values or procedures.
- To work with text files that can be used from both CMS and
Windows:
fpcool:jake.mission,lines=nl,nlvalue=0D0A,trans=yes,userid=elwood, password=mypass - To use an SFS directory as a repository for binary files:
fpcool:jake.mission,lines=none,trans=no,userid=elwood,password=mypass
- To work with text files that can be used from both CMS and
Windows:
Hints and Tips
- Unexplained mount problems? Try configuring your client first to
force version 3, then try version 2.
-
See MOUNT
for a complete syntax description.
Still having trouble? Try
Diagnosing Mount Problems.
- Your NFS administrator can define export entries to make it
easier to mount a VM file system. Your NFS client may have a window
describing the hosts defined to it. Double-click on a host name 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.
- 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.
- If the editing tool uses the line feed character to mark end-of-line,
you do not need the nlvalue= parameter.
-
Access to SFS files and directories is not based on UIDs and GIDs, but
on the authorities granted to the VM
user ID associated with the request. This can be the
username
defined for your host
under the security tab (when PCNFSD
is available on the server)
or the VM user ID
specified on the userid= parameter.
-
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.
- 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.