Using the Node Management Services (NMS) Utilities (32022-90053)

Appendix A 255
NMS Error Messages
NMGR Error and Warning Messages
MESSAGE: Cannot specify a negative number for expansion.
(NMGRERR 383)
NMGRERR 383 CAUSE: Maintenance mode interface: The user gave a negative number
of records to expand the file.
ACTION: Supply a positive number of records.
MESSAGE: Cannot open command file “NMMGRCMD”.
(NMGRERR 384)
NMGRERR 384 CAUSE: The command file NMMGRCMD could not be opened.
ACTION: Check for any file equations set for “NMMGRCMD”. See the
accompanying file system error message for problem resolution.
MESSAGE: An NMMGR configuration file name must be specified.
(NMGRERR 385)
NMGRERR 385 CAUSE: Maintenance mode interface: An error message is issued when
the configuration file argument for the OPENCONF command is missing.
ACTION: Reissue the command with the configuration file name.
MESSAGE: Invalid subsystem name, enter valid name (ie, NETXPORT,
SNANODE). (NMGRERR 386)
NMGRERR 386 CAUSE: Maintenance mode interface: An error message is issued when
an invalid subsystem name is entered.
ACTION: Reissue the command with a correct subsystem name.
MESSAGE: Unable to OPEN, and unable to CREATE config file.
(NMGRERR 387)
NMGRERR 387 CAUSE: File system error.
ACTION: Check to see if user is allowed to access file. Check to see if
user and account capabilities of NA or NM are set.
MESSAGE: Attempted to access non data or page data screen with
PATHCONF. (NMGRERR 388)
NMGRERR 388 CAUSE: Incorrect use of PATHCONF command.
ACTION: Make sure that the screen you are trying to access is data or
paged data. This can be checked by looking at the screen and seeing if
there is a data flag in the upper right corner of the screen. If not, you
are trying to access a screen which has no data fields.
MESSAGE: Attempt to access field which does not exist.
(NMGRERR 389)
NMGRERR 389 CAUSE: You are trying to access a field N+k when there are only N
fields on the form.