DIGITAL TCP/IP Services for OpenVMS
Management Command Reference

LIST COMMUNICATION_CONTROLLER

Displays the communication controllers known to DIGITAL TCP/IP Services for OpenVMS.
Related commands: DEFINE COMMUNICATION_CONTROLLER, DELETE COMMUNICATION_CONTROLLER

Format

LIST COMMUNICATION_CONTROLLER [ controller ] [ /INTERNET_INTERFACE=character ]

restrictions

Requires OPER privileges.

Parameters

controller
Optional. Default: All devices.
Displays the specified OpenVMS device name.
Specify a 2-letter name that you entered with the DEFINE COMMUNICATION_CONTROLLER command.

Qualifiers

/INTERNET_INTERFACE=character
Optional. Default: All letters.
Displays entries with the specified letter, which represents the first letter of an interface name.

Examples

#1
TCPIP> LIST COMMUNICATION_CONTROLLER Communication Controller Configuration Controller: LO Internet Interface: L Description: Type: LOCAL Controller: WI Internet Interface: W Description: Type: WIRELESS Controller: EC Internet Interface: C Description: Type: CLUSTER ETHERNET Controller: XE Internet Interface: D Description: Type: CLUSTER ETHERNET Controller: EF Internet Interface: F Description: 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 Description: Type: CLUSTER FDDI Controller: FC Internet Interface: C Description: Type: CLUSTER FDDI Controller: IC Internet Interface: C Description: Type: CLUSTER TOKEN_RING Controller: IR Internet Interface: R Description: Type: CLUSTER TOKEN_RING Controller: SL Internet Interface: S Description: Type: SERIAL Controller: CL Internet Interface: I Description: ATM Classical IP Type: FDDI TCPIP>

TCPIP> LIST COMMUNICATION_CONTROLLER  
  
                    Communication Controller Configuration  
 
Controller:  LO   Internet Interface:  L 
                         Description: 
                                Type:  LOCAL 
 
Controller:  WI   Internet Interface:  W 
                         Description: 
                                Type:  WIRELESS 
 
Controller:  EC   Internet Interface:  C 
                         Description: 
                                Type:  CLUSTER ETHERNET 
 
Controller:  XE   Internet Interface:  D 
                         Description: 
                                Type:  CLUSTER ETHERNET 
 
Controller:  EF   Internet Interface:  F 
                         Description: 
                                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 
                         Description: 
                                Type:  CLUSTER FDDI 
 
Controller:  FC   Internet Interface:  C 
                         Description: 
                                Type:  CLUSTER FDDI 
 
Controller:  IC   Internet Interface:  C 
                         Description: 
                                Type:  CLUSTER TOKEN_RING 
 
Controller:  IR   Internet Interface:  R 
                         Description: 
                                Type:  CLUSTER TOKEN_RING 
 
Controller:  SL   Internet Interface:  S 
                         Description: 
                                Type:  SERIAL 
 
 
Controller:  CL   Internet Interface:  I 
                         Description:  ATM Classical IP 
                                Type:  FDDI 
 
 
TCPIP>

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

LOOP

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

Format

LOOP [ host ]
[ /ALL ]
[ /NUMBER_PACKETS=n ]
[ /PACKET_SIZE=n ]
[ /[NO]ROUTE ]

restrictions

Requires OPER privileges.

Parameters

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

Qualifiers

/ALL
Optional. Default: Not all requests.
Displays all ICMP ECHO_REQUESTs, even if not in direct response to this operation.
/NUMBER_PACKETS=n
Optional. Default: 1 per second.
Number of packets to send.
/PACKET_SIZE=n
Optional. Default: 64 bytes.
Size of the ICMP ECHO_REQUEST.
/ROUTE

/NOROUTE
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.

Examples

#1
TCPIP> LOOP thrush

Tests the connectivity path to UNIX host thrush.

#2
TCPIP> LOOP

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

#3
TCPIP> LOOP /NOROUTE thrush

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

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 style 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:

Map the file system.
Export the file system (add an entry in the export database).
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 and GENERATE MAP.
Related commands: SHOW MAP, UNMAP

Format

MAP "file system name" logical_file_system

restrictions

Requires SYSPRV and BYPASS privileges.

Parameters

"file system name"
Required.
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.
logical_file_system
Required.
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:[vms.directory.name]

Examples

#1
TCPIP> 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> MAP "/remote" VERDIN$DUA3: TCPIP> 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.)

MOUNT

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:

Required order of command keywords: the MOUNT keyword, immediately followed by mount_point. Example: MOUNT DNFS01:
For the qualifiers that require a time value, specify OpenVMS delta time.
Whenever you specify multiple options and values, use the following syntax:
/qualifier=(option_a:value1,option_b:value2,value3)

