DIGITAL TCP/IP Services for OpenVMS
Management Command Reference

Previous Contents Index


Displays the communication controllers known to DIGITAL TCP/IP Services for OpenVMS.





Requires OPER privileges.



Optional. Default: All devices.

Displays the specified OpenVMS device name.

Specify a 2-letter name that you entered with the DEFINE COMMUNICATION_CONTROLLER command.



Optional. Default: All letters.

Displays entries with the specified letter, which represents the first letter of an interface name.



                    Communication Controller Configuration  
Controller:  LO   Internet Interface:  L 
                                Type:  LOCAL 
Controller:  WI   Internet Interface:  W 
                                Type:  WIRELESS 
Controller:  EC   Internet Interface:  C 
                                Type:  CLUSTER ETHERNET 
Controller:  XE   Internet Interface:  D 
                                Type:  CLUSTER ETHERNET 
Controller:  EF   Internet Interface:  F 
                                Type:  CLUSTER ETHERNET 
Controller:  CL   Internet Interface:  I 
                         Description:  ATM Classical IP 
                                Type:  FDDI 
Controller:  EL   Internet Interface:  L 
                         Description:  ATM Emulated LAN 
                                Type:  FDDI 
Controller:  PP   Internet Interface:  P 
                         Description:  Point to Point Protocol 
                                Type:  PPP 
Controller:  EB   Internet Interface:  B 
                         Description:  Shared Memory LAN 
                                Type:  CLUSTER ETHERNET 
Controller:  EI   Internet Interface:  I 
                         Description:  Fast Ethernet - I82558 
                                Type:  CLUSTER ETHERNET 
Controller:  FA   Internet Interface:  A 
                                Type:  CLUSTER FDDI 
Controller:  FC   Internet Interface:  C 
                                Type:  CLUSTER FDDI 
Controller:  IC   Internet Interface:  C 
                                Type:  CLUSTER TOKEN_RING 
Controller:  IR   Internet Interface:  R 
                                Type:  CLUSTER TOKEN_RING 
Controller:  SL   Internet Interface:  S 
                                Type:  SERIAL 
Controller:  CL   Internet Interface:  I 
                         Description:  ATM Classical IP 
                                Type:  FDDI 

Displays all the information in the table used to match OpenVMS device names with internet interface names.


Sends ICMP ECHO packets to hosts to determine if they are active. Same as the PING command.


LOOP [ host ]
[ /ALL ]
[ /[NO]ROUTE ]


Requires OPER privileges.



Optional. Default: None.

Host to which the packets are sent. Omitting host tests the local TCP/IP software.



Optional. Default: Not all requests.

Displays all ICMP ECHO_REQUESTs, even if not in direct response to this operation.


Optional. Default: 1 per second.

Number of packets to send.


Optional. Default: 64 bytes.




Optional. Default: /ROUTE.
/ROUTE Request is routed through the normal routing tables.
/NOROUTE Normal routing tables are bypassed.
If the host is not on the LAN, you get an error.



TCPIP> LOOP thrush  

Tests the connectivity path to UNIX host thrush.



Tests the local DIGITAL TCP/IP Services for OpenVMS software.



Tests the path to the UNIX host thrush without using normal routing tables.


Maps (logically links) one of the following to the NFS server:

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:

MAP settings are not permanent. To map file systems in the permanent configuration database, issue SET CONFIGURATION [NO]MAP and GENERATE MAP.

Related commands: SHOW MAP, UNMAP


MAP "file system name" logical_file_system


Requires SYSPRV and BYPASS privileges.


"file system name"


Name for either a disk or a container file system. In the case of mapping a disk, the "/path" can be only one level from the root.



File system to make known to the NFS server.
To map an OpenVMS file system, specify its disk:

TCPIP> MAP "/disk" disk:  

To map a container file system, specify the disk and the directory name:

TCPIP> MAP "/container_name" disk:[]   




Maps local disk CANARY$DUA2: to /usr. This disk can be exported to users on remote NFS clients as /usr.


TCPIP> MAP "/remote" VERDIN$DUA3:   

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.)


Makes a physically remote file system accessible to local users. Applies to the NFS client.

Mounts a remote directory to local device DNFSn:. Similar in function to the UNIX /etc/mount command, MOUNT gives a file system a UNIX style path name. (In format and style, MOUNT resembles the DCL command MOUNT.)

You can mount either OpenVMS or UNIX file systems.

Related commands: DISMOUNT, SHOW MOUNT

restrictions and tips

If you mount remote OpenVMS directories where the NFS server is running DIGITAL TCP/IP Services for OpenVMS software, use the /NOADF qualifier on the MOUNT command line unless you are using the OpenVMS to OpenVMS integration feature.

The /NOADF requirement applies only if the remote NFS server is running versions of DIGITAL TCP/IP Services for OpenVMS earlier than Version 3.3 and cannot participate in OpenVMS to OpenVMS mode operation. Other tips include:


MOUNT mount_point [ volume_label ] [ logical_name ]
[ /HOST=host ]
[ /PATH="/path/name" ]
[ /ACP_PARAMS=options ]
[ /[NO]ADF[=option] ]
[ /BACKGROUND[=options] ]
[ /CACHE_TIMEOUT[=options] ]
[ /DATA=[options] ]
[ /FILEIDS[=options] ]
[ /[NO]FORCE ]
[ /GID=gid ]
[ /GROUP ]
[ /OWNER_UIC=n ]
[ /PROCESSOR=acp_option ]
[ /PROTECTION=protections ]
[ /RETRIES=n ]
[ /SERVER_TYPE=type ]
[ /SHARE ]
[ /[NO]SUPERUSER=uid ]
[ /TIMEOUT=OpenVMS_delta_time ]
[ /UID=uid ]
[ /USER=user ]
[ /[NO]WRITE ]




Local device (and optional directory tree) on which to mount the remote NFS file system. Specify this mount point as one of the following:


n Value from 0 to 9999. Specifying 0 causes the client to choose the next available unit number. (It does not mount a device named DNFS0:.)
[ dir] or
[ dir.subdir]
Directory to mount
(up to eight in addition to the [000000] directory)
file Individual file to mount


Type the device name (mount_point) immediately after the keyword MOUNT.


Optional. Default: First 12 characters of the combined values of /HOST and /PATH qualifiers.
ODS-2 volume label used for the remote path name.
You can use this qualifier to provide a unique volume label on a system where there is a conflict. The client:


Optional. Default: None.

Logical name associated with the volume.

The client creates the following logical definitions depending on what you specify.

The client places the logical name in the SYSTEM logical name table, unless you specify the /GROUP or /SHARE qualifier. The client deletes the logical name from the SYSTEM table when you dismount the volume. The process must have SYSNAM privilege to mount a system mount point. Without SYSNAM or GRPNAM privilege, the user must specify /SHARE for a JOB mount. (See the /SHARE qualifier for more information.)




Modifiable process parameters for the ancillary control process (ACP).

These parameters are dynamic. The NFS client applies your settings at each first start of an ACP.

For descriptions of these options, see the section on RUN (PROCESS) in the OpenVMS DCL Dictionary.

/ADF [ = { CREATE | UPDATE | USE } ]


Optional. Default: /ADF=CREATE.

If Attributes Data Files (ADFs) exist on the NFS server, the /ADF qualifier lets you use them.

The server uses ADFs to store OpenVMS file attributes. These files appear on the server as .$ADF$file files, but you cannot directly view them on the local client system.

The options mean:

/NOADF --- No ADFs are created.


Compaq strongly recommends that you do not use /ADF=UPDATE or /ADF=USE.


Optional. Defaults:
For the MOUNT command: No automounting
For the /AUTOMOUNT qualifier: /AUTOMOUNT=INACTIVITY:00:05:00
(5 minutes)

Automatically mounts a file system when you access its path name.

INACTIVITY=OpenVMS_delta_time means:

/BACKGROUND [= {DELAY:OpenVMS_delta_time | RETRY:n}]

Optional. Defaults:
For the MOUNT command: No background mode
For the /BACKGROUND qualifier: /BACKGROUND=(DELAY:00:00:30,RETRY:10)

Attempts the mount in background mode. If the first attempt fails, the NFS client retries the mount after the delay time has passed for a specified number of retries. The options mean:

[ DIRECTORY:OpenVMS_delta_time ] [ ATTRIBUTE:OpenVMS_delta_time ] [ READ_DIRECTORY ]

Optional. Defaults: /CACHE_TIMEOUT=(DIRECTORY:00:00:30,ATTRIBUTE:00:00:15)

Specifies the following caching timeout information for the mount point:



Optional. Default: /CONVERT.

Converts files with the following attributes to STREAM_LF files:

The convert feature works with some utilities and DCL commands, but not with others. For example, it works with the CREATE command and with EDIT/TPU. It does not work with COPY, BACKUP, or EDIT/EDT. There is no simple way to identify what works. However, for the feature to take effect, the following conditions must be satisfied:

You can convert only those files opened using RMS sequential access. For additional information, see the DIGITAL TCP/IP Services for OpenVMS Management manual.

/DATA [= {read_bytes | write_bytes}]

Optional. Default: /DATA=(8192,8192).

Largest amount of NFS data received or transmitted in one network operation. The options mean:

If you specify only one value, it applies to both READ and WRITE.


You do not need to use /DATA unless a remote NFS server imposes a restriction on data size. If the server requests a smaller transfer size than you specified, the server's requested value overrides the one you set.


Optional. Default: /FILEIDS=UNIQUE.

With UNIQUE, the client uses the file name and 32-bit NFS file ID when processing the directory information returned by the server to determine whether cached information is valid.

With NONUNIQUE, the client uses the file handle instead of the file ID. This can refresh directory entries in the client's cache more quickly. However, this can degrade performance since the client must issue additional RPC requests to get the file handle.



Optional. Default: /NOFORCE.

Performs an overmount or a mount that can cause file system occlusion.

Required privileges:


Optional. Default: --2.

Default GID if no GID mapping exists for file access.

Restriction: Requires OPER privileges.


Optional. Default: user-mounted.

Adds the logical name to the group logical name table. If the mount is the first one on the volume, /GROUP marks the volume as being group-mounted.




Remote NFS server on which the physical files reside. Type either domain-name or IP-address format.


Optional. Default: Ownership recorded on the volume.

UIC-assigned ownership of the volume while you mount it.

Applied only on the first mount of an NFS disk.



Path name on the NFS server (specified by /HOST). Must match an exported directory, subdirectory, or file of an exported file system on the server.

The /path/name is mounted as the Master File Directory (MFD) of the specified device.


Optional. Default: New ACP for each mount.

Associates an ancillary control process (ACP) to process the volume, overriding the default manner in which the client associates ACPs with NFS devices (starting a new ACP for each mount request). The options are:



Protection code for the volume. If you omit a category, the client denies access to that category of user.

Applied only on the first mount of an NFS device and ignored with subsequent mounts on that device.

Restrictions: Requires OPER privileges.


Optional. Default: /RETRIES=0 (the client retries the request forever or until the server responds).

Maximum number of read or write retries if the NFS server fails to respond.

/RETRIES=0 is a close equivalent to a UNIX hard mount. If you attempt to abort a command or program while it is still retrying the I/O operation on a client device, the process enters RWAST state and remains in that state until the NFS server responds. A process in RWAST state cannot be terminated. If the server does not become available, the only way remove the process without rebooting the client host is to dismount the client device with the /ALL qualifier.


Optional. Default: UNIX.

Operating system of the host running NFS server. The values for type are:

If the server is DIGITAL TCP/IP Services for OpenVMS Version V3.3 or later, this qualifier is ignored because the client and server always operate in OpenVMS to OpenVMS mode.


Places the logical name in the job logical name table and increments the volume mount count regardless of the number of job mounts. When the job logs out, all job mounts are dismounted, causing the volume mount count to be decremented. See the DIGITAL TCP/IP Services for OpenVMS Management manual for more information.



Optional. Default: /NOSUPERUSER.

Maps users with SYSPRV, BYPASS, or READALL privileges to the superuser UID. The NFS server must allow superuser access.

The normal superuser UID is 0.

/NOSUPERUSER: No mapping.


Optional. Default: System-mounted.

Places the logical name in the system logical name table unless you specify the /GROUP or /SHARE qualifier. The client deletes the logical name from the system table when you dismount the volume.



Optional. Default: ::01 (one second).

Previous Next Contents Index