TCPIP$UCP_HELP.HLB  —  CONVERT
    The TCP/IP Services management program provides three kinds of
    CONVERT commands:

    CONVERT/CONFIGURATION  Converts BIND server configuration
    BIND                   information to BIND Version 8.1 format.

    CONVERT/VMS            Populates a TCP/IP Services for OpenVMS
                           database with entries from a UNIX database
                           file.
    CONVERT/UNIX           Reads a TCP/IP Services database and
                           converts the information to a UNIX-
                           formatted (sequential) database file.

1    /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.
    Note: Specify /CONFIGURATION BIND without an underscore when
    entering this command. 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]

1.1  –  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.

1.2  –  Qualifiers

1.2.1    /CLUSTER

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

1.3  –  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.

2    /UNIX

    The CONVERT/UNIX commands read a TCP/IP Services database and
    convert the information to a UNIX-formatted (sequential) database
    file.

2.1  –  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 ]

2.1.1  –  Qualifiers

2.1.1.1    /DOMAIN

       /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:

    o  The domain name must be fully qualified.

    o  The closing dot is not required.

    o  Do not use wildcards.

    o  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:

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

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

2.1.1.2    /LOG

       /LOG
       /NOLOG

    Optional. Default: /NOLOG.

    Shows records as they are processed.

2.1.2  –  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.

2.2  –  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 ]

2.2.1  –  Restrictions

    Requires:

    o  Read access to the hosts database.

    o  Write access to []ETC.HOSTS.

2.2.2  –  Parameters

 destination_file

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

    Allows you to specify the name for the new file.

2.2.3  –  Qualifiers

2.2.3.1    /BYADDRESS

    Optional. Default: Sorts by name.

    Sorts entries in the converted file by IP address.

2.2.3.2    /LOG

    Optional. Default: No display.

    Interactively displays the processing.

2.2.4  –  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.

2.3  –  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 ]

2.3.1  –  Restrictions

    Requires:

    o  Read access to the hosts database.

    o  Write access to the file []ETC.NETWORKS.

2.3.2  –  Parameters

 destination_file

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

    Specifies the name of the new UNIX formatted file.

2.3.3  –  Qualifiers

2.3.3.1    /BYADDRESS

    Optional. Default: Sorts by name.

    Sorts the converted file by network number.

2.3.3.2    /LOG

    Optional. Default: No display.

    Displays messages generated during processing.

2.3.4  –  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.

3    /VMS

    The CONVERT/VMS commands populate a TCP/IP Services database with
    entries from a UNIX database file.

3.1  –  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 ]

3.1.1  –  Restrictions

    Requires:

    o  Read and write access to the hosts database (if using /ADD_
       HOST qualifier).

    o  Read access to the hosts database.

3.1.2  –  Parameters

 source_file

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

    File to be converted.

3.1.3  –  Qualifiers

3.1.3.1    /ADD_HOST

    Optional. Default: No adding.

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

3.1.3.2    /FILE

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

3.1.4  –  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.

3.2  –  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 ]

3.2.1  –  Restrictions

    Requires:

    o  Read and write access to the hosts database.

    o  Read access to the UNIX formatted hosts file.

    o  Exclusive use of the hosts database.

3.2.2  –  Parameters

 source_file

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

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

3.2.3  –  Qualifiers

3.2.3.1    /LOG

    Optional. Default: No logging.

    Displays records as they are being processed.

3.2.3.2    /UPCASE

    Optional. Default: Not created.

    Creates an uppercase alias name for each host.

3.2.4  –  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.

3.3  –  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 ]

3.3.1  –  Restrictions

    Requires:

    o  Read and write access to the networks database.

    o  Read access to []ETC.NETWORKS.

    o  Exclusive use of the networks database.

3.3.2  –  Parameters

 source_file

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

    Name of the file to be converted.

3.3.3  –  Qualifiers

3.3.3.1    /LOG

    Optional. Default: Log file created.

    Interactively displays records as they are being processed.

3.3.3.2    /UPCASE

    Optional. Default: Alias not created.

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

3.3.4  –  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.

3.4  –  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 ]

3.4.1  –  Restrictions

    Requires:

    o  Read and write access to the proxy database.

    o  Read access to []ETC.PASSWORD.

    o  Exclusive use of the proxy database.

3.4.2  –  Parameters

 source_file

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

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

3.4.3  –  Qualifiers

3.4.3.1    /LOG

    Optional. Default: No display.

    Displays records as they are being processed.

3.4.4  –  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.
Close Help