# DIGITAL TCP/IP Services for OpenVMS
Management

Previous | Contents

FTP performance is affected by the RMS overhead taken up by the file extension process. One way to tune performance is to reset the appropriate parameters. Redefine the FTP logical names that control the following parameters:

- Reset buffer sizes.
- Preallocate disk blocks.
- Increase the inactivity timer.

## A.7.2 Buffer Sizes

Changing the buffer size might improve FTP performance. To set or modify the window size of the send and receive buffers, either define or redefine the logical name UCX$FTP_WNDSIZ.

- For a systemwide change --- Redefine this logical name in the system table.
  Edit the SYS$MANAGER:UCX$SERVICES_SETUP file to add this line:

      $ DEFINE /SYSTEM /EXEC UCX$FTP_WNDSIZ 4096

- For the change to apply to one user --- Define the logical name in the LOGIN.COM file in the default directory of that user.

## A.7.3 File Allocation and Extension Sizes

FTP logical names preallocate disk blocks.

> Note

> FTP tells RMS to truncate unused blocks so that disk space is not wasted.

To reduce the RMS overhead, use the following logical names:

- UCX$FTP_FILE_ALQ --- Allocation quantity
  Specifies the number of blocks to be allocated to a disk file when it is created. For example,

      $ DEFINE UCX$FTP_FILE_ALQ 500

- UCX$FTP_FILE_DEQ --- Default extension quantity
  Specifies the number of blocks to be added when RMS automatically extends the file. For example,

      $ DEFINE UCX$FTP_FILE_DEQ 100

Both of these logical names are specified in the SYS$MANAGER:UCX$SERVICE_SETUP.COM file. Due to the possibility of disk quotas controlling the system, these logical names are defined by default as zero (system RMS defaults) or are undefined. For file transfers between UCX hosts both using VMS Plus mode, these logical names have no effect.

## A.7.4 Inactivity Timer

The larger the inactivity timer, the longer FTP maintains sessions without timing out. Excessive inactive sessions might slow down performance, degrade security, or prevent other users from establishing sessions.

To increase the inactivity timer, change the value of the UCX$FTPD_IDLETIMEOUT logical name (default is 15 minutes).

Example:

    $ DEFINE UCX$FTPD_IDLETIMEOUT 600

# A.8 Printing: LPD

For LPD troubleshooting, use the following tools:

- Log file UCX$LPD_RCV_STARTUP.LOG
  All LPD receiver diagnostic messages are written to this file.
- Logical names UCX$LPD_RCV and UCX$LPD_DEBUG
  These system logical names can turn on all LPR/LPD diagnostic tests. They track what the LPD client sends compared to what the receiver receives.

## A.8.1 UCX$LPD_DEBUG and UCX$LPD_RCV Logical Names

UCX$LPD_DEBUG and UCX$LPD_RCV are independent, as follows:

- LPD_DEBUG
  - Applies to outbound jobs (LPD client).
  - Writes diagnostics to an LPD queue's log file.
- LPD_RCV
  - Applies to inbound jobs (LPD server).
  - Writes diagnostics to the receiver's log file, UCX$LPD_RCV_LOGFILE.LOG.

To define UCX$LPD_DEBUG and UCX$LPD_RCV, issue:

    $ DEFINE /SYSTEM LPD_RCV 7

    $ DEFINE /SYSTEM LPD_DEBUG 7

If you have problems, turn on all the LPR/LPD diagnostics. Define UCX$LPD_DEBUG and UCX$LPD_RCV to 15. However, leaving these diagnostics on during normal use might impact the performance of LPD and produce large log files.

UCX$LPD_DEBUG and UCX$LPD_RCV are bit-mapped values. The low-order three bits turn on all diagnostics generated by either the sender or the receiver.

If you set the fourth bit, the LPD symbiont logs each buffer that it sends over the TCP/IP link, and the LPD receiver logs each buffer that it receives from the TCP/IP link. The log files let you see exactly what the LPD is sending (for outbound jobs) and receiving (for inbound jobs).

To set the fourth bit, issue:

    $ DEFINE /SYSTEM LPD_RCV 8

    $ DEFINE /SYSTEM LPD_DEBUG 8

# A.9 Printing: TELNETSYM

To avoid potential problems with TELNET printing, track the following situations and guidelines.

## A.9.1 Using UCX$TELNETSYM for the First Time

If you use the public domain TELNET symbiont and want to switch to the UCX TELNET symbiont, remember to change the value of /PROCESSOR on the TELNET symbiont queues, including any command procedures that start up the queues. Change:

    /PROCESSOR=TELNETSYM

to:

    /PROCESSOR=UCX$TELNETSYM

## A.9.2 Printing to DIGITAL Terminal Servers

When you print to a DECserver system, ensure that:

- Input flow control for the port you are printing to is set to DISABLED. Issue:

      > CHANGE PORT port INPUT FLOW DISABLED

- The TELNET server for the terminal server port is properly set. Issue:

      > CHANGE PORT port -
      _> TELNET SERVER NEWLINE TO HOST <CRLF>

## A.9.3 Stalled Print Queues

When you print a job to a TELNETSYM queue, a link must be established between the queue and the printer. If there is high contention for the printer, it might be busy, causing the first attempt at link-establishment to fail.

TELNETSYM continues to try to establish the link, according to the retry interval logical name UCX$TELNETSYM_RETRY_INTERVAL. Until the link is established, the execution queue stalls. When the link comes up, the job prints. A "stalled" TELNETSYM queue is not necessarily an error.

If the queue stalls while printing a job, the printer is probably out of paper.

If TELNETSYM causes a print queue to fail, reset the queue. Issue the following command:

    $ STOP /QUEUE /RESET queue_name

## A.9.4 TELNETSYM Logging

OPCOM messages sent by TELNETSYM include the name of the execution queue. In addition, each TELNETSYM queue has a log file named UCX$TELNETSYM_qname.LOG.

If you define the logical name UCX$TELNETSYM_SCRATCH, the log files are stored in the UCX$TELNETSYM_SCRATCH directory.

If you do not define UCX$TELNETSYM_SCRATCH, the log files go into UCX$LPD_SPOOL.

If UCX$LPD_SPOOL is not defined, the log files go into SYS$SPECIFIC:[SYSEXE].

## A.9.5 Format Problems

To track down problems with wrong formatting on the printed page (for example, "garbage" for a graphics file or unwanted blank pages), use Bit 2 of the the TELNETSYM logical name UCX$TELNETSYM_DEBUG. Defining UCX$TELNETSYM_DEBUG helps determine whether or not the source of the problem is TELNETSYM. Follow these steps:

1. Define UCX$TELNETSYM_DEBUG to 4 in the system table. Issue:

       $ DEFINE /SYSTEM UCX$TELNETSYM_DEBUG 4
       $ STOP /QUEUE /RESET TELNETSYM_qname
       $ START /QUEUE TELNETSYM_qname

2. Print the job that does not print properly.
3. Look at the TELNETSYM log file for the queue.
   This file has messages that show you every byte sent over the link to the printer, such as control characters and setup/reset modules.
   If the raw TCP logical name is not defined, you see doubled IAC characters (hexadecimal FF).
   If you print /PASSALL with the raw TCP logical name not defined, the job starts with the TELNET options negotiation sequence "do binary, will binary."
4. Identify the problem. Either fix it or report it to your DIGITAL support representative.
5. Start the TELNETSYM queue.

## A.9.6 Buffer Dumps

TELNETSYM logs control characters and non-printing characters by preceding the hexadecimal value of the byte with a backslash. For example, this sequence:

    Carriage Control
    Form Feed
    Carriage Control
    Line Feed
    Tab
    the text "Use Your Screen Saver to Conserve Energy."
    Carriage Return
    Line Feed

is logged as:

    \0D\0C\0D\0A\09Use Your Screen Saver to Conserve Energy.\0D\0A

The "do binary will binary" sequence starting off a /PASSALL job appears as:

\FF\FD\00\FF\FB\00

# A.10 SLIP

To debug SLIP problems, use the following methods:

