HP 3000 Manuals HP 3000 Manuals
NDIERR Messages
NDIERR messages are produced by errors from the Network Directory
intrinsics. In most cases, they are accompanied by other messages
(NMGRERRs or MPE File System errors). You should take the action
recommended for the accompanying messages first.
NDIERR 001 MESSAGE Directory file not open. (NDIERR 001)
CAUSE No directory file was opened.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 002 MESSAGE Directory is not open for write access. (NDIERR
002)
CAUSE The currently opened directory was not opened
with write access.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 003 MESSAGE FLOCK failed - internal error. (NDIERR 003)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 004 MESSAGE Requires Network Administrator capability.
(NDIERR 004)
CAUSE User does not have Network Administrator
capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 006 MESSAGE Not enough room in directory for new entry.
(NDIERR 006)
CAUSE The directory file is full.
ACTION Expand the directory file capacity using the
NMMGR maintenance mode EXPANDDIR command.
--------------------------------------------------------------------------
NDIERR 007 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 007)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 008 MESSAGE Name type invalid; must be 1 (NS name) or 5
(domain name). (NDIERR 008)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 009 MESSAGE Name length invalid for name type. (NDIERR 009)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 010 MESSAGE Path report list length cannot be negative.
(NDIERR 010)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 011 MESSAGE Path report list length greater than ND'CREATE
maximum. (NDIERR 011)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginnng of this
appendix.
--------------------------------------------------------------------------
NDIERR 012 MESSAGE Duplicate node name in directory - cannot add
new entry. (NDIERR 012)
CAUSE An entry with the same node name and
global/local flag setting already exists in the
directory.
ACTION Supply a different node name and/or global/local
setting.
--------------------------------------------------------------------------
NDIERR 013 MESSAGE FFINDBYKEY failed - corrupt file likely.
(NDIERR 013)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 020 MESSAGE Directory file not open. (NDIERR 020)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 021 MESSAGE Cannot close directory file - internal error.
(NDIERR 021)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 022 MESSAGE Requires Node Manager or Network Administrator
capability. (NDIERR 022)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 040 MESSAGE Directory size too small; must be 0. (NDIERR
040)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 041 MESSAGE Directory size too large; must be <<= 10,000
records. (NDIERR 041)
CAUSE Directory size parameter too large.
ACTION If a larger file is really desired, create one
at the maximum size, then use NMMGR maintenance
mode EXPANDDIR command to increase the file to
desired size. If this fails, see "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 042 MESSAGE Maximum path report list length negative; must
be 0. (NDIERR 042)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 043 MESSAGE Maximum path report list length too large; must
be <= 500. (NDIERR 043)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 044 MESSAGE Cannot create directory file. (NDIERR 044)
CAUSE The network directory file could not be opened.
ACTION See the accompanying file system error message
for problem resolution.
--------------------------------------------------------------------------
NDIERR 045 MESSAGE FWRITE of header record failed - internal error.
(NDIERR 045)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 046 MESSAGE FCLOSE failed - internal error. (NDIERR 046)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 047 MESSAGE Directory name cannot contain a lockword.
(NDIER 047)
CAUSE Directory file names may not be lockword
protected.
ACTION Resubmit the file name with no lockword or a
null lockword.
--------------------------------------------------------------------------
NDIERR 048 MESSAGE Requires Network Administrator capability.
(NDIERR 048)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 060 MESSAGE ND FSERR called when no file system error had
occurred. (NDIERR 060)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 080 MESSAGE Directory file not open. (NDIERR 080)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 081 MESSAGE Item number invalid; must be 1, 2, 3, 4, 5, or
6. (NDIERR 081)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 082 MESSAGE Requires Node Manager or Network Administrator
capability. (NDIERR 082)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 083 MESSAGE FGETINFO failed - internal error. (NDIERR 083)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 084 MESSAGE FLOCK failed - internal error. (NDIERR 084)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 085 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 085)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 100 MESSAGE Cannot open directory file. (NDIERR 100)
CAUSE Could not open the directory file due to various
MPE file system errors.
ACTION Consult accompanying file system error message
for problem resolution.
--------------------------------------------------------------------------
NDIERR 101 MESSAGE FGETINFO failed - internal error. (NDIERR 101)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 102 MESSAGE Wrong filecode for directory file; expected
1211. (NDIERR 102)
CAUSE The file name specified is not a network
directory file.
ACTION Correct filename to refer to a network directory
file.
--------------------------------------------------------------------------
NDIERR 103 MESSAGE Access mode invalid; must be 0 or 1. (NDIERR
103)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 104 MESSAGE Share option invalid; must be 0, 1, 2 or 3.
(NDIERR 104)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 105 MESSAGE FLOCK failed - internal error. (NDIERR 105)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 106 MESSAGE Incompatible directory version - outdated
directory. (NDIERR 106)
CAUSE The current level of software does not support
the format of the directory file.
ACTION Install correct versions of NMC software or
restore correct version of the network directory
file.
--------------------------------------------------------------------------
NDIERR 107 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 107)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 108 MESSAGE FCLOSE failed - internal error. (NDIERR 108)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 109 MESSAGE Directory name cannot contain a lockword.
(NDIERR 109)
CAUSE The network directory file cannot be lockword
protected.
ACTION Remove the lockword from the filename, or
replace it with a null lockword.
--------------------------------------------------------------------------
NDIERR 110 MESSAGE Requires Node Manager or Network Administrator
capability. (NDIERR 110)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 111 MESSAGE File is not a Network Directory. (NDIERR 111)
CAUSE User calling ND'OPEN passed a file that is not a
network directory file. The most likely CAUSE
is that the file is not a KSAM file.
ACTION Correct the filename.
--------------------------------------------------------------------------
NDIERR 120 MESSAGE One or more required parameters are missing.
(NDIERR 120)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 121 MESSAGE Directory file not open. (NDIERR 121)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 122 MESSAGE Relop parameter invalid; must be 0, 1, 2, 4, 5,
or 6. (NDIERR 122)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 123 MESSAGE Name type invalid; must be 1 (NS name) or 5
(domain name). (NDIERR 123)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 124 MESSAGE Name length invalid for name type. (NDIERR 124)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 125 MESSAGE FFINDBYKEY failed - corrupt file likely.
(NDIERR 125)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 126 MESSAGE Cannot find a matching node name in the
directory.
(NDIERR 126)
CAUSE In the directory, no entry could be found with
the requested nodename and global/local flag
setting, or a partial nodename (generic key) was
requested and no match could be found.
ACTION Supply the nodename of an existing entry, or a
generic key to satisfy the match.
--------------------------------------------------------------------------
NDIERR 127 MESSAGE FREAD failed - corrupt file likely. (NDIERR
127)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 128 MESSAGE FLOCK failed -internal error. (NDIERR 128)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 129 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 129)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 130 MESSAGE Requires Node Manager or Network Administrator
capability. (NDIERR 130)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 131 MESSAGE Select parameter invalid; must be 0, 1 or 2.
(NDIERR 131)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 132 MESSAGE FSPACE failed - corrupt file likely. (NDIERR
132)
CAUSE Probable corrupt directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 140 MESSAGE Directory file not open. (NDIERR 140)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 141 MESSAGE Directory is not open for write access. (NDIERR
141)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 142 MESSAGE FLOCK failed - internal error. (NDIERR 142)
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 143 MESSAGE Cannot remove node name - internal error.
(NDIERR 143)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 144 MESSAGE Requires Network Administrator capability.
(NDIERR 144)
CAUSE User does not have Network Administrator
capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 145 MESSAGE FREAD failed - corrupt file likely. (NDIERR
145)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 146 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 146)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 147 MESSAGE Name type invalid; must be 1 (NS name) or 5
(domain name). (NDIERR 147)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 148 MESSAGE Name length invalid for name type. (NDIERR 148)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 149 MESSAGE FFINDBYKEY failed - corrupt file likely.
(NDIERR 149)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 150 MESSAGE No such name in directory - cannot remove it.
(NDIERR 150)
CAUSE The name does not exist in the directory file.
ACTION Correct the nodename and/or global/local
setting.
--------------------------------------------------------------------------
NDIERR 160 MESSAGE Directory file not open. (NDIERR 160)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 161 MESSAGE Requires Node Manager or Network Administrator
capability. (NDIERR 161)
CAUSE User does not have Node Manager or Network
Administrator capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 162 MESSAGE Request parameter invalid; must be 1 or 2.
(NDIERR 162)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 163 MESSAGE FREADBYKEY failed - corrupt file likely.
(NDIERR 163)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 164 MESSAGE FREAD failed - corrupt file likely. (NDIERR
164)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 165 MESSAGE FLOCK filed - internal error. (NDIERR 165)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 166 MESSAGE FCONTROL/FUNLOCK failed - internal error.
(NDIERR 166)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 167 MESSAGE Cannot read node name back reference record -
corrupt file likely. (NDIERR 167)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 180 MESSAGE FOPEN of message catalog failed. (NDIERR 180)
CAUSE The message catalog NMMGRCAT.PUB.SYS could not
be opened. Possible CAUSEs and solutions
include incorrect software installation,
insufficient user access rights to the file, or
incorrect version of software.
ACTION Restore NMMGRCAT.PUB.SYS from a back-up tape,
increase user's access rights, or reinstall the
product.
--------------------------------------------------------------------------
NDIERR 181 MESSAGE GENMESSAGE failed. (NDIERR 181)
CAUSE A message could not be read from the message
catalog. A possible CAUSE is incorrect version
of the software.
ACTION Reinstall the product.
--------------------------------------------------------------------------
NDIERR 190 MESSAGE Error in NMCONF Intrinsic; check for error
status. (NDIERR 190)
CAUSE A problem was encountered when calling an NMCONF
procedure.
ACTION Refer to the accompanying NMCONF error message.
--------------------------------------------------------------------------
NDIERR 191 MESSAGE Error in Network Directory intrinsic; check for
error status. (NDIERR 191)
CAUSE This is an internal error.
ACTION Refer to the accompanying NMCONF error message.
If the associated error is number 58, then the
configuration file to merge from does not have
any directory data in it. The file must first
be read by the network transport by bringing up
the transport in order to extract the directory
data.
--------------------------------------------------------------------------
NDIERR 192 MESSAGE Requires Network Administrator capability.
(NDIERR 192)
CAUSE User does not have Network Administrator
capabilities.
ACTION Change user capabilities.
--------------------------------------------------------------------------
NDIERR 200 MESSAGE File recovery: cannot open message catalog.
(NDIERR 200)
CAUSE The message catalog NMMGRCAT.PUB.SYS could not
be opened. Possible CAUSEs include: improper
product installation, insufficient user access
rights to the catalog file, or an incorrect
version of the software installed.
ACTION Reinstall the product, increase the user's
access rights, or restore NMMGRCAT.PUB.SYS from
a back-up tape.
--------------------------------------------------------------------------
NDIERR 201 MESSAGE File recovery: FOPEN of temporary command file
failed. (NDIERR 201)
CAUSE MPE could not open a scratch file to write file
recovery commands into. This could be CAUSEd by
one or more of the following reasons:
* Duplicate file name. BeCAUSE the file
name generated is random, this CAUSE is
very unlikely.
* User does not have Save Files capability.
* Other file system error.
ACTION 1. Consult the associated file system error for
problem resolution.
2. Attempt manual recovery of the directory
file using KSAMUTIL.PUB.SYS.
--------------------------------------------------------------------------
NDIERR 202 MESSAGE File recovery: GEMMESSAGE failed. (NDIERR 202)
CAUSE Could not read a message from the catalog
NMMGRCAT.PUB.SYS. A possible CAUSE is that an
incorrect version of the software is installed.
ACTION Reinstall the product, restore NMMGRCAT.PUB.SYS,
or attempt manual recovery of the directory file
using KSAMUTIL.PUB.SYS.
--------------------------------------------------------------------------
NDIERR 203 MESSAGE File recovery: FWRITE to temporary command file
failed. (NDIERR 203)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 204 MESSAGE File recovery: FCLOSE of temporary command file
failed. (NDIERR 204)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 205 MESSAGE File recovery: CREATEPROCESS of
KSAMUTIL.PUB.SYS failed. (NDIERR 205)
CAUSE Problem encountered trying to create a son
process to run KSAM.PUB.SYS. It is possible that
the program file KSAMUTIL.PUB.SYS is missing.
ACTION Restore KSAMUTIL.PUB.SYS.
CAUSE Out of some type of system resource - check
SYSDUMP configuration.
ACTION Consult CREATEPROCESS errors in the MPE
Intrinsics Reference Manual.
--------------------------------------------------------------------------
NDIERR 206 MESSAGE File recovery: cannot open directory file
exclusively. (NDIERR 206)
CAUSE The network directory file could not be opened
exclusively in order to recover the file.
ACTION See the accompanying file system error message.
If FSERR 192 is displayed, recover the network
directory file.
--------------------------------------------------------------------------
NDIERR 207 MESSAGE File recovery: FCLOSE failed - internal error.
(NDIERR 207)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 208 MESSAGE File recovery: FFINDBYKEY failed - internal
error. (NDIERR 208)
CAUSE Network directory file is irrecoverable.
ACTION Attempt manual recovery of the file using
KSAMUTIL.PUB.SYS or restore the data and key
files from a back-up tape.
--------------------------------------------------------------------------
NDIERR 209 MESSAGE File recovery: FREAD failed - internal error.
(NDIERR 209)
CAUSE Network directory file is irrecoverable.
ACTION Attempt manual recovery of the file using
KSAMUTIL.PUB.SYS or restore the data and key
files from a back-up tape.
--------------------------------------------------------------------------
NDIERR 220 MESSAGE FPOINT to header record failed - corrupt file
likely. (NDIERR 220)
CAUSE The file is corrupt, empty, or is not a network
directory file.
ACTION Restore the data and key files from a back-up
tape.
--------------------------------------------------------------------------
NDIERR 221 MESSAGE FREADC of header record failed - corrupt file
likely. (NDIERR 221)
CAUSE The file is not a KSAM file (and thus not a
network directory file), or is a corrupt network
directory.
ACTION Restore the proper KSAM file from a back-up tape
(data and key files) or attempt manual recovery
on the file using KSAMUTIL.PUB.SYS.
--------------------------------------------------------------------------
NDIERR 222 MESSAGE Length of header record incorrect - corrupt file
likely. (NDIERR 222)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 230 MESSAGE FPOINT to header record failed. (NDIERR 230)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 231 MESSAGE FUPDATE of header record failed. (NMIERR 231)
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 240 MESSAGE FUPDATE of existing record failed. (NDIERR 240)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 241 MESSAGE FWRITE of new record failed. (NDIERR 241)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 250 MESSAGE Actual path report list length differs from
passed length. (NDIERR 250)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 251 MESSAGE Path report list length too small to support
minimal report. (NDIERR 251)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 252 MESSAGE Domain report in path report list too short ( 6
bytes). (NDIERR 252)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 253 MESSAGE Version of domain report in path report list 0.
(NDIERR 253)
CAUSE The version number (1st octet) of a domain
indicates an unsupported version.
ACTION Possible version mismatch; reinstall the
product. If this fails, see "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 254 MESSAGE Domain number of domain report in path report
list 1. (NDIERR 254)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 260 MESSAGE Cannot read a node name back reference record -
corrupt file likely. (NDIERR 260)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 261 MESSAGE A required node name record is not in dir -
corrupt file likely. (NDIERR 261)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 262 MESSAGE FUPDATE failed - internal error. (NDIERR 262)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 270 MESSAGE FGETINFO failed - internal error. (NDIERR 270)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NDIERR 271 MESSAGE FFINDBYKEY failed - corrupt file likely.
(NDIERR 271)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------
NDIERR 272 MESSAGE FREAD failed - corrupt file likely. (NDIERR
272)
CAUSE Possible corrupt network directory file.
ACTION Restore the data and key files from a back-up
tape. If this fails, see "Submitting an SR" at
the beginning of this appendix.
--------------------------------------------------------------------------