HomeNewsAcademicAdministrativeSystemsSuny Links
CornerAcademic Support ITEC HomeCorner
Space
[OpenVMS documentation]
[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
Updated: 24 May 2001

DIGITAL TCP/IP Services for OpenVMS
Management Command Reference


Previous Contents Index

1.1.4 Adding and Deleting Records

To add and delete records from the DIGITAL TCP/IP Services for OpenVMS databases, use the CONVERT, ADD, and REMOVE management commands.

The DIGITAL TCP/IP Services for OpenVMS management program provides three kinds of CONVERT commands:

  • CONVERT/CONFIGURATION BIND
    Converts BIND configuration information to BIND 8.1 format.
  • CONVERT/VMS
    Populates a DIGITAL TCP/IP Services for OpenVMS database with entries from a UNIX database file.
  • CONVERT/UNIX
    Reads a DIGITAL TCP/IP Services for OpenVMS database and converts the information to a UNIX-formatted (sequential) database file.

The following commands add records to and delete records from the proxy and export databases:

  • ADD EXPORT, REMOVE EXPORT
  • ADD PROXY, REMOVE PROXY

You cannot modify information that you enter into databases with ADD commands. Instead, delete the record with REMOVE and then issue a new ADD.

1.1.5 Starting and Stopping Software

You can interactively start and stop software components with the following commands:

  • START MAIL
  • STOP MAIL
  • START ROUTING
  • STOP ROUTING

For example:


TCPIP> START ROUTING /SUPPLY  

For the server components that are started by the auxiliary server upon an incoming client request, the ENABLE SERVICE command tells the auxiliary server to listen for requests and act upon them.

The DISABLE SERVICE command tells the auxiliary server to stop listening for incoming requests.

The following commands set components to start when DIGITAL TCP/IP Services for OpenVMS starts up. The permanent configuration is stored in the configuration database.

  • SET CONFIGURATION ENABLE SERVICE, SET CONFIGURATION ENABLE NOSERVICE
  • SET CONFIGURATION START ROUTING, SET CONFIGURATION START NOROUTING

1.1.6 Validating Data Integrity

The following commands verify the integrity of DIGITAL TCP/IP Services for OpenVMS files:

  • ANALYZE CONTAINER
  • ANALYZE MAIL
  • ANALYZE SERVICE

1.1.7 Managing NFS

The NFS server requires the following management commands:

  • MAP, SET CONFIGURATION MAP
  • SHOW MAP, SHOW CONFIGURATION MAP
  • UNMAP, SET CONFIGURATION NOMAP
  • GENERATE MAP
  • SET NFS_SERVER, SHOW NFS_SERVER
  • CREATE EXPORT, ADD EXPORT, REMOVE EXPORT, SET EXPORT, SHOW EXPORT
  • CREATE PROXY or CONVERT/VMS PROXY
    ADD PROXY, REMOVE PROXY, SHOW PROXY

1.1.8 Using NFS

The DIGITAL TCP/IP Services for OpenVMS software includes commands for using NFS. By issuing the following commands, users can view container file systems and copy files to and from them:

  • CREATE DIRECTORY, DIRECTORY, REMOVE DIRECTORY, REMOVE FILE
  • CREATE CONTAINER, DELETE CONTAINER
  • EXPORT
  • IMPORT

For using NFS client (working with files that reside on remote hosts), DIGITAL TCP/IP Services for OpenVMS offers:

  • MOUNT
  • SHOW MOUNT
  • DISMOUNT

1.1.9 Displaying Information

The SHOW and LIST commands display configuration, status, and performance information.

The ZERO commands reset the performance counters.

1.2 UNIX Management Commands

The TCP/IP Services Version 5.0 product provides UNIX management commands for system managers experienced in managing a UNIX network subsystem. Table 1-3 introduces these commands.

Table 1-3 UNIX Management Commands
Command Description
ifconfig Configures or displays network interface parameters, redefines an address for a particular interface, or sets options such as an alias list, broadcast address, or access filter.
netstat Displays network statistics of sockets, data link counters, specified protocols or aliases, network interfaces, and a host's routing table.
sysconfig Displays and maintains the network subsystem attributes.
route Manually manipulates the routing table. Normally a system routing table management daemon, such as GATED or ROUTED, will tend to this task.
arp Controls and displays ARP tables for the specified host.

To use UNIX management commands at the DCL prompt, execute the command procedure SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM. For example, enter:


 
$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS 

This command procedure defines foreign commands that enable you to enter UNIX commands from the DCL prompt. The following sample shows how to obtain information about an interface configured on your host:


 
$ ifconfig "WF0" 

The following is displayed:


WF0: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX> 
     rxmt 1000, reach time 30000, dad tries 1, MT 4352, hops 64, token len 64 
     inet 16.20.208.100 netmask ffff0000 broadcast 16.20.255.255 ipmtu 4470 
     inet6 fe80::200:f8ff:fe66:2e35 

You must enclose uppercase options in quotation marks when entering UNIX commands at the DCL prompt.

For more information about UNIX command options and flags, enter HELP unix_command at the TCPIP> prompt. For example, to display information about the netstat command enter:


 
TCPIP> HELP NETSTAT 
 
NETSTAT 
 
     SYNOPSIS 
 
 
       netstat [-rn | [-an] [-f address_family] [interval] 
 
       netstat [-adHimMnrstv] [-f address_family] [interval] 
 
       netstat [-ntdz] [-I interface] [interval] 
 
 
     The netstat command displays network-related data in various 
     formats. 
 
 
 
 
  Additional information available: 
 
  FLAGS      DESCRIPTION 
 
NETSTAT Subtopic? 
<RECTO_HEAD>(CANCEL_H) <VERSO_HEAD>(CANCEL_H)


Chapter 2
Command Descriptions

This chapter contains command descriptions, in alphabetical order, for the DIGITAL TCP/IP Services for OpenVMS management commands.

For information about how to enter commands, see Chapter 1.


ADD EXPORT

Adds an export entry, in the form of a 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:
  • An OpenVMS disk
  • A subset of an OpenVMS disk
  • A UNIX style container file system

Applies to the NFS server.

Related commands: MAP, REMOVE EXPORT, SHOW EXPORT, SHOW HOST


Format

ADD EXPORT "/path/name" /HOST=host
[ /OPTIONS=
{ [NO]DATA_CONVERSION
[NO]NAME_CONVERSION
[NO]PURGE_VERSIONS
[NO]TYPELESS_DIRECTORIES } ]

restrictions and tips

This command requires read and write access to the export database. The following restrictions and instruction apply:
  • Do not use wildcards within a UNIX style directory specification.
  • For each host, define both its host name and alias name.
  • For each entry, use uppercase and lowercase consistently.
  • 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.

Parameters

"/path/name"

Required.

File system to add to the export database.

Separate directory and subdirectory names with slashes.


Qualifiers

/HOST=host

Required.

The NFS client host or hosts that will have access to the specified NFS file system.

You may use a wildcard to allow access to all hosts.

/OPTIONS=
{ [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:

  • 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.
  • 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 back 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.
  • PURGE_VERSIONS, NOPURGE_VERSIONS
    Default: NOPURGE_VERSIONS
    Deletes multiple versions of files when created or detected. (The NFS CREATE and RENAME calls can create multiple versions. The NFS READDIR call can sense multiple versions.)
  • TYPELESS_DIRECTORIES, NOTYPELESS_DIRECTORIES
    • TYPELESS_DIRECTORIES
      Removes .dir.1 from the name of directories. A naming conflict could arise, for example, if two files exist in the parent directory. For example:
      DOVE.;1 (regular file)
      DOVE.DIR;1 (directory file)
      The name 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.

Examples

#1

TCPIP> ADD EXPORT "/gold/finch" /HOST=GOLD  
      

Adds the name of UNIX style 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.


ADD PROXY

Adds entries to the proxy database that give 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:

  • 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 is not relevant.
    • Required qualifiers: /HOST, /REMOTE_USER.
  • 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 NFS Proxies

ADD PROXY user { /GID=n | /HOST=host | /UID=n }
[ /NFS=options ]
[ /PERMANENT ]


Format for Communication Proxies

ADD PROXY user { /HOST=host | /REMOTE_USER=user }
[ /PERMANENT ]

restrictions and tips

Requires read and write access to the proxy database and one of the following:

  • SYSPRV privileges
  • BYPASS and OPER privileges

For each host, define both its host name and alias name.

For each entry, use uppercase and lowercase consistently.


Parameters

user

Required.

Local OpenVMS identity for the user of: NFS server, NFS client, PC-NFS, remote shell, or LPR/LPD.


Qualifiers

/GID=n

Required for an NFS proxy.

Group identifier (GID) for an NFS user.

Wildcards not allowed.

/HOST=host

Required.

Host name on which the NFS user is working.

  • The host must be seen on the SHOW HOST display. It is important to use the SHOW HOST command to verify that the host is known to DIGITAL TCP/IP Services for OpenVMS because ADD PROXY does not do this check.
  • A wildcard is allowed.
  • Suggested: define the host name and its alias name.

/NFS=INCOMING

/NFS=OUTGOING

Optional. Default: /NFS=(INCOMING,OUTGOING).

Creates an NFS proxy for local clients, remote clients, or PC-NFS clients. Specify one of the following:

  • /NFS=OUTGOING --- Proxy to use NFS client
  • /NFS=INCOMING --- Proxy to use NFS server
  • /NFS=(OUTGOING,INCOMING) --- Both

/PERMANENT

Optional. Default: Both permanent and volatile databases.

Adds the entry only to the permanent proxy database.

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

/REMOTE_USER=user

Required for a communication proxy. Not valid on NFS proxy.

Remote client's user name.

A wildard is allowed.

/UID=n

Required for an NFS proxy.

User identifier (UID) for an NFS user.

Wildcards not allowed.


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 NFS client and 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 /REMOTE_USER="cygnet" 
/HOST="babyswan"   
      

Adds to the proxy database communication proxy REMOTE_UGLY_DUCKLING for remote user cygnet at host babyswan.


ANALYZE CONTAINER

Verifies the integrity of a UNIX style container file, including:
  • Superblock validation
  • Inode validation
  • Directory validation
  • Internal allocation validation
  • Directory hierarchy validation

Reports, and optionally corrects, problems within the structure of the container directory. Applies to the NFS server.

Related commands: DIRECTORY, SHOW CFS, MAP, UNMAP


Format

ANALYZE CONTAINER device:path.name
[ /[NO]CONFIRM ]
[ /[NO]REPAIR ]

restrictions and tips

Before you issue ANALYZE CONTAINER, map the OpenVMS volume on which the container directory resides.

Compaq recommends that you unmap the container file system to prevent access to it while you analyze it.

You must have BYPASS privileges.


Parameters

device:path.name

Required.

Device and container directory to analyze.


Qualifiers

/CONFIRM

/NOCONFIRM

Optional. Default: /NOCONFIRM.

Use only with the /REPAIR qualifier.

When the software encounters a problem with the services database, it displays a description and solution and then requests confirmation before making each correction. Enter one of the following:

  • Y to repair the problem
  • N to ignore the problem
  • G to change to NO CONFIRMATION mode

Example:


%TCPIP-E-ANA_SUP_BADIICGSIZE, Problem: Bad initial inode cell        
group size: bad_value  
Solution: Will be replaced by  
default size: good_value  
        CONFIRM [Y/N/G]:  

/REPAIR

/NOREPAIR

Optional. Default: /NOREPAIR.

Analyze will repair any errors.


Examples

#1

TCPIP> MAP "/dua0" DUA0:  
TCPIP> ANALYZE CONTAINER DUA0:[WREN$20]  
      

Verifies the integrity of container DUA0:[WREN$20].


ANALYZE MAIL

Verifies the consistency of the SMTP queues with SMTP control files.

Related commands: REMOVE MAIL, SHOW MAIL


Format

ANALYZE MAIL [ user ]
[ /[NO]CONFIRM ]
[ /DELETE[=options ]
[ /HOLD=time ]
[ /LOG=file ]
[ /[NO]REPAIR ]

restrictions

Requires SYSNAM, SYSPRV, or BYPASS privileges to access mail that is not yours.

Parameters

user

Optional. Default: All users.

User whose mail you want to analyze.


Qualifiers

/CONFIRM

/NOCONFIRM

Optional. Default: /NOCONFIRM

Use only with the /REPAIR or /DELETE qualifier.

When the software encounters a problem, it displays a description and solution. It then requests confirmation before making a correction or deleting each record. Enter one of the following:

  • Y to repair the problem
  • N to ignore the problem
  • G to change to NO CONFIRMATION mode

/DELETE [=BEFORE=time | =SINCE=time]

Optional. Default: Files not deleted.

Deletes each control file without a corresponding queue entry.

  • =BEFORE=time
    • Deletes files created before the specified time.
    • Default: Current date and time.
  • =SINCE=time
    • Deletes files created since the specified time.
    • Default: Deletes all files.

Use the /DELETE and /REPAIR qualifiers on the same command line only if their time frames do not conflict.

The following example re-queues lost mail created since yesterday and deletes all previous mail:


TCPIP> ANALYZE MAIL /REPAIR /DELETE=BEFORE=YESTERDAY     

/HOLD=time

Optional. Default: Immediate retransmission.

Hold, until the specified time, lost control files that you re-queued.

/LOG[=file]

Optional. Default: [current_default_dir]:TCPIP$SMTP_ANALYZE.LOG.

Writes the ANALYZE MAIL log to the specified file.

/REPAIR

/NOREPAIR [=BEFORE=time | =SINCE=time]

Optional. Default: /NOREPAIR.

Corrects errors as follows:

  • Resubmits for delivery each valid control file in the SMTP directory with no entry in an SMTP queue.
  • Deletes each invalid control file (fails the internal consistency check) and the corresponding queue entry.
  • Either re-queues or deletes messages placed on hold.

Supports the following options:

  • =BEFORE=time
    • Deletes files created before the specified time.
    • Default: Current date and time.
  • =SINCE=time
    • Deletes files created since the specified time.
    • Default: Deletes all files.

Do not use /REPAIR with /DELETE if their time frames conflict.


Examples

#1

TCPIP> ANALYZE MAIL /REPAIR  
      

Displays status for the SMTP queues and re-queues each valid control file lacking a corresponding queue entry.

#2

TCPIP> ANALYZE MAIL /DELETE  
      

Creates the summary of SMTP queues and deletes each valid control file lacking a corresponding SMTP queue entry.

#3

TCPIP> ANALYZE MAIL DRAKE  
  
%TCPIP-I-ANA_RUNING, ANALYZE runs on node DODO  
  
%TCPIP-I-ANA_NOENTR, no queue entry found for file   
NEST3$:[DRAKE]93042311394417_DRAKE.TCPIP_DODO;1  
  
%TCPIP-I-ANA_COMPLE, ANALYZE completed on node DODO  
  
%TCPIP-I-ANA_FEPAIR, found 0 file-queue entry pairs  
%TCPIP-I-ANA_DELQEN, deleted 0 queue entries  
%TCPIP-I-ANA_FILNOQ, found 1 files with no queue entries  
%TCPIP-I-ANA_FILHLD, holding 0 files in directory  
%TCPIP-I-ANA_FILDEL, deleted 0 files from the Postmaster directory  
%TCPIP-I-ANA_SUBFIL, submitted 0 files to the generic queue  
%TCPIP-I-ANA_FILACE, encountered 0 file access errors  
%TCPIP-I-ANA_NONCFF, found 0 non-unknown files in Postmaster directory  
%TCPIP-I-ANA_FILCOR, found 0 corrupted CF files in Postmaster directory  
TCPIP>  
  
      

Creates a summary of SMTP entries and control files for user DRAKE.

#4

TCPIP> ANALYZE MAIL DRAKE /REPAIR /DELETE=BEFORE=24-SEP-1997  
      

  • Creates a summary of SMTP entries and control files for user DRAKE.
  • Re-queues control files lacking corresponding queue entries.
  • Deletes control files created before September 24, 1997.


Previous Next Contents Index

[Site home] [Send comments] [Help with this site] [How to order documentation] [OpenVMS site] [Compaq site]
[OpenVMS documentation]

Copyright © Compaq Computer Corporation 1998. All rights reserved.

Legal
6527PROFILE_001.HTML

ITEC bullet Buffalo State College bullet Twin Rise 200 bullet 1300 Elmwood Avenue bullet Buffalo, NY 14222 bullet (716) 878-4832
[ Home ] [ Academic Support ] [ Administrative Support ] [ Systems Support ] [ News ] [ SUNY Links ]

E-mail ITEC: scacad@itec.mail.suny.edu