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

146 Chapter6
NMMAINT
Running NMMAINT
Explanation of NMMAINT Output
The first group of numbers in the above example are the version ID
numbers of the modules of the Node Management Services subsystem.
Notice that the first five characters of the version for each module listed
in this group are the same. This means that all the software modules in
the subsystem match. It is necessary for all the modules of a given
subsystem to be the same version. If a subsystem module does not
match, NMMAINT prints the following error message:
Program file: NMMAINT.PUB.SYS ** MODULE ERROR **
ONE OR MORE SUBSYSTEM MODULES ARE INVALID. (NMERR 105)
This message indicates that the modules of the subsystem are not
compatible.
Because the module version ID numbers match, NMMAINT displays
the overall subsystem version number for the node management
services; for the above example, it is B.00.10. The rest of the
subsystems are handled in a similar fashion.
NMMAINT also checks that all the modules that belong with a
particular subsystem are present. If a module is missing, NMMAINT
displays the name of the module with the following error message in
place of the version number.
SL procedure: NMVERS01 ** REQ’D MODULE MISSING **
ONE OR MORE REQUIRED SUBSYSTEM MODULES ARE MISSING. (NMERR 104)
If an optional module is not present, NMMAINT displays a message
similar to the following:
Program file: NMDUMP.PUB.SYS **NOT INSTALLED**
If the modules were correct when installed, only unusual circumstances
such as a reload, a disk problem, or a system failure would result in
missing or invalid modules. Restore a known valid version of the
modules in error.
Question marks displayed for the overall version number indicate that
the fix levels of the individual modules do not match. Remember that
the internal fix level, represented by the last three numbers of the
version ID, does not need to match between modules for the software to
be compatible. Fix numbers are requested in service requests for HP to
use when troubleshooting.
As each subsystem is displayed, NMMAINT checks that all the modules
are present and compatible. However, NMMAINT does not perform any
cross-subsystem version verification. When a system has HP-to-IBM
products as well as HP-to-HP products installed, the Node
Management Services, link services and the port software are used by
both types of data communications products. Therefore, it is important
to check that the version numbers of these common subsystems and