Using the Node Management Services (NMS) Utilities (MPE/iX 7.0, 7.5)

Appendix A 277
NMS Error Messages
NMMGRVER Messages, Errors and Warnings
incorrect. This could indicate that an incorrect cell was accessed or that
the user is trying to convert an invalid configuration file. The cell is not
converted.
ACTION: Verify that the original file was a valid version. Using another
tool, examine the cell data and verify the data. Since the cell was not
touched, the data may have to be entered manually.
NMMGRVERERR
16
MESSAGE:
Conversion failure.
PATH: !
MIDASSTAT: !
(NMMGRVERERR 16)
CAUSE: This is a generic message which allows the path name and
status to be output.
ACTION: Depends on status and user needs.
NMMGRVERERR
17
MESSAGE:
Path not allowed for this version. Path purged.
Path: !
(NMMGRVERERR 17)
CAUSE: Certain paths are not supported on the current version of the
configuration file, even though they were supported on previous
versions.
ACTION: None necessary. You may want to verify which paths have
been deleted.
NMMGRVERERR
18
MESSAGE: File type has not been defined. (NMMGRVERERR 18)
CAUSE: Internal error. User entered valid data but it somehow has been
corrupted. The type of the file passed to NMMGRVER is not within the
valid range of: 1= MPE V NSCONF type; 2= MPE V NMCONF type.
ACTION: Run NMMGRVER again. If the error still occurs, submit a
Change Request. See “Submitting a CR” at the beginning of this
appendix.
NMMGRVER
ERR 19
MESSAGE: Unable to create LINK subtree (NMMGRERR 19)
CAUSE: You specified that the configuration file was an MPE V file.
Therefore, NMMGRVER checked to make sure the LINK subtree did
not exist. Since it did not exist, NM tried to create it because iX
configuration files need it. However, the NM intrinsic failed during this
process. One possible reason for this is that the configuration file may
be full.
ACTION: Run NMMGRVER again. If the error still occurs, submit a
Service ReRun NMMGR and expand the size of the configuration file.
Then run NMMGRVER again.