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 solution. It then requests confirmation before making a 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

Deletes the corrupted records.

Examples

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.

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 [Return]  
  
    Service             Port  Proto    Process          Address  
  
    NESTING               69  UDP      NEW_EGGS_TCPIP   0.0.0.0              
Remove? [N]: YES [Return]  
  
      

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

Converts the UCX BIND V4.* name server configuration to the BIND 8.1 format. Applies to the BIND name server. Use this command if you have a BIND configuration from an earlier release of DIGITAL TCP/IP services for OpenVMS. 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.

Specifies the alternate name or location of the BIND configuration file. If you do not specify a file, the default is used: SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND.CONF.

Qualifiers

/CLUSTER=lbroker_conf_file

Optional.

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

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

Converts the UCX BIND server configuration to BIND 8.1 format, creating 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.

TCPIP> CONVERT /CONFIGURATION  BIND SITE2_BIND.CONF
      

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

See the DIGITAL TCP/IP Services for OpenVMS Management guide for more information about the BIND name server, resolver, and load broker.

Creates a BIND server database and populates it with records from the hosts and the routes 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 will be created.

Related commands: SET HOST, SET MX_RECORD

Format

CONVERT/UNIX BIND [ out_file ] /DOMAIN=domain.name [ /[NO]LOG ]

Parameters

out_file

Optional. Default: SYS$SPECIFIC:[TCPIP$BIND]domain.DB.

This is the device and directory specified in the file SYSUAF.DAT for the BIND server's user name.

In domain names, dots ( . ) are changed to underscores ( _ ). For example, if the BIND server's directory is SYS$SPECIFIC:[TCPIP$BIND] and you have specified the domain abc.def.com, the default output file is named: SYS$SPECIFIC:[TCPIP$BIND]ABC_DEF_COM.DB

Compaq suggests that you do not change the default. If you do, the file is created in your current directory. Specify the full OpenVMS file specification without the version number. Do not use wildcards.

Qualifiers

/DOMAIN=domain.name

Required.

Domain for which to extract data. Determines whether forward translation or reverse translation is to be performed.

• Must be fully qualified.
• Closing dot is not required.
• Do not use wildcards.
• Specify between 4 and 0 parts of the IP address for varying degrees of selectivity. Example of reverse translation:
  /DOMAIN=16.IN-ADDR.arpa --- less selective
  /DOMAIN=8.20.16.IN-ADDR.arpa --- more selective

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

• Ending = IN-ADDR.arpa
  • Reverse translation is performed.
  • The domain is some part of an IP address, reversed, and added to IN-ADDR.arpa.
  • Includes the contents of the hosts database in the output.
• All other endings
  • Forward translation is performed.
  • All hosts in domain.name or in any of its subdomains are selected for the output file.
  • Example: /DOMAIN=DAW.MAG.COM
    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

TCPIP> CONVERT/UNIX BIND  
  
      

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.edu, are extracted, converted, and written to KESTREL_SMALL_FALCON.DB.

TCPIP> CONVERT/UNIX BIND /LOG
 
      

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

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) in the directory that has the BIND server.

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

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.

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)

Name of the new UNIX style formatted file.

Qualifiers

/BYADDRESS

Optional. Default: Sorts by name.

Sorts the converted file by network number.

/LOG

Optional. Default: No display.

Displays processing.

Examples

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.

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 a networks database file /etc/networks on a UNIX system.

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.

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

Examples

TCPIP> CONVERT/VMS BOOTP BOOTP.DAT /ADD_HOST   
      

This command specifies the following:

• CONVERT/VMS BOOTP --- Converts a UNIX ASCII boot data file to an OpenVMS indexed file
• BOOTP.DAT --- Specifies the source UNIX style boot file to convert
• /ADD_HOST --- For new hosts, also adds them to the hosts database

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

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.

TCPIP> CONVERT/VMS HOST HOSTS.TXT
      

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

Populates the existing networks database with entries from a BIND-formatted 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 is created for each network name.

Examples

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.

TCPIP> CONVERT/VMS NETWORK /UPPERCASE
      

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

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, and 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 DIGITAL TCP/IP Services for OpenVMS proxy database.

Qualifiers

/LOG

Optional. Default: No display.

Displays records as they are being processed.

Examples

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.

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.

Copies information in the configuration database from one OpenVMS Cluster node to another. All configuration information is copied clusterwide, with the exception of the following node-specific components:

• NFS server (SET CONFIGURATION MAP)
• BIND server (UCX V4.* BIND configuration)
• SMTP

If you copy a configuration, modify the following definitions for the destination node:

• Local host name
  If you copy communication information, use SET CONFIGURATION/LOCAL.
• Interface configuration
  Use SET CONFIGURATION INTERFACE /HOST.

Related commands: All the SET CONFIGURATION commands

Format

COPY CONFIGURATION component dest_node
[ /ON=source_node ]
[ /OVERRIDE ]

restrictions

Requires:

• Read, write, and delete access to the configuration database.
• SYSPRV or BYPASS privileges.

If you copy all components of the BIND server configuration, you must use the /OVERRIDE qualifier, or specify BIND as the component. This command copies only V4.* style BIND configuration information. Do not use this command in a BIND 8.1 environment.

Parameters

component

Required.

The name of a component configured with the SET CONFIGURATION command. You can use a wildcard.

dest_node

Required.

Node to which you want to copy the component's configuration.

Qualifiers

/ON=source_node

Optional. Default: The local node.

Node with the configuration you want to copy to another node.

/OVERRIDE

Optional. Default: Configuration for the BIND server is not copied if you specify a wildcard.

Copies the BIND server configuration. (The BIND server software can run on only one cluster node.)

Not required to copy this configuration if you specify:

TCPIP> COPY CONFIGURATION BIND destination_node

Examples

TCPIP> COPY CONFIGURATION SMTP ROBIN  
      

Copies the SMTP configuration in the configuration database from the local node to node ROBIN in the cluster.

TCPIP> COPY CONFIGURATION * WREN  
      

Copies all component information (except for the BIND server) in the configuration database from the local node to node WREN in the cluster.

TCPIP> COPY CONFIGURATION COMMUNICATION DRAKE /ON=MALARD   
      

Copies the routing information in node MALARD's configuration database to another node in the cluster, DRAKE. The command is issued from another node in the same cluster.