DIGITAL TCP/IP Services for OpenVMS
Management
Previous
| Contents
This error message is issued when a mail file name has been detected
for which an illegal month, day, hour, minute, or second has been
detected.
User Action: Check the mail file in question for
possible deletion manually.
B.6.4 UCP Error Messages
%UCX-$-E-UCP-BADVALUE, Value value is incorrect
Explanation: The syntax of the named value is not
correct.
User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more
information about this command, and reissue the command with a valid
value.
%UCX-%$-E-UCP-BINDNOTINIT, Error initializing BIND resolver
Explanation: A SET NAME_SERVICE command has been
issued, but data structures needed for host name lookup have not been
created.
User Action: Stop and restart the internet.
%UCX-%$-E-UCP-CONFIGERROR, Error processing CONFIGURATION request
Explanation: An error was detected while processing a
SET CONFIGURATION command.
User Action: The secondary error message describes the
problem.
%UCX-%$-E-UCP-DUPQUEUE, Conflicting or duplicate queue information for
node node
Explanation: This node already has a complete SMTP
configuration and is now being configured into a SMTP cluster queue.
User Action: None.
%UCX-%$-I-UCP-GEN_ALIAS, Record is a generated alias
Explanation: An alias name is returned that does not
actually exist in an alias list. This name would be a variation on
character case, and/or domain specification.
User Action: None.
%UCX-%$-E-UCP-INVHOSTENT, Hostent structure is invalid
Explanation: An invalid hostent structure was returned
from the BIND resolver.
User Action: Select a different BIND server with the
SET NAME_SERVICE/SERVICE command.
%UCX-%$-E-UCP-LISTEXISTS, list list already exists
Explanation: A reject list is being specified when an
accept list for that class already exists - or the other way around.
User Action: Issue a SHOW command in order to see
which security lists already exist.
%UCX-%$-I-UCP-LOADSERV, Loading UCX Server proxy information
Explanation: An internet startup is in progress, and
all records in the proxy database that apply to communication will be
loaded into the internet proxy cache.
User Action: None.
%UCX-%$-E-UCP-MISNAME, NAME SERVICE database mismatch
Explanation: A new version of UCX was installed
without a proper shut down of a previous version.
User Action: Shutdown UCX and then restart.
%UCX-%$-E-UCP-MXERROR, Error processing MX request
Explanation: An error was detected in the processing
of a command involving access to an MX database.
User Action: The secondary error explains the problem.
%UCX-%$-E-UCP-NAMESTARTED, NAME SERVICE already started
Explanation: A START NAME_SERVICE command has been
issued, and the NAME_SERVICE data structures have already been
initialized.
User Action: None.
%UCX-%$-E-UCP-NAMESTOPPED, NAME SERVICE already stopped
Explanation: A STOP NAME_SERVICE command has been
issued, and the NAME_SERVICE data structures were not initialized.
User Action: None
%UCX-%$-E-UCP-NOAPPLIC, The UCX-IP-APP license is not enabled
Explanation: The command requires that the product PAK
be enabled.
User Action: Enable the product PAK.
%UCX-%$-E-UCP-NOCFS, Error resolving UCX$CFS_SHR entry point
Explanation: The command requires access to the
container file system, and UCX$CFS_SHR.EXE has not been installed.
User Action: Perform a UCX$NFS_STARTUP.
%UCX-%$-E-UCP-NODELQUEUE, Queues on node node cannot be
deleted - serves other nodes
Explanation: An attempt was made to delete an SMTP
configuration for a node that is serving other OpenVMS nodes.
User Action: Issue SHOW SMTP to see the SMTP cluster
members for this node.
%UCX-%$-E-UCP-NODESERVED, Node is configured via node node
Explanation: This node is already included in the
configuration of the specified node.
User Action: Remove this node's configuration
information from the specified node's configuration.
%UCX-%$-E-UCP-NOINETADDR, Could not resolve address for host
host
Explanation: Host lookup has failed for the specified
host name.
User Action: None.
%UCX-%$-E-UCP-NOMOD, Value for record cannot be modified
Explanation: The specified value may not be changed
User Action: Delete the record containing this value,
and re-enter the information using the new value.
%UCX-%$-E-UCP-NONFSLIC, The UCX-IP-NFS license is not enabled
Explanation: The command requires that the product PAK
be enabled
User Action: Enable the product PAK.
%UCX-%$-E-UCP-NOQUEUE, No queue information for node node
Explanation: The SMTP configuration for the specified
node is complete because no sender queues have been assigned.
User Action: See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference manual for more
information about the SET CONFIGURATION SMTP command.
%UCX-%$-E-UCP-NORUNLIC, The UCX-IP-RT license is not enabled
Explanation: The command requires that the product PAK
be enabled.
User Action: Enable the product PAK.
%UCX-%$-E-UCP-NOSERVINIT, Error initializing UCX Server
Explanation: A problem was encountered in starting the
auxiliary server The secondary error describes the problem.
User Action: None.
%UCX-%$-E-UCP-NOSMTPSHR, Error resolving SMTP_MAILSHR entry point
Explanation: An SMTP command was issued that requires
that UCX$SMTP_MAILSHR.EXE be installed.
User Action: Stop and restart SMTP.
%UCX-%$-E-UCP-NOSUPPORT, This command is not supported for
version
Explanation: There is a version mismatch in the
product, probably due to a reinstallation.
User Action: Ensure that UCX is totally shut down, and
then restart.
%UCX-%$-E-UCP-NOTSERVED , Not served by this node
Explanation: The configuration cannot be modified
because it is not owned by this node.
User Action: Issue the SHOW CONFIGURATION command to
see which node owns the configuration.
%UCX-%$-E-UCP-NOWILD , Value cannot be wildcarded
Explanation: A wildcard character is not a valid value
for the parameter or qualifier you specified.
User Action: Reissue the command with an explicit
value.
%UCX-%$-E-UCP-QUALREQ , Qualifier value for qualifier is
required
Explanation: For the command you want to issue, the
specified qualifier and a value for it are required.
User Action: Reissue the command with both the
qualifier and a value.
%UCX-%$-E-UCP-QUEUE, Error processing queue queue
Explanation: An error was detected in trying to
perform a queue operation.
User Action: The secondary error explains the problem.
%UCX-%$-E-UCP-SERVERROR, Error processing SERVICE request
Explanation: An error was detected in performing
access to the UCX$SERVICE database.
User Action: The secondary error explains the problem.
%UCX-%$-I-UCP-SERVLOADED, UCX Server loaded with record proxy
records
Explanation: The auxiliary server's proxy cache has
been loaded with the specified number of entries.
User Action: Issue a SHOW PROXY /COMMUNICATION command
if you want to see which entries were loaded.
%UCX-%$-E-UCP-SMTPERROR, Error processing SMTP request
Explanation: An error was detected in performing a
SMTP command.
User Action: The secondary error explains the problem.
Appendix C
ANALYZE CONTAINER Validation Messages
The DIGITAL TCP/IP Services for OpenVMS (UCX) management utility
provides the ANALYZE CONTAINER command, described in the DIGITAL TCP/IP Services for OpenVMS Management Command Reference
manual. ANALYZE CONTAINER produces the following types of messages:
- Information messages that describe the current processing of the
analysis
- Error messages that describe problems found in the container file
and the NFS file system
Error messages appear in two parts:
- The first part describes the problem.
- The second part describes the solution that ANALYZE CONTAINER will
use to correct the problem.
If you suspect a malfunction in the software, contact your DIGITAL
support representative and provide the following information:
C.1 Summary Information
The following messages are printed at the end of the ANALYZE CONTAINER
analysis. They provide NFS status.
Analysis Summary Report
=======================
Cell size: n bytes
Container size: n cells (n bytes)
Container usage: n cells used (n%)
Number of errors detected:
Number of corrections made:
Lost+found changed/created:
Number of directories:
Number of regular files:
Number of symbolic files:
Number of imported files:
C.2 General Information Messages
The following messages are for your information.
%UCX$-I-ANA_STARTSUPER, Starting super block validation
%UCX$-I-ANA_ENDSUPER, End of super block validation
Explanation: Beginning and ending messages of
successful super block validation initiated by issuing an ANALYZE
CONTAINER command.
User Action: None.
%UCX$-I-ANA_STARTINODE, Starting inode validation
%UCX$-I-ANA_ENDINODE, End of inode validation
Explanation: Beginning and ending messages of
successful inode validation initiated by issuing an ANALYZE CONTAINER
command.
User Action: None.
%UCX$-I-ANA_STARTDIR, Starting directory validation
%UCX$-I-ANA_ENDDIR, End of directory validation
Explanation: Beginning and ending messages of
successful directory validation initiated by issuing an ANALYZE
CONTAINER command.
User Action: None.
%UCX$-I-ANA_STARTBITMAP, Starting bitmap validation
%UCX$-I-ANA_ENDBITMAP, End of bitmap validation
Explanation: Beginning and ending messages of
successful bitmap validation initiated by issuing an ANALYZE CONTAINER
command.
User Action: None.
%UCX$-I-ANA_STARTFIX, Validating the directory hierarchy
%UCX$-I-ANA_ENDFIX, End validating the directory hierarchy
Explanation: Beginning and ending messages of
successful correction of any directory hierarchy problems initiated by
issuing an ANALYZE CONTAINER command. Disconnected files and
directories are placed in the lost and found directory.
User Action: None.
%UCX$-I-ANA_QUIT, Unable to continue analysis
Explanation: An ANALYZE CONTAINER command is unable to
complete the analysis due to fatal errors found in the container file.
User Action: See other error messages generated by the
ANALYZE CONTAINER to determine the appropriate action.
%UCX$-I-ANA_ENDSUCCESS, End of analysis
Explanation: An ANALYZE CONTAINER command has
successfully completed the analysis.
User Action: None.
C.3 Super Block Validation Messages
The following error messages are related to errors detected in the
super block. Generally, these problems are corrected automatically, if
the /REPAIR option is set, without user confirmation or action. All
other errors indicate data corruption caused by a hardware or software
problem or because the system was shut down abruptly while the NFS file
system was active. If you believe the problem was due to software,
contact your DIGITAL support representative.
%UCX$-E-ANA_SUP_BADBCGSIZE, Problem: Bad bitmap cell group
size: bad_value Solution: is replaced by default value
good_value
Explanation: Super block contains an invalid value for
the initial bitmap cell group allocation size.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADBITMAP, Problem: Invalid Bitmap inode
number: bad_inode_number Solution: Will rebuild bitmap file
Explanation: The super block container has an invalid
bitmap file inode number.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADCELLSIZE, Problem: Bad container file cell
size: bad_value Solution: Will be replaced by default size
good_value
Explanation: The super block contains an invalid value
for the NFS file system cell size.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADCHKSUM, Problem: Super Block has mismatched
cell group checkbytes chksum1<>chksum2
Solution: Will set checkbytes to same value
Explanation: The front checkbyte byte of the super
block cell group does not match its rear checkbyte byte. The super
block may contain corrupted data.
User Action: None. The error is repaired automatically
if /REPAIR option is set.
%UCX$-E-ANA_SUP_BADCGRTYPE, Problem: Wrong super block cell
group type: bad_value Solution: Will set cell group type to
super block type
Explanation: The type field of the super block cell
group does not identify itself as super block.
User Action: None. The error is repaired automatically
if /REPAIR option is set.
%UCX$-E-ANA_SUP_BADCFEXTEND, Problem: Bad container file
extension size: bad_value Solution: Will be replaced by
default value good_value
Explanation: The super block contains an invalid value
for the initial container file extension size.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADCGSIZE, Problem: bad super block cell group
size: bad_value Solution: Will be replaced by correct super
block size good_value
Explanation: The size field of the super block cell
group does not correctly describe the size of the cell group.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADDCGSIZE, Problem: Bad initial directory cell
group size: bad_value Solution: Will be replaced by default
value good_value
Explanation: Super block contains an invalid value for
the initial directory cell group allocation size.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADECGSIZE, Problem: Bad initial extension cell
group size: bad_value Solution: Will be replaced by default
size good_value
Explanation: Super block contains invalid value for
the initial extension cell group allocation size.
User Action: None. Error is repaired automatically if
/REPAIR option is set.
%UCX$-E-ANA_SUP_BADFID, Problem: Bad container file FID:
bad_FID Solution: Will be replaced by correct FID:
good_FID
Explanation: The OpenVMS file identification (FID) of
the container file in the super block does not match the real container
file FID.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
%UCX$-E-ANA_SUP_BADHIBK, Problem: Bad maximum container file
size: bad_value Solution: Will be replaced by default value
good_value
Explanation: The value in the super block for the
maximum size to which the container file can be expanded is invalid.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADIICGSIZE, Problem: Bad initial inode cell
group size: bad_value Solution: Will be replaced by default
size good_value
Explanation: The super block contains an invalid value
for the initial inode cell group allocation size.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_SUP_BADSUPBLK, Problem: Super Block irremediably
corrupted. ** End ANALYZE **
Explanation: The super block is totally
unrecognizable. The ANALYZE CONTAINER command cannot continue the
analysis.
User Action: Create a new container file using the
CREATE CONTAINER command, delete (or save) the corrupted container
file, and run the ANALYZE CONTAINER command again.
The ANALYZE CONTAINER command analyzes the container file and moves the
entire directory hierarchy to the lost and found directory. This means
the root directory is under the lost and found directory, but all files
and directories under root are intact.
%UCX$-E-ANA_SUP_BADRTHRESH, Problem: Bad directory relocation
threshold: bad_value Solution: Will be replaced by default
value good_value
Explanation: The super block contains an invalid value
for the directory's relocation threshold that controls the directory's
size.
User Action: None. The error is repaired automatically
if the REPAIR option is set.
%UCX$-E-ANA_SUP_BADVERSION, Problem: Bad container file
version: bad_value Current version is good_value
Solution: Will abort ANALYZE CONTAINER
Explanation: The container file version number in the
super block is not a valid version number or a currently supported
version number.
User Action: None. The ANALYZE CONTAINER command will
abort the analysis.
%UCX$-E-ANA_SUP_BADVOL, Problem: Bad volume name:
bad_string Solution: Will be replaced by: good_string
Explanation: The OpenVMS volume name of the device on
which the container file is located does not match the real volume name.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
The following error messages are related to errors detected in inodes.
Generally the problem is corrected automatically, if the /REPAIR option
is set, without user confirmation or action. Problems might be:
- File or directory has been copied or restored from backup.
- A non-NFS file system file has been copied into the NFS file
system's OpenVMS directory hierarchy, or the file has been renamed to a
name that does not conform to the NFS file system convention.
- Data corruptions caused either by a hardware problem or software
problem, or the system was shut down abruptly while the NFS file system
was active.
If you believe the problem was due to software, contact your DIGITAL
support representative.
%UCX-E-ANA_INO_BADCHKSUM, Problem: file_type inode
inode_number has mismatched cell group checkbytes
chksum1 <> chksum2 Solution: Will set
checkbytes to same value
Explanation: The front checkbytes of the inode cell
group do not match its trailer checkbytes byte. The inode may contain
corrupted data.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADATIME, Problem: file_type inode
inode_number has wrong accessed time: wrong_time
Solution: Will be replaced by correct time: correct_time
Explanation: The file accessed time in the inode is
less than the actual accessed time.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADBUFSFILENAM, Problem: Bad NFS file name:
bad_file
Explanation: The name of the OpenVMS file in the NFS
file system does not have the correct NFS file system name format.
User Action: Correct the name of the OpenVMS file.
%UCX-E-ANA_INO_BADCGSIZE, Problem: Bad file_type
inode inode_number inode cell group size: bad_value
Solution: Will be replaced by initial inode size good_value
Explanation: The size field of the inode cell group
does not correctly describe the size of the cell group.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADCGTYPE, Problem: Bad file_type
inode cell group type: bad_value Solution: Will be replaced by
correct cell group type: good_value
Explanation: The type field of the inode cell group
does not identify itself as an inode.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADCHKSUMDEL, Problem: file_type inode
inode_number has mismatched checkbytes: chksum1
<> chksum2 Solution: Will be deleted
Explanation: The front checkbytes of the inode cell
group do not match its trailer checkbyte byte. The inode is either a
symbolic link or an imported file that may contain corrupted data.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADCTIME, Problem: file_type inode has
wrong change time: wrong_time Solution: Will be replaced by
correct time: correct_time
Explanation: The file's change time attribute in the
inode is different from the actual creation time.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADEXTMPTR, Problem: Extension map pointer of
file_type inode inode_number contains the wrong size:
bad_value Solution: Will be replaced by correct size:
good_value
Explanation: The inode's extension map pointer
contains the wrong cell group size for the extension cell group.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADFID, Problem: file_type inode
contains bad FID: bad_FID Solution: Will be replaced by
correct FID: good_FID
Explanation: The OpenVMS file identification (FID) of
the file in the file's inode does not match the real FID of the file.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
%UCX-E-ANA_INO_BADFILESIZE, Problem: file_type inode
inode_number contains bad file size: bad_value bytes
Solution: Will be replaced by the correct size: good_value
Explanation: The file size field of the inode does not
correctly describe the size of the file.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADFNAM, Problem: file_type inode
inode_number file name string has invalid characters Solution:
The inode will be deleted
Explanation: The symbolic link or imported file inode
contains an invalid file name.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADINODE, Problem: Bad file_type inode
inode_number cannot be recovered Solution: Will be deleted
Explanation: The inode contains too many errors to be
repaired.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADINODEOK, Problem: Bad file_type
inode inode_number; cannot be recovered Solution: Will try to
rebuild it
Explanation: The inode contains too many errors to be
repaired. It (inode number) should be deleted and rebuilt.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX$-E-ANA_INO_BADINUM, Problem: Bad file_type inode
number: bad_inode_number Solution: Replaced by the correct
inode number: good_inode_number
Explanation: Each inode contains its own inode number.
The value in the inode number field of this file is not its inode
number.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADMAXMPTR, Problem: Bad
file_type_inode/extension_inode max. number of mapptrs:
bad_value Solution: Will be replaced by the correct number:
good_value
Explanation: Each inode with its extensions has a
dynamic portion that contains a certain number of internal map
pointers. The field is wrong that describes the limit of map pointers
in the dynamic portion.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADMODE, Problem: file_type inode
contains bad file mode: bad_mode Solution: Will be replaced by
the correct mode: good_mode
Explanation: The inode contains the wrong file mode
(file type and protection bits).
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADMPTR, Problem: Bad map pointer in
file_type inode (cg:cell_group_number) Solution: Will
be cleared
Explanation: The inode contains an invalid map pointer
to the file data.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADMPUSED, Problem: file_type inode
inode_number has bad used map pointers count:
bad_value Solution: Will be replaced by the correct count:
good_value
Explanation: Each inode with its extensions has a
dynamic portion that contains a certain number of internal map
pointers. The field is wrong that describes the number of map pointers
being used.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADMTIME, Problem: file_type inode has
wrong modification time: wrong_time Solution: Will be replaced
by correct time: correct_time
Explanation: The file-modified time in the inode is
less than the actual modified time.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADNAMLEN, Problem: file_type inode
inode_number has bad filename length: bad_value
Solution: The inode will be deleted.
Explanation: The symbolic link or imported file inode
contains invalid file name length.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADOWNINUM, Problem: file_type inode
cg: cell_group_number contains bad owning inode number:
bad_value Solution: Will be replaced by correct owning inode
number: good_value
Explanation: Each inode with its extensions has a
dynamic portion that contains the inode number of the inode. The inode
number in the dynamic portion does not match the inode's real inode
number.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADPTRSUP, Problem: Bad Super Block inode map
pointer: bad_map_pointer Solution: Will be replaced by map
pointer to super block: good_map_pointer
Explanation: The super block inode contains a bad map
pointer to the super block.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADSEGNO, Problem: Bad file_type inode
inode_number segment number: bad_seg_value
Solution: Will be replaced by correct segment number:
good_value
Explanation: Each inode with its extensions has a
dynamic portion that is enumerated sequentially by its segment number.
The segment number is out of sequence.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_BADTYPE, Problem: Bad file_type inode
inode_number type: bad_type Solution: Will be
replaced by correct inode type: good_type
Explanation: The type field in the inode does not
correctly describe the type of the file that owns the inode.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_BADVMSDIR, Problem: Cannot read OpenVMS directory
directory, probably corrupted Solution: Directory and its
subdirectories will be removed from container_file container
file
Explanation: The OpenVMS directory in the CFS file
system is not readable. It is probably corrupted. The DCL ANALYZE DISK
command is recommended.
User Action: None. The error is repaired automatically
if the /REPAIR option is set.
%UCX-E-ANA_INO_NOVMSDIR, Problem: VMS directory inconsistency:
directory directory not found in container directory Solution:
Will remove the directory
Explanation: The OpenVMS container directory contains
an entry for the directory, which does not exist on the disk. Using the
ANALYZE DISK command is recommended.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
%UCX-E-ANA_INO_NOVMSFILE, Problem: VMS directory
inconsistency: file file not found in directory
directory Solution: Will remove the file from VMS directory.
Explanation: The OpenVMS container directory contains
no entry for the file, which does not exist on the disk. Using the
ANALYZE DISK command is recommended.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
%UCX-E-ANA_INO_NULVMSOWNER, Problem: File/directory has
invalid owner UIC: [xx,xx] Solution: Will be replaced by the parent
directory owner UIC.
Explanation: A OpenVMS directory or file in the
container file system has an invalid UIC.
User Action: If the /CONFIRM option is set, you are
prompted to confirm the solution before it is implemented.
C.4 Directory and Raw Data Validation Messages
The following error messages are related to errors detected in
directories and raw data cell groups (internal use only). All these
problems are corrected automatically (if the /REPAIR option is set)
without user confirmation or action.
Previous
| Next
| Contents