About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Mounting a BFS 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 x: hostname:/../VMBFS:FPCOOL:ROOT/u/jake,trans=yes,xlat=POSIX - To use a BFS directory as a repository for binary files:
MOUNT -lvmuserid x: hostname:/../VMBFS:FPCOOL:ROOT/u/jake,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.
- At the prompt
enter the logon password for the VM user ID specified on the
-l OS/2 option.
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= and
password= parameters to
your mount string.
On the password= parameter,
enter the logon password for the VM user ID specified on
userid=.
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.
Also use the -unnnn and -gnnnn OS/2 options instead of the -l OS/2 option, entering the UID and GID associated with the VM user ID specified on the userid= parameter.
- Do not use the -v option on an OS/2 MOUNT command
or your UID and GID will be set improperly.
- For hostname:, use the system on which the file pool
server resides to avoid unnecessary overhead.
-
You must use a fully-qualified BFS directory name on the MOUNT command.
Be careful - case is important!
-
If you want EBCDIC-ASCII translation to
be done based on the value of the
file extension,
use the trans=ext
parameter instead of
trans=yes or
trans=no.
-
Use the
SMSG command to obtain more information
if you receive an error
but don't understand what went wrong when using a BFS directory.
-
If you created a text file using an OS/2 editor and want to use
the XEDIT command to edit it from CMS, it may be
necessary to use the BFSLINE /X'0D15'/ option.
- NFS server support for BFS 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.