[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here HP TCP/IP Services for OpenVMS

HP TCP/IP Services for OpenVMS
Management Command Reference


Previous Contents Index


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 privilege 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 either the /REPAIR or the /DELETE qualifier.

When the software encounters a problem, it displays a description and solution. If you specify the /CONFIRM qualifier, the software 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 command requeues 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 requeued.

/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 requeues 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 requeues each valid control file that lacks a corresponding queue entry.

#2

TCPIP> ANALYZE MAIL /DELETE
      

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

#3

TCPIP> ANALYZE MAIL DRAKE /REPAIR /DELETE=BEFORE=24-APR-2003
      

This command does the following:

  • Creates a summary of SMTP entries and control files for user DRAKE.
  • Requeues control files that lack corresponding queue entries.
  • Deletes control files created before April 24, 2003.

ANALYZE SERVICE

Searches through the services database for corrupted definitions. Displays invalid records and, with the /REPAIR qualifier, deletes them.

Related commands: SET SERVICE, SHOW SERVICE


Format

ANALYZE SERVICE [ /[NO]CONFIRM ]
[ /[NO]REPAIR ]

restrictions

Requires write access to the directory with the services database.

Qualifiers

/CONFIRM

/NOCONFIRM

Optional. Default: /NOCONFIRM.

Use only with the /REPAIR qualifier.

When the software encounters a problem, it displays a description and a solution. If you specify the /CONFIRM qualifier, the software then requests confirmation before making a correction.

Respond to the CONFIRM: prompt by entering one of the following:

  • Y to repair the problem
  • N to ignore the problem

/REPAIR

/NOREPAIR

Optional. Default: /NOREPAIR

Deletes the corrupted records.


Examples

#1

TCPIP> ANALYZE SERVICE
                    Invalid IP option records
    Service             Port  Proto    Process          Address

    TOE                   25  TCP      TOED             0.0.0.0
    NESTING              560  TCP      NEW_EGGS_TCPIP   0.0.0.0

IP option records
  Total:              0
  Invalid:            0

TCP option records
  Total:              7
  Invalid:            2
      

Displays total and invalid protocol option records found in two service definitions, TOE and NESTING.

#2

TCPIP> ANALYZE SERVICE /REPAIR /CONFIRM
                    Invalid IP option records
    Service             Port  Proto    Process          Address

    TOE                   67  UDP      TOED             0.0.0.0
Remove? [N]: YES


    Service             Port  Proto    Process          Address

    NESTING               69  UDP      NEW_EGGS_TCPIP   0.0.0.0
Remove? [N]: YES
      

Displays the total protocol option records and deletes, after confirmation, the invalid records.


CONVERT/CONFIGURATION_BIND

Converts the UCX BIND Version 4.x name server configuration to the BIND Version 8.1 format. Applies to the BIND name server. Use this command if you have a BIND configuration from an earlier release (Version 4.2 or lower) of the TCP/IP Services software. This command extracts the BIND configuration information from the file UCX$CONFIGURATION.DAT and creates the ASCII file TCPIP$BIND.CONF.

Related commands: SET CONFIGURATION BIND, SHOW CONFIGURATION BIND


Format

CONVERT/CONFIGURATION BIND [bind_conf_file]
[/CLUSTER=lbroker_conf_file]


Parameters

bind_conf_file

Optional. Default: SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND.CONF.

Specifies the alternate name or location of the BIND configuration file to be created.


Qualifiers

/CLUSTER=lbroker_conf_file

Optional. Default: SYS$SYSDEVICE:[TCPIP$LD_BKR]TCPIP$LBROKER.CONF

Creates the file used by the load broker for cluster load balancing. Here, lbroker_conf_file specifies the name of the load broker configuration file.


Examples

#1

TCPIP> CONVERT /CONFIGURATION  BIND -
_TCPIP> /CLUSTER=SYS$SYSDEVICE:[TCPIP$LD_BKR]TCPIP$LBROKER.CONF
      

Converts the UCX BIND server configuration to BIND Version 8.1 format and creates the configuration file SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND.CONF. The /CLUSTER qualifier creates the configuration file TCPIP$LBROKER.CONF used by the load broker.

#2

TCPIP> CONVERT /CONFIGURATION  BIND SITE2_BIND.CONF
      

Converts the UCX BIND server configuration and creates the configuration file SITE2_BIND.CONF.

Refer to the HP TCP/IP Services for OpenVMS Management manual for more information about the BIND name server, resolver, and load broker.


CONVERT/UNIX BIND

Creates a BIND server database and populates it with records from the local host and MX databases. This command will create either a forward translation file or a reverse translation file. If you specify a domain.name that ends in IN-ADDR.arpa , a reverse translation file is created.

Related commands: SET HOST, SET MX_RECORD


Format

CONVERT/UNIX BIND

/DOMAIN=domain.name
[ /[NO]LOG ]


Qualifiers

/DOMAIN=domain.name

Required.

Domain for which to extract data. Determines whether to perform forward translation or reverse translation. The following restrictions and instructions apply:

  • The domain name must be fully qualified.
  • The closing dot is not required.
  • Do not use wildcards.
  • Specify up to four parts of the IP address for varying degrees of selectivity. For example:
    /DOMAIN=16.IN-ADDR.arpa is less selective.
    /DOMAIN=8.20.16.IN-ADDR.arpa is more selective.

The end of domain.name determines whether a forward or reverse translation is performed. For example:

  • If the domain name ends in IN-ADDR.arpa:
    • Reverse translation is performed.
    • The domain is some part of an IP address, reversed, and added to IN-ADDR.arpa.
    • The selection includes the contents of the hosts database in the output.
  • If the domain name ends in anything else (for example, /DOMAIN=DAW.MAG.COM ):
    • Forward translation is performed.
    • All hosts in domain.name or in any of its subdomains are selected for the output file.
    • CONVERT/UNIX BIND does a forward translation and selects hosts in DAW.MAG.COM and in its subdomains.

/LOG

/NOLOG

Optional. Default: /NOLOG.

Shows records as they are processed.


Examples

#1

TCPIP> CONVERT/UNIX BIND /DOMAIN=KESTREL.SMALL.FALCON

      

On host KESTREL, creates a BIND server database with default file name SYS$SPECIFIC:[TCPIP$BIND]KESTREL_SMALL_FALCON.DB.

BIND and MX records for the host's domain, kestrel.small.falcon , are extracted, converted, and written to KESTREL_SMALL_FALCON.DB.

#2

TCPIP> CONVERT/UNIX BIND /LOG /DOMAIN=ABC.COM
      

Creates a BIND server database. The /LOG qualifier indicates that records will be displayed as they are processed.


CONVERT/UNIX HOST

Reads the hosts database and converts the information to an ASCII file formatted for use as a hosts file on a UNIX system.

The name and location of the hosts database is specified by the logical name TCPIP$HOST. If this name is not defined, the command looks for TCPIP$HOST.DAT in your current directory.

Related commands: CREATE HOST, SET HOST, SHOW HOST


Format

CONVERT/UNIX HOST [ destination_file ]
[ /BYADDRESS ]
[ /LOG ]

restrictions

Requires:
  • Read access to the hosts database.
  • Write access to []ETC.HOSTS.

Parameters

destination_file

Optional. Default: []ETC.HOSTS (UNIX formatted)

Allows you to specify the name for the new file.


Qualifiers

/BYADDRESS

Optional. Default: Sorts by name.

Sorts entries in the converted file by IP address.

/LOG

Optional. Default: No display.

Interactively displays the processing.


Examples

#1

TCPIP> CONVERT/UNIX HOST
      

Converts the hosts database TCPIP$HOST to an ASCII file that is formatted for use as a hosts file on a UNIX system. The resulting file is named (default) ETC.HOSTS in the current directory and can be used on a UNIX system as the file /etc/hosts .


CONVERT/UNIX NETWORK

Converts the networks database to an ASCII file formatted for use on a UNIX system.

The name and location of the networks database is specified by the logical name TCPIP$NETWORK. If this name is not defined, the command looks for TCPIP$NETWORK.DAT in your current directory.

Related commands: CREATE NETWORK, SET NETWORK, SHOW NETWORK


Format

CONVERT/UNIX NETWORK [ destination_file ]
[ /BYADDRESS ]
[ /LOG ]

restrictions

Requires:
  • Read access to the hosts database.
  • Write access to the file []ETC.NETWORKS.

Parameters

destination_file

Optional. Default: []ETC.NETWORKS (UNIX formatted).

Specifies the name of the new UNIX formatted file.


Qualifiers

/BYADDRESS

Optional. Default: Sorts by name.

Sorts the converted file by network number.

/LOG

Optional. Default: No display.

Displays messages generated during processing.


Examples

#1

TCPIP> CONVERT/UNIX NETWORK /LOG
      

Converts the networks database (TCPIP$NETWORK) to the ASCII file []ETC.NETWORKS. This resulting file can be used as a networks database file /etc/networks on a UNIX system. The /LOG qualifier displays each record as it is converted.

#2

TCPIP> CONVERT/UNIX NETWORK NETWORKS.TXT
      

Converts the networks database (TCPIP$NETWORK) to the ASCII file []NETWORKS.TXT. The resulting file may be used as the networks database file /etc/networks on a UNIX system.


CONVERT/VMS BOOTP

Populates the existing BOOTP database with entries from a BIND-formatted UNIX /etc/bootptab file.

If the logical name TCPIP$BOOTP is defined, it is used to specify the directory and file name for the database. If TCPIP$BOOTP is not defined, the database is created as [current_directory]TCPIP$BOOTP.DAT.

Related commands: CREATE BOOTP, SET BOOTP, SHOW BOOTP


Format

CONVERT/VMS BOOTP [ source_file ]
[ /ADD_HOST ]
[ /FILE=sys_image_file ]

restrictions

Requires:
  • Read and write access to the hosts database (if using /ADD_HOST qualifier).
  • Read access to the hosts database.

Parameters

source_file

Optional. Default: []ETC.BOOTPTAB in your current directory.

File to be converted.


Qualifiers

/ADD_HOST

Optional. Default: No adding.

Adds new host names found in the UNIX /etc/bootptab file to TCPIP$HOST.DAT.

/FILE=sys_image_file

Optional. Default: None.

Specifies the name of the client's system image file to download if this file name is not in the BOOTP database.


Examples

#1

TCPIP> CONVERT/VMS BOOTP BOOTP.DAT /ADD_HOST
      

Converts a UNIX ASCII boot data file to an OpenVMS indexed file. BOOTP.DAT specifies the source UNIX boot file to convert. For new hosts, the /ADD_HOST qualifier adds the host to the hosts database.


CONVERT/VMS HOST

Populates the existing hosts database with entries from a UNIX /etc/hosts file.

The name and location of the hosts database is specified by the logical name TCPIP$HOST. If this name is not defined, the command looks for TCPIP$HOST.DAT in your current directory.

Related commands: CREATE HOST, SET HOST, SHOW HOST


Format

CONVERT/VMS HOST [ source_file ]
[ /LOG ]
[ /UPCASE ]

restrictions

Requires:
  • Read and write access to the hosts database.
  • Read access to the UNIX formatted hosts file.
  • Exclusive use of the hosts database.

Parameters

source_file

Optional. Default: ETC.HOSTS in your current directory.

UNIX formatted file to be converted to the TCPIP$HOST database file.


Qualifiers

/LOG

Optional. Default: No logging.

Displays records as they are being processed.

/UPCASE

Optional. Default: Not created.

Creates an uppercase alias name for each host.


Examples

#1

TCPIP> CONVERT/VMS HOST
      

Converts the UNIX formatted hosts database file to the file TCPIP$HOST.DAT. The name of the UNIX formatted file is ETC.HOSTS in your current directory.

#2

TCPIP> CONVERT/VMS HOST HOSTS.TXT
      

Converts the UNIX formatted hosts database file HOSTS.TXT to the file TCPIP$HOST.DAT.


CONVERT/VMS NETWORK

Populates the existing networks database with entries from a UNIX /etc/networks file.

The name and location of the networks database is specified by the logical name TCPIP$NETWORK. If this name is not defined, the command looks for TCPIP$NETWORK.DAT in your current directory.

Related commands: CREATE NETWORK, SET NETWORK, SHOW NETWORK


Format

CONVERT/VMS NETWORK [ source_file ]
[ /LOG ]
[ /UPCASE ]

restrictions

Requires:
  • Read and write access to the networks database.
  • Read access to []ETC.NETWORKS.
  • Exclusive use of the networks database.

Parameters

source_file

Optional. Default: ETC.NETWORKS in your current directory.

Name of the file to be converted.


Qualifiers

/LOG

Optional. Default: Log file created.

Interactively displays records as they are being processed.

/UPCASE

Optional. Default: Alias not created.

Specifies that an uppercase alias name be created for each network name.


Examples

#1

TCPIP> CONVERT/VMS NETWORK
      

Converts a UNIX formatted /etc/networks database file into a TCP/IP Services formatted networks database. The OpenVMS file name of /etc/networks is ETC.NETWORKS in your current directory.

#2

TCPIP> CONVERT/VMS NETWORK /UPCASE
      

Converts a UNIX formatted database file to a TCP/IP Services formatted networks database. An uppercase alias name is created for each network name.


CONVERT/VMS PROXY

Populates the existing proxy database with entries from a UNIX /etc/passwd file.

The name of the proxy database is specified by the logical name TCPIP$PROXY. If this name is not defined, the command looks for TCPIP$PROXY.DAT in your current directory.

Related commands: ADD PROXY, CREATE PROXY

Applies to: NFS server, NFS client, PC-NFS


Format

CONVERT/VMS PROXY [ source_file ]
[ /LOG ]

restrictions

Requires:
  • Read and write access to the proxy database.
  • Read access to []ETC.PASSWORD.
  • Exclusive use of the proxy database.

Parameters

source_file

Optional. Default: ETC.PASSWD in your current directory.

ASCII file to convert to a TCP/IP Services proxy database.


Qualifiers

/LOG

Optional. Default: No display.

Displays records as they are being processed.


Examples

#1

TCPIP> CONVERT/VMS PROXY
      

Converts a UNIX formatted /etc/passwd file to an OpenVMS formatted proxy database. The OpenVMS file name of /etc/passwd is ETC.PASSWD in your current directory.

#2

TCPIP> CONVERT/VMS PROXY UNIX_PASSWDS.TXT
      

Converts a UNIX formatted /etc/passwd file to an OpenVMS formatted proxy database. In this example, the file UNIX_PASSWDS.TXT contains the /etc/passwd data.


Previous Next Contents Index