Running NMMAINT

NMMAINT Output

This example of NMMAINT output shows a system with NS 3000/iX services and an IEEE 802.3 link installed. (The IPCVERSION module is port software. This is not part of the NetworkIPC user service, nor does it form a subsystem, but its individual version ID number is displayed by NMMAINT for your information.)

Notice that version ID numbers include version, update, fix levels, and an internal fix level in the format vuuffiii. For NMVERS00, the version ID number is A0103023. A is the version level, the next two digits represent the update level, and the next two digits are the fix level. The remaining numbers, 023, show the internal fix level, which is used only within Hewlett-Packard.

	NOTE: The version numbers shown in this example are not intended to be the same as the version numbers of your software.

Example

:RUN   NMMAINT.PUB.SYS

NMS Maintenance Utility 32098-20014B.00.08   (C) Hewlett Packard Co. Subsystem version ID's

Node Management Services 32098-20014 module versions:

Node Management Services 32098-20014 overall version = B.00.08

@COMPUTERTEXTW = Network Transport 32098-20023 module versions:

Network Transport 32098-20033 overall version = B.05.07

Network Services individual module versions:

Network Services overall subsystem version:   B.00.10

Link Support Services 32098-20015 module versions:

XL procedure: Version:  C0104014NL procedure: Version:  C0104008SL procedure: Version:  C0104012NL procedure: Version:  C0104506NL procedure: Version:  C0104503

Link Support Services 32098-20015 overall version = C.01.04

Node Management Configurator 32098-20016 module versions:

Node Management Configurator 32098-20015 overall version = B.04.00

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 A.01.03. 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 port software module are correct. It is possible for the HP-to-IBM products to use previous versions of the common software that are not compatible with the HP-to-HP products.

NMMAINT displays information on only the subsystems for the products installed on your system. In the example above, none of the HP-IBM products were installed, so their subsystems were not displayed.

Running NMMAINT With Subsystem ID

NMMAINT can also be executed to display the version information for just one subsystem, by entering a command: NMMAINT, Subsystem number, where the subsystem number can be obtained from running NMDUMP.

For example, NMMAINT,3 displays the version information for Network Transport 32098-20033.

The only exception for using the subsystem number found from running NMDUMP is for the NMS, Node Management Services, which would be 0. Use NMMAINT, 10000 to display NMS version information.