# DIGITAL TCP/IP Services for OpenVMS
Management Command Reference

Previous | Contents

To terminate the display, type Ctrl/Z.

### /PARAMETERS

Optional.

Shows parameter settings. You can specify any protocol.

##

### Examples

#1

    UCX> SHOW PROTOCOL TCP

    TCP
    Connect initiated:           242    Connect accepted:             329
    Connect established:         562    Connect closed:               741
    Connect dropped:               9    Embry connect drop:             6
    Attempt rtt:              321204    Succeeded rtt:             320876
    XMT Delayed ACKs:         201701    Connect timeout:                0
    ReXMT timeout:                89    Persist timeout:               97
    Keepalive timeout:         35886    Keepalive probes:               0
    Keepalive drops:               0    Total XMT packets:         560331
    XMT packets:              326701    XMT bytes:               15681003
    XMT packet reXMT:             91    XMT bytes reXMT:            22606
    XMT ACK only:             200413    XMT window probes:             95
    XMT URG only:                  3    XMT wind update pack:       32371
    XMT CTRL packets:            657    Total RCV packets:         615207
    RCV packets:              360404    RCV bytes:               58152405
    RCV chksum error:              0    RCV bad offset:                 0
    RCV too short:                 0    RCV dup only pack:             16
    RCV dup only bytes:           13    RCV part dup pack:              6
    RCV part dup bytes:           52    RCV bad order pack:           335
    RCV bad order bytes:       49035    RCV pack after wind:            0
    RCV bytes after wind:          0    RCV pack after close:          34
    RCV window probes:            67    RCV dup ACKs:                1042
    RCV ACK for unXMT:             0    RCV ACK packets:           321381
    RCV ACK bytes:          15691799    RCV wind update pack:        1571

> The following abbreviations are used for the TCP counters display:

> - rtt --- retries
> - XMT --- transmit
> - reXMT --- retransmit
> - ACK --- acknowledge
> - URG --- urgent
> - RCV --- receive
> - CTRL --- control
> - chksum --- checksum
> - dup --- duplicate
> - Embry --- embryonic connections (connections not yet established)
> - wind --- window

#2

    UCX> SHOW PROTOCOL TCP /PARAMETERS

    TCP
      MTU size segment:      disabled
      Delay ACK:              enabled
      Loopback:              disabled
      Drop timer:                 600
      Probe timer:                 75

                              Receive                Send

      Checksum:               enabled             enabled
      Push:                  disabled            disabled
      Quota:                     4096                4096
    UCX>

> Displays the TCP parameters.

# SHOW PROXY

> Displays entries in the proxy database.

> Related commands: ADD PROXY, REMOVE PROXY

> Applies to: NFS server, NFS client, PC-NFS, Remote Shell, LPR/LPD, and customer-developed services

## Format

> ### SHOW PROXY [user_name] [/COMMUNICATION | /GID=n | /HOST=host | /NFS=[options] | /UID=n]

## Restrictions

> Requires read access to the proxy database.

## PARAMETERS

> ### user_name

> Optional. Default: SHOW PROXY * (all entries).

> Local OpenVMS identity for the user of NFS server, NFS client, PC-NFS, Remote Shell, or LPR/LPD.

## QUALIFIERS

> ### /COMMUNICATION

> Optional. Default: Both communication and NFS proxies.

> Displays communication proxies.

> ### /GID=n

> Optional. Default: All NFS proxies.

> Displays the database entries for all clients with the specified GID.

> ### /HOST=host

> Optional. Default: All hosts (/HOST=*).

> Remote host from which information is to be displayed.

> ### /NFS=INCOMING

> ### /NFS=OUTGOING

> Optional. Default:
> - For the command: both communication and NFS proxies.
> - For the /NFS qualifier: /NFS=(INCOMING,OUTGOING)

> Displays NFS proxies.

> These entries might be for local clients, remote clients, or PC-NFS clients. Specify one:

> /NFS=OUTGOING | Proxy to use NFS client
> /NFS=INCOMING | Proxy to use NFS server
> /NFS=(OUTGOING,INCOMING) | Both

> ### /UID=n

> Optional. Default: All NFS proxies.

> Displays the database entry for the client with the specified UID.

##

### Examples

#1

    UCX> SHOW PROXY /NFS

    VMS User_name     Type      User_ID    Group_ID   Host_name

    WEBSTER           OD            311          10   *
    SHERMAN           ND            115          10   *
    COHEN             OND           115          10   *
    SILK              ON            115          10   *