- From another window, issue a TCPIPTRACE command to see packets going in and out of the system.
- Watch the modem's Send and Receive data LEDs as you attempt communication with the TELNET or PING commands.
- Display a count of the packets being sent and received on the problem interface, in full screen format, updated every second. Issue:

      UCX> SHOW INTERFACE SLn /CONTINUOUS=1

# A.11 SMTP

Try to narrow down the cause of an SMTP problem by following these steps:

1. Check the directory SYS$SPECIFIC:[UCX_SMTP] for the following log files:
   - UCX$SMTP_LOGFILE.LOG
     Monitors the symbiont (queue activity).
   - UCX$SMTP_RECV_LOGFILE.LOG
     Is created with every message received.
   Purge this directory regularly.
2. Use the logical name UCX$SMTP_LOG_LEVEL debugging tool to define one of the following values:

   Value | Description
   --- | ---
   0 or undefined | No logging
   1 | Log daily activities (similar to UNIX sendmail)
   2 | Log relevant headers
   5 | Log full debugging messages (same as smb_debug)

3. Check the mail in the UCX_SMTP account.
   Lost mail is delivered to the Postmaster's mailbox (UCX_SMTP). Forward SMTP mail to the SYSTEM account for monitoring. By default, there is no remote login allowed into UCX_SMTP.
4. Check the directory SYS$SPECIFIC:[UCX_SMTP] for lost mail.
   If a mail message was undeliverable, and the error message was also undeliverable, an SMTP temporary file is placed in this directory, not in the queue.
