Using the Node Management Services (NMS) Utilities (MPE/iX 7.0, 7.5)
178 AppendixA
NMS Error Messages
NMCN Error and Warning Messages
NMCNERR 47 MESSAGE: NMLG FILES
mmmm
THRU
nnnn
SKIPPED. (NMCNERR 47)
CAUSE: NM log files
mmmm
through
nnnn
were skipped over when NMS
Logging tried to open a new disk log file. Files NMLG
mmmm
.PUB.SYS
through NMLG
nnnn
.PUB.SYS already exist. This is an information
message only; no error occurred.
ACTION: None.
NMCNERR 48 MESSAGE: NMLG FILES 0000 THRU 9999 ALL USED, NONE
AVAILALBLE FOR NEXT LOGFILE. (NMCNERR 48)
CAUSE: NMS Logging finds that files NMLG0000 through NMLG9999 all
already exist. It is more likely that a directory problem or an internal
problem exists.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMCNMSG 49 MESSAGE: MainLogMon: NMGLOBAL file found, purged (not needed
for this version). (NMCNMSG 49)
CAUSE: Privileged file NMGLOBAL.PUB.SYS was found. This file is not
needed in this version of NMS software. The file information is
transferred to the Cold Load area of disk, and the file is purged.
ACTION: None. Informative message.
NMCNERR 50 MESSAGE: NM Log Process: Cannot access NMCAT.PUB.SYS to
format a log msg. (NMCNERR 50)
CAUSE: NM Log Process could not open the message catalog and so
could not format a logging message.
ACTION: See “Invalid Software Installation” at the beginning of this
appendix.
NMCNERR 51 MESSAGE: NM Log Process: Logging class ! not configured for
subsystem ! in !. (NMCNERR 51)
CAUSE: A logging message was received from NMS subsystem
m
that
specified log class
n
. However, log class
n
is not configured. The log
message is discarded.
ACTION: Use NMMGR to configure logging class
n
under subsystem
m
in the specified configuration file. The NMMGR subtree is LOGGING.
SUB
mmmm
.CLAS
nnnn
, where
mmmm
is the subsystem number
m
with
leading zeros, and
nnnn
is the class number
n
with leading zeros.
NMCNWARN 70 MESSAGE: Link Manager unable to open NM logging.
(NMCNWARN 70)
CAUSE: A Link Manager process encountered an error from
NMOPENLOG.
ACTION: The specific NMERR will be reported in a console message
immediately following this message. The Link Manager process will