Format

MOUNT mount_point [ volume_label ] [ logical_name ]
[ /HOST=host ]
[ /PATH="/path/name" ]
[ /ACP_PARAMS=options ]
[ /[NO]ADF[=option] ]
[ /AUTOMOUNT[=INACTIVITY:time] ]
[ /BACKGROUND[=options] ]
[ /CACHE_TIMEOUT[=options] ]
[ /[NO]CONVERT ]
[ /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 ]
[ /SYSTEM ]
[ /TIMEOUT=OpenVMS_delta_time ]
[ /UID=uid ]
[ /USER=user ]
[ /[NO]WRITE ]

Parameters

mount_point
Required.
Local device (and optional directory tree) on which to mount the remote NFS file system. Specify this mount point as one of the following:
DNFSn: DNFSn:[dir.subdir] DNFSn:[dir.subdir]file
where:

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

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

volume_label
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:

Accepts only the first 12 characters for all other entries.
Applies volume_label only on the first mount of a particular disk.
Ignores volume_label with subsequent mounts on that disk.

logical_name
Optional. Default: None.
Logical name associated with the volume.
The client creates the following logical definitions depending on what you specify.
If you mount DNFSn:[000000], the client defines the logical name as DNFSn:
If you mount DNFSn:[dir.dir], the client defines the logical name as DNFSn:[dir.dir.] The extra dot allows for relative directory specifications. If you issue
$ SET DEFAULT logical:[subdir]
the full default definition becomes:
DNFSn:[dir.dir.subdir]
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.)

Qualifiers

/ACP_PARAMS=
{ BUFFER_LIMIT=n DUMP IO_DIRECT=n IO_BUFFERED=n MAX_WORKSET=pages PAGE_FILE=file PRIORITY=base-priority WORKSET=pages }
Optional.
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 } ]

/NOADF
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:

CREATE
The client uses and updates the ADFs, and creates ADFs for new files.
UPDATE
The client uses and updates the ADFs.
USE
The client uses the ADFs.

/NOADF --- No ADFs are created.

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

/AUTOMOUNT[=INACTIVITY:time]
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:

Optional.
Maximum inactive period for the mount attempt.
When this inactive period expires, the NFS client dismounts the path name.
Specify time as hh:mm:ss.

/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:
DELAY:OpenVMS_delta_time

Maximum delay period you can specify is approximately 49 days.
Specify OpenVMS_delta_time as hh:mm:ss.
RETRY:n

Number of attempts, if the first try fails, that the client makes to mount in background mode.
RETRY:0 means that the client uses the first try only.

Note
If you use the /BACKGROUND qualifier, Compaq strongly recommends that you also use the /RETRIES qualifier specifying a non-zero value. For example,

$ TCPIP MOUNT DNFS0: /BACKGROUND=RETRY:9 /RETRIES=4 /HOST="robin" - _$ /PATH="/USR/USERS/GEORGE"

