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

Appendix A 275
NMS Error Messages
NMMGRVER Messages, Errors and Warnings
MESSAGE:
Invalid path found in source file.
Path: !
(NMMGRVERERR 75)
NMMGRVERERR
75
CAUSE: An invalid path was found in the source configuration file. The
path may have been created by an unofficial NMMGR tool. Conversion
will continue if possible. NMMGRVERERR 76 will usually be displayed
along with this message.
ACTION: Note that the configuration file may have been changed.
Depending on which subsystem is involved, the invalid path may or
may not be deleted from the converted file. Restore a backup copy of the
configuration file if possible and run NMMGRVER again. If the error
still occurs, submit a Service Request. See “Submitting an SR” at the
beginning of this appendix.
MESSAGE: Attempting to continue conversion. (NMMGRVERERR 76)
NMMGRVERERR
76
CAUSE: This is used to inform the user that NMMGRVER is continuing
the conversion process.
ACTION: None.
MESSAGE: The default NS LINK physical path is 6/4.2; User
modification may be needed. (NMMGRVERERR 77)
NMMGRVERERR
77
CAUSE: The default physical path has been set to 6/4.2.
ACTION: Confirm that this value is correct for your system and modify
it with NMMGR if needed.
MESSAGE: The default DTS LINK physical path is 2/4.2; User
modification may be needed. (NMMGRVERERR 78)
NMMGRVERERR
78
CAUSE: The default physical path has been set to 2/4.2.
ACTION: Confirm that this value is correct for your system and modify
it with NMMGR if needed.
MESSAGE: An error has occurred during LINKCONF CONVERSION.
(NMMGRVERERR 80)
NMMGRVERERR
80
CAUSE: An error occurred during the LINKCONF part of the
conversion process. The actual error is listed in an error message which
should be displayed along with this one.
ACTION: Restore a backup copy of the configuration file if possible. Use
the version of NMMGR that created the configuration file to make sure
that each data screen in the configuration file has data associated with
it and that its data flag is set to Y. Run NMMGRVER again. If the same
error occurs again, check any accompanying error message and take the
action listed for it in this appendix. If this fails, submit a Service
Request. See “Submitting an SR” at the beginning of this appendix.