1 – BOOTP
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
1.1 – 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.
1.2 – Examples
1.TCPIP> CREATE BOOTP
Creates an empty BOOTP database.
2 – CONFIGURATION
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
2.1 – 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.
2.2 – Examples
1.TCPIP> CREATE CONFIGURATION
Creates an empty configuration database.
3 – CONTAINER
Creates a UNIX file system with:
o An empty OpenVMS style root directory
o An empty local directory that corresponds to the UNIX root
directory
o 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 ]
3.1 – Restrictions
Requires:
o Read and write access to the specified device and directory.
o SYSPRV or BYPASS privilege.
3.2 – Parameters
device:directory
CONTAINER command)
Required.
Device and directory of the UNIX container.
3.3 – Qualifiers
3.3.1 /HOST
/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.
3.3.2 /LOG
/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).
3.3.3 /OWNER
/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.)
3.3.4 /ROOT_MODE
/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:
o 0 - No access
o 1 - Execute access
o 2 - Write access
o 3 - Write and execute access
o 4 - Read access
o 5 - Read and execute access
o 6 - Read and write access
o 7 - Read, write, and execute access
For example, /ROOT_MODE=751 provides:
User Read, write, and 7 rwx
execute access
Group Read and execute 5 rx
access
Other Execute access 1 x
3.3.5 /SIZE
/SIZE=option=value
Optional. Default: /SIZE=(INITIAL=8917,EXTEND=160,MAXIMUM=0).
Specifies the following file size attributes:
o INITIAL
Specifies the initial size, in OpenVMS blocks, of the
container. Maximum value: 8917.
o 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.
o MAXIMUM
Specifies the maximum size of the container.
If the value is zero, the size of the container file can
increase without limits.
3.3.6 /UID
/UID=n
Optional. Default: UID in the selected proxy record.
Specifies the owner of the UNIX container root directory.
3.3.7 /USER_NAME
/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.
3.4 – Examples
1.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.
4 – DIRECTORY
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 ]
4.1 – Restrictions
Requires:
o Read and write access to the parent directory.
o 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.
4.2 – Parameters
"/path/name"
Required.
Name of the directory you want to create.
4.3 – Qualifiers
4.3.1 /HOST
/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.
4.3.2 /LOG
/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).
4.3.3 /MODE
/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:
o 0 - No access
o 1 - Execute access
o 2 - Write access
o 3 - Write and execute access
o 4 - Read access
o 5 - Read and execute access
o 6 - Read and write access
o 7 - Read, write, and execute access
For example, /MODE=751 provides:
User Read, write, and 7 rwx
execute access
Group Read and execute 5 rx
access
Other Execute access 1 x
4.3.4 /UID
/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:
o UID and GID fields determine the root directory's UNIX
identity.
o 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.
4.3.5 /USER_NAME
/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.
4.4 – Examples
1.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]
5 – EXPORT
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
5.1 – 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.
5.2 – Examples
1.TCPIP> CREATE EXPORT
Creates an empty export database.
6 – HOST
Creates a hosts database file with:
o One entry for LOCALHOST
o LOCALHOST's alias, localhost
o 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
6.1 – Restrictions
Requires:
o Write access to the directory with the hosts database.
o Read and write access to the hosts database.
CAUTION
Do not execute this command unless you intend to reconfigure
your entire cluster.
6.2 – Examples
1.TCPIP> CREATE HOST
Creates a hosts database with one entry for LOCALHOST.
7 – NETWORK
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
7.1 – 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.
7.2 – Examples
1.TCPIP> CREATE NETWORK
Creates an empty networks database.
8 – PROXY
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
8.1 – 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.
8.2 – Examples
1.TCPIP> CREATE PROXY
Creates an empty proxy database.
9 – ROUTE
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
9.1 – 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.
9.2 – Examples
1.TCPIP> CREATE ROUTE
Creates an empty routes database.