Adds information to the configuration database that maps (logically links) one of the following to the NFS server: o OpenVMS disk - Requires one execution of SET CONFIGURATION MAP to map the disk to a UNIX path name (logical file system). o Container file system - Requires two executions of SET CONFIGURATION 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. When the NFS server starts up, it issues a GENERATE MAP command, which creates the mappings for disks and container file systems; these mappings are viewable with the SHOW MAP command. Related commands: ADD EXPORT, SHOW EXPORT, REMOVE EXPORT, MAP, UNMAP, SET CONFIGURATION NOMAP, SHOW MAP, SHOW CONFIGURATION MAP Format SET CONFIGURATION MAP "file system name" logical_file_system
1 – Restrictions
Requires SYSPRV and BYPASS privileges.
2 – Parameters
"file system name" Required. Specifies the name for the file system or disk. When mapping a disk, the "/path" can be only one level from the root. This parameter specifies the name by which users 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 as follows: $ SET CONFIGURATION MAP "/disk" disk: To map a container file system, specify the disk and the directory name as follows: TCPIP> SET CONFIGURATION MAP "/container_name" - _TCPIP> disk:[vms.directory.name]
3 – Examples
1.TCPIP> SET CONFIGURATION MAP "/usr" CANARY$DUA2: Maps local disk CANARY$DUA2: to /usr. This disk can be exported to users on remote NFS clients as /usr. 2.TCPIP> SET CONFIGURATION MAP "/remote" VERDIN$DUA3: - _TCPIP> SET CONFIGURATION MAP "/flyers" VERDIN$DUA3:[UNIX_BIRD_FILES] Maps [UNIX_BIRD_FILES], a container file system on disk VERDIN$DUA3:, to /flyers. This file system can be exported to NFS server users as /flyers. (The first MAP command maps the underlying OpenVMS file system.)