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

Appendix A 267
NMS Error Messages
NMMGRVER Messages, Errors and Warnings
ACTION: Purge unnecessary files from disk to recover some space.
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.
CAUSE: An internal error occurred with intrinsics, midasgetdata,
midasnextpath, midasupdatedata, or midasaddpath.
ACTION: The configuration file may be corrupted. 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.
CAUSE: An unexpected internal error has occurred.
ACTION: 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: CLOSE FILE ERROR: File may have been changed.
(NMMGRVERERR 6).
NMMGRVERERR
6
CAUSE: An internal NMMGRVER error has occurred when attempting
to close the configuration file.
ACTION: Note that the configuration file may have been changed.
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: User has Insufficient Capability to Run NMMGRVER.
(NMMGRVERWARN 7)
NMMGRVER
WARN 7
CAUSE: The user is required to have NM or NA capability to run
NMMGRVER. However, the current user does not have sufficient
capability.
ACTION: Check user capability with program LISTDIR5.PUB.SYS,
and modify the capability list. Contact the account manager or system
manager, if needed.
MESSAGE: ACCESS VIOLATION: Cannot convert file.
(NMMGRVERWARN 8)
NMMGRVER
WARN 8
CAUSE: NMMGRVER was unable to write (update or add data) to the
existing configuration file due to inconsistent access type (FSERR 40).
Usually occurs when updating a file across account boundary. The
WRITE, SAVE access types of the GROUP or ACCOUNT for this
configuration file are limited to ACCOUNT only. The file is SECURED.
NOTE: The configuration file is not changed.
ACTION: Release file security and rerun NMMGRVER, or run NMMGRVER
in the GROUP and ACCOUNT where the configuration file is stored.