Technical data

MAP
MAP
Maps (logically links) one of the following to the NFS server:
• OpenVMS disk — Requires one execution of MAP to map the disk to a UNIX
path name.
• Container file system — Requires two executions of MAP. The first maps the
disk, and the second maps the file system.
Mapping creates a logical file system, also called an NFS file system. A logical file
system (with an entry in the export database) is accessible to NFS client users for
mounting.
To make a file system available on all nodes of a cluster, map it on each node.
Mapping is one step in the tasks necessary to give remote users access to a file
system that physically resides on an OpenVMS host running an NFS server:
1. Map the file system.
2. Export the file system (add an entry in the export database).
3. Give potential users entries in the proxy database.
MAP settings are not permanent. To map file systems in the permanent
configuration database, issue SET CONFIGURATION [NO]MAP.
Related commands: ADD EXPORT, SHOW EXPORT, REMOVE EXPORT, SET
CONFIGURATION MAP, SET CONFIGURATION NOMAP, SHOW MAP, SHOW
CONFIGURATION MAP, UNMAP
Format
MAP "file system name" logical_file_system
Restrictions
Requires SYSPRV and BYPASS privileges.
Parameters
"file system name"
Required.
Specifies the name for the file system or disk. In the case of mapping a disk, the
"/path" can be only one level from the root. This parameter specifies the name by
which users will access the file system.
logical_file_system
Required.
Specifies the file system to make known to the NFS server.
To map an OpenVMS file system, specify its disk:
MAP "/disk" disk:
To map a container file system, specify the disk and the directory name:
TCPIP> MAP
"/container_name" disk:[vms.directory.name]
Command Descriptions 2–61