5. Check the consistency of the SMTP queues against the directories with the SMTP utility files.
   Issue the ANALYZE MAIL command (see Section A.11.1).

   ## A.11.1 Verifying SMTP Control Files

   The ANALYZE MAIL command verifies the consistency of the SMTP queues with SMTP control files. ANALYZE MAIL does the following:

   - It checks that all the current entries in the SMTP queues have a supporting control file in the mail directory of a user.
     You can specify a user or analyze the mail of all users.
   - It checks that there are no lost control files in the SMTP working directory.
   - The /DELETE qualifier deletes each control file lacking a corresponding queue entry.
   - The /REPAIR qualifier fixes these errors:
     - 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.

   Example 1:
   This command encounters a problem, displays a description and solution, and then requests confirmation before fixing each record.

       UCX> ANALYZE MAIL /REPAIR /CONFIRM

       %UCX-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]:

   Example 2:
   This command creates a summary of SMTP entries and control files for user DRAKE.

       UCX> ANALYZE MAIL DRAKE

       %UCX-I-ANA_RUNING, ANALYZE runs on node DODO

       %UCX-I-ANA_NOENTR, no queue entry found for file
       NEST3$:[DRAKE]93042311394417_DRAKE.UCX_DODO;1

       %UCX-I-ANA_COMPLE, ANALYZE completed on node DODO

       %UCX-I-ANA_FEPAIR, found 0 file-queue entry pairs
       %UCX-I-ANA_DELQEN, deleted 0 queue entries
       %UCX-I-ANA_FILNOQ, found 1 files with no queue entries
       %UCX-I-ANA_FILHLD, holding 0 files in directory
       %UCX-I-ANA_FILDEL, deleted 0 files from the Postmaster directory
       %UCX-I-ANA_SUBFIL, submitted 0 files to the generic queue
       %UCX-I-ANA_FILACE, encountered 0 file access errors
       %UCX-I-ANA_NONCFF, found 0 non-unknown files in Postmaster directory
       %UCX-I-ANA_FILCOR, found 0 corrupted CF files in Postmaster directory

   Example 3:
   This command:

   - Creates a summary of SMTP entries and control files for user DRAKE.
   - Requeues control files lacking corresponding queue entries.
   - Deletes control files created before November 24, 1997.

       UCX> ANALYZE MAIL DRAKE /REPAIR /DELETE=BEFORE=24-NOV-1997

   # A.12 Troubleshooting POP

   The following sections describe ways to troubleshoot problems associated with using the POP server:

   - Review error and OPCOM messages sent to the log file
   - Simulate a POP client and issue XTND commands

   ## A.12.1 Reviewing POP Server Messages

   Many of the problems encountered with using POP pertain to failed or misinterpreted commands or authorization errors. Therefore, you should review the messages provided by the POP server as the first step toward solving problems.

   The POP server logs command error and OPCOM (authorization) messages to the UCX$POP_RECV_STARTUP.LOG file. Appendix B outlines the possible POP server messages you can encounter.

   By default, the POP server sends informative error messages to the client about specific errors. If the UCX SERVICE database log option REJECT is set, the POP server sends OPCOM messages when it rejects POP client commands due to authorization failures. These errors include the receipt of a client's USER command with an invalid user name or a PASS command with an invalid password.

   By default, OPCOM messages are displayed on the client system and listed in the log file. To disable OPCOM messages, disable the REJECT logging option for the POP service as follows:

       $ UCX SET SERVICE POP/LOG=NOREJECT

   ## A.12.2 Using POP Extension Commands

   For troubleshooting purposes, you can simulate a POP client and issue the XTND commands listed in Table A-8 to obtain information.

   Table A-8 POP Extension (XTND) Commands
   Command | Action
   --- | ---
   XTND CLIENT | Logs POP client information (if the client supplies it). Helpful for troubleshooting if you use POP with a variety of POP clients that identify themselves.
   XTND LOGLEVEL | Dynamically adjusts POP logging level. Supported levels are INFORMATIONAL (default), ERROR, THREAD, and DEBUG.
   XTND STATS | Displays POP statistics in the following format:
        +OK Statistics follow

        Version Number : UCX X4.2, OpenVMS V7.1 Alpha

        Logging Level : DEBUG

        Current Time : 1997-04-06 06:13:46

        Start Time : 1997-04-04 06:42:17

        CPU Seconds : 7.89 (0 mins, 7 secs)

        Current Threads : 1

        Total Threads : 6

        Max Threads : 1

        Too Many Threads : 0

        Normal Disconnects : 5

        Abnormal Disconnects : 0

        Client Timeouts : 0

        Blocked Socket Count : 0

        Retrieved Messages : 4

        Retrieved Octets : 1102

        Average Octets : 275

        Minimum Octets : 222

        Maximum Octets : 319

        Auth Failures : 1

        Current Users :

        0. smith
   XTND SHUTDOWN | Performs an orderly shutdown of POP. Waits for current client connections to disconnect. Recommended over the DCL command STOP.

   To simulate a POP client and obtain information:

   1. Issue the TELNET command to the POP port (110).
   2. Using the USER and PASS command, enter your user name and password.
   3. Enter an XTND command.

   For example:

       $ TELNET UCXSYS 110

       %TELNET-I-TRYING, Trying ... 16.20.208.53
       %TELNET-I-SESSION, Session 01, host ucxsys, port 110
       +OK UCX POP server UCX V4.1, OpenVMS V6.1 Alpha at ucxsys.acme.com, up
       since 1996-04-04 06:42:17 <24A00E61._6_APR_1996_06_02_31_15@ucxsys.acme.com>

       USER username

        +OK Password required for "username"

       PASS password

        +OK Username/password combination ok

       XTND LOGLEVEL DEBUG

        +OK logging level changed to debug

       QUIT

        +OK UCX POP server at ucxsys.acme.com signing off.

   # A.13 TELNET

   To improve TELNET performance, try modifying some of the internet parameters. These changes might also decrease the use of system resources.

   ## A.13.1 TELNET Characteristics That Affect Performance

   The settings for the TELNET systemwide characteristics might affect UCX and TELNET performance. To display the TELNET systemwide characteristics, issue:

       UCX> SHOW SERVICE TELNET /FULL

   The command generates a display similar to this:

       Service: TELNET
         State:  Enabled
        Port: 23  Protocol:  TCP  Address:  0.0.0.0
        Inactivity:  1  User_name: Process:  not defined
        Limit:30  Active: 1  Peak:  4
        File: not defined
        Flags:  Listen Priv Rtty
        Socket Opts:  Keepalive
        Receive: 3000  Send:  3000

        Log Opts:  Actv Dactv Conn Error Logi Logo Mdfy Rjct Addr

        File:  not defined

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

   ## A.13.2 Internet ACP Byte Limit Quota

   The TELNET server uses internet device sockets allocated to the internet ancillary control process (INETACP). To run TELNET, increase this process's byte limit quota.

   Edit SYS$COMMON:[SYSMGR]UCX$INET_STARTUP.COM. Modify the /BUFFER_LIMIT qualifier of the DCL RUN command so its value exceeds the following sum:

   - Maximum number of incoming TELNET connections times 5000
   - Maximum number of incoming remote login connections times 5000
   - Number of network interfaces times:
     - 8 times the LRPSIZE for IP (LRPSIZE for a SYSGEN parameter for large request packets)
     - 4 times the LRPSIZE for ARP
     or

         (5000 * TELNET) + (5000 * RLOGIN) + I * (24 * LPRSIZE)

   Example:
   This example calculates /BUFFER_LIMIT=n to be 124,000.

       (5000 * 10) + (5000 * 10) + 24000 =
       50000       + 50000       + 24000 =

       124000

   ## A.13.3 Requests That Cannot Be Satisfied

   The TELNET Server sends the following error message for a TELNET login request that cannot be satisfied: SS$_EXQUOTA. This error is due to insufficient local resources, such as:

   - Too many sessions
     Check to see if the maximum number of allowed concurrent sessions is exceeded. Issue:

         UCX> SHOW SERVICE TELNET

     If this number has been exceeded, the display shows: PEAK=limit. To increase the number of allowed sessions, issue:

         UCX> SET SERVICE TELNET /LIMIT=n

   - Insufficient OpenVMS nonpaged pool
     Check to see if the OpenVMS nonpaged pool is insufficient for servicing a new TELNET connection. If so, monitor the server.
     To tune any of the parameters, redefine the logical names.
   - Excessive OpenVMS login sessions
     Check to see if the limit for maximum OpenVMS sessions is exceeded. If the current value is not appropriate, redefine it.
   - Too few device sockets
     If you discover too few device sockets, see Section A.2.3.1.

   Verify that the CHANNELCNT parameter (in SYSGEN) is larger than the number of simultaneous TELNET and RLOGIN sessions that you plan to support.

   ## A.13.4 Data Buffer Allocation

   To optimize data buffer allocation, TELNET keeps a list of free internal data buffers and control buffers. The default number of internal data buffers is 5. To change this value, issue the SET COMMUNICATION /REMOTE_TERMINAL=LARGE=n command.

   Example:
   These commands reset the number of internal data buffers to 10. The first command is immediate, and the second takes effect upon the next UCX startup.

       UCX> SET COMMUNICATION /REMOTE_TERMINAL=LARGE=10

       UCX> SET CONFIGURATION COMMUNICATION /REMOTE_TERMINAL=LARGE=10

   # Appendix B
   Error Messages

   This appendix lists the error messages that are directed to the user terminal and to the operator console.

   # B.1 Display Terminal Error Messages

   These errors are displayed at the user terminal.

   > %UCX-I-BIND_NONAUTH, The server was changed, but it is nonauthoritative

   Explanation: The address for the given server was not in the BIND database. A nonauthoritative server is a slave server that does not have control over the data. The server gets information from another server (primary or secondary), caches the information, and updates the information periodically. Therefore, the answer provided by this server may not be correct.
   User Action: Check that the given server name has been defined for the system.

   > %UCX-E-BIND_NOSERVERS, Default servers are not available

   Explanation: No BIND servers are defined.
   User Action: Run SYS$MANAGER:UCX$CONFIG to define the default BIND servers.

   > %UCX-W-BIND_NOSERVNAM, Cannot find server name for address

   Explanation: The server name for the given address is not in the local database.
   User Action: Check that the given server address has been defined for the system.

   > %UCX-E-BIND_READERR, Error reading or interpreting query response

   Explanation: The BIND query to the remote server was not completed due to internet communication problems.
   User Action: Check that your internet is properly configured and running and try again. Check the communications with the remote servers by using the command PING.

   > %UCX-E-DUPHOSTNAME, Duplicate UCX$HOST host name for host

   Explanation: An additional IP address has been defined for a host that already exists in the database.
   User Action: None.

   > %UCX-I-HOSTADD, Host information added to database

   Explanation: This message is displayed along with the %UCX-I-DUPHOSTNAME message.
   User Action: None.

   > %UCX-F-NFS_ABORT, NFS server server aborted

   Explanation: Caused by an internal NFS fatal error that is preceded by an NFS error.
   User Action: Examine the log file.

   > %UCX-I-NFS_ACCDEF, Failed to delete account account from volatile database

   Explanation: The record was not found in the volatile database.
   User Action: Check the record information supplied with the REMOVE PROXY command.

   > %UCX-I-NFS_ACCDES, Deleted account account from volatile database

   Explanation: The record was deleted from the volatile database.
   User Action: None.

   > %UCX-W-NFS_ACCNOA, Access to the VMS account account is denied

   Explanation: Someone attempted to access the NFS server over the network when network access was restricted on account account.
   User Action: See your system manager to determine when network access is allowed. You must have network access.

   > %UCX-F-NFS_ALLMEM, Failed to allocate virtual memory in module module

   Explanation: Memory is needed to open another file, but the memory quota was exceeded for the NFS process.
   User Action: Change the virtual memory limit or page file quotas in the NFS startup file.

   > %UCX-F-NFS_AUTHER, Invalid RPC authentication

   Explanation: NFS server did not find entry in proxy database.
   User Action: Check for possible intruder.

   > %UCX-F-NFS_BCPCHH, Failed to assign channel to mailbox n

   Explanation: An OpenVMS system call failed.
   User Action: Examine the error code returned. Check process quotas, privileges, and available memory.

   > %UCX-F-NFS_BCPMBR, Failed to read from mailbox

   Explanation: An OpenVMS system call failed.
   User Action: Examine the error code returned. Check process quotas, privileges, and available memory.

   > %UCX-F-NFS_BCPMBW, Failed to write into mailbox

   Explanation: An OpenVMS system call failed.
   User Action: Examine the error code returned. Check process quotas, privileges, and available memory.

   > %UCX-F-NFS_BCPWAA , Failed to set write attention for mailbox

   Explanation: An OpenVMS system call failed.
   User Action: Examine the returned error code. Check process quotas, privileges, and available memory.

   > %UCX-E-NFS_BFSCAL , BFS_call call failure

   Explanation: The NFS server provides mapping between RMS errors and NFS errors.
   User Action: Depends on the RMS error code returned by the NFS process. To analyze the situation, supply the system manager with the expanded RMS error codes.

   > %UCX-E-NFS_BFSCLS, CLOSE call failure

   Explanation: There is an error in closing a file. The error could be caused by a file protection violation or if the file was being accessed when an attempt was made to close the file.
   User Action: See the error code returned.

   > %UCX-F-NFS_DEAMEM, Failed to deallocate virtual memory in module module

   Explanation: Internal NFS error de-allocating memory.
   User Action: Contact your DIGITAL support representative and provide the following information:
   - Attempt to isolate the cause of the problem to one client and the sequence of the steps.
   - Describe the configuration of the client and server hosts.
   - Submit error and output files to your DIGITAL support representative.

   > %UCX-F-NFS_DEFLNM, Failed to create logical name logical_name

   Explanation: Failure to create one of the run-time logical names.
   User Action: Check default logical names that are set by the NFS startup command file for being present and their values.

   > %UCX-I-NFS_DISERR, Disable writing into the NFS error log file

   Explanation: A SET NFS_SERVER/DISABLE=reporting_option command was issued.
   User Action: None.

   > %UCX-F-NFS_DUPUID, Duplicate NFS proxy information for host host

   Explanation: Information for the specified host was already found in the proxy database. Second occurrence is ignored.
   User Action: Correct the proxy database.

   > %UCX-I-NFS_ENAERR, Enable writing into the NFS error log file

   Explanation: A SET NFS_SERVER/ENABLE=reporting_option command was issued.
   User Action: None.

   > %UCX-I-NFS_ERRLOG, Failed to write into log file

   Explanation: An OpenVMS error follows this error. The error log file is disabled and will remain disabled until the SET NFS_SERVER command is issued.
   User Action: Examine the error message and take appropriate action.

   > %UCX-F-NFS_EXPBCP, Failed to access EXPORT database

   Explanation: There was an error in accessing the export database.
   User Action: Depends on the RMS error code returned by the NFS process. Possible causes include deleting export file or changing protection.

   > %UCX-W-NFS_EXPNRC, Failed to find in EXPORT database file system directory

   Explanation: Unauthorized attempt to mount a directory. It could be an intruder attempt.
   User Action: Check for possible intruder.

   > %UCX-F-NFS_FATERR, NFS Server internal error in module module

   Explanation: Internal program error in the NFS code.
   User Action: Report the problem to your DIGITAL support representative and include the following information:
   - Attempt to isolate the cause of the problem to one client and the sequence of the steps.
   - Describe the configuration of the client and server hosts.
   - Submit error and output files to your DIGITAL support representative.

   > %UCX-F-NFS_FOPLIM, Exceeded FILLM quota or process channel limit

   Explanation: Open files quota for the particular user is exceeded.
   User Action: May need to modify FILLM quota in the account with the AUTHORIZE utility.

   > %UCX-S-NFS_HSTNAM, NFS Server is running on host host

   Explanation: Informational.
   User Action: None.

   > %UCX-F-NFS_INECTL, Error translating host name to host address

   Explanation: Internet software error translating host name into host address.
   User Action: Enter the server host name into the hosts database.

   > %UCX-F-NFS_INIERR, Failed to start NFS Server initialization

   Explanation: Fatal error during initialization before log file was created.
   User Action: Examine the additional NFS or OpenVMS error messages on the operator console.

   > %UCX-F-NFS_INEGBN, Failed to find host host in hosts database

   Explanation: Specified host is not found in hosts database.
   User Action: Add host name and address to the hosts database.

   > %UCX-F-NFS_INETAS, Failed to assign channel to network device

   Explanation: Failure to assign new channel to the device.
   User Action: Check quotas of channels that are available to the process.

   > %UCX-E-NFS_INETWH, Error writing to host host (no name) on socket socket

   Explanation: During a read or write operation, the NFS server attempted to send a message to an unreachable host. NFS could not translate the remote host name into an address.
   User Action: None.

   > %UCX-F-NFS_INETRE, Error reading from socket

   Explanation: Error reading from the network. An OpenVMS error message will follow this message.
   User Action: Examine the OpenVMS status code and determine the cause of the error.

   > %UCX-F-NFS_INETST, Error creating or setting socket parameters

   Explanation: An OpenVMS system call failed.
   User Action: Verify if the NFS process privileges that are set in the NFS startup procedure are correct and then take the appropriate action.

   > %UCX-E-NFS_INETWR, Error writing to socket

   Explanation: Error writing to the network. An OpenVMS error message will follow this error message.
   User Action: Examine the returned error code.

   > %UCX-F-NFS_INICMB , Failed to create mailbox mailbox_address

   Explanation: NFS process failed to create a communication channel with the UCX Management module.
   User Action: Correct the problem specified by the OpenVMS error code. Possible causes are byte limits, quota, insufficient memory, or privilege violation (requires SYSNAM privilege).

   > %UCX-F-NFS_INIEXP, Failed to initialize EXPORT database

   Explanation: There is an error during the initialization stage of accessing the export data base. See the returned status code.
   User Action: Verify the export file accessibility including presence, device, protection, and internal RMS errors.

   > %UCX-F-NFS_INIGPI, Failed to create system logical name logical_name

   Explanation: The OpenVMS system call failed to create the logical name. An OpenVMS error message will follow this message.
   User Action: Examine the error message and take appropriate action.

   > %UCX-F-NFS_INIINE, Failed to establish network communication

   Explanation: Failed to initialize the internet communication software.
   User Action: Examine the error message and take appropriate action.

   > %UCX-F-NFS_INILNM, Failed to find server host logical name

   Explanation: Neither of the server host logical names, UCX$INET_HOST or UCX$NFS_HOST, are defined. If UCX$INET_HOST is not defined, then it is likely that there is no active internet interface.
   User Action: Check the presence and value of all default logical names that are set by the NFS startup process. Correct the error.

   > %UCX-F-NFS_INIMAN, Failed to initialize NFS management subsystem

   Explanation: Failure to initialize connection with the NFS management module.
   User Action: Examine the error message and take appropriate action.

   > %UCX-F-NFS_INIMEM, Failed to initialize virtual memory in module module

   Explanation: The cause of the error could be one of the following:
   - Virtual memory allocation failure caused within the NFS process or a page file quota violation.
   - There is a proxy or export database initialization problem. The problem is caused by errors during the building of the internal database structure.
   User Action: Change NFS process parameters.

   > %UCX-F-NFS_INIPDB, Failed to access Proxy Database

   Explanation: The NFS process cannot access the proxy database.
   User Action: Verify the proxy database file accessibility.

   > %UCX-F-NFS_INIRDB, Failed to get rights information for user user

   Explanation: The OpenVMS rights database does not include the expected rights identifier for the specified user.
   User Action: Verify the rights database information for account account.

   > %UCX-F-NFS_INISCR, UCX$NFS_REMOTE identifier missing rrom Rights database

   Explanation: NFS_SECURITY logical name is set to provide security features, but UCX$NFS_REMOTE identifier is not added to the rights database. This identifier is normally added to the rights database when UCX is installed.
   User Action: Add the UCX$NFS_REMOTE identifier to the rights database.

   > %UCX-F-NFS_INISPI, Invalid NFS server parameters detected

   Explanation: One of the NFS server parameters defined by the logical names has an inappropriate value.
   User Action: Check default logical names that are set by the NFS startup command file and their values.

   > %UCX-F-NFS_INITHR, Failed to initialize multiple threads

   Explanation: An error occurred during the initialization of the multithreading environment. There is a possible virtual memory allocation failure or page file quota violation. See the returned OpenVMS status.
   User Action: Check the default logical values UCX$NFS_THREAD and UCX$NFS_XID to be sure these values are valid and the NFS process parameters in the NFS startup file are correct.

   > %UCX-F-NFS_INIUAI, Failed to get account information for user user

   Explanation: Any proxy database entry using account will be disabled because this account was not found.
   User Action: Verify that account account is in the OpenVMS SYSUAF file.

   > %UCX-F-NFS_INIVDB, Failed to initialize proxy database

   Explanation: Failed to initialize the proxy database. An OpenVMS error message will follow this error message.
   User Action: Examine the error message and take appropriate action.

   > %UCX-S-NFS_INISUC, NFS Server is starting using log file file

   Explanation: Informational.
   User Action: None.

   > %UCX-W-NFS_INTRUD, Inconsistent Hosts Database or intruder attempt

   Explanation: The host IP address cannot be verified. It could be a possible intruder.
   User Action: Check for possible intruder.

   > %UCX-I-NFS_LGFCLO, Failed to close log file

   Explanation: An OpenVMS error will follow this error. The log file becomes disabled and will remain disabled until the SET NFS_SERVER command is issued.
   User Action: Examine the error message and take appropriate action.

   > %UCX-I-NFS_LGFCRE, Failed to create log file

   Explanation: An OpenVMS error will follow this error. The log file becomes disabled and will remain disabled until the SET NFS_SERVER command is issued.
   User Action: Examine the error message and take appropriate action.

   > %UCX-F-NFS_LNMDBG, Failed to translate logical name UCX$NFS00000000_DEBUG

   Explanation: The logical name UCX$NFS00000000_DEBUG could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMERR, Failed to translate logical name UCX$NFS00000000_ERROR

   Explanation: The logical name UCX$NFS00000000_ERROR could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMGID, Failed to translate logical name UCX$NFS00000000_GID

   Explanation: The logical name UCX$NFS00000000_GID could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMHST, Failed to translate logical name UCX$NFS00000000_HOST

   Explanation: The logical name UCX$NFS00000000_HOST could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMINA, Failed to translate logical name UCX$NFS00000000_INACTIVITY

   Explanation: The logical name UCX$NFS00000000_INACTIVITY could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMOPC, Failed to translate logical name UCX$NFS00000000_OPCOM

   Explanation: The logical name UCX$NFS00000000_OPCOM could not be translated.
   User Action: Check value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMSEC, Failed to translate logical name UCX$NFS00000000_SECURITY

   Explanation: The logical name UCX$NFS00000000_SECURITY could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMTDF, Failed to translate logical name UCX$NFS_TIME_DIFFERENTIAL

   Explanation: The logical name UCX$NFS00000000_DIFFERENTIAL could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMTHR, Failed to translate logical name UCX$NFS00000000_THREADS

   Explanation: The logical name UCX$NFS00000000_THREADS could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMUID, Failed to translate logical name UCX$NFS00000000_UID

   Explanation: The logical name UCX$NFS00000000_UID could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-F-NFS_LNMXID, Failed to translate logical name UCX$NFS00000000_XID

   Explanation: The logical name UCX$NFS00000000_XID could not be translated.
   User Action: Check the value of the logical name in the startup command file.

   > %UCX-I-NFS_MNTSUC, Mounted file system directory

   Explanation: Informational.
   User Action: None.

   > %UCX-I-NFS_NOACNT, No NFS Clients authorized to use server

   Explanation: No records in proxy database with valid OpenVMS accounts.
   User Action: Check proxy database and OpenVMS accounts in AUTHORIZATION file.

   > %UCX-F-NFS_NOAMAP, Attempted to set file ownership to unregistered user

   Explanation: Caused by a client trying to set ownership of the file to a user who is not registered in the proxy database.
   User Action: None.

   > %UCX-W-NFS_NOCMAP, Failed to find record in proxy database

   Explanation: Client has no record in the proxy database.
   User Action: Make entry in proxy database, if necessary.

   > %UCX-F-NFS_NODLIM, Exceeded maximum host limit, not all clients can access server

   Explanation: The amount of hosts in the proxy database exceeds the amount of hosts allowed by the parameter that can be set by the logical name UCX$NFS_HOST. Some of the hosts cannot access the server.
   User Action: Change logical name value. Modify the logical UCX$NFS_HOST in the NFS startup file and restart the NFS server.

   > %UCX-F-NFS_NOPROC, Unknown procedure in RPC message

   Explanation: RPC request for the procedure is not supported by the NFS server.
   User Action: Verify that the client supports the NFS software version.

   > %UCX-F-NFS_NOPROG, Requested RPC program unavailable

   Explanation: RPC request for the procedure is not supported by the NFS server.
   User Action: Verify that the client supports the NFS software version.

   > %UCX-W-NFS_NOSMAP, Failed to find Proxy record for default account to map supervisor

   Explanation: The NFS process changes the root client's UID and GID into values specified by UCX$00000000UID and UCX$00000000GID logical values. The proxy database must have a record to map the UID/GID into an OpenVMS account. Either the record is not in proxy database or the OpenVMS account does not exist or it is disabled.
   User Action: Check OpenVMS account and add proxy record if necessary.

   > %UCX-W-NFS_PORTNP, Remote service requested from nonprivileged port

   Explanation: Security logical name is set to disable nonprivileged ports from connecting to the NFS server and there is a message from the nonprivileged port.
   User Action: Identify the client.

   > %UCX-F-NFS_PROGVS, Invalid RPC program version number

   Explanation: RPC made a request for a program or program version that is not supported by the NFS server.
   User Action: Determine if the client supports the correct version of the NFS software.

   > %UCX-F-NFS_PRXEMP, Proxy Database file is empty

   Explanation: No information in the proxy database. No clients will be able to access the server.
   User Action: Create and populate a proxy database.

   > %UCX-I-NFS_READDF , Failed to add account account to volatile database

   Explanation: The record was not added to the volatile database for one of the following reasons:
   - The record already exists in the volatile database.
   - The dynamic memory failed.
   - UCX failed to get the information for the account from the UAF file.
     Either the account was not in the UAF file or the account was disabled.
   - The host names limit has been reached.
   - Incorrect input data was used.
   User Action: Depending on the reason that the add failed, do the following:
   - If the record already exists in the volatile database, no action is necessary.
   - If the dynamic memory allocation failed, provide enough memory for the process by either increasing the page file quotas in the NFS startup file or use SYSGEN to increase the virtual page count.
   - If the account is not in the SYSUAF, you must add the account.
   - If the account is disabled, you must enable the account.
   - If the host names limit has been reached, you must increase the value for the host names parameter in the UCX$_NFSSTARTUP.COM and restart NFS.
   - If incorrect input data was used, correct the information supplied by the parameters with the UCX management command.

   > %UCX-I-NFS_READDS, Added account account to volatile database

   Explanation: The record record was added to the volatile database
   User Action: None.

   > %UCX-F-NFS_RPCPRS, Invalid RPC message format

   Explanation: The client host is using a protocol different from the server.
   User Action: Verify that the client supports the correct NFS protocol version.

   > %UCX-I-NFS_SETGID, Setting default GID to GID

   Explanation: A SET NFS_SERVER/GID_DEFAULT=gid command was issued.
   User Action: None.

   > %UCX-I-NFS_SETITM, Setting inactivity timer to hh.mm

   Explanation: A SET NFS_SERVER/INACTIVITY_TIMER=time command was issued.
   User Action: None.

   > %UCX-I-NFS_SETUID, Setting default UID to UID

   Explanation: A SET NFS_SERVER/UID_DEFAULT=uid command was issued.
   User Action: None.

   > %UCX-I-NFS_SHUTDW, NFS Server is shutting down

   Explanation: Server is shutting down.
   User Action: None.

   > %UCX-E-NFS_STALEF, operation uses stale file handle

   Explanation: The NFS client cached and used a file handle, but the file did not exist.
   User Action: None.

   > %UCX-E-STARTERROR, Error starting service service

   Explanation: A START SERVICE command was executed, and the specified service was already active.
   User Action: None.

   > %UCX-E-STOPERROR, Error stopping service service

   Explanation: A STOP SERVICE command was executed, and the specified service was not active.
   User Action: None.

   > %UCX-E-SUBNAM, Substitute host name host for host name

   Explanation: An NFS client used an alias host name that was not in the volatile proxy database. NFS updates the volatile database.
   User Action: None.

   > %UCX-F-NFS_UIDMAX, Invalid UID range

   Explanation: Maximum UID value of 65535 is exceeded by the client.
   User Action: Enter an acceptable UID value.

   > %UCX-I-NFS_UMASUC, All file systems are unmounted

   Explanation: Informational.
   User Action: None.

   > %UCX-I-NFS_UMNSUC, Unmounted file system directory

   Explanation: Informational.
   User Action: None.

   > %UCX-W-NFS_USRMNT, User-level mount request rejected

   Explanation: Security logical name is set to disable user level mounts on the server, and an attempt was made to do a mount.
   User Action: Change security logical value if necessary.

   > %UCX-W-NFS_VDBREC, NFS proxy account account disabled, client record ignored

   Explanation: A user's account on OpenVMS is disabled. This user will not be able to access NFS server.
   User Action: Enable OpenVMS account if necessary.

   > %UCX-I-UCX_ACPQIO , Failure on Internet ACP QIO

   Explanation: An interface operation requiring the INET_ACP has failed.
   User Action: Review the interface command and re-enter with corrected information.

   > %UCX-I-UCX_ADR_HOST , IP address specifies a host

   Explanation: The IP address specifies a host address when a network address is required.
   User Action: Reissue the command with the network address.

   > %UCX-I-UCX_ADR_NETW, IP address specifies a network

   Explanation: The IP address specifies a network address when a host address is required.
   User Action: Reissue the command with the host address.

   > %UCX-I-UCX_ALIAS, Record is an alias

   Explanation: The host or network information returned from the database came from an alias of a host or network entry.
   User Action: None.

   > %UCX-E-UCX_ARPERROR, Error processing ARP request

   Explanation: An error was detected while processing an ARP command.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the ARP command and re-enter the command.

   > %UCX-E-UCX_BCPMBX , Cannot open UCX data mailbox

   Explanation: UCX could not open a temporary mailbox that it uses to receive data from NFS and the UCX directory.
   User Action: Check for the required process privileges and process quotas.

   > %UCX-E-UCX_BINDERROR, Error processing BIND or UNBIND request

   Explanation: An error was detected while processing a BIND or UNBIND command.
   User Action: If the error is a duplicate name, then issue a SHOW BIND command for a list of bound directories. See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the BIND or UNBIND command and re-enter the command.

   > %UCX-E-UCX_BINDNOCFS, Container directory is not bound

   Explanation: An operation involving a container directory is being attempted, and the container directory has not been bound.
   User Action: Execute a BIND command for the container directory.

   > %UCX-E-UCX_BINDNOSYS, File system is not bound

   Explanation: An operation involving a directory, which is in a container directory or on an OpenVMS disk, is being attempted, and the file system has not been bound.
   User Action: Execute a BIND command for the directory.

   > %UCX-E-UCX_BINDNOVMS, Target VMS disk volume is not bound

   Explanation: An operation involving a container file is being attempted, and the OpenVMS disk where the container directory resides has not been bound.
   User Action: Execute a BIND command for the OpenVMS disk on which the container directory is to reside.

   > %UCX-F-UCX_BUGCHK, UCX internal error

   Explanation: There is an internal error in the UCX code.
   User Action: Contact your DIGITAL support representative and provide the following information:
   - A description of the command that was entered.
   - The saved database files, if the command involved one or more databases.

   > %UCX-E-UCX_CFSERROR, Error processing UCX file system request

   Explanation: An error was detected in an operation requiring a call to the UCX directory.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_CMDERR, NFS command error

   Explanation: NFS does not have the functionality to process a command sent by the UCX component.
   User Action: Check to see that the UCX and NFS processes were derived from the same UCX release.

   > %UCX-E-UCX_COMERR, NFS Server has not created a command mailbox

   Explanation: NFS is still in an initialization state. It has not created a mailbox to which the UCX component can issue commands.
   User Action: Wait until NFS has completed initialization and reissue the command.

   > %UCX-E-UCX_DATAPROB, Error accessing the database database

   Explanation: There was an error in accessing the database database.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_DELINTER, Error deleting interface: interface

   Explanation: The specified interface could not be deleted.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-I-UCX_DIRECTORY, Path name resolves to a directory

   Explanation: A path name that is a directory was specified for a container directory operation that requires a data file as an object.
   User Action: Issue a DIRECTORY command on the directory to locate the target file.

   > %UCX-I-UCX_DRIVERQIO, Failure on internet driver QIO

   Explanation: An interface operation that is handled by the internet driver has failed.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the interface command and re-enter with corrected information.

   > %UCX-W-UCX_DUPALLHOST, File system already exported to all hosts

   Explanation: A new record was added to the export database; however, the directory was already exported to all hosts.
   User Action: None required; however, you may want to review the export database entries for this directory to eliminate duplicate entries.

   > %UCX-W-UCX_DUPHIEXPO, File system already exported at higher level

   Explanation: A new record was added to the export database; however, the directory was already exported to the host at a higher level. For example, the new record specified /a/b, when /a was already present in the database.
   User Action: None required; however, you may want to review the export database entries for this directory to eliminate duplicate entries.

   > %UCX-E-UCX_DUPHOST, Duplicate UCX$HOST entry for host

   Explanation: Information specified in a SET HOST command is already present in the hosts database.
   User Action: None.

   > %UCX-W-UCX_DUPHOSTEXPO, File system already exported at specific host

   Explanation: A new host record, specified with a wildcard, was added to the export database; however, the directory was already exported to a specific host.
   User Action: None required, but you may want to review the export database entries for this directory to eliminate duplicate entries.

   > %UCX-W-UCX_DUPLOEXPO, File system(s) already exported at lower level

   Explanation: A new record was added to the export database; however, a directory was already exported to the host at a lower level. For example, the new record specified /a, when /a/b was already present in the database.
   User Action: None required; however, you may want to review the export database entries for this directory to eliminate duplicate entries.

   > %UCX-E-UCX_DUPNETWORK, Duplicate UCX$NETWORK entry for network

   Explanation: Information specified in a SET NETWORK command is already present in the networks database.
   User Action: None.

   > %UCX-E-UCX_DUPRECORD, Duplicate record information

   Explanation: You attempted to enter a record that has duplicate key information.
   User Action: Issue a SHOW command for the particular database to obtain a list of entries.

   > %UCX-E-UCX_ETCHOST, Error processing /etc/hosts file

   Explanation: A UNIX-formatted /etc/hosts file could not be accessed while processing a CONVERT/qualifier HOST command.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the CONVERT command.

   > %UCX-E-UCX_ETCNETWORK, Error processing /etc/networks file

   Explanation: A UNIX-formatted /etc/networks file could not be accessed while processing a CONVERT/qualifier NETWORK command.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the CONVERT command.

   > %UCX-E-UCX_ETCPASSWD, Error processing /etc/passwd file

   Explanation: A UNIX-formatted /etc/passwd file could not be accessed while processing a CONVERT PROXY command.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the CONVERT command.

   > %UCX-I-UCX_EXPORTADD, Export information added to database

   Explanation: Information was added to the export database although there were some warning messages.
   User Action: None.

   > %UCX-E-UCX_EXPORTERROR, Error processing EXPORT request

   Explanation: An error was detected in an operation requiring an access to the export database.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-I-UCX_FILE, Path name resolves to a file

   Explanation: A path name that is a data file was specified for a container file system operation that requires a directory as an object.
   User Action: Issue a DIRECTORY command on the directory to locate the target directory.

   > %UCX-W-UCX_FLDTRN, Field value has been truncated : field_value

   Explanation: The specified string or integer value is greater than the maximum field size.
   User Action: Make the specified string or integer value smaller than the maximum field size.

   > %UCX-E-UCX_HOSTERROR, Error processing HOST request

   Explanation: An error was detected in an operation requiring an access to the hosts database.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_IMPLEMENT , This service has not been implemented

   Explanation: You issued an unsupported command.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for the names of all the supported comamnds.

   > %UCX-E-UCX_INETERROR , Error accessing internet

   Explanation: An error was detected in an operation requiring access to UCX internet software.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_INSARP, Insufficient ARP information

   Explanation: You attempted to add an ARP table entry but did not provide enough information.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for information about the SET ARP command.

   > %UCX-E-UCX_INSKE, Insufficient information for record record

   Explanation: You attempted to enter a record into a database, but you did not specify enough information.
   User Action: Reissue the command with the necessary qualifiers.

   > %UCX-E-UCX_INTEERROR, Error defining or modifying interface

   Explanation: An error was detected in specifying an internet interface.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_INVADR , Invalid IP address: IP_address

   Explanation: The IP address specified has an invalid format.
   User Action: Correct the IP address. See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for an explanation of valid IP addresses.

   > %UCX-E-UCX_INVBRDMASK , Invalid broadcast mask

   Explanation: There is a syntax error in the specification of an internet broadcast mask.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Concepts and Planning guide for a description of an internet broadcast mask.

   > %UCX-E-UCX_INVCLUST , Invalid cluster definition for interface: interface

   Explanation: The cluster host for the interface could not be defined.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the SET INTERFACE command.

   > %UCX-E-UCX_INVDEVNAME , Invalid internet device name

   Explanation: The device name you specified is not valid.
   User Action: For a discussion of valid internet device names, see Chapter 2.

   > %UCX-E-UCX_INVDIR, Error referencing VMS directory

   Explanation: There is a problem in translating an OpenVMS directory specification. Typically, this error is caused by a logical name being the same as the directory name.
   User Action: Examine the directory specification for errors. If this error occurred when a path name was specified, issue a SHOW BIND command to examine the OpenVMS directory specification.

   > %UCX-E-UCX_INVDISK, Invalid VMS disk specification

   Explanation: An incorrect syntax has been specified for an OpenVMS disk device.
   User Action: Issue SHOW DEVICE for a list of valid OpenVMS disk names.

   > %UCX-E-UCX_INVETHER, Invalid Ethernet address: address

   Explanation: The Ethernet address specified has an invalid format.
   User Action: Reissue the command with an Ethernet address with the format xx-xx-xx-xx-xx-xx, where xx is a 2-character hexadecimal value.

   > %UCX-E-UCX_INVETHERNAM, Invalid Ethernet name

   Explanation: This is a UCX$UCP internal error.
   User Action: Report the problem to your DIGITAL support representative with a copy of the command that was used when the error occurred. Include a listing from a SHOW INTERFACE command.

   > %UCX-E-UCX_INVGATEWAY, Gateway specifies a network

   Explanation: The gateway for a route specified using a SET ROUTE /GATEWAY or a SET ROUTE /G_ADDRESS specifies a network address.
   User Action: Reissue the SET ROUTE command with a gateway that specifies a host address.

   > %UCX-E-UCX_INVINTER, Error defining interface: interface

   Explanation: A problem was encountered while trying to process an interface request.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_INVINTERNAM, Invalid interface name

   Explanation: The specified interface name is not valid.
   User Action: Review the list of supported UCX interface device names.

   > %UCX-E-UCX_INVKEY , Invalid information for file file

   Explanation: A value for a key was not in an acceptable range of values.
   User Action: See the command description for the command you want to issue in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.

   > %UCX-E-UCX_INVNET, Invalid network number: network_number

   Explanation: There is a syntax error in the specification of an internet network number, probably because the IP address specifies a host.
   User Action: Check that a valid address exists for the host. For a description of network numbers, see the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.

   > %UCX-E-UCX_INVNETADDR, Invalid IP address

   Explanation: There is a syntax error in the specification of the IP address.
   User Action: Correct the syntax error. For a description of IP addresses, see the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.

   > %UCX-E-UCX_INVNETFLAG , Invalid interface flags

   Explanation: An illegal combination of flags was entered with a SET INTERFACE command.
   User Action: For a description of the /FLAGS qualifier of the SET INTERFACE command, see the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.

   > %UCX-E-UCX_INVNETMASK, Invalid network mask

   Explanation: There is a syntax error in the specification of an internet network mask.
   User Action: For a description of internet network masks, see Chapter 4 in this manual.

   > %UCX-E-UCX_INVPARM , Invalid parameter value for: parameter

   Explanation: A parameter value from a command line could not be processed.
   User Action: See the complete description of the command you want to issue in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference.

   > %UCX-E-UCX_INVPATH, Invalid path name

   Explanation: There is a syntax error in the specified path name.
   User Action: Correct the syntax of the path name and resubmit the command.

   > %UCX-E-UCX_INVQUAL, Invalid qualifier value for /qualifier

   Explanation: A qualifier value from a command line could not be processed.
   User Action: See the command description for the command you want to issue in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual.

   > %UCX-E-UCX_INVRECORD, Invalid record for file file

   Explanation: An RMS error occurred while RMS tried to access a database file.
   User Action: The error message contains the RMS status. See the RMS documentation.

   > %UCX-E-UCX_INVSOCKNAM, Invalid socket name

   Explanation: There is a syntax error in the socket specification.
   User Action: Correct the syntax of the device socket name and reissue the command. You may want to execute a SHOW DEVICE command to obtain a list of device sockets on your system.

   > %UCX-I-UCX_LOOPACT, operation is alive

   Explanation: The LOOP operation to the specified host is successful and the host has responded.
   User Action: None.

   > %UCX-E-UCX_LOOPERROR, Error processing LOOP request

   Explanation: A problem was encountered while trying to process a LOOP request.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-I-UCX_LOOPINACT, operation does not respond

   Explanation: The LOOP operation to the specified host is successful, but the remote host has not responded.
   User Action: None.

   > %UCX-E-UCX_MISROUTE, Routes Database mismatch

   Explanation: There is an inconsistency in the routes database, normally due to an entry in the routes database that specifies a host or network that is no longer present in the internet database.
   User Action: Issue the SHOW ROUTE command to determine the problem.

   > %UCX-E-UCX_NETWORKERROR, Error processing NETWORK request

   Explanation: An error was detected in an operation requiring access to the networks database.
   User Action: Other messages are printed with this error. Review these messages to determine the problem.

   > %UCX-E-UCX_NFSERROR, Error communicating with NFS

   Explanation: A problem was encountered while trying to communicate with the NFS process.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_NFSMBX, Cannot open NFS command mailbox

   Explanation: The UCX component has insufficient privileges to find information about the NFS server.
   User Action: Check the process privileges and the process quotas.

   > %UCX-W-UCX_NOARP, No ARP entries found

   Explanation: There is no ARP entry for the specified host. If the specified host is not currently accessing the local host, no ARP entry is present.
   User Action: None.

   > %UCX-W-UCX_NOAUTOROUT, Automatic route not found

   Explanation: An interface's IP address is being modified, and there is no automatic route record present in the routes database.
   User Action: No action is necessary; however, this condition signals the possibility that the routes database is corrupted.

   > %UCX-E-UCX_NOCONTAINER, Container file not found

   Explanation: The specified container file does not reside in the named directory.
   User Action: Issue SHOW BIND to find the container file's OpenVMS directory.

   > %UCX-E-UCX_NOCONVERT , Specify /ULTRIX or /VMS

   Explanation: A CONVERT command was issued without specifying /ULTRIX or /VMS.
   User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more information about the CONVERT command.

   > %UCX-E-UCX_NOCREATE, Could not create database

   Explanation: A problem was encountered while trying to create a UCX database file.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_NODESTNAM, Destination name is not defined

   Explanation: The host or network name that was specified with a SET ROUTE command has not been defined in the host or networks database.
   User Action: Do the following:
   1. Define the host name with a SET HOST command.
   2. Define the network name with a SET NETWORK command.
   3. Issue a SET ROUTE /ADDRESS command.

   > %UCX-W-UCX_NODEVLOCL , Local device not found

   Explanation: A LOOP command is being requested and the local interface is not defined.
   User Action: Execute the command procedure SYS$MANAGER:UCX$INET_SET_INTERFACES.COM in order to define the local host.

   > %UCX-E-UCX_NOFILE , Cannot find file file

   Explanation: The logical name that points to a UCX database has not been defined, or a logical name points to a database file specification that has no corresponding file.
   User Action: Check all database logical name definitions. See the DIGITAL TCP/IP Services for OpenVMS Installation and Configuration manual for a list of logical database file names.

   > %UCX-E-UCX_NOFUNCTION, Unsupported function

   Explanation: CFS does not have the functionality to process a command sent by the UCX component.
   User Action: Check to see that the UCX and NFS processes were derived from the same UCX component release.

   > %UCX-E-UCX_NOGATENAM, Gateway name is not defined

   Explanation: The host name specified with a SET ROUTE/GATEWAY command has not been defined in the hosts database.
   User Action: Define the host name with a SET HOST command or issue a SET ROUTE/G_ADDRESS command.

   > %UCX-E-UCX_NOINET, The internet driver is not loaded

   Explanation: You attempted to perform an internet command, and the internet software has not been installed or activated.
   User Action: Activate or install the internet software. See the DIGITAL TCP/IP Services for OpenVMS Installation and Configuration manual for the installation procedure.

   > %UCX-E-UCX_NONFS, NFS Server is not active

   Explanation: The NFS server has not been started.
   User Action: Start the NFS server.

   > %UCX-E-UCX_NOPATH, No files found

   Explanation: No files were present for the specified DIRECTORY command.
   User Action: Issue the directory command with a wildcard to obtain a list of files present in the directory.

   > %UCX-E-UCX_NOPRIV, Insufficient privilege for command command

   Explanation: Insufficient privilege for command command.
   User Action: See the command description of the command you want to issue in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference. It lists the required privileges.

   > %UCX-E-UCX_NORESPOND , NFS Server is not responding

   Explanation: One of the following has happened:
   - The NFS server did not respond to the UCX management command you issued before the UCX communication timer expired. This is expected when the server is busy processing NFS requests.
   - The NFS process was stopped during the execution of a UCX management command.
   User Action: Perform one of the following actions:
   - If the NFS server is still active, reissue the command.
   - If the NFS server has been stopped, restart it.

   > %UCX-W-UCX_NORECORD , Information not found

   Explanation: The information requested does not exist in a database where logical_name is the logical name for the database file.
   User Action: Re-enter the command.

   > %UCX-E-UCX_NOSERVICE , No such service

   Explanation: The service specified to an NFS command is not known to the NFS process.
   User Action: Issue a SHOW NFS /SERVICE command for a list of supported NFS services.

   > %UCX-E-UCX_NOTSTARTED, The internet software has not been started

   Explanation: A command that requires active UCX internet software was attempted.
   User Action: Execute the command procedure SYS$MANAGER:UCX$INET_STARTUP.COM to start the UCX internet software.

   > %UCX-E-UCX_NOUSER, No such user

   Explanation: A SHOW NFS /USERNAME command was issued with a specified user who is not known to the NFS process.
   User Action: Re-enter with the proper name.

   > %UCX-I-UCX_NOVMSUSER, VMS user: user does not exist

   Explanation: The OpenVMS user name for the proxy record was added with the ADD PROXY command but has not been defined in the OpenVMS UAF file.
   User Action: Define the OpenVMS user name with the OpenVMS Authorize utility.

   > %UCX-I-UCX_PARENT, Record is a parent

   Explanation: The host or network information returned from the database came from an original host or network entry (not an alias).
   User Action: None.

   > %UCX-E-UCX_PROTERR, Unsupported protocol

   Explanation: There is a communication protocol mismatch between UCX and NFS processes. This may occur when the UCX and NFS processes are derived from dissimilar releases.
   User Action: Check to make sure that the UCX and NFS processes come from similar UCX releases.

   > %UCX-I-UCX_PROXYADD, Proxy information added to database

   Explanation: Information was added to the proxy database although there were warning messages.
   User Action: None.

   > %UCX-E-UCX_PROXYERROR, Error accessing proxy database

   Explanation: An error was detected in an operation requiring access to the proxy database.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_ROUTEERROR, Error accessing Routes Database

   Explanation: An error was detected in an operation requiring access to the routes database.
   User Action: Other messages are printed with this error. Review these messages to correct the problem.

   > %UCX-E-UCX_SEQERR, NFS transaction sequence error

   Explanation: There is an internal communication message mismatch between UCX and NFS processes.
   User Action: Reissue the last command and if the problem persists, rerun UCX.

   > %UCX-E-UCX_STARTED, The internet software has been started

   Explanation: A command was attempted that requires the UCX internet software to be inactive.
   User Action: Execute the command procedure UCX$INET_SHUTDOWN.COM, located in SYS$MANAGER:, to stop the UCX internet software.

   # B.2 PING Messages

   > %UCX-E-UCX_PACKLARGE, Packet size too large

   Explanation: The maximum packet size that PING accepts is 4088 bytes.
   User Action: Rerun PING with a smaller packet size.

   > %UCX-E-UCX_CRSOCK, Error in creating a socket

   Explanation: Failed to create an end point communication. This error is most commonly seen if there is a network error, or if network has not been started, or when the device socket quota exceeds the limit set by the system manager.
   User Action: Make sure network communication is active on the system. Change the limit that is set for the socket quota. If you cannot change it, ask the system manager to change it.

   > %UCX-E-UCX_GETHST, Error in getting host name

   Explanation: Failed to get the host information.
   User Action: Check to see whether the hosts database exists. Check that the remote host is in the database.

   > %UCX-I-UCX_RECVERR, Error in receiving packet

   Explanation: Failure in receiving the ICMP packet reply over the network. This might be due to a network communication problem.
   User Action: Check to see whether the network communication is up and running properly. If the error persists, contact your DIGITAL support representative and describe the conditions leading to the error.

   > %UCX-E-UCX_MALLERR, Error in memory allocation

   Explanation: Failed to allocate memory before ioctl call.
   User Action: Check memory allocation.

   > %UCX-E-UCX_IOCTLERR, Error in ioctl

   Explanation: The call to ioctl failed.
   User Action: Contact your DIGITAL support representative and describe the conditions leading to the error.

   > %UCX-E-UCX_SENDERR, Error in sending packet

   Explanation: Failure in sending the ICMP packet over the network. This might be due to a network communication problem.
   User Action: Check to see whether the network communication is up and running properly. If the error persists, contact your DIGITAL support representative and describe the conditions leading to the error.

   > %UCX-E-UCX_LOOPINTERR, Internal error

   Explanation: Internal error in the ping interface or in time routines.
   User Action: Contact your DIGITAL support representative and describe the conditions leading to the error.

   # B.3 File System Messages

   This section contains file system error messages that are directed to the operator's console by default. If the messages cannot be written to the operator's console, they are directed to the device defined by the logical name UCX$CFS_FATAL_MESSAGES. This logical name must point to a device, because the messages are written using $QIO system service calls.

   > %UCX-E-CFS_ATTRFAIL, Failed to [read/write] file attributes

   Explanation: The file system attempted to read or write a file's attributes using the appropriate Files-11 QIO, and it received an error message that it did not expect.

   > %UCX-E-CFS_DATAFAIL, Failed to [read/write] file data

   Explanation: The file system attempted to read or write virtual blocks of a file, and it received an error message that it did not expect.

   > %UCX-E-CFS_DEACCESS, Files to de-access file

   Explanation: The file system received an error message when it attempted to de-access a file using the appropriate Files-11 QIO.

   > %UCX-E-CFS_DASSGN, Failed to de-assign channel

   Explanation: The file system received an error message when it attempted to de-assign a channel as part of de-accessing a file.

   > %UCX-E-CFS_DELETEINO, Failed to delete inode

   Explanation: NFS attempted to delete an inode within the file system's container file, and the underlying file system routines returned an unexpected error.

   > %UCX-E-CFS_ERROR, Error: error_text

   Explanation: This message is used to return error information that does not indicate a problem with the file system. Rather, this information is of general use to the system manager in determining the cause of other types of problems.

   > %UCX-E-CFS_INVFSDEF, Incompatible file system definition

   Explanation: A file system definition in the UCX$CFS_* logical name tables is either from a previous release or was placed into the table without using UCX.

   > %UCX-E-CFS_IVCHAN, Invalid CFS channel number

   Explanation: A problem was detected when processing an internal UNIX file system channel.

   > %UCX-E-CFS_LCKDEQ, Attempt to $DEQ lock failed, lock ID hex-lock-ID

   Explanation: An unexpected error was returned when the file system attempted to $DEQ a resource lock.

   > %UCX-E-CFS_LCKENQ, Attempt to $ENQ lock failed

   Explanation: An unexpected error was returned when the file system attempted to $ENQ a resource lock. Often this message indicates that a process quota is too low.

   > %UCX-E-CFS_LCKLCKD, Attempt to lock resource previously locked

   Explanation: An attempt to lock a resource on which a lock is already held by the current file system operation was detected.

   > %UCX-E-CFS_LCKNCVT, Attempt to $ENQ lock from <lock-mode> to lock-mode failed

   Explanation: An attempt to change the lock mode of a particular resource has failed. The starting and requested modes are shown.

   > %UCX-E-CFS_ULCKNLCKD, Attempt to release resource not previously locked

   Explanation: An attempt to unlock a resource on which no lock is currently held for the current file system operation was detected.

   > %UCX-E-CFS_UNXBLKAST, Unexpected blocking AST received for type 0-4

   Explanation: A blocking AST was received, indicating that the file system's notion of a resource lock's state is not consistent with the system's view.

   > %UCX-E-CFS_UNXQIOSTS, Unexpected $QIO status returned

   Explanation: An unexpected return status was detected for a $QIO. This message is generated purely for diagnostic purposes and does not indicate a problem in the file system.

   > %UCX-E-CFS_VMSDIRFMT, Inconsistent format within VMS directory file

   Explanation: The contents of an OpenVMS ODS2 directory do not appear to be valid. This message is generated to warn the system manager that the file system attempted to read a directory (NFS READDIR) that did not contain valid contents.

   > %UCX-E-CFS_VMSDIRINI, Failed to initialize VMS directory contents

   Explanation: Part of the OpenVMS directory creation code failed. In particular, the directory entry has been created and the file header initialized, but the initial data blocks of the directory were not written properly.

   > %UCX-E-CFS_PRCEXIT, Process exit forced due to unrecoverable condition

   Explanation: The file system code executing in EXECUTIVE mode detected a condition from which it could not recover. It deemed the situation severe enough to terminate the process. It generates this message as a courtesy to the system manager, to explain the reason for the disappearance of a process.

   Previous | Next | Contents