Chapter Contents |
Previous |
Next |
Using the NFS Client |
The following commands are used primarily by users who are running NFS client applications:
The format used to invoke the
NFSLOGIN
,
MOUNT
, and
UMOUNT
commands is generally
identical to that shown in the following reference information. On MVS, system
administration considerations may require use of the TSO CALL command or other
techniques. See your system administrator for details. See MOUNT, NFSLOGIN, and
UMOUNT for reference information.
NFSLOGIN |
Authorizes TSO or CMS
users to access files via NFS
Format 1:
NFSLOGIN
[
-s
server] [
-u
username] [
-p
password] [
-n
] | |
Format 2:
NFSLOGIN -f
|
The
NFSLOGIN
command authorizes TSO or
CMS users to access files via NFS. In some cases the NFS client software can
determine the correct server and username without
you specifying them. If a RACF compatible security system is installed, the
site can define particular mainframe users as having access to specified UNIX
userids without requiring a password. If no password is required, and if the
other values are correct by default, you do not need to use this command.
The login will occur automatically when you access the first NFS file or directory.
The
NFSLOGIN
command is provided for sites
and situations where either a password is needed or the default server or
username values must be overridden.
See Logging on to the NFS Network for an introductory discussion of NFS login considerations. Also
seeNFS Security Administration and the
description of the
nfslogin
function in SAS Technical
Report C-113, SAS/C Connectivity
Support Library, Release 1.00 for more detailed information.
The
-f
option requests a full-screen display.
This display has fields for entering the same information that can be specified
on the command line. The full-screen option provides non-display password
entry.
The server parameter is the host name of the login server that you want to contact. This may differ from the servers on which files are being accessed. The specified host must be running the appropriate login server software. See Installing and Administering the NFS Client for details. You can usually omit this option because the site can set up a default at installation time. Note also that, when a security system is installed, the mainframe security administrator controls your access to login servers. Using an unauthorized server causes a RACF violation.
If you do not have a RACF compatible security system,
or if you want to login as a username that is not associated with your RACF
profile, use the
-p
option or the password field to specify your password
on the login server. The mainframe security system (if present) can also control
whether a password will or will not be allowed on your NFSLOGIN.
Note that the
-p
option requires a value.
The
-n
option is required for the special case where
the UNIX (or other login server operating system) system account has a null
password. The
-p
and
-n
options are mutually
exclusive. Not specifying either
-p
or
-n
indicates that the user expects the mainframe security system to authorize
access to the login server username. The full-screen display also allows for
the special case of a null password.
If the login attempt fails,
NFSLOGIN
prints a message
describing the reason. Otherwise it prints a message indicating success. The
login fails if the login server is not running on the NFS network.
Note that you don't need to log out from the login server;
your UID and GID permissions will expire after you log off of TSO or CMS.
If you want to access files under a different user name, you can issue
NFSLOGIN
again. A login will expire after two days. If you are connected
to a session for several days, you will need to log in again.
nfslogin -f
Invoke the full-screen login panel.
nfslogin -u bbritten -p ocean
Log in to the default login server with username
bbritten
and password
ocean
.
MOUNT |
Mounts remote NFS file systems into
the NFS client file system
structure.
Format 1:
MOUNT
server
:directory mount-point [options] |
The
MOUNT
command is one method of mounting
remote NFS file systems into the NFS client file system structure on the mainframe.
This command is useful only when you have configured your session to save
file system context. Otherwise, the effect of the mount disappears when the
MOUNT
command completes.
The options string is not required. It specifies mount options for the file system. See Mount Options. The string of options must be separated by commas, with no intervening spaces.
You cannot mount on a directory that is already being
used as a mount point. You must first unmount the existing file system with
the
UMOUNT
command.
Be aware that mounts made by this command are preceded
by mounts from any
fstab
file.
These examples assume that there is no
fstab
file and that file system context is being saved.
mount byrd.unx:/local/u/bill /
Mount
bill's
home directory on "
byrd.unx
" as the root directory on the mainframe.
mount server.unx:/tools /tools ro
Add the
/tools
directory from
server.unx
as a subdirectory and treat it as read-only.
UMOUNT |
Removes a previously established mount
Format 1:
UMOUNT
mount-point |
The
UMOUNT
command removes a previously
established mount. This command is useful only when you have configured your
session to save file system context. Otherwise, the effect of the unmount
disappears when the
UMOUNT
command completes.
You cannot unmount the root directory. If you want to
mount a totally different root directory, delete the
mnttab
file and then mount the new root directory. NFSLOGIN also deletes the
mnttab
file.
UMOUNT failed: file or record in use.
This example assumes that file system context is being saved.
umount /tools
Remove the file system that was previously mounted at
/tools
. If the file system mounted at / had any files in its
tools
subdirectory, these now become
visible.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.