1 – EXPORT
Adds an export entry, in the form of a UNIX path name, to the
export database for a Network File System (NFS) file system. The
path name is a name that is mapped to one of the following:
o An OpenVMS disk
o A subdirectory on an OpenVMS disk
o A UNIX container file system
Related commands: MAP, REMOVE EXPORT, SET CONFIGURATION MAP, SHOW
EXPORT, SHOW HOST
Applies to: NFS server
Format
ADD EXPORT "/path/name"
/HOST=host
[ /OPTIONS=
{ CASE_BLIND|CASE_SENSITIVE }
[NO]DATA_CONVERSION
[NO]NAME_CONVERSION
[NO]PURGE_VERSIONS
[NO]TYPELESS_DIRECTORIES ]
1.1 – Restrictions and Tips
This command requires read and write access to the export
database. The following restrictions and instructions apply:
o Do not use wildcards within a UNIX directory specification.
o For each host, define both its host name and any alias names.
o For each entry, use uppercase and lowercase consistently.
o If you remove an export entry and replace the entry using
different options; each client must dismount and remount for
the new options to take effect.
1.2 – Parameters
"/path/name"
Required.
File system to add to the export database.
Separate directory and subdirectory names with slashes.
If the TYPELESS-DIRECTORIES option is set and the path name is
mapped to an OpenVMS ODS-5 disk volume, omit the file extension
.DIR from the directory name used in the path name. For example,
specify the path name for directory dove.dir;1 as dove, as in the
following command line:
ADD EXPORT "/white/dove"
If TYPELESS_DIRECTORIES is not set (the default is NOTYPELESS_
DIRECTORIES), then specify the path name for directory dove.dir;1
as dove.dir.
1.3 – Qualifiers
1.3.1 /HOST
/HOST=host
Required.
The NFS client host or hosts that will have access to the
specified NFS file system.
You can use a wildcard to allow access to all hosts.
1.3.2 /OPTIONS
/OPTIONS= { { CASE_BLIND|CASE_SENSITIVE } |[NO]DATA_CONVERSION
|[NO]NAME_CONVERSION |[NO]PURGE_VERSIONS |[NO]TYPELESS_
DIRECTORIES }
Optional.
NOTE
For clients operating in OpenVMS to OpenVMS mode, the
server ignores the options in the export record and uses
the settings required for OpenVMS to OpenVMS mode.
Options for the specified directory:
o CASE_BLIND, CASE_SENSITIVE
- CASE_BLIND (default)
The NFS server ignores the case of file names when looking
up files.
- CASE_SENSITIVE
The NFS server is case-sensitive when looking up files.
For example, NFS would preserve the case in the file names
AaBBc.TXT and AABBC.TXT, regarding them as two different
files.
o DATA_CONVERSION, NODATA_CONVERSION
- DATA_CONVERSION (default)
Converts the following kinds of sequential files:
* Variable
* Variable with fixed-length control (VFC)
* Fixed-record formats
Converts sequential files according to the rules applied by
the following record attributes:
* Carriage return/carriage control (CR)
* Fortran carriage control (FTN)
* Print file-format control (PRN)
Stream formats are returned unconverted.
The data in files with nonstream records cannot be written
back to the file.
- NODATA_CONVERSION
File data is considered raw and is returned without
conversion. Nonstream records are returned with their
record control information mixed with the record data.
Files can be rewritten randomly.
o NAME_CONVERSION, NONAME_CONVERSION
- NAME_CONVERSION
A non-OpenVMS client can create files with mixed-case
names and names containing characters that are invalid
for OpenVMS file names. The server converts such names to
valid OpenVMS file names, and reverses the conversion when
displaying the file names to a non-OpenVMS client.
- NONAME_CONVERSION (default)
Clients can only create files with valid OpenVMS names.
The server performs case-insensitive lookups and displays
directories in lowercase.
o PURGE_VERSIONS, NOPURGE_VERSIONS
Default: NOPURGE_VERSIONS
Deletes multiple versions of files. (The NFS CREATE and RENAME
calls can create multiple versions. The NFS READDIR call can
sense multiple versions.)
o TYPELESS_DIRECTORIES, NOTYPELESS_DIRECTORIES
- TYPELESS_DIRECTORIES
Removes .dir.1 from the name of directories. A naming
conflict could arise if, for example, two files exist in
the parent directory:
DOVE.;1 (regular file)
DOVE.DIR;1 (directory file)
The name of the regular file is returned as dove., rather
than dove, if a file and a conflicting directory exist.
- NOTYPELESS_DIRECTORIES (default)
Returns names as file.ext and file.dir.
1.4 – Examples
1.TCPIP> ADD EXPORT "/gold/finch" /HOST=GOLD
Adds the name of UNIX directory /gold/finch to the export
database and gives NFS client users on the remote host gold
access to this directory.
2.TCPIP> ADD EXPORT "/gold/finch" /HOST=(PURPLE,FINCH)
Adds the directory /gold/finch to the export database and gives
NFS client users on multiple remote hosts (PURPLE and FINCH)
access to this directory.
2 – PROXY
Adds entries to the proxy database that give remote users an
OpenVMS identity (account name). Applies to the NFS server, NFS
client, PC-NFS, RSH, LPR/LPD, and customer-developed services.
The proxy database contains communication proxies and NFS
proxies:
o Communication proxy
- Provides an identity for users of RSH, RLOGIN,
REXEC, RMT/RCD, LPR/LPD, and customer-written
services, if these services are marked with
SET SERVICE /FLAGS=APPLICATION_PROXY.
NOTE
The ROOT account does not require a communication
proxy in the proxy database. The /FLAGS=APPLICATION_
PROXY flag, therefore, is not relevant when you are
setting up a communication proxy for a UNIX root
account.
- Required qualifiers: /HOST, /REMOTE_USER.
o NFS proxy
- Provides an identity for users of NFS client, NFS server,
PC-NFS. No two proxies can have the same UID and host
combination.
- Required qualifiers: /HOST, /GID, /UID.
You can combine NFS and communication proxies in one record.
Related commands: SHOW HOST, DCL command AUTHORIZE, CONVERT/VMS
PROXY, REMOVE PROXY, SHOW PROXY
Format for Communication Proxies
ADD PROXY user { /HOST=host | /REMOTE_USER=user }
[ /PERMANENT ]
Format for NFS Proxies
ADD PROXY user { /GID=n | /HOST=host | /UID=n }
[ /NFS=options ]
[ /PERMANENT ]
2.1 – Restrictions and Tips
Requires read and write access to the proxy database and one of
the following privileges:
o SYSPRV
o SYSLCK
o OPER
For each host, define both its host name and alias names.
For each entry, use uppercase and lowercase consistently.
2.2 – Parameters
user
Required.
Local OpenVMS identity for the user of: NFS server, NFS client,
PC-NFS, remote shell, or LPR/LPD.
2.3 – Qualifiers
2.3.1 /GID
/GID=n
Required for an NFS proxy.
Group identifier (GID) for an NFS user.
Wildcards not allowed.
2.3.2 /HOST
/HOST=host
Required.
Host name on which the NFS user is working.
o The host must be seen on the SHOW HOST/LOCAL display. It is
important to use the SHOW HOST command to verify that the host
is known to TCP/IP Services because ADD PROXY does not do this
check.
o A wildcard is allowed.
o HP recommends that you define both the host name and any alias
names.
2.3.3 /NFS
/NFS=[ INCOMING | OUTGOING ]
Optional. Default: /NFS=(INCOMING,OUTGOING).
Creates an NFS proxy for local clients, remote clients, or PC-NFS
clients. Specify one of the following:
o /NFS=OUTGOING - Proxy to use NFS client
o /NFS=INCOMING - Proxy to use NFS server
o /NFS=(OUTGOING,INCOMING) - Proxy to use both NFS server and
NFS client
2.3.4 /PERMANENT
Optional. Default: Both permanent and volatile databases.
Adds the entry only to the permanent proxy database.
o Communication proxy
- If REMOTE_USER is not active, changes are made to the
permanent database.
- If REMOTE_user is active, changes to the permanent database
take effect after you restart RSH, RLOGIN, or LPD.
2.3.5 /REMOTE_USER
/REMOTE_USER=user
Required for a communication proxy. Not valid on NFS proxy.
Specifies the remote client's user name.
A wildcard is allowed.
2.3.6 /UID
/UID=n
Required for an NFS proxy.
Specifies the user identifier (UID) for an NFS user.
Wildcards are not allowed.
2.4 – Examples
1.TCPIP> ADD PROXY HAWAIIAN_GOOSE /NFS=(OUTGOING,INCOMING) -
_TCPIP> /GID=10 /UID=444 /HOST="nene"
Creates a proxy called HAWAIIAN_GOOSE, authorizing use of both
the NFS client and the NFS server to and from host nene.
2.TCPIP> ADD PROXY COUSINS /GID=10 /UID=40 /NFS=OUTGOING -
_TCPIP> /HOST=("grackle","blackbird")
Enters an NFS proxy called COUSINS for a local NFS client
user named COUSINS. This user can access remote files from
NFS servers grackle and blackbird.
3.TCPIP> ADD PROXY REMOTE_UGLY_DUCKLING -
_TCPIP> /REMOTE_USER="cygnet" /HOST="babyswan"
Adds to the proxy database communication proxy
REMOTE_UGLY_DUCKLING for remote user cygnet at host babyswan.