> Shows the NFS entries in the proxy database:

> - WEBSTER has authorization to use the local NFS client (outgoing rights).
> - SHERMAN can use the local NFS server (incoming rights).
> - COHEN can use both the NFS server and client.
> - SILK can use both the NFS server and client. This information is not currently known to NFS because SILK is not loaded in the dynamic database.

> In the display, the values in the Type field mean:

> N | NFS server
> O | NFS client
> ON | NFS server and client
> C | Communication
> OD, ND, OND | Loaded in the NFS cache
> CD | Loaded in the communication cache

> To set up N, O, or ON proxies, see ADD PROXY /NFS=INCOMING=OUTGOING.

#2

    UCX> SHOW PROXY /COMMUNICATION

    VMS User_name     Type   Remote User_name         Host_name

    BLUEJAY           CD     JAY                      *
    QUETZAL           CD     quetzal                  central.america.com
    FALCON            CD     FALCON                   HAWK
    MYNA              C      MYNA                     PARROT,parrot
    CANVASBACK        CD     CBACK                    DUCK,duck

> Shows all the communication proxies.

# SHOW ROUTE

> Displays the permanent or volatile routes database. To display the permanent database, specify the /PERMANENT qualifier.

> Looks up the destination you specify first in the hosts database and then, if this lookup fails, in the networks database.

> Displays routes and their types, which can be:

> - N --- Network route
> - H --- Host route
> - A --- Automatic route (generated by SET INTERFACE)

> Related command: SET ROUTE

> Applies to: Routing

## Format

> ### SHOW ROUTE [destination] [/FULL | /GATEWAY=host | /LOCAL | /OUTPUT=file | /PERMANENT]

## Restrictions

> Requires read access to the routes database.

## PARAMETERS

> ### destination

> Optional. Default: Displays all routes.

> Destination host.

## QUALIFIERS

> ### /FULL

> Optional. Default: Displays routes as specified in the routes database.

> Displays mapping between destination addresses and names and gateway addresses and names.

> ### /GATEWAY=host

> Optional. Default: All gateways.

> Displays information for the specified host that performs as a gateway.

> ### /LOCAL

> Optional. Default: The command checks the hosts database and, if a lookup fails, it checks the BIND resolver.

> Limits name-to-address lookups to the local hosts database.

> ### /OUTPUT=file

> Optional. Default: Screen display.

> Sends output to the specified file.

> ### /PERMANENT

> Optional.

> Displays only the permanent routes database.

> - If UCX is running and you omit /PERMANENT, the volatile database is displayed.
> - If UCX is not running, the permanent database is displayed.

##

### Examples

#1

    UCX> SHOW ROUTE /FULL

                                 DYNAMIC database
    Type           Destination                      Gateway

    AN   * 150.111.0.0   destin_host1      * 150.110.5.118   gate_host
    AH     150.111.4.10  destin_host2        150.110.5.120   gate_host_2

> Displays all defined routes.

> An asterisk (*) next to the destination IP address means it was specified with the /ADDRESS qualifier.

> An asterisk next to the gateway IP address means it was specified with the /G_ADDRESS qualifier.

> If the hosts database or networks database has a route that was entered by address, SHOW ROUTE does not display it if you specify a name. Display this route by specifying either its address or a wildcard.

> No host name next to the IP address means there is no entry in the hosts database or networks database for this address.

#2

    UCX> SHOW ROUTE "robin"

> Displays the network route to host robin.

# SHOW SERVICE

> Displays the following information about configured services:
> - Service name
> - Port for listening
> - Protocol
> - Process name
> - IP address
> - State
> - RPC information

> Related commands: SET SERVICE, DISABLE SERVICE, ENABLE SERVICE

## Format

> ### SHOW SERVICE [service] [/ADDRESS=address | /FULL | /PERMANENT | /PORT=n | /PROCESS=process | /PROTOCOL=protocol | /RPC]

## PARAMETERS

> ### service

> Optional. Default: All services.

> Service for which you want information.

## QUALIFIERS

> ### /ADDRESS=address

> Optional. Default: All services.

> Displays information only for services that use the specified address.

> ### /FULL

> Optional. Default: Brief description is displayed.

> Provides a full display.

> ### /PERMANENT

> Optional. Default: UCX not running: permanent; running: dynamic.

> Displays information from the permanent database.

> ### /PORT=n

> Optional. Default: All services.

> Displays information only for services that use the specified port.

