HP OpenVMS Systems Documentation

Creates the BOOTP database file, using the file name and location specified by the logical name TCPIP$BOOTP. If the logical name is not defined, creates the database file in your current directory as TCPIP$BOOTP.DAT.

Related commands: CONVERT/VMS BOOTP, SET BOOTP

Format

CREATE BOOTP

restrictions

Requires write access to the directory with the BOOTP configuration database.

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

Examples

TCPIP> CREATE BOOTP
      

Creates an empty BOOTP database.

Creates the configuration database file, using the file name and location specified by the logical name TCPIP$CONFIGURATION. If the logical name is not defined, creates the database file in your current directory as TCPIP$CONFIGURATION.DAT.

Format

CREATE CONFIGURATION

restrictions

Requires write access to the directory with the configuration database.

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

Examples

TCPIP> CREATE CONFIGURATION
      

Creates an empty configuration database.

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

CONTAINER command) 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 the export database file, using the file name and location specified by the logical name TCPIP$EXPORT. If the logical name is not defined, creates the database file in your current directory as 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

The hosts database file name and location are specified by the logical name TCPIP$HOST. If the logical name is not defined, the database file name will be TCPIP$HOST.DAT in your current directory.

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 the networks database file, using the file name and location specified by the logical name TCPIP$NETWORK. If the logical name is not defined, creates the database file in your current directory as 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 the proxy database file, using the file name and location specified by the logical name TCPIP$PROXY. If the logical name is not defined, creates the database file in your current directory as 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 the routes database file, using the file name and location specified by the logical name TCPIP$ROUTE. If the logical is not defined, creates the database file named TCPIP$ROUTE.DAT in your current directory.

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.

Defines the mapping between a communication controller device and its corresponding Internet interface. Each mapping or controller definition is stored as a record in the configuration database.

To modify an existing controller definition, you must delete the old controller definition from the configuration database (using the DELETE COMMUNICATION_CONTROLLER command) and then define the new controller definition (using the DEFINE COMMUNICATION_CONTROLLER command).

Internet devices are uniquely identified using 2-character names. The first character is determined by the /INTERNET_INTERFACE qualifier. The second character is determined by the controller type you specify with the /TYPE qualifier, as follows:

Controller Type	Second Character of Interface Name
ETHERNET	E
FDDI	F
PPP	P
SERIAL	L
TOKEN_RING	T

For example, with the following command, the communication controller EW maps to the interface WE:

TCPIP> DEFINE COMMUNICATION_CONTROLLER EW - _TCPIP> /INTERNET_INTERFACE=W /TYPE=ETHERNET

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

Format

DEFINE COMMUNICATION_CONTROLLER controller
[ /DESCRIPTION=text ]
/INTERNET_INTERFACE=character
/TYPE=(option[,...])

Parameters

controller

Required.

Specifies the OpenVMS device name of the communication controller (as displayed by the DCL command SHOW DEVICE) to be mapped to an Internet interface. For examples of communication controllers with their corresponding Internet interfaces, refer to the LIST COMMUNICATION_CONTROLLER command. For more information on configuring network interfaces, refer to the HP TCP/IP Services for OpenVMS Management manual.

Qualifiers

/DESCRIPTION=text

Optional. Default: None.

Optional text describing the communication controller.

/INTERNET_INTERFACE=character

Required.

Specifies the first character of the Internet interface name. If you prefer using a standard name, call your HP support representative.

/TYPE=(option[,...])

Required.

Specifies the communication controller type and cluster attribute. You must specify one of the following communication controller types: ETHERNET, FDDI, PPP, SERIAL, or TOKEN_RING.

Optionally, specify the CLUSTER attribute to indicate that the interface can join an Internet cluster. To enable a cluster alias (alias host identifier) with an interface, use the SET INTERFACE /CLUSTER command.

Examples

TCPIP> DEFINE COMMUNICATION_CONTROLLER ES -
_TCPIP> /INTERNET_INTERFACE=S /TYPE=(ETHERNET,CLUSTER) -
_TCPIP> /DESCRIPTION="DESVA-Class Ethernet Adapter"

      

Defines the OpenVMS device ES as the Internet interface SE, which can join an Internet cluster.

Deletes communication controller definitions from the configuration database.

Related commands: DEFINE COMMUNICATION_CONTROLLER, LIST COMMUNICATION_CONTROLLER

Format

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

restrictions

Requires OPER privilege.

Parameters

controller

Required.

Specifies the OpenVMS device name of the communication controller.

Qualifiers

/CONFIRM

/NOCONFIRM

Optional. Default: /CONFIRM if you use wildcards; otherwise, /NOCONFIRM.

If you specify the /CONFIRM qualifier, a message displays asking you to confirm the delete request. Respond to the CONFIRM: prompt by entering one of the following:

• Y to delete the entry
• N to retain the entry

If you specify the /NOCONFIRM qualifier, the operation is performed without asking you to confirm the request.

/INTERNET_INTERFACE=character

Optional. Default: All alphabetic characters.

Specifies the first character of the Internet interface name of communication controller definitions to delete from the configuration database.

Examples

TCPIP> DELETE COMMUNICATION_CONTROLLER EZ
      

Deletes from the configuration database the communication controller definition corresponding to the OpenVMS device EZ.

TCPIP> DELETE COMMUNICATION_CONTROLLER * -
_TCPIP> /INTERNET_INTERFACE=W

      

Deletes all the communication controller definitions having an Internet interface name that begins with the letter W.