HP 3000 Manuals HP 3000 Manuals
Running NMMAINT To run NMMAINT, enter the command: :RUN NMMAINT.PUB.SYS NMMAINT responds with the following: NMS Maintenance Utility 32099-11018v.uu.ff (C) Hewlett Packard Co. 1985 NMMAINT then lists the version identification numbers for each software module and information for each subsystem. As shown in the example below, the NMMAINT utility displays version information for the subsystems of the products actually installed on your system. The node management services, link services, and network transport subsystems are displayed if an NS3000/iX link product is installed. The Network Services subsystem is displayed if the NS3000/iX services product is installed. The SNA Transport, SNA NRJE, RJE, SNA DHCF, APPC, HP SNADS, SNA/X.25, NS Over SNA, HP SNADS, and SNA IMF subsystems are displayed if the appropriate HP-to-IBM data communications products are installed on your system. NMMAINT Output This example of NMMAINT output shows a system with NS3000/iX services and an IEEE802.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: SL procedure: NMVERS00 Version: B0008037 SL procedure: NMVERSCSL Version: B0008039 SL procedure: NMVERS01 Version: B0008008 SL procedure: NMLOGSLVERS Version: B0008034 SL procedure: NMLOGDATAVERS Version: B0008023 SL procedure: NMVERS04 Version: B0008011 SL procedure: NMWRITEVERS Version: B0008013 CM program file: NMMAINT.PUB.SYS Version: B0008011 CM program file: NMFILE.PUB.SYS Version: B0008009 CM program file: NMTRCMON.PUB.SYS Version: B0008062 NM program file: NMLOGMON.PUB.SYS Version: B0008021 NM program file: NMCONSOL.PUB.SYS Version: B0008019 CM program file: NMINIT.PUB.SYS Version: B0008006 CM program file: NMDUMP.PUB.SYS Version: B0008064 Catalog file: NMCAT.PUB.SYS Version: B0008035 NM program file: NMLOGICS.PUB.SYS Version: B0008005 SL procedure: SUBSYS0FMTVERS Version: B0008013 SL procedure: NMINTERVERS Version: B0008003 SL procedure: BFM'MOD'54'VERS Version: B0008009 NL procedure: BMGR_MOD_51_VERS Version: B0008067 NL procedure: BMGR_MOD_52_VERS Version: B0008070 NL procedure: BMGR_MOD_53_VERS Version: B0008028 NL procedure: NMVERS30 Version: B0008010 NL procedure: NMVERS33 Version: B0008018 NL procedure: NMVERS34 Version: B0008024 NL procedure: NMVERS32 Version: B0008018 Node Management Services 32098-20014 overall version = B.00.08 Network Transport 32098-20023 module versions: NM program file: NETCP.NET.SYS Version: B0507013 NL procedure: NET_CF_VERS Version: B0507006 NL procedure: NET_IPC_VERS Version: B0507014 NL procedure: NET_IPC_VERS2 Version: B0507013 NL procedure: NET_IPC_VERS3 Version: B0507012 NL procedure: NET_IPC_VERS4 Version: B0507011 NL procedure: PIVERS Version: B0507010 NL procedure: SIVERS Version: B0507009 Catalog file: SOCKCAT.NET.SYS Version: B0507000 CM program file: SOCKREG.NET.SYS Version: B0507001 NL procedure: NWTMVERS Version: B0507011 NL procedure: TI_T1_VERS Version: B0507004 NM program file: PT2PNSTN.NET.SYS Version: B0507004 Catalog file: NETMSG.NET.SYS Version: B0507003 SL procedure: NET'UI'VERS Version: B0507004 SL procedure: NET'SL'VERS Version: B0507002 NL procedure: NET_NI_VERS Version: B0507008 SL procedure: NET'PROBE'VERS Version: B0507001 NL procedure: NET_ARP_VERS Version: B0507015 SL procedure: NET'DIAL'VERS Version: B0507000 NM program file: TCPSIP.NET.SYS Version: B0507000 SL procedure: NET'STUB'VERS Version: B0507001 NL procedure: NET_TCP_VERS Version: B0507062 NL procedure: NET_UDP_VERS Version: B0507012 NL procedure: NET_DICT_VERS Version: B0507001 SL procedure: NET'PXP0'VERS Version: B0507001 SL procedure: NET'PXP1'VERS Version: B0507000 NL procedure: NET_IP_VERS Version: B0507007 SL procedure: NET'IPU'VERS Version: B0507000 NL procedure: NET_X25_VERS Version: B0507002 SL procedure: NET'PD'VERS Version: B0507100 NL procedure: NET_PD_VERS Version: B0507002 NL procedure: NET_MAP_VERS Version: B0507008 NL procedure: NET_GLBL_VERS Version: B0507013 NL procedure: NET_REG_VERS Version: B0507001 SL procedure: NET'REG'CM'VERS Version: B0507001 SL procedure: DCLDM_FMT_VERS Version: B0507001 NL procedure: DCLDM_PS_VERS Version: B0507002 NL procedure: DCLDM_CONF_VERS Version: B0507002 NL procedure: NSLOPENLINK_VERS Version: B0507004 NL procedure: RLM_SERVER_VERS Version: B0507000 NL procedure: RLM_CONFIG_VERS Version: B0507000 NL procedure: RLM_LOAD_TABLE_VERS Version: B0507000 SL procedure: RLM_FMT_VERS Version: B0507000 NL procedure: NET_FC_VERS Version: B0507000 SL procedure: SOCKIOVERS Version: B0507000 SL procedure: SOCKACCESSVERS Version: B0507000 SL procedure: SOCKMISC1VERS Version: B0507002 SL procedure: SUBSYS3FMTVERS Version: B0507006 SL procedure: SUBSYS5FMTVERS Version: B0507001 NL procedure: LEVEL2_RESOLVE_VERS Version: B0507001 NM program file: ICMPSERV.NET.SYS Version: B0507001 NM program file: NETTOOL.NET.SYS Version: B0507012 NL procedure: NETTMRVERS Version: B0507000 Network Transport 32098-20033 overall version = B.05.07 Network Services individual module versions: NM Program: DSDAD.NET.SYS Version: B0010007 SL procedure: ASCXVERS Version: B0010008 SL procedure: ASBUFVERS Version: B0010000 SL procedure: ASENVVERS Version: B0010005 SL procedure: DSUTILVERS Version: B0010007 SL procedure: SUBSYS6FMTVERS Version: B0010001 Catalog file: ASCAT.NET.SYS Version: B0010001 SL procedure: VTSRVTVER Version: B0010000 NL procedure: VTS_LDMVER Version: B0010005 NL procedure: VTS_UTILVER Version: B0010005 CM Program: LOOPBACK.NET.SYS Version: B0010000 CM Program: LOOPINIT.NET.SYS Version: B0010000 CM Program: NSSTATUS.NET.SYS Version: B0010002 NL procedure: NSSTATUSNMVERS Version: B0010001 NL procedure: NSINFONMVERS Version: B0010002 CM Program: CONFPROG.NET.SYS Version: B0010000 CM Program: MASTMAKE.NET.SYS Version: B0010000 NL procedure: VTS_SMVER Version: B0010005 NL procedure: NSUTILNMVERS Version: B0010001 NL procedure: ASCXNMVERS Version: B0010001 NL procedure: ASENVNMVERS Version: B0010001 NM Program: RASERVER.NET.SYS Version: B0010003 NM Program: VTSERVER.NET.SYS Version: B0010005 CM Program: DSSERVER.NET.SYS Version: B0010000 SL procedure: ASRFAVERS Version: B0010002 SL procedure: ASPTOPVERS Version: B0010001 CM Program: NFT.NET.SYS Version: B0010018 NL procedure: NFTNMVERS Version: B0010001 Catalog file: NFTCAT2.NET.SYS Version: B0010002 SL procedure: ASRPMVERS Version: B0010001 NL procedure: RPMNMVERS Version: B0010001 CM Program: RPMDAD.NET.SYS Version: B0010003 NL procedure: RFANMVERS Version: B0010001 Network Services overall subsystem version: B.00.10 Link Support Services 32098-20015 module versions: NL procedure: TRACE_INT_VERS Version: C0104016 NM program file: TRACEMGR.PUB.SYS Version: C0104039 NL procedure: TVPGEN00VERS Version: C0104007 SL procedure: SUBSYS18FMTVERS Version: C0104008 XL procedure: LSSLINKCONTROLVERS Version: C0104145 XL procedure: LSSLINKCONTROLVERS01 Version: C0104014 NL procedure: LSSLKTBLVERS Version: C0104008 SL procedure: LSSVERS00 Version: C0104012 NL procedure: DCC_VERSION Version: C0104506 NL procedure: DCC_VALID Version: C0104503 Link Support Services 32098-20015 overall version = C.01.04 Node Management Configurator 32098-20016 module versions: SL procedure: NMCVERS Version: B0407000 SL procedure: NMVERS06 Version: B0407000 SL procedure: NETDIRVERS Version: B0407000 NL procedure: NMNETDIRVERS Version: B0407002 NM program file: NMMGR.PUB.SYS Version: B0407035 CM program file: NMMGRVER.PUB.SYS Version: B0407003 CM program file: NMMGRVAL.PUB.SYS Version: B0407000 CM program file: NMSIG.PUB.SYS Version: B0407000 V+ forms file: NMMGRF.PUB.SYS Version: B0407026 Catalog file: NMMGRCAT.PUB.SYS Version: B0407012 Catalog file: NMMGRHLP.PUB.SYS Version: B0407013 NM conf file: NMSAMP1.PUB.SYS Version: B0407004 NM conf file: NMAUX1 Version: B0407014 NM conf file: NMNOVA.PUB.SYS Version: B0407003 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.