HP 3000 Manuals HP 3000 Manuals
NMERR Messages
NMERR 1 MESSAGE Invalid parameter specified. (NMERR 1)
CAUSE The caller of an NMS procedure has passed an
invalid value for one or more of the parameters.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 2 MESSAGE Invalid SubsystemID parameter. (NMERR 2)
CAUSE The caller of an NMS procedure has passed an
invalid value for the parameter SubsystemID.
Returned by NMOPENTRACE, NMOPENLOG,
NMGETTRACEID, NMVERSCHECK. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 3 MESSAGE Invalid UserID parameter. (NMERR 3)
CAUSE The caller of an NMS procedure has passed an
invalid value for the parameter UserID. Returned
by NMOPENTRACE, NMGETTRACEID. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 4 MESSAGE Invalid TraceType parameter. (NMERR 4)
CAUSE The caller of an NMS procedure passed an invalid
value to the TraceType parameter. Returned by
NMOPENTRACE, NMGETRACEID. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 5 MESSAGE Invalid TraceElement parameter. (NMERR 5)
CAUSE The caller of an NMS procedure passed an invalid
value to the TraceElement parameter. Returned
by NMOPENTRACE, NMGETTRACE. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 6 MESSAGE Invalid Dest parameter. (NMERR 6)
CAUSE The caller of an NMS procedure passed an invalid
value to the Dest parameter. Returned by
NMOPENTRACE. This is usually an internal error
in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 7 MESSAGE Invalid TraceID parameter. (NMERR 7)
CAUSE The caller of an NMS procedure passed an invalid
value to the TraceID parameter. Returned by
NMWRITETRACE, NMCLOSETRACE. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 8 MESSAGE Invalid InfoMode parameter. (NMERR 8)
CAUSE The caller of an NMS procedure passed an invalid
value to the InfoMode parameter. Returned by
NMWRITETRACE. This is usually an internal error
in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 9 MESSAGE Invalid Mode parameter. (NMERR 9)
CAUSE The caller of an NMS procedure passed an invalid
value to the Mode parameter. Returned by
NMWRITETRACE, NMCLOSETRACE, NMOPENLOG,
NMWRITELOG, NMCLOSELOG. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 10 MESSAGE Invalid FileName, RecordSize, and/or FileSize
parameter. (NMERR10)
CAUSE The caller of an NMS procedure passed an invalid
value to the FileName, RecordSize, and/or
FileSize parameters. Returned by NMOPENTRACE,
NMCONFOPEN. An invalid file name, record size,
or filesize was specified by the user in a CI
command, subsystem command, or NMMGR screen or
in a configuration file.
ACTION Correct and retry.
CAUSE One or more of these parameters are being passed
incorrectly by the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 11 MESSAGE Invalid LogID parameter. (NMERR 11)
CAUSE The caller of an NMS procedure passed an invalid
value to the LogID parameter. Returned by
NMWRITELOG, NMCLOSELOG. This is usually an
internal error in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 12 MESSAGE Invalid LogClass parameter. (NMERR 12)
CAUSE The caller of an NMS procedure passed an invalid
value to the LogClass parameter. Returned by
NMWRITELOG. This is usually an internal error in
the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 13 MESSAGE Invalid LogDataMode parameter. (NMERR 13)
CAUSE The caller of an NMS procedure passed an invalid
value to the LogDataMode parameter. Returned by
NMWriteLog. This is usually an internal error
in the calling subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 15 MESSAGE Unable to create new datafile. (NMERR 15)
CAUSE Returned by NMCONFOPEN. NMCONFOPEN detected an
error on MIDASOPEN, attempted on the user's
stack, on a new file that was to be created. A
File System error occurred. (Normal File System
restrictions apply when creating NM files.)
ACTION See "File System Error" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 16 MESSAGE Unable to open the datafile. (NMERR16)
CAUSE Returned by NMCONFOPEN. A File System error
occurred. (Normal File System restrictions
apply when accessing NM files.)
ACTION See "File System Error" at the beginning of this
appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 17 MESSAGE Unable to close the datafile. (NMERR 17)
CAUSE Returned by NMCONFCLOSE. NMFILE detected an
error on MIDASCLOSE.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 18 MESSAGE Unable to write to datafile. (NMERR 18)
CAUSE Returned by NMCONFGETDATA, NMCONFUPDATEDATA.
NMFILE detected an error on MIDASGETDATA,
besides NMFSERR 9 or 18.
ACTION See "File System Error" and "Submitting an SR"
at the beginning of this appendix.
CAUSE Returned by NMOPENTRACE, NMWRITETRACE,
NMCLOSETRACE, NMWRITELOG, and NMCLOSELOG. NMS
Tracing or Logging could not write to a trace or
log file. Check for File System errors such as
out of file, group, account, or system disc
space, or I/O errors.
ACTION If error persists and no File System error is
detectable, then see "Submitting an SR" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 19 MESSAGE Unable to read from datafile. (NMERR 19)
CAUSE Returned by NMCONFGETDATA. NMFILE detected an
error on MIDASGETDATA, besides NMFSERR 9 or
NMFSERR 18. A File System error occurred.
(Normal File System restrictions apply when
accessing NM files.)
ACTION See "File System Error" at the beginning of this
appendix.
CAUSE An internal error occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 20 MESSAGE Unable to obtain data segment for tracing.
(NMERR 20)
CAUSE Main NMLogMon was unable to get an extra data
segment, or if internal tracing was specified,
was unable to lock the extra data segment it did
get.
ACTION See "Insufficient MPE Resources" and "Submitting
an SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 21 MESSAGE Must have 1<= 8192 bytes. (NMERR21)
CAUSE A call to NMCONFadddata or NMCONFupdatedata
cannot send more than 8192 bytes of data. This
is probably an internal error in the calling
subsystem.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 25 MESSAGE Multiple accesses to a trace entity are not
supported. (NMERR 25)
CAUSE The trace entity passed to NMOPENTRACE is a
duplicate trace entry. NMS tracing will not
support multiple NMOPENTRACE calls for the same
trace entity. A trace entity is a unique
combination of the parameters SubSystemID,
TraceElement, and TraceType. A user entered a
command requesting a particular kind of trace
when this trace is already active.
ACTION Do not request a trace when that trace is
already active.
CAUSE An internal error has occurred.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 26 MESSAGE Trace entity is not currently being traced.
(NMERR 26)
CAUSE A request was made for the TraceID of a trace
entity that is not currently active. Returned
by NMGETTRACEID. (A trace entity is composed of
a SubSystemID, TraceElement, and TraceType).
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 27 MESSAGE Request can not be completed immediately.
(NMERR 27)
CAUSE A nowait type request cannot be processed
immediately. Returned by some of the NMnnTRACE
and NMnnLOG procedures when the MODE parameter
is set to 1 (nowait mode) and NMS Tracing or NMS
Logging cannot process the request immediately.
ACTION Normally this is not an error condition.
--------------------------------------------------------------------------
NMERR 28 MESSAGE Subsystem not configured in logging
configuration. (NMERR 28)
CAUSE The SubSystemID passed to NMOPENLOG cannot be
found in the LOGGING subtree of the
NMCONFIG.PUB.SYS configuration file. The
subsystem has not been configured for logging,
or the entry is spelled wrong, or the
configuration file has been corrupted.
ACTION Manually check the configuration using NMMGR and
ensure the logging entry for that subsystem is
configured properly. Refer to the appropriate
Reference Manual for assistance.
--------------------------------------------------------------------------
NMERR 29 MESSAGE LogClass not configured in configuration file.
(NMERR 29)
CAUSE NMS logging cannot find the specified log class
in the configuration file NMCONFIG.PUB.SYS.
Returned by NMWRITELOG. The log class specified
for the calling subsystem is not configured
correctly in NMCONFIG.PUB.SYS.
ACTION Use NMMGR to manually check and correct the
logging configuration in CONFIG.PUB.SYS. Make
sure that the class name is spelled correctly.
Refer to the appropriate reference manual for
assistance.
--------------------------------------------------------------------------
NMERR 31 MESSAGE Unable to repetition trace to beginning of file.
(NMERR 31)
CAUSE FCONTROL 5 failed.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 32 MESSAGE This program may not be run as a user process.
(NMERR 32)
CAUSE User attempted to RUN one of the NMS program
files that are not allowed to be RUN. These
program files include LINKMGR.PUB.SYS,
NMFILE.PUB.SYS, NMLOGMON.PUB.SYS,
PCMANAGE.PUB.SYS, NMLOGICS.PUB.SYS.
ACTION None.
--------------------------------------------------------------------------
NMERR 33 MESSAGE Unable to access logging configuration file.
(NMERR 33)
CAUSE An unexpected error occurred while NMS logging
was trying to read the logging configuration
data in NMCONFIG.PUB.SYS. Returned by NMOPENLOG.
ACTION See "Corrupt Configuration File" at the
beginning of this appendix.
--------------------------------------------------------------------------
NMERR 34 MESSAGE Invalid reference parameter specified. (NMERR
34)
CAUSE Condition code ">" returned from an internal
data segment move routine. One of the
parameters, passed by reference, would cause a
bounds violation if written to. This message is
returned if a bad condition code is received
after call of one of the move routines between
data segments: MBFDS, MFDS, MBTDS, MTDS. This
is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 35 MESSAGE Internal error: Invalid data segment number.
(NMERR 35)
CAUSE Condition code ">" returned from an internal
data segment move routine. An invalid DST
number was specified. This message is returned
if a bad condition code is received after call
of one of the move routines between data
segments: MBFDS, MFDS, MBTDS. This is an
internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 36 MESSAGE Unable to find port for NM Monitor process.
(NMERR 36)
CAUSE Returned by NMMONADDID and NMMONMAINTREQ. NMMON
does not have an entry in Port Dictionary.
Cause: internal problem, or bad software
installation.
ACTION See "Version Incompatibilities" and "Submitting
an SR" at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 37 MESSAGE Calls from split stack are not supported.
(NMERR 37)
CAUSE Returned by NMMONADDID, NMMONSTARTREQ,
NMMONMAINTREQ, NMOPENLINK, NMCLOSELINK,
NMMANAGELINK, NMLINKINFO and NMLINKDIAL. Attempt
to call above procedures in Split stack. 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 38 MESSAGE Parameter length out of range. (NMERR 38)
CAUSE Returned by NMMONSTARTREQ, NMOPENLINK, and
NMOPENLOG2. Length given for string parameter
negative or too long. 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 39 MESSAGE System shutdown in progress. Can't complete
request. (NMERR 39)
CAUSE Returned by NMMONADDID, NMMONSTARTREQ,
NMMONMAINTREQ, NMOPENLINK, NMCLOSELINK,
NMMANAGELINK, NMLINKINFO and NMLINKDIAL. NMMON
and Link Manager are in the process of shutting
down.
ACTION This is normally not an error condition.
--------------------------------------------------------------------------
NMERR 40 MESSAGE Port table full. Unable to expand capacity.
(NMERR 40)
CAUSE Returned by NMMONADDID. NMMON cannot expand its
DL DB area. 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 41 MESSAGE Port identifier not found in port table. (NMERR
41)
CAUSE Returned by NMMONDELETEID. Port ID to be deleted
does not exist in NMMON's table, NMMONADDID was
not called for this ID. 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 42 MESSAGE Unable to create specified system process.
(NMERR 42)
CAUSE Returned by NMMONSTARTREQ. Error calling
CREATEPROCESS intrinsic. Caused by not enough
MPE resources in system, an internal error, a
loader error, or bad software installation.
ACTION See "Insufficient MPE Resources," "Invalid
Software Installation," and "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 43 MESSAGE Unable to obtain data segment for port. (NMERR
43)
CAUSE Returned by NMOPENLINK. Link Manager found an
error calling procedure INITPORTDST.
ACTION See "Insufficient MPE Resources," "Invalid
Software Installation," and "Submitting an SR"
at the beginning of this appendix.
--------------------------------------------------------------------------
NMERR 44 MESSAGE Unable to create IPC port. (NMERR 44)
CAUSE Returned by NMOPENLINK. Link Manager found an
error calling CREATEPORT.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 45 MESSAGE Add to NM Monitor port table failed. (NMERR 45)
CAUSE Returned by NMOPENLINK. Error calling procedure
NMMONADDID (see message NMERR 40 above). Caused
by an internal error, or bad software
installation.
ACTION See "Invalid Software Installation" and
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMERR 46 MESSAGE Add to port dictionary failed. (NMERR 46)
CAUSE Returned by NMOPENLINK. Error calling procedure
DICTADD to add Link Manager in Port Dictionary.
Caused by an internal error, or bad software
installation.
ACTION See "Invalid Software Installation" and
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------