Creates a UNIX file system with:

• An empty OpenVMS style root directory
• An empty local directory that corresponds to the UNIX root directory
• A container file in the OpenVMS style root directory

Applies to: NFS server

Format

CREATE CONTAINER device:directory [ /HOST=host ]
[ /[NO]LOG ]
[ /OWNER=[uic] ]
[ /ROOT_MODE=n ]
[ /SIZE=option=value ]
[ /UID=n ]
[ /USER_NAME=vms_user_name ]

restrictions

Requires:

• Read and write access to the specified device and directory.
• SYSPRV or BYPASS privilege.

Parameters

device:directory

Required.

Device and directory of the UNIX container.

Qualifiers

/HOST=host

Required. Default: None.

If the proxy database has multiple entries with the same user name and UID, the NFS server selects the entry specified with this qualifier.

/LOG

/NOLOG

Optional. Default: Displays host, UID, GID, and user name.

Displays a full description of the specified proxy database record for you to determine ownership (see /USER_NAME).

/OWNER=[uic]

Optional. Default: UIC in the selected proxy record.

OpenVMS ownership of the container file directory and container file.

(The other files in this directory are owned by the OpenVMS users whose proxy database entries correspond to the UNIX owner UIDs of the individual files.)

/ROOT_MODE=n

Optional. Default: 755 (provides the following protection for owner, group, and world rwx-rx-rx).

UNIX protection of the default container files: root directory, bit map, and superblock.

Specify octal values in the following order: for user, for group, for others. The values are:

• 0 --- No access
• 1 --- Execute access
• 2 --- Write access
• 3 --- Write and execute access
• 4 --- Read access
• 5 --- Read and execute access
• 6 --- Read and write access
• 7 --- Read, write, and execute access

For example, /ROOT_MODE=751 provides:

User	Read, write, and execute access	7	rwx
Group	Read and execute access	5	rx
Other	Execute access	1	x

/SIZE=option=value

Optional. Default: /SIZE=(INITIAL=8917,EXTEND=160,MAXIMUM=0).

Specifies the following file size attributes:

• INITIAL
  Specifies the initial size, in OpenVMS blocks, of the container. Maximum value: 8917.
• EXTEND
  When an extension is necessary, specifies the number of blocks by which the container is extended. Maximum value: 8192.

  Note Using large values might impact system performance and disk usage. In most cases, the default is sufficient.

• MAXIMUM
  Specifies the maximum size of the container.
  If the value is zero, the size of the container file can increase without limits.

/UID=n

Optional. Default: UID in the selected proxy record.

Specifies the owner of the UNIX container root directory.

/USER_NAME=vms_user_name

Required.

Specifies the user name of the owner of the container file system. The user name must be in the proxy database. The specified user becomes the owner of the internal root directory of the container.

Examples

TCPIP> CREATE CONTAINER DUCK$4:[DUCKLING] /HOST=MALLARD -
_TCPIP> /OWNER=[300,12] /ROOT_MODE=755 /UID=7015 -
_TCPIP> /USER_NAME=G_JONES
 
      

Creates container directory DUCK$4:[DUCKLING]. The local OpenVMS owner is [300,12]. Remote users see the root directory as owned by UID 7015. The root directory is writable only by UID 7015; it is readable and executable by all others. Before you execute this command, user G_JONES should have both an OpenVMS account with UIC [300,12] and an incoming proxy record specifying UID 7015 on host MALLARD.

Creates a directory within an existing UNIX container.

Applies to: NFS server

Related commands: DIRECTORY, REMOVE DIRECTORY

Format

CREATE DIRECTORY "/path/name" [ /HOST=host ]
[ /[NO]LOG ]
[ /MODE=n ]
[ /UID=n ]
[ /USER_NAME=vms_user_name ]

restrictions

Requires:

• Read and write access to the parent directory.
• SYSPRV or BYPASS privilege if you specify /USER_NAME with a name other than your own.

The container file system must be mapped with the MAP command.

Parameters

"/path/name"

Required.

Name of the directory you want to create.

Qualifiers

/HOST=host

Optional. Default: Uses the first user name found.

If the proxy database has multiple entries with the same user name and UID combination, the value of /HOST determines the specified record.

/LOG

/NOLOG

Optional. Default: Displays values for host, UID, GID, and user name.

Displays a full description of the specified proxy database record for you to determine ownership (see /USER_NAME).

/MODE=n

Optional. Default: 755 (provides the following protection for owner, group, and world: rwx-rx-rx).

UNIX protection of the new directory.

Specify octal values in the following order: for user, for group, for others. The values are:

• 0 --- No access
• 1 --- Execute access
• 2 --- Write access
• 3 --- Write and execute access
• 4 --- Read access
• 5 --- Read and execute access
• 6 --- Read and write access
• 7 --- Read, write, and execute access

For example, /MODE=751 provides:

User	Read, write, and execute access	7	rwx
Group	Read and execute access	5	rx
Other	Execute access	1	x

/UID=n

Optional. Default: None.

Entry in the proxy database that determines, if necessary, the ownership of the container root directory.

In the proxy database:

• UID and GID fields determine the root directory's UNIX identity.
• User name field determines the OpenVMS ownership.

Required to access an entry in the proxy database that lacks a unique UID, user name, and host combination.

You can use /UID with the /HOST and /USER_NAME qualifiers. If you do not have SYSPRV or BYPASS privilege, the values you specify must correspond to the values for your user name in the proxy database.

/USER_NAME=vms_user_name

Optional. Default: UID=0 and GID=1 (if you have SYSPRV or BYPASS privilege).

Selects an entry in the proxy database and creates the UID, GID, and OpenVMS UIC for the directory files.

To select a user name that has a UIC different than the UIC of the process running the management program, you need SYSPRV or BYPASS privilege.

You can use /USER_NAME in combination with /HOST and /UID. However, if you do not have SYSPRV or BYPASS privilege, the values you specify must correspond to the values for your user name in the proxy database.

Examples

TCPIP> MAP "/user" dua0:[group_a] 
TCPIP> CREATE DIRECTORY "/user/umbrella.bird"
      

Creates a UNIX directory for user UMBRELLA called umbrella.bird. In this example, the user UMBRELLA is running the TCP/IP Services management program from the directory ([UMBRELLA.BIRD]). The UIC for [UMBRELLA] is [340,6] and the TCPIP$PROXY entry is defined as follows:

User	UID	GID	Host
UMBRELLA	300	12	*
SYSTEM	0	1	*

If UMBRELLA does not have SYSPRV or BYPASS privilege, the directory is created as follows:

UID = 300
GID = 12
UIC = [340,6]

If UMBRELLA has SYSPRV or BYPASS privilege, the directory is created as follows:

UID = 0
GID = 1
UIC = [SYSTEM]

Creates an empty export database file.

If the logical name TCPIP$EXPORT is defined, CREATE EXPORT uses the definition to create the directory and file name for the export database. If TCPIP$EXPORT is not defined, the database is created as SYS$COMMON:[SYSEXE]TCPIP$EXPORT.DAT.

Related commands: ADD EXPORT, SHOW EXPORT

Applies to: NFS server

Format

CREATE EXPORT

restrictions

Requires write access to the directory with the export database.

Caution Do not execute this command unless you intend to reconfigure your entire cluster.

Examples

TCPIP> CREATE EXPORT
      

Creates an empty export database.

Creates a hosts database file with:

• One entry for LOCALHOST
• LOCALHOST's alias, localhost
• LOCALHOST's address, 127.0.0.1

If the logical name TCPIP$HOST is defined, CREATE HOST uses the definition to create the directory and file name for the hosts database. If TCPIP$HOST is not defined, the database is created as SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT.

Related commands: SET HOST, SHOW HOST, CONVERT/VMS HOST

Format

CREATE HOST

restrictions

Requires:

• Write access to the directory with the hosts database.
• Read and write access to the hosts database.

Caution Do not execute this command unless you intend to reconfigure your entire cluster.

Examples

TCPIP> CREATE HOST
      

Creates a hosts database with one entry for LOCALHOST.

Creates an empty networks database file.

If the logical name TCPIP$NETWORK is defined, CREATE NETWORK uses the definition to create the directory and file name for the networks database. If TCPIP$NETWORK is not defined, the database is created as SYS$COMMON:[SYSEXE]TCPIP$NETWORK.DAT.

Related commands: SET NETWORK, SHOW NETWORK, CONVERT/VMS NETWORK

Format

CREATE NETWORK

restrictions

Requires write access to the directory with the networks database.

Caution Do not execute this command unless you intend to reconfigure your entire cluster.

Examples

TCPIP> CREATE NETWORK
      

Creates an empty networks database.

Creates an empty proxy database file.

If the logical name TCPIP$PROXY is defined, CREATE PROXY uses the definition to create the directory and file name for the proxy database. If TCPIP$PROXY is not defined, the database is created as SYS$COMMON:[SYSEXE]TCPIP$PROXY.DAT.

Related commands: ADD PROXY, SHOW PROXY, CONVERT/VMS PROXY

Format

CREATE PROXY

restrictions

Requires write access to the directory with the proxy database.

Caution Do not execute this command unless you intend to reconfigure your entire cluster.

Examples

TCPIP> CREATE PROXY
      

Creates an empty proxy database.

Creates an empty permanent routes database file.

If the logical name TCPIP$ROUTE is defined, CREATE ROUTE uses the definition to create the directory and file name for the routes database. If TCPIP$ROUTE is not defined, the database is created as SYS$COMMON:[SYSEXE]TCPIP$ROUTE.DAT.

Related commands: SET ROUTE, SHOW ROUTE

Format

CREATE ROUTE

restrictions

