# DIGITAL TCP/IP Services for OpenVMS
Management

Previous | Contents

The following messages can appear in conjunction with the prior messages to provide additional information about the particular problem that is being reported:

> %UCX-I-CFS_BIND, File system file-spec bound as path-spec

> %UCX-I-CFS_CHANNEL, Channel number hex-number

> %UCX-I-CFS_CLUSTER, Virtual blocks start through end

> %UCX-I-CFS_CONTAINERID, Container device-file-ID-spec

> %UCX-I-CFS_FHANDLE, File handle hex-file-handle

> %UCX-I-CFS_FILENAME, File name file-name-string

> %UCX-I-CFS_FILESPEC, File specification file-spec-string

> %UCX-I-CFS_FILESYSTEM, File system file-system-string

> %UCX-I-CFS_FILEID, File device-file-ID-spec

> %UCX-I-CFS_INODE, Inode number hex-number

> %UCX-I-CFS_LOCKSTS, Lock mode lock-mode, number/number granted status hex-number

> %UCX-I-CFS_OFFSET, File offset <hex-number>, length hex-number

> %UCX-I-CFS_PATHNAME, Path name path-name-string

> %UCX-I-CFS_THREAD, Service service-name-string, sequence number

> %UCX-I-CFS_RDCB, Resource descriptor address hex-number, type <0-4>

> %UCX-I-CFS_RESOURCE, Resource is resource-type-string

> %UCX-I-CFS_UNBIND, File system path-name-string is unbound

> %UCX-I-CFS_IVRESSTS, Invalid resource state

> %UCX-E-CFS_BAD_ID, CF packid mismatch

Explanation: NFS pack identification does not match the OpenVMS disk volume
User Action: Run ANALYZE CONTAINER to correct the identification.

> %UCX-E-UFS_BHDRETCNT, Failed to perform CACHE while processing container file. Container FID=(xx,xx,xx); return count was incorrect (should be 1).

Explanation: An internal container file system error occurred in performing the CACHE operation while processing the container file (FID=(xx,xx,xx).
User Action: Run ANALYZE/CONTAINER on the specified container file.

> %UCX-E-UFS_BITCLEAR, Bitmap bit to be cleared already cleared: base bbb, position ppp, bitno nnn

Explanation: An internal container file system error has occurred in performing a bitmap clear bit operation: inconsistent bitmap information encountered.
User Action: Contact your DIGITAL support representative and provide information describing the conditions under which this message was generated.

> %UCX-E-UFS_BITOPFAIL, To perform BITOP; operation: operation, status STATUS

Explanation: An internal container file system error has occurred in performing the bitmap operation operation.
User Action: Contact your DIGITAL support representative and provide a description of the conditions under which this message was generated.

> %UCX-E-UFS_BITSET, Bitmap bit to be set already set: base bbb, position ppp, bitno nnn

Explanation: An internal container file system error has occurred in performing a bitmap set bit operation: inconsistent bitmap information encountered.
User Action: Contact your DIGITAL support representative and describe the conditions under which this message was generated.

> %UCX-E-UFS_BMEXTFAIL, Failed to extend container file, status STATUS

Explanation: The NFS file system is full and its size has reached the maximum size limit, or an internal container file system error has occurred that prevents the NFS file system from being extended.
User Action: Examine the error message and take appropriate action. If this message is preceded by a %UCX-E-UFS_NOROOM message, see the user action for that message. Otherwise, contact your DIGITAL support representative and describe the conditions under which this message was generated.

> %UCX-E-UFS_BMOUTCF, Bitmap operation extends beyond existing cells (xxx > yyy )

Explanation: An internal container file system error in performing a bitmap operation. The byte range requested exceed the file system boundary.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_CACHEFAIL, Failed to perform CACHE operation operation, status Status

Explanation: An internal container file system error in performing disk I/O.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_CGIOERROR, Failed to complete CG_IO: cg_id

Explanation: An internal container file system error in performing cell group I/O to disk.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_CGTOOBIG, Failed to create cell group; required length required_length exceeds maximum maximum_length

Explanation: Unable to create a cell group; the required cell group length cannot be satisfied.
User Action: Examine the error message and take appropriate action. If this message is caused by something other than a full NFS file system, contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_CGTYPERR, Cell nnn type is not TYPE1, but TYPE2

Explanation: An internal container file system error. Cell number nnn is type TYPE2, not the expected type TYPE1.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_DEALLCFAIL, Failed to deallocate cell cells; status STATUS

Explanation: An internal container file system error in deallocating # cells number of cells has occurred.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_DIREXTFAIL, Failed to extend directory cell group

Explanation: Unable to extend a directory cell group.
User Action: Examine the error message and take appropriate action. If this message is caused by something other than a full NFS file system, submit an SPR with all the information describing the conditions under which this message was generated.

> %UCX-E-UFS_DOBITFAIL, Failed to set/clear bit in bitmap; status STATUS

Explanation: An internal container file system error has occurred in performing bit set/clear operation.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_ENTRYOPERR, Failed to complete ENTRYOP

Explanation: An internal container file system error has occurred in performing directory entry operations.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_EXTBMPFAIL, Failed to create bitmap cell group

Explanation: An internal container file system error has occurred in allocating bitmap cell groups.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_FRDCBFAIL, Failed to create RDCB; object object, status STATUS

Explanation: An internal container file system error has occurred in creating resource descriptor control block for the object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_INVOPER, Invalid operation requested: operation

Explanation: An internal container file system error has occurred. Invalid directory entry operation was requested to module module.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_INVRDCB, Invalid RDCB: object

Explanation: An internal container file system error. The resource descriptor control block indicates the object has changed is invalid.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_INVSIZE, Invalid size specified: object_size

Explanation: An internal container file system error. Invalid size has been specified for object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_INVTYPE, Invalid type specified: object_type

Explanation: An internal container file system error. Invalid type has been specified for object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_LOCKFAIL, Failed to set lock on object RDCB

Explanation: An internal container file system error has occurred in creating a lock on the resource descriptor control block for object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-W-UFS_NOROOM , NFS file system is full

Explanation: We need to provide an explanation here.
User Action: Remove unused files from the NFS file system to free up space or start using a new file system.

> %UCX-E-UFS_NOTFOUND, Failed to find object

Explanation: An internal container file system error occurred. The object object was not found.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_RELDRDCBF, Failed to release object RDCB, status STATUS

Explanation: An internal container file system error has occurred in deallocating a resource descriptor control block for object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

> %UCX-E-UFS_RELOCKFAIL, Failed to release lock on object RDCB, status STATUS

Explanation: An internal container file system error has occurred in releasing a lock on the resource descriptor control block for object object.
User Action: Contact your DIGITAL support representative describing the conditions under which this message was generated.

# B.4 PPP OPCOM messages

> %UCX-S-PPPCONNECT, Connected,

Explanation: User successfully initiated a PPP connection.
User Action: None.

> %UCX-W-PPPSETMODERR,

Explanation: An error occurred during a PPP connect negotiation.

> %UCX-W-PPPCRELNMERR,

Explanation: Error creating The logical name UCX_HOSTADDRR.

> %UCX-I-SETPROXYARP,

Explanation: Indicates that proxy ARP is set for the PPP destination.
User Action: None.

> %UCX-I-SETDEFRT,

Explanation: Indicates the default route is set to the PPP interface.
User Action: None.

> %UCX-S-PPPDISCONN, Disconnected,

Explanation: User entered a PPPD DISCONNECT command. PPP line successfully disconnected.
User Action: None.

# B.5 POP Server Messages

This section lists POP server error and OPCOM messages.

## B.5.1 POP Error Messages

The following POP server error messages are sent to the client as a result of failed or misinterpreted commands.

Note that when failures occur, there is often additional information written to the POP server log file (UCX$POP_RECV_STARTUP.LOG).

> -ERR Message `n' does not exist,

> -ERR Message `n' has been deleted,

Explanation: The message number is either out of range or was deleted previously, where n is the message number specified in the command. This message is displayed in response to any command that takes a message number as a parameter, such as LIST or RETR.
Possible Cause: The POP client and server protocol are not synchronized.
User Action: Report the problem to the system manager.

> -ERR Message `n' has already been deleted,

Explanation: The message was deleted previously, where n is the message number specified in the DELETE command.
Possible Cause: The POP client and server protocol are not synchronized.
User Action: Report the problem to the system manager.

> -ERR Too few arguments for the `cmd' command,

Explanation: There are too few arguments to the command, where cmd is any command sent to the POP server.
Possible Cause: The POP client is not compliant with RFC 1725.
User Action: Report the problem to the system manager.

> -ERR Too many arguments for the `cmd' command,

Explanation: There are too many arguments to the command, where cmd is any command sent to the POP server.
Possible Cause: The POP client is not compliant with RFC 1725.
User Action: Report the problem to the system manager.

> -ERR Unknown command: `cmd',

Explanation: The command sent by the POP client is not known to the POP server, where cmd is any command sent to the POP server.
Possible Cause: The POP client is not compliant with RFC 1725.
User Action: Report the problem to the system manager.

> -ERR The USER command has been administratively disabled,

> -ERR The PASS command has been administratively disabled,

Explanation: The USER or PASS command was sent by the POP client but the DISUSERPASS POP server configuration option is set.
Possible Cause: The POP client is configured to use the USER and PASS commands for authentication rather than the APOP command.
User Action: Change your POP client to use the APOP command or ask the system manager to enable the use of the USER and PASS commands.

> -ERR password supplied for `username' is incorrect,

Explanation: The password sent by the POP client does not match the password for the account in the SYSUAF file on the POP server system, where username is the password specified in response to the PASS command.
Possible Cause: The POP client is misconfigured (for example, the password is spelled incorrectly) or the password was changed on the POP server system but not on the POP client system.
User Action: Check your POP client to make sure you entered the correct password. If you believe your password to be correct, report the problem to the system manager.

> -ERR No such user "`username'",

Explanation: There is no account in the SYSUAF file for the user name specified, where username is the user name specified in response to the USER or APOP command.
Possible Cause: The POP client is misconfigured (for example, the user name is spelled incorrectly) or the account was deleted from the SYSUAF file.
User Action: Check your POP client to make sure you entered the correct user name. If the user name is correct, report the problem to the system manager.

> -ERR account `username' has expired,

Explanation: There is an account in the SYSUAF file for the user, where username is the user name specified in the USER or APOP command, but the account has expired. An account cannot be used after its expiration date has passed.
Possible Cause: The account is expired.
User Action: Report the problem to the system manager.

> -ERR account "`username'" is administratively disabled,

Explanation: There is an account in the SYSUAF file for the user, where username is the user name specified in the USER or APOP command, but the DISUSER or DISMAIL flag is set.
Possible Cause: The DISUSER or DISMAIL flag is set for the account.
User Action: Report the problem to the system manager.

> -ERR MD5 digest supplied for "`username'" is wrong length,

Explanation: The MD5 digest, where username is the user name specified with the APOP command, is 32 ASCII characters in length.
Possible Cause: The POP client is not compliant with RFC 1725.
User Action: Report the problem to the system manager.

> -ERR Can't open MD5 shared secret file `f'. errno = `e', vaxc$errno =`v',

Explanation: An error occurred when the POP server attempted to open the shared secret file in response to the APOP command, where:

- f is the name of the file in which the POP server was looking for the shared secret to compute the MD5 digest for validation purposes.
- e is the integer value of the VAXC$ERRNO symbol after the FOPEN operation.
- v is the OpenVMS error text indicated by the VAXC$ERRNO symbol after the FOPEN operation.

Possible Causes: You forgot to create the file, you specified an incorrect file name, or you put the file in the wrong directory.
User Action: Create the shared secret file and try again.

> -ERR Read error on shared secret file `f'. errno = `e', vaxc$errno =`v',

Explanation: An error occurred when the POP server attempted to read the shared secret file in response to the APOP command, where:

- f is the name of the file in which the POP server was looking for the shared secret to compute the MD5 digest for validation purposes.
- e is the integer value of the VAXC$ERRNO symbol after the READ operation.
- v is the OpenVMS error text indicated by the VAXC$ERRNO symbol after the READ operation.

Possible Cause: To determine the cause, check the text of the VAXC$ERRNO symbol parameter.
User Action: Correct the shared secret file and try again.

> -ERR Empty shared secret file `f',

Explanation: The POP server located an empty file in response to the APOP command, where f is the name of the file in which POP server was looking for the shared secret to compute the MD5 digest for validation purposes.
Possible Cause: The user created an empty shared secret file.
User Action: Create the shared secret file and try again. For information about how to create the shared secret file, see Chapter 13.

> -ERR MD5 digest mismatch. Check shared secret on client and server systems,

Explanation: The MD5 digest computed by the POP server did not match the MD5 digest sent in the APOP command.
Possible Cause: The shared secrets of the client and server do not match.
User Action: Check the shared secret on both the client and server to make sure they match. If not, correct the error and try again. Note that the MD5 algorithm is case sensitive and the shared secrets on each side must match exactly. Also note that on the POP client, you might need to take additional action for your correction to take effect. If the shared secrets appear to be correct, report the problem to the system manager.

> -ERR Access to user account `username' denied,

Explanation: The POP server security configuration option is set to SECURE and an authorization error occurred in response to the USER or APOP command. When the security option is set to SECURE, this message is displayed for all authorization errors.
Possible Cause: There can be many reasons for the error. For information about POP security, see Chapter 13.
User Action: Report the problem to the system manager.

> -ERR Not validated for the XTND `sub-cmd' command,

Explanation: The user of the session does not have a BYPASS, OPER, or SYSPRV privilege set, where sub-cmd is the XTND subcommand.
Possible Cause: The account does not have the required privilege.
User Action: Report the problem to the system manager.

> -ERR Can't build message list for `username': Out of memory,

Explanation: The POP server ran out of dynamic memory while building an internal list of information about each of the user's messages, where username is the user name specified in response to the PASS or APOP command.
Possible Cause: A memory leak occurred with the POP server.
User Action: Stop the POP server process and retry. Report further problems to the system manager.

> -ERR Error getting info from SYSUAF. sys$getuai: `v',

Explanation: The SYS$GETUAI system service returned an error when called with the user name specified in the APOP or USER command, where v is the error text associated with the SYS$GETUAI completion status.
Possible Cause: Check the error text for the possible cause.
User Action: Report the problem to the system manager.

> -ERR Error determining password validity. sys$hash_password: `v',

Explanation: SYS$HASH_PASSWORD returned an error when called with the password from the PASS command, where v is the error text associated with the SYS$HASH_PASSWORD completion status. Note that this error is not the result of an invalid password.
Possible Cause: Check the error text for the possible cause.
User Action: Report the problem to the system manager.

> -ERR Opening mail user context: `v',

> -ERR Getting mail user info: `v',

> -ERR Opening mail file context: `v',

> -ERR Opening mail message context: `v',

> -ERR Selecting mail folder: `v',

Explanation: These error messages are displayed as a result of errors in callable OpenVMS mail routines in response to the PASS or APOP command, where v is the error text associated with an callable OpenVMS mail call completion status.
Possible Cause: Check the error text for the possible cause.
User Action: Report the problem to the system manager.

## B.5.2 POP OPCOM Messages

The POP server displays the following OPCOM messages on the operator console. These messages pertain to authorization errors, which occur when POP authorization commands encounter errors.

When you receive an OPCOM message, refer to the POP server log file UCX$POP_RECV_STARTUP.LOG for troubleshooting information.

- POP server authentication error: password supplied for "jones" is incorrect.
  Occurs when a POP client sends a PASS command containing an invalid password.
- POP server authentication error: Error determining password validity for "smith".
  Occurs when the POP server encounters an error (often a failure status from a system service call) when trying to validate the user's password.
- POP server authentication error: User account "example" is invalid.
  Occurs when the account (specified in a USER or an APOP command) is nonexistent or one or more of the SYSUAF flags checked by the POP server are set. See Chapter 13 for the SYSUAF flags that, when set, instruct POP to not allow access to the mail file.
- POP server authentication error: Max # of authentication attempts exceeded.
  Occurs when two authentication errors occur in the context of one POP server thread.
- POP server authentication error: MD5 digest supplied for "neely" is incorrect.
  Occurs when the MD5 digest sent in an APOP command does not match the one calculated, or another error occurs in computing the MD5 digest.
- POP server authentication error: The USER command has been administratively disabled.
  Occurs when a POP client has issued a USER command and the USER and PASS commands have been disabled in the POP configuration.
- POP server authentication error: The PASS command has been administratively disabled.
  Occurs when a POP client has issued a PASS command and the USER and PASS commands have been disabled in the UCX POP configuration.

# B.6 SMTP Error Messages

This section lists the following SMTP error messages:

- Messages displayed on the sender's screen
- Messages sent by the SMTP symbiont, displayed on the operator's console
- Messages sent by the ANALYZE utility, displayed on the operator's console

## B.6.1 Messages Displayed on the Sender's Screen

> %UCX-E-SMTP_ABORT, SMTP session aborted.

Explanation: The OpenVMS mail session has been interrupted. The control file has been deleted, and the message will not be submitted to the queue.
User Action: Re-send the message.

> %UCX-E-SMTP_BADADDR, Recipient address is illegal. Unparsed string: string_text

Explanation: The recipient address does not conform with any of the accepted patterns (SMTP, MAIL11, distribution list). The unparsed string shows where the parsing failed.
User Action: Consult the DIGITAL TCP/IP Services for OpenVMS User's Guide for correct addressing.

> %UCX-I-SMTP_BADLIST, Distribution list illegal.

Explanation: Distribution list contains one or more illegal addresses.
User Action: Edit the distribution list to correct the address(es).

> %UCX-E-SMTP_CFERROR, Control File Error in file

Explanation: Error occurred while processing the file where the mail is saved for queuing.
User Action: The temporary mail file is created in the user's mail profile directory. Check that this directory exists. Otherwise, contact your DIGITAL support representative and describe the conditions leading to the error.

> %UCX-E-SMTP_INTERNAL, Internal error

Explanation: An internal error occurred in OpenVMS mail/SMTP sender.
User Action: Contact your DIGITAL support representative and describe the conditions leading to the error.

> %UCX-E-SMTP_NOFORG, SMTP does not support foreign file.

Explanation: SMTP does not support foreign file formats.
User Action: This is a restriction.

> %UCX-E-SMTP_PARSERR, Internal error in parsing routine.

Explanation: An internal error occurred in the address parsing routine.
User Action: Contact your DIGITAL support representative and describe the conditions leading to the error.

> %UCX-E-SMTP_STRLONG, Address too long. Maximum allowed is 255.

Explanation: The given path is longer than the maximum path allowed by the SMTP protocol (255 characters).
User Action: If the sender name was too long (for example, the mail has been forwarded so many times that the "From:" path is too long), this is a restriction. If the recipient line is too long, use a distribution list instead.

> %UCX-I-SMTP_USERSPEC, Invalid user specification user_specification

Explanation: Address in distribution list is invalid.
User Action: Edit the distribution list to correct the address in question.

> %UCX-E-SMTP_VMSMAIL, Internal error occurred in VMSmail-SMTP interface.

Explanation: An internal error has occurred between the OpenVMS mail and SMTP protocols.
User Action: Contact your DIGITAL support representative and describe the conditions leading to the error.

## B.6.2 SMTP Symbiont Error Messages

> %UCX-E-SMTP_CFGETERROR, Error getting CF header,
> type of file_type

Explanation: Remote sender failed to access headers in temporary mail file.
User Action: This indicates a possible corruption of the temporary mail file. Issue UCX ANALYZE MAIL.

> %UCX-E-SMTP_CFSETERROR, Error getting CF address

Explanation: Remote sender failed to access address in temporary mail file.
User Action: This indicates a possible corruption of the temporary mail file. Run $ UCX ANALYZE MAIL

> %UCX-I-SMTP_LOGFAIL, Error creating log file file

Explanation: Informational.
User Action: None.

> %UCX-I-SMTP_LOGSUC, Using log file file

Explanation: Informational.
User Action: None.

> %UCX-E-SMTP_SNDERROR, Error detected while sending mail to local_mail_address

Explanation: Symbiont failed to deliver local mail.
User Action: Check for errors in the logfile SYS$SPECIFIC:[UCX_SMTP]UCX$SMTP_LOGFILE.LOG.

> %UCX-I-SMTP_SYMBERR, Symbiont error in symbiont

Explanation: The symbiont is exiting after error has occurred.
User Action: Check other error messages in the logfile SYS$SPECIFIC:[UCX_SMTP]UCX$SMTP_LOGFILE.LOG.

> %UCX-I-SMTP_SYMBRUN, Symbiont is running the queue symbiont_queue

Explanation: Informational.
User Action: None.

> %UCX-I-SMTP_SYMBSTOP, Symbiont is stopped

Explanation: Informational.
User Action: None.

## B.6.3 SMTP ANALYZE Utility Error Messages

> %UCX-F-ANA_INTERR, internal ANALYZE error

Explanation: ANALYZE MAIL has failed an internal consistency check, indicating a possible dysfunction.
User Action: Report this problem to your DIGITAL support representative.

> %UCX-F-ANA_INITER, ANALYZE initialization error

Explanation: ANALYZE MAIL has failed to complete its initialization routines.
User Action: Report this problem to your DIGITAL support representative.

> %UCX-F-ANA_RESERR, ANALYZE resource allocation error (memory)

Explanation: ANALYZE MAIL has failed to allocate dynamic memory.
User Action: Check system and process parameters to possibly increase available process virtual memory, including VIRTUALPAGCNT and the process page file quota.

> %UCX-F-ANA_ABORT, ANALYZE aborted

Explanation: ANALYZE MAIL has encountered a fatal error, including one of the error conditions described above.
User Action: See error conditions above for specific action.

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

Explanation: This message is issued whenever ANALYZE MAIL starts.
User Action: None.

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

Explanation: This message is issued whenever ANALYZE MAIL finishes.
User Action: None.

> %UCX-I-ANA_NOFILE, no file found for entry entry_number in the queue SMTP_queue

Explanation: An entry in the SMTP queue has been found for which the mail file specified does not exist.
User Action: None. ANALYZE MAIL will automatically delete this entry.

> %UCX-I-ANA_NOENTR, no queue entry found for file file

Explanation: An SMTP mail file has been found for which there is no SMTP queue entry.
User Action: Use the ANALYZE MAIL/REPAIR to requeue the mail file, or use the ANALYZE MAIL/DELETE to delete the mail file.

> %UCX-I-ANA_ADENTR, file file submitted to queue queue as entry entry_number

Explanation: During the ANALYZE MAIL/REPAIR command, the specified file has been requeued to the SMTP queue.
User Action: None.

> %UCX-I-ANA_DELFIL, file file is deleted from the postmaster directory

Explanation: During the ANALYZE MAIL/DELETE command, the specified file has been deleted from the postmaster directory.
User Action: None.

> %UCX-I-ANA_DELENT, entry entry_number deleted from the queue queue

Explanation: The ANALYZE MAIL command has deleted the specified entry from the SMTP queue.
User Action: None.

> %UCX-I-ANA_HOLDFL, file file is kept in the Postmaster directory

Explanation: The ANALYZE MAIL command has left the specified mail file in the Postmaster directory and has not requeued or deleted them.
User Action: None.

> %UCX-I-ANA_FEPAIR, found # entries file-queue entry pairs

Explanation: This message prints the number of mail files found for which there were matching entries in the SMTP queue.
User Action: None.

> %UCX-I-ANA_DELQEN, deleted # entries queue entries

Explanation: This message prints the number of SMTP queue entries for which the mail file does not exist, and which entries were therefore deleted from the queue.
User Action: None.

> %UCX-I-ANA_FILNOQ, found # files files with no queue entries

Explanation: This message prints the number of mail files found for which there were no matching SMTP queue entries.
User Action: None.

> %UCX-I-ANA_FILHLD, holding # files files in directory

Explanation: This message prints the number of mail files found for which there were no matching SMTP queue entries, and were left in the Postmaster directory and did not requeue or delete them.
User Action: None.

> %UCX-I-ANA_FILDEL, deleted # files files from the Postmaster directory

Explanation: This message prints the number of mail files that were deleted from the Postmaster directory.
User Action: None.

> %UCX-I-ANA_SUBFIL, submitted # files files to the generic queue queue

Explanation: This message prints the number of mail files that were requeued to the SMTP queue.
User Action: None.

> %UCX-I-ANA_FILACE, encountered # files file access errors

Explanation: This message prints the number of access errors that were encountered while attempting to access SMTP mail files.
User Action: Check the log file for messages that indicate which files caused the access errors.

> %UCX-I-ANA_NONCFF, found # files non-unknown files in Postmaster directory

Explanation: This message has not yet been implemented.
User Action: None.

> %UCX-I-ANA_FILCOR, found # files corrupted CF files in Postmaster directory

Explanation: This message prints the number of SMTP mail files for which there were errors detected in the internal format of the mail file.
User Action: Check the log file for indications as to which file(s) are corrupted, and save these files for possible submission to DIGITAL. Corrupted mail files may be an indication of either a hardware problem or a software dysfunction.

> %UCX-W-ANA_PSDIRL, Postmaster directory directory is locked

Explanation: This message indicates that ANALYZE MAIL has locked the user Postmaster directory for analysis.
User Action: None.

> %UCX-W-ANA_QUEUEL, queue queue is locked

Explanation: This message indicates that ANALYZE MAIL has locked the specified SMTP queue for analysis.
User Action: None.

> %UCX-W-ANA_PSDIRN, Postmaster directory directory is unlocked

Explanation: This message indicates that ANALYZE MAIL has released the previous lock on the Postmaster directory.
User Action: None.

> %UCX-W-ANA_QUEUEU, queue queue unlocked

Explanation: This message indicates that ANALYZE MAIL has released the previous lock on the specified SMTP queue.
User Action: None.

> %UCX-W-ANA_FILEAC, file file access error access_error #

Explanation: This message indicates that an RMS error has occurred while attempting to access the specified mail file.
User Action: Check the RMS error and act appropriately. This may be the result of an access conflict with another process, such as the SMTP Queue Symbiont.

> %UCX-W-ANA_PSDIRC, Postmaster directory access error access_error #

Explanation: This message indicates that an error has occurred while attempting to lock the Postmaster directory.
User Action: Check for proper user privileges and retry the command.

> %UCX-W-ANA_QUEACC, queue queue access failure

Explanation: This message indicates that an error has occurred while attempting to lock the specified SMTP queue.
User Action: Check for proper privileges and retry the command.

> %UCX-W-ANA_NOGENQ, no queue queue is defined

Explanation: The specified SMTP queue does not exist.
User Action: Check the consistency of the SMTP queues, and ensure that there is no logical name conflict with the queue name(s).

> %UCX-W-ANA_NOUSER, No such user user

Explanation: The user name specified for analysis does not exist.
User Action: Check the user name and retry the command.

> %UCX-W-ANA_ILLTIME, Illegal or conflicting BEFORE and SINCE times

Explanation: ANALYZE MAIL has detected a conflict between the BEFORE and SINCE keywords used with the /DELETE and/or /REPAIR qualifiers.
User Action: /REPAIR and /DELETE keywords can be used to specify time frames that are used to compare to the creation date(s) of the file(s) to be deleted or requeued. These time frames must not overlap, and the SINCE date and time must precede those of the BEFORE date and time. Check the time frames for consistency and retry the command.

> %UCX-W-ANA_ILLDATE, Illegal date in CF file name

Explanation: SMTP mail files names are created using the date and time of the creation of the file. The file names have the format: YYMMDDHHmmsscc_username.UCX_nodename, where: YYMMDDHHmmsscc is the timestamp taken when the file was created, username is the name of the file's creator, and nodename is the name of the local host.

Previous | Next | Contents