Mounting an SFS directory on OS/2
Examples
These instructions assume that PCNFSD is available on your NFS server.
- To work with text files that can be used from both CMS and
OS/2:
MOUNT -lvmuserid s: hostname:fpcool:jake.mission,lines=nl,trans=yes,nlvalue=0D0A - To use an SFS directory as a repository for binary files:
MOUNT -lvmuserid t: hostname:fpcool:jake.mission,lines=none,trans=no
Hints and Tips
-
See MOUNT command,
MOUNTPW command, and
UMOUNT command,
for complete syntax descriptions.
Still having trouble? Try
Diagnosing Mount Problems.
- 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.
- When PCNFSD
is available on your NFS server,
enter the logon password for the VM user ID specified on the
-l local OS/2 option at the prompt.
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.
- If PCNFSD
is not available on your NFS server,
add the userid=
option to your mount string, and
use the -v option instead of the -l
entering the password associated with the user ID at the prompt.
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.
-
Access to SFS files and directories is not based on UIDs and GIDs, but
on the authorities granted to the
user ID specified on the
-l or
userid=
parameter.
-
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.