Requires write access to the directory with the routes database.

Caution Do not execute this command unless you intend to reconfigure your entire cluster.

Examples

TCPIP> CREATE ROUTE
      

Creates an empty routes database file TCPIP$ROUTE.DAT in the directory SYS$COMMON:[SYSEXE].

Adds new mapping correspondence to the internal TCP/IP Services table. Use this command to add support for new communication controller devices that are added to an OpenVMS system after the latest release of TCP/IP Services is installed.

Related commands: LIST COMMUNICATION_CONTROLLER, DELETE COMMUNICATION_CONTROLLER, all INTERFACE commands

Format

DEFINE COMMUNICATION_CONTROLLER controller
/INTERNET_INTERFACE=character
/TYPE=options
[ /DESCRIPTION=text ]

Parameters

controller

Required.

Specifies the OpenVMS device name of the communication controller (as displayed by the DCL command SHOW DEVICE).

You must specify the controller. For examples of controllers with their corresponding device names, see the LIST COMMUNICATION_CONTROLLER command. See the Compaq TCP/IP Services for OpenVMS Management guide for more information.

Qualifiers

/DESCRIPTION=text

Optional. Default: None.

Specifies entry. For example, specify the device's name, such as DEFZA or DEUNA.

You can modify this value.

/INTERNET_INTERFACE=character

Required.

Specifies the first letter of the interface name. The second character of the two-character interface name is automatically assigned, depending on what you specify for the /TYPE qualifier. If you prefer a standard name, call your Compaq support representative. If a standard interface name is not important, you can use any unique alphabetic character for this first character.

/TYPE=options

Required.

Specifies the controller type and implies the second character of the interface name. You must specify one of the following: Ethernet, FDDI, PPP, Serial or Token_Ring. You can specify only one type at a time. If you specify Ethernet, then the implied second character of the interface name is E. If you specify FDDI, then the implied second character of the interface name is F. If you specify PPP, then the implied second character of the interface name is P. If you specify Serial, then the implied second character of the interface name is L. If you specify Token_Ring, then the implied second character of the interface name is T.

To change this definition, enter the following command:

Examples

TCPIP> DEFINE COMMUNICATION_CONTROLLERcontroller -   
_TCPIP> /TYPE=([NO]old_type,new_type)   
      

The old_type,new_type options are:

• CLUSTER
  • The interface can join an internet cluster. To do this, also issue SET INTERFACE /CLUSTER.
  • You can specify CLUSTER with a controller type, for example, /TYPE=(ETHERNET,CLUSTER).
• [NO]ETHERNET
• [NO]FDDI
• [NO]TOKEN_RING

TCPIP> DEFINE COMMUNICATION_CONTROLLER XE -   
_TCPIP> /INTERNET_INTERFACE=D /TYPE=(ETHERNET,CLUSTER) -   
_TCPIP> /DESCRIPTION=DEUNA   
  
      

Defines interface D as the OpenVMS device XE.

Deletes an entry for a communication controller from the configuration file.

Related commands: DEFINE COMMUNICATION_CONTROLLER, LIST COMMUNICATION_CONTROLLER

Format

DELETE COMMUNICATION_CONTROLLER [ controller ]
[ /[NO]CONFIRM ]
[ /INTERNET_INTERFACE=character ]

restrictions

Requires OPER privilege.

Parameters

controller

Optional. Default: All devices.

OpenVMS device name of the communication controller (as displayed by the DCL command SHOW DEVICE).

Specify the controller name that you entered with the DEFINE COMMUNICATION_CONTROLLER command.

Qualifiers

/INTERNET_INTERFACE=character

Optional. Default: All letters.

Deletes the specified letter (which represents the first letter of an interface name).

/CONFIRM

/NOCONFIRM

Optional. Default: /CONFIRM if you use a wildcard.

Displays a message asking you to confirm the delete request.

Examples

TCPIP> DELETE COMMUNICATION_CONTROLLER EZ   
      

Deletes all the entries for the Ethernet controller with device name EZ.

TCPIP> DELETE COMMUNICATION_CONTROLLER -   
_TCPIP /INTERNET_INTERFACE=E   
  
      

Deletes all the communication controller entries with an Internet interface name that begins with the letter E from the table used to match OpenVMS device names with Internet interface names.

Deletes a container file system and all its contents.

Applies to: NFS server

Related commands: CREATE CONTAINER, SHOW CFS

Format

DELETE CONTAINER container_file_system

restrictions

Wildcards are not allowed.

Requires both read and delete access to the directory.

Requires BYPASS privilege.

Parameters

container_file_system

Required.

Device and directory name of the container file (no wildcards).

The container file has file type .CONTAINER.

Examples

TCPIP> DELETE CONTAINER WORK1$:[DOVE.NEST_BUILDING]  
      

Deletes the container directory WORK1$:[DOVE.NEST_BUILDING] along with the container file, all subdirectories, and files.