HP 3000 Manuals HP 3000 Manuals
NMERR Messages (contd)
NMERR 47 MESSAGE Unable to access message catalog NMCAT.PUB.SYS.
(NMERR 47)
CAUSE Returned by Version Checking Routines. Unable
to FOPEN file NMCAT.PUB.SYS. Caused by a bad
software installation.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 48 MESSAGE Unable to open $STDIN for process. (NMERR 48)
CAUSE Returned by NMOPENLINK. Unable to FOPEN $STDIN
for Link Manager process. Caused by an internal
error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 49 MESSAGE Unable to open $STDLIST for process. (NMERR 49)
CAUSE Returned by NMOPENLINK. Unable to FOPEN $STDLIST
for Link Manager process. Caused by an internal
error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 50 MESSAGE Unable to find port for Link Manager process.
(NMERR 50)
CAUSE Returned by NMOPENLINK. Link Manager does not
have an entry in Port Dictionary. Caused by an
internal problem, or bad software installation.
ACTION See "Invalid Software Installation" and
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 51 MESSAGE Length of data to be logged not in range 1<=Log
Data Size 2034 bytes. (NMERR 51)
CAUSE Caller of NMWRITELOG has requested either too
much or too little data to be logged.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 53 MESSAGE Invalid NMCONF pathname. Non-printable
characters not allowed.
CAUSE Returned by most NMCONF intrinsics. Caller has
sent NMCONF intrinsic a pathname with
non-printable character(s). May be a subsystem
problem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 54 MESSAGE Invalid transaction number. (NMERR 54)
CAUSE Returned by most of the NMCONF procedures.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 55 MESSAGE NMTC FILES 0000 THRU 9999 ALL USED, NONE
AVAILABLE FOR NEXT TRACEFILE. (NMERR 55)
CAUSE NMS Trace finds that files NMTC0000 through
NMTC9999 all already exist. It is more likely
that a directory problem or an internal problem
exists.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 56 MESSAGE Invalid infolen, must be in range: 1 <= infolen
<= 8. (NMERR56)
CAUSE Returned by: NMCONFFILEINFO.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 57 MESSAGE Duplicate identifier already exists. (NMERR 57)
CAUSE Returned by NMCONFADDPATH, NMCONFRENAMEPATH.
NMFILE detected NMFSERR 21 on MIDASADDPATH. User
of configuration program entered erroneous
information.
ACTION Enter correct data specifications.
CAUSE Configuration database has internal error.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
CAUSE Internal software error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 58 MESSAGE Unable to find identifier in path name. (NMERR
58)
CAUSE Returned by NMCONFGETDATA, NMCONFADDPATH,
NMCONFPURGEPATH, NMCONFNEXTPATH, NMCONFADDDATA,
NMCONFUPDATEDATA NMCONFDATALENGTH,
NMCONFRENAMEPATH, NMCONFPURGEDATA. NMFILE
detected message NMFSERR 9. User of
configuration program or caller of procedure
entered erroneous pathname.
ACTION Enter correct pathname.
CAUSE Configuration file internal error.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 59 MESSAGE Path depth < minimum or > maximum allowed.
(NMERR 59)
CAUSE Returned by NMCONFNEXTPATH. Procedure received a
path depth < 0, or > 256. Returned by:
NMCONFADDDATA, NMCONFUPDATEDATA, NMCONFGETDATA,
NMCONFDATALENGTH, NMCONFPURGEDATA,
NMCONFRENAMEPATH, NMCONFPURGEPATH,
NMCONFADDPATH. Procedure received a path depth <
1, or > 256. Internal error in the calling
program.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 60 MESSAGE Unable to find NM Log Monitor. (NMERR 60)
CAUSE An NM Trace or Logging procedure is unable to
locate the server trace or log process
(NMLogMon). Returned by NMOPENTRACE,
NMGETTRACEID, NMCLOSETRACE, NMOPENLOG,
NMCLOSELOG, and by the SHOWNMLOG CI command.
The trace or log server process creation failed
at system startup due to a bad software
installation, a loader error, or an internal
error.
ACTION See "Invalid Software Installation" and
"Submitting an SR" at the beginning of this
appendix.
CAUSE An =SHUTDOWN or NMMAINT,SHUTDOWN has been
executed prior to the Trace or Logging procedure
call. The server process has already shut down.
This is not an error condition.
ACTION None.
--------------------------------------------------------------------------
NMERR 61 MESSAGE DB register at absolute. (NMERR 61)
CAUSE Caller's DB register is at an absolute DB
location (WHERES'DB returned a < condition
code). This is not allowed in the called
procedure. Returned by those trace and log
procedures that can otherwise be called in split
stack mode. This is probably an internal error
by the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 62 MESSAGE NM trace dictionary table is full. (NMERR 62)
CAUSE An unexpectedly large number of NMOPENTRACE
calls have been made, each specifying a
different combination of SubSystemID, TraceType,
and TraceElement. If this is being done by user
request, turn off some of the traces, then
retry. If this is not being done by user
request, then this is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 63 MESSAGE NM log table is full. (NMERR 63)
CAUSE An unexpectedly large number of NMOPENTRACE
calls have been made, each specifying internal
memory tracing or a different destination
filename. If this is being done by user
request, turn off some of the traces, then
retry. If this is not being done by user
request, then this is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 64 MESSAGE Specified file is a system file. (NMERR 64)
CAUSE The file name (FileName) parameter of the
NMOPENTRACE procedure contains a system file
name (the first ASCII character is "$"). User
specified an incorrect filename either in the
command that starts tracing, or in the
configuration file.
ACTION Specify a valid file name and retry.
--------------------------------------------------------------------------
NMERR 65 MESSAGE Specified file is a back referenced file.
(NMERR 65)
CAUSE The file name (FileName) parameter of the
NMOPENTRACE procedure contains a back referenced
file name (the first ASCII character is "*").
User specified an incorrect filename either in
the command that starts trace for that
subsystem, or in the configuration file for that
subsystem.
ACTION Specify a valid file name and retry.
--------------------------------------------------------------------------
NMERR 67 MESSAGE User logging entries are not available. (NMERR
67)
CAUSE The LogBuf XDS used for a particular NMS trace
file or for NMS logging has no more available
entries to add one more user. An additional
entry is used for tracing whenever additional
traces are requested to go to an existing open
trace file. An additional entry is used for
logging whenever a subsystem opens a log file.
The user has requested an unexpectedly large
number of concurrent traces to go to the same
trace file.
ACTION Turn off some of the traces and retry.
CAUSE An internal error has occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 69 MESSAGE Unable to create the trace process. (NMERR 69)
CAUSE The tracing subsystem is unable to create a
trace server process for the NMOPENTRACE request
(NMMONSTARTREQ failed).
ACTION See "Invalid Software Installation,"
"Insufficient MPE Resources," and "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 70 MESSAGE Unable to initialize the trace process. (NMERR
70)
CAUSE The tracing subsystem is unable to initialize
the trace server process for the NMOPENTRACE
request (unable to create a port or acquire a
data segment).
ACTION See "Invalid Software Installation,"
"Insufficient MPE Resources," and "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 71 MESSAGE Logging has stopped. (NMERR 71)
CAUSE An I/O error or File System error occurred
earlier and logging is not currently taking
place. Returned by NMOPENLOG.
ACTION Enter the SHOWLOG command to find out the status
of the log file and the type of error. Correct
the error, and restart logging with a
RESUMENMLOG or a SWITCHNMLOG command. Then
retry the action that led to this error.
--------------------------------------------------------------------------
NMERR 72 MESSAGE This command has no parameter. (NMERR 72)
CAUSE Parameters were specified for an NMS command
that does not require any parameters. Returned
by SHOWNMLOG, RESUMENMLOG, and SWITCHNMLOG. User
entered parameters for an NMS CI command
SHOWNMLOG, SWITCHNMLOG, or RESUMENMLOG.
ACTION Enter the command name alone without any other
text on the $STDIN or $STDINX record.
--------------------------------------------------------------------------
NMERR 73 MESSAGE Invalid logging configuration file. (NMERR 73)
CAUSE NMCONFIG.PUB.SYS contains invalid logging
configuration data. Returned by NMOPENLOG,
NMWRITELOG.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 74 MESSAGE NM Log dictionary table is full. (NMERR 74)
CAUSE Network management logging facility has a log
dictionary table with a fixed number of
available entries. If no free entries are
available to complete the caller request this
error message is returned. Incompatible
software versions installed.
ACTION See "Invalid Software Installation" and "Version
Incompatibilities" at the beginning of this
appendix. If this does not resolve the problem,
then see "Submitting an SR" at the beginning of
this appendix.
--------------------------------------------------------------------------
NMERR 75 MESSAGE Data is already associated with this identifier.
(NMERR 75)
CAUSE Returned by: NMCONFADDDATA. NMFILE detected
NMFSERR 12. User attempted to add data to a
path location where data already exists. This
may not necessarily be an error if the calling
program is trying to determine if data already
exists at that location. This could also be
caused by database corruption, or by an internal
error.
ACTION If data base corruption is suspected, then see
"File System Error" at the beginning of this
appendix. If an internal error is suspected,
then see "Submitting an SR" at the beginning of
this appendix.
--------------------------------------------------------------------------
NMERR 76 MESSAGE File associated with this transaction is not
locked. (NMERR 76)
CAUSE Returned by: NMCONFUNLOCKFILE. NMFILE
determined that an NMCONFUNLOCKFILE was
attempted on a transaction without a
corresponding NMCONFLOCKFILE. This is not
necessarily an error if the intent of the caller
was to determine the lock status of the file.
This could also be caused by an internal error.
ACTION If an internal error is suspected, see
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 77 MESSAGE File associated with this transaction is locked.
(NMERR 77)
CAUSE Returned by: NMCONFADDDATA, NMCONFUPDATEDATA,
NMCONFPURGEDATA, NMCONFADDPATH, NMCONFPURGEPATH,
NMCONFRENAMEPATH. Some other process has the
NMCONF type file locked.
ACTION Wait until the file is unlocked by the other
user(s) before proceeding.
--------------------------------------------------------------------------
NMERR 78 MESSAGE No data associated with this identifier. (NMERR
78)
CAUSE Returned by: NMCONFGETDATA, NMCONFDATALENGTH,
NMCONFPURGEDATA, NMCONFUPDATEDATA. NMFILE
detected NMFSERR 18. This may not be an error
if the call to these procedures was using this
return to test if data was associated with the
identifier. If it was an error, it could be due
to corruption of the database.
ACTION If file corruption is suspected, see "Corrupt
Configuration File" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 82 MESSAGE Buffer length parameter out of allowable range.
(NMERR 82)
CAUSE Returned by NMCONFGETDATA. Length parameter is
longer than 8192 or less than 7. Probable
internal error by caller.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 83 MESSAGE Unable to get data length from datafile. (NMERR
83)
CAUSE Returned by NMCONFDATALENGTH. NMFILE detected an
error on MIDASDATALENGTH, besides NMFSERR 18.
This is probably due to corruption of the
configuration data file.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 85 MESSAGE Data structures internal error in NMFILE. (NMERR
85)
CAUSE Returned by most NMCONF procedures.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 86 MESSAGE Switch to CM failed. (NMERR 86)
CAUSE Returned by native mode NMS procedures if an
error is returned by SWITCH.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 87 MESSAGE CM data segment improperly mapped to NM object.
(NMERR 87)
CAUSE Returned by native mode NMWRITETRACE if an error
is returned by wrap-dst.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 88 MESSAGE Parameter not aligned properly. (NMERR 88)
CAUSE Internal error by the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 90 MESSAGE Invalid path type value, must be 1 or 2. (NMERR
90)
CAUSE Returned by NMCONFNEXTPATH. NMCONFNEXTPATH
detected invalid path type value. Internal
error by the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 92 MESSAGE Unable to purge datafile. (NMERR 92)
CAUSE Returned by NMCONFPURGE NMOPENTRACE. File system
error.
ACTION Try to purge the file from a CI session, and
note the error. Correct this and retry.
--------------------------------------------------------------------------
NMERR 94 MESSAGE No identifiers beyond this point in datafile.
(NMERR 94)
CAUSE Returned by NMCONFNEXTPATH. NMFILE detected
warning NMFSWARN 23, in MIDASNEXTPATH. This may
not be an error if the caller's intention is to
search the data file. Otherwise it might
indicate corruption of the file.
ACTION If file corruption is suspected, see "Corrupt
Configuration File" at the beginning of this
appendix. If this is not a problem, it may be
due to incompatible software modules, or an
internal error by the calling subsystem. See
"Version Incompatibilities" and "Submitting an
SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 95 MESSAGE Read truncated to capacity of buffer. (NMERR
95)
CAUSE Returned by NMCONFGETDATA. NMFILE detected
NMFWARN 19 on MIDASGETDATA. This is probably an
internal error by the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 96 MESSAGE File code mismatch. (NMERR 96)
CAUSE Returned by NMCONFOPEN. NMFILE detected NMFSWARN
6 on MIDASOPEN. The file is not a valid
configuration file.
ACTION Type LISTF <filename>, 1 on the file. The file
type should be type NCONF.
CAUSE Internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 97 MESSAGE Failure of DICTSEND procedure. (NMERR 97)
CAUSE Returned by all NMCONF procedures. Error
detected on DICTSEND.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 100 MESSAGE Subsystem does not support version checking.
(NMERR 100)
CAUSE Returned by NMVERSCHECK. Coding error by caller
of NMVERSCHECK. The SUBSYSID parameter must
refer to a subsystem number that has a second
level version cross check routine.
ACTION See "Invalid Software Installation" at the
beginning of this appendix.
--------------------------------------------------------------------------