In this example, you are asking for four data retries on each mount attempt and nine mount attempts, for 36 tries in all. If you use the default value for /RETRIES, the first mount attempt can never complete except by succeeding, and the process doing the mount will hang until the server becomes available.
/CACHE_TIMEOUT=
[ 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:

DIRECTORY:OpenVMS_delta_time

Amount of time that the client waits between rereading a directory's status or contents.
Specify OpenVMS_delta_time as hh:mm:ss.

ATTRIBUTE:OpenVMS_delta_time

Amount of time that the client waits between rereading a file's attributes from the NFS server.
Specify OpenVMS_delta_time as hh:mm:ss.

READ_DIRECTORY

Forces the client to read the contents of the directory requested when the cache timeout occurs rather than relying on the directory's modified time.
By reading the directory contents, the client can be aware of any changes to the number of files within the directory even if the directory's modify time was not updated.

/CONVERT

/NOCONVERT
Optional. Default: /CONVERT.
Converts files with the following attributes to STREAM_LF files:

Sequential
Variable-length
Carriage return carriage control (VAR-CR)

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:

The file attributes must be sequential, variable length, and carriage return carriage control.
The file must be opened for exclusive write access (generally true for newly created files).
The file must be opened with the FAB$M_SQO bit set in the FAB$L_FOP field.
The file creation and the open for write must be done in one step. That is, if the program first creates the file and afterwards opens it for write, the convert feature does not work.

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:

read_bytes --- Data received. Minimum value = 512.
write_bytes --- Data transmitted. Minimum value = 512.

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

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

/FILEIDS [= {UNIQUE | NONUNIQUE}]
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.
/FORCE

/NOFORCE
Optional. Default: /NOFORCE.
Performs an overmount or a mount that can cause file system occlusion.
Required privileges:

OPER
Overmounting a /SYSTEM mount requires SYSPRV privileges.
Overmounting a /GROUP mount requires GRPNAM privileges.

/GID=n
Optional. Default: --2.
Default GID if no GID mapping exists for file access.
Restriction: Requires OPER privileges.
/GROUP
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.
Restrictions:

Requires GRPNAM privileges.
/GROUP and /SYSTEM are mutually exclusive.

/HOST=host
Required.
Remote NFS server on which the physical files reside. Type either domain-name or IP-address format.
/OWNER_UIC=n
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="/path/name"
Required.
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.
/PROCESSOR= {UNIQUE | SAME:DNFSn: | FILE:file}
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:

UNIQUE

Creates a new ACP for the new NFS device.
Requires OPER privileges.

SAME:DNFSn:

Uses the same ACP as the specified device.
Requires OPER privileges.

FILE:file

Creates a new ACP running the image specified by file. Do not use wildcards, host names, or directory names.
Requires CMKRNL or OPER privileges.

/PROTECTION=protections
Optional. Default: /PROTECTION=(S:RWED,O:RWED,G:RWED,W:RWED).
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.
/RETRIES=n
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.
/SERVER_TYPE=type
Optional. Default: UNIX.
Operating system of the host running NFS server. The values for type are:

UNIX
IBM_VM

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.
/SHARE
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.
/SUPERUSER=uid

/NOSUPERUSER
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.
/SYSTEM
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.
Restrictions:

Requires SYSNAM privileges.
The /GROUP, /SYSTEM, and /SHARE qualifiers are mutually exclusive.
Without SYSNAM or GRPNAM privilege, you must use /SHARE for a job mount.

/TIMEOUT=OpenVMS_delta_time
Optional. Default: ::01 (one second).

Previous Next Contents Index

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

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

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

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

DIGITAL TCP/IP Services for OpenVMSManagement Command Reference

LIST COMMUNICATION_CONTROLLER

Format

LIST COMMUNICATION_CONTROLLER [ controller ] [ /INTERNET_INTERFACE=character ]

restrictions

Parameters

controller

Qualifiers

/INTERNET_INTERFACE=character

Examples

LOOP

Format

LOOP [ host ] [ /ALL ] [ /NUMBER_PACKETS=n ] [ /PACKET_SIZE=n ] [ /[NO]ROUTE ]

restrictions

Parameters

host

Qualifiers

/ALL

/NUMBER_PACKETS=n

/PACKET_SIZE=n

/ROUTE

/NOROUTE

Examples

MAP

Format

MAP "file system name" logical_file_system

restrictions

Parameters

"file system name"

logical_file_system

Examples

MOUNT

restrictions and tips

Format

Parameters

mount_point

volume_label

logical_name

Qualifiers

/ACP_PARAMS= { BUFFER_LIMIT=n DUMP IO_DIRECT=n IO_BUFFERED=n MAX_WORKSET=pages PAGE_FILE=file PRIORITY=base-priority WORKSET=pages }

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

/NOADF

/AUTOMOUNT[=INACTIVITY:time]

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

/CACHE_TIMEOUT= [ DIRECTORY:OpenVMS_delta_time ] [ ATTRIBUTE:OpenVMS_delta_time ] [ READ_DIRECTORY ]

/CONVERT

/NOCONVERT

/DATA [= {read_bytes | write_bytes}]

/FILEIDS [= {UNIQUE | NONUNIQUE}]

/FORCE

/NOFORCE

/GID=n

/GROUP

/HOST=host

/OWNER_UIC=n

/PATH="/path/name"

/PROCESSOR= {UNIQUE | SAME:DNFSn: | FILE:file}

/PROTECTION=protections

/RETRIES=n

/SERVER_TYPE=type

/SHARE

/SUPERUSER=uid

/NOSUPERUSER

/SYSTEM

/TIMEOUT=OpenVMS_delta_time

DIGITAL TCP/IP Services for OpenVMS
Management Command Reference

LOOP [ host ]
[ /ALL ]
[ /NUMBER_PACKETS=n ]
[ /PACKET_SIZE=n ]
[ /[NO]ROUTE ]

/ACP_PARAMS=
{ BUFFER_LIMIT=n DUMP IO_DIRECT=n IO_BUFFERED=n MAX_WORKSET=pages PAGE_FILE=file PRIORITY=base-priority WORKSET=pages }

/CACHE_TIMEOUT=
[ DIRECTORY:OpenVMS_delta_time ] [ ATTRIBUTE:OpenVMS_delta_time ] [ READ_DIRECTORY ]