Using the Node Management Services (NMS) Utilities (32022-90053)
Appendix A 173
NMS Error Messages
NMDUMP Error and Warning Messages
MESSAGE: Error — File is not of trace type. (NMDUMPERR 5)
NMDUMPERR 5 CAUSE: User specified that he wanted to format a trace file, but the
input file specified was not type NTRAC.
ACTION: Check spelling of filename. Check file’s type code. Correct
input and re-enter.
MESSAGE: Invalid date and time string entered. (NMDUMPERR 6)
NMDUMPERR 6 CAUSE: User entered an invalid date and/or time. User entered the
date and/or time in improper format. Type “Help” for a list of allowed
formats.
ACTION: Correct input and re-enter.
MESSAGE: Time not within time range of file. (NMDUMPERR 7)
NMDUMPERR 7 CAUSE: User entered a date and/or time that is beyond the time range
of the input file.
ACTION: Correct input and re-enter.
MESSAGE: Finishing time earlier than starting time. (NMDUMPERR 8)
NMDUMPERR 8 CAUSE: User entered a finishing date and time that was earlier than
the starting date and time.
ACTION: Correct input and re-enter.
MESSAGE: LOADPROC failed on procedure !, LOADPROC error !. Will
output this subsystemid’s entries in dump format. (NMDUMPWARN 9)
NMDUMPWARN
9
CAUSE: NMDUMP was unable to LOADPROC (via MODCAL ADDR
function) the trace or log formatter procedure for the specified
subsystemid number. The procedure name is SUBSYSnLOGFORMAT
or SUBSYSnTRACEFORMAT, for log or trace files, for subsystemid = n.
NMDUMP will continue and will print out data for this subsystemid,
but it will be in a raw dump (hex and ASCII) format. The procedure is
not in an SL accessible to NMDUMP. Normally it should be present in
SL.PUB.SYS on those systems that have installed the NMS software.
Either the initial installation of these procedures was faulty, or these
procedures have been deleted since their initial installation.
ACTION: Get a known good copy of these procedures and install them
in SL.PUB.SYS.
MESSAGE: LOADPROC failed on procedure !, LOADPROC error !.
Default formatting options will be assumed for this subsystemid.
(NMDUMPWARN 13)
NMDUMPWARN
13
CAUSE: Similar to NMDUMPWARN 9, except the procedure that failed
to load was a menu procedure.
ACTION: Get a known good copy of these procedures and install them
in SL.PUB.SYS.