> ### /PROCESS=process

> Optional. Default: All services.

> Displays information only for services that use the specified process.

> ### /PROTOCOL=protocol

> Optional. Default: All services.

> Displays information only for services that use the specified protocol.

> ### /RPC

> Optional. Default: No RPC information is displayed.

> Displays RPC information for the service previously set with the /RPC qualifier of the SET SERVICE command. /RPC together with /PERMANENT displays a brief summary of the services that are configured with RPC information.

##

### Examples

#1

    UCX> SHOW SERVICE /RPC /PERMANENT

                             RPC              Protocol Versions
    Service             Program Number         Lowest / Highest

    MOUNT                     100005                 1        1
    NFS                       100003                 2        2
    PCNFS                     150001                 1        2
    PORTMAPPER                100000                 2        2
    UCX>

> Displays all previously set RPC information.

#2

    UCX> SHOW SERVICE NFS /FULL /PERMANENT

    Service: NFS

    Port:             2049     Protocol:  UDP             Address:  0.0.0.0
    Inactivity:          0     User_name: UCX$NFS         Process:  UCX$NFS
    Limit:               1

    File:         SYS$SYSDEVICE:[UCX$NFS]UCX$NFS_STARTUP.COM
    Flags:        UCX

    Socket Opts:  Rcheck Scheck
     Receive:        64000     Send:           64000

    Log Opts:     Acpt Actv Dactv Conn Error Exit Logi Mdfy Rjct TimO Addr
     File:        SYS$SYSDEVICE:[UCX$NFS]UCX$NFS_STARTUP.LOG

    RPC Opts
     Program number:   100003  Low version:      2   High version:      2

    Security
     Reject msg:  not defined
     Accept host: 0.0.0.0
     Accept netw: 0.0.0.0
    UCX>

> The /FULL and /PERMANENT qualifiers display RPC information for the NFS server, whose program number is 100003, lowest version is 2, and highest version is 2. For the NFS server to run, this information is required.

#3

    UCX> SHOW SERVICE PCNFS /FULL /PERMANENT

    Service: PCNFS

    Port:             5151  Protocol:  TCP,UDP         Address:  0.0.0.0
    Inactivity:          0  User_name: UCX$PCNFS       Process:  UCX$PCNFSD
    Limit:               1

    File:         SYS$SYSDEVICE:[UCX$PCNFS]UCX$PCNFSD_STARTUP.COM
    Flags:        UCX Prot

    Socket Opts:  Rcheck Scheck
     Receive:            0     Send:               0

    Log Opts:     Acpt Actv Dactv Conn Error Exit Logi Mdfy Rjct TimO Addr
     File:        SYS$SYSDEVICE:[UCX$PCNFS]UCX$PCNFSD_STARTUP.LOG

    RPC Opts
     Program number: 150001  Lowest version:     1    Highest version:     2

    Security
     Reject msg:  not defined
     Accept host: 0.0.0.0
     Accept netw: 0.0.0.0

> Shows the full configuration in the permanent database for PC-NFS. The RPC information shows that PC-NFS runs as Program 150001, its lowest version number is 1, and its highest version number is 2.

#4

    UCX> SHOW SERVICE PORTMAPPER

    Service     Port      Protocol        Process     Address     State

    PORTMAPPER   111       TCP,UDP      UCX$PORTM     0.0.0.0     Enabled

> Monitors the Portmapper service process, showing that it is enabled.

#5

    UCX> SHOW SERVICE LOADMETRIC /FULL /PERMANENT

    Service: LOADMETRIC

    Port:             6666   Protocol:  UDP             Address:  0.0.0.0
    Inactivity:          5   User_name: UCX$LOADMETRIC  Process:  UCX$METRICD
    Limit:               1

    File:         SYS$SYSDEVICE:[UCX$BIND]UCX$METRIC.COM
    Flags:        Listen

    Socket Opts:  Rcheck Scheck
     Receive:            0     Send:               0

    Log Opts:     Error Rjct
     File:        SYS$SYSDEVICE:[UCX$BIND]UCX$METRIC.LOG

    Security
     Reject msg:  not defined
     Accept host: 0.0.0.0
     Accept netw: 0.0.0.0

> Displays the settings for cluster load balancing.

#6

    UCX> SHOW SERVICE REXEC /FULL /PERMANENT

    Service: REXEC

    Port:              512  Protocol:  TCP              Address:  0.0.0.0
    Inactivity:          5  User_name: not defined      Process:  UCX$REXECD
    Limit:               3

    File:         SYS$SYSDEVICE:[UCX$REXEC]UCX$REXECD_STARTUP.COM
    Flags:        Case Listen Rexe UCX

    Socket Opts:  Rcheck Scheck
     Receive:            0     Send:               0

    Log Opts:     Acpt Actv Dactv Error Exit Mdfy Rjct TimO Addr
     File:        UCX$REXEC.LOG

    Separators:
     Port:   0    User_name: 0    Password:  0    Command:  0

    Security
     Reject msg:  not defined
     Accept host: 0.0.0.0
     Accept netw: 0.0.0.0

> Shows the full configuration in the permanent database for REXEC.

# SHOW VERSION

> Displays the version of the UCX software that is currently running, including individual components.

## Format

> ### SHOW VERSION [/ALL]

## QUALIFIERS

> ### /ALL

> Optional. Default: UCX version.

> Displays the version of all running UCX components.

##

### Examples

#1

    UCX> SHOW VERSION

      DIGITAL TCP/IP Services for OpenVMS VAX Version 4.0
      on a VAX 8800 running OpenVMS V6.0

> Displays the:

> - Version of DIGITAL TCP/IP Services for OpenVMS that is running.
> - Model of hardware platform.
> - Version of OpenVMS that is running.

#2

    UCX> SHOW VERSION /ALL

      DIGITAL TCP/IP Services for OpenVMS Alpha Version 4.0
      on a DIGITAL 4000 Model 620 running OpenVMS V6.2

     Image Name               Image ID           Link Date       Location

    BGDRIVER                 UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYS$LDR]
    UCX$INTERNET_SERVICES    UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYS$LDR]
    UCX$INETACP              UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$INETDRIVER           UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$INET_ROUTING         UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$UCXCP                UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$ACCESS_SHR           UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSLIB]
    UCX$IPC_SHR              UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSLIB]
    UCX$PING                 UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$PORTMAPPER           UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$RPCINFO              UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    SNMP_AGENT               UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    TELNETCLIENT             UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    UCX$TELNETSYM            UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYSEXE]
    TNDRIVER                 UCX VAX 4.0        24-NOV-95     SYS$COMMON:[SYS$LDR]
    .
    .
    .
    NESTING                  BIRDWARE V1        24-NOV-95     SYS$CUSTOM:[SYSEXE]
    HATCHER                  BIRDWARE V1        24-NOV-95     SYS$CUSTOM:[SYSEXE]

> Displays the version of the running UCX components and operating system. Also shows the hardware model.

# START COMMUNICATION

> Starts the lower-layer software on the running system using the information in the relevant databases.

> Reads the UCX configuration database to configure the system upon startup.

> Related command: STOP COMMUNICATION

> > Note

> > DIGITAL strongly recommends that, instead of issuing this command, you run the SYS$COMMON:[SYSMGR]UCX$INET_STARTUP.COM procedure.

## Format

> ### START COMMUNICATION [/INITIALIZE]

## QUALIFIERS

> ### /INITIALIZE

> Optional. Default: Interactively start.

> Upon the next UCX startup:

> - Starts the lower-level internet software, based on the information in the configuration database.
> - Allocates the correct type of buffer --- Ethernet or FDDI --- if neither was defined with the SET COMMUNICATION /TYPE command.
>   (Default settings for buffers are systemwide, not per interface.)
> - Defines interfaces.
> - Enables services.
> - Loads proxies.
> - Enables the BIND resolver.
> - If you defined a cluster address, also:
>   - Sets the cluster timer to 0.
>   - Turns on IP forwarding, eliminating the need for you to issue SET PROTOCOL IP /FORWARD.

## Restrictions

> Requires OPER privileges.

##

### Examples

#1

    UCX> START COMMUNICATION /INITIALIZE

> Upon the next UCX startup, will activate all the software other than the services.

# START MAIL

> Manually starts the SMTP sender queues (not the receiver [server])

> Before you issue this command, the configuration database must have the SMTP configuration.

> Related commands: SHOW MAIL, STOP MAIL, ENABLE SERVICE SMTP, SHOW CONFIGURATION SMTP

> Applies to: SMTP

## Format

> ### START MAIL

## Restrictions

> Requires SYSPRV or BYPASS privileges.

> SMTP consists of the sender and the receiver. Start the sender before you enable the receiver.

> Do not issue this command unless SMTP has been configured (with the SET CONFIGURATION SMTP command).

##

### Examples

#1

    UCX> START MAIL

> Starts the SMTP sender.

> (To start the SMTP sender when UCX starts up, see the SET CONFIGURATION ENABLE SERVICE command. To start the SMTP receiver, see the ENABLE SERVICE command.)

# START ROUTING

> Interactively starts dynamic routing on the running UCX software.

> Related command: STOP ROUTING

## Format

> ### START ROUTING [/SUPPLY=option | /LOG]

## QUALIFIERS

> ### /SUPPLY[=DEFAULT]

> Optional.

> Broadcasts routing information to other hosts (every 30 seconds).

> /SUPPLY=DEFAULT: Local host supplies the default network route.

> ### /LOG

> Optional. Default: No logging.

> Logs routing activity to OPERATOR.LOG.

##

### Examples

#1

    UCX> START ROUTING

> Interactively starts dynamic routing on the running system.

#2

    UCX> START ROUTING /SUPPLY

> Immediately starts dynamic routing. The local host both broadcasts and receives network routing information.

# STOP COMMUNICATION

> Shuts down all the running UCX software, specifically:
> - Stops I/O operations
> - Closes device sockets, pending cancellation of I/O operations
> - Deallocates buffers
> - Deletes interfaces
> - Deletes automatic routes from the routes database

> To resume communications, reload and restart UCX.

> Related command: START COMMUNICATION

## Format

> ### STOP COMMUNICATION

## Restrictions

> - If you use this command, you must also issue several other commands. DIGITAL highly recommends that, instead of this command, you use the UCX$INET_SHUTDOWN.COM procedure.
> - Requires OPER privileges.

# STOP MAIL

> Stops SMTP queuing.

> Usually, you need to issue this command only immediately before issuing ANALYZE MAIL.

> > Note

> > DIGITAL recommends that you do not use this command.

> Related commands: ANALYZE MAIL, SHOW MAIL, START MAIL

> Applies to: SMTP

## Format

> ### STOP MAIL

## Restrictions

> Requires SYSPRV or BYPASS privileges.

##

### Examples

#1

    UCX> STOP MAIL

> Stops SMTP queuing.

# STOP NAME_SERVICE

> Deallocates the existing data structures needed for host lookups and stops the BIND resolver.

> > Note

> > DIGITAL recommends that you do not issue STOP NAME_SERVICE. Use this command only in rare instances when you cannot stop the resolver with normal methods.

> Applies to: BIND resolver

## Format

> ### STOP NAME_SERVICE

##

### Examples

#1

    UCX> STOP NAME_SERVICE

> Stops the BIND resolver.

# STOP ROUTING

> Stops dynamic routing.

> When dynamic routing is running, you cannot use SET NOROUTE to remove a route. To have full manual control over your routing table, issue STOP ROUTING and then use SET NOROUTE.

> Related command: START ROUTING

> Applies to: Routing

## Format

> ### STOP ROUTING

# TCPIPTRACE

> Issue the TCPIPTRACE command at the DCL ($) prompt. For a description of the TCPIPTRACE utility, see the discussion of performance tuning in the DIGITAL TCP/IP Services for OpenVMS Management manual.

# UNBIND

> See the UNMAP command.

# UNMAP

> Makes unknown to the NFS server either a mapped (logically linked) OpenVMS disk or container file system.

> Unmapping removes a logical file system, also called Network File System (NFS). Unmapped file systems are not accessible to remote users working on NFS clients.

> Related commands: MAP, SHOW MAP, SET CONFIGURATION NOMAP

> Applies to: NFS server

## Format

> ### UNMAP /path/name /[NO]NOCONFIRM

## Restrictions

> Requires SYSPRV and BYPASS privileges.

## PARAMETERS

> ### /path/name

> Required.

> UNIX-style name of the file system to unmap.

> You can use wildcards.

## QUALIFIERS

> ### /CONFIRM

> ### /NOCONFIRM

> Optional. Default: /CONFIRM if you use a wildcard.

> Requests confirmation before unmapping each file system.

##

### Examples

#1

    UCX> UNMAP "/disk_host"

> Unmaps the NFS /disk_host.

# ZERO INTERFACE

> Clears statistics for the specified internet interface.

> Related commands: SET INTERFACE, SHOW INTERFACE

## Format

> ### ZERO INTERFACE interface

## Restrictions

> Requires OPER privileges.

## PARAMETERS

> ### interface

> Required.

> Previous | Next | Contents