Using the Node Management Services (NMS) Utilities HP e3000 MPE/iX Computer Systems Edition 8 Manufacturing Part Number: 32022-90054 E0801 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction NMMGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Entering Help Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Getting Help on Specific Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Getting Help with Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Error Information Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Maintenance Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 ADDCONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 ADDLDEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 ADDLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6. NMMAINT Software Version ID Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 Getting Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Running NMMAINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 NMMAINT Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 2-1. Common Screen Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Figure 2-2. Error Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Figure 3-1. Open Configuration/Directory File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Figure 3-2. Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Figure 3-3.
Figures 8
Tables Table 2-1. NMMGR Screen Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 5-1. NMMGR Maintenance Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Table 7-1. General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Table 7-2. Log Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Table 7-3. X.
Tables 10
Preface This is the reference manual for users of the Node Management Services Utilities. These utilities are: • The Node Management Services Configuration Manager (NMMGR). • The Node Management Maintenance Utility (NMMAINT). • The Node Management Services Trace/Log File Analyzer (NMDUMP). • The Node Management Services Conversion Utility (NMMGRVER). • The Node Management Services Validation Utility (NMMGRVAL). The major part of this manual covers the NMMGR program.
Special Note MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP e3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX.
Related Publications The following manuals may be of interest to you when working with products that use the Node Management Services.
1 Introduction This chapter introduces you to the Node Management Services Utilities for MPE/iX systems. These programs, installed on your HP e3000 system as part of the fundamental operating system (FOS), allow you to perform various functions related to the configuration of networking and terminal communications.
Introduction NMMGR NMMGR The Node Management Configuration Manager (NMMGR) is the utility used to create or update configuration and network directory files. These files define the configuration for terminal and serial printer connections and networked connections for HP e3000 computers.
Introduction NMMGR product-specific manuals for details on changes that can be made online. Backup Configuration File Specify a backup configuration file name whenever you open or create a configuration file. The default backup configuration file name is NMCBACK.group.account, where group and account are the logon group and account. Change the name of the file by typing a new name in place of the default. The backup file also has the file type NCONF.
Introduction NMMGR Operating Modes NMMGR includes two interfaces thatcan be used to enter or modify data: • The screen interface, a VPLUS block-mode interface, presents a series of screens that you can use to display or modify existing configuration data or enter new data. When using this interface, you are operating NMMGR in screen mode. • The maintenance interface, a character interface, is used primarily from within batch jobs to update configuration data.
Introduction NMMAINT NMMAINT The Node Management Services Maintenance Utility (NMMAINT), lists individual modules and version numbers of the NS and SNA links and services installed on the HP e3000 system on which it is run. Each software module within a subsystem has its own version ID number. If the version, update, and fix levels of these modules do not match, the subsystem will not work correctly. NMMAINT helps diagnose system problems by detecting missing or invalid software modules.
Introduction NMDUMP NMDUMP The Node Management Services Trace/Log File Analyzer (NMDUMP) is the NMS utility that you use to format files created by the logging and tracing facilities. NMDUMP translates the log and trace files into a format that is easier to read. Logging and tracing are diagnostic and debugging services provided by NMS. Tracing Tracing records subsystem calls and/or the sequences of module execution. Tracing is provided at both the user level and at an internal level.
Introduction NMMGRVER NMMGRVER The Node Management Services Conversion Utility (NMMGRVER) is a program that converts configuration files created with NMMGR from an earlier version to the latest format. NMMGRVER helps provide a migration path for configuration files developed using one version of the software so that you can more easily move to a later version.
Introduction NMMGRVAL NMMGRVAL This utility checks to see if the configuration file has been validated. It can be included in a shutdown UDC or command script to check whether the DTC subsystem has been validated before attempting to shut down the system.
2 Basics of NMMGR This chapter describes the basic functions of the Node Management Configuration Manager (NMMGR) in detail. Use this chapter to gain an understanding of how the utility works and how to navigate through NMMGR screens. The following topics are discussed: • NMMGR screens, including a discussion of common screen elements and function keys. • Moving between screens in NMMGR.
Basics of NMMGR NMMGR Screens NMMGR Screens Each NMMGR screen may have multiple purposes. Some screens provide menus of items for selecting a subbranch of screens that you will be moving through. Some screens present a selection of configured items and allow you to either choose items you want to modify or add new items to the list. Still other NMMGR screens allow you to enter data to define configuration values for a selected item.
Basics of NMMGR Common Screen Elements Common Screen Elements The screen shown in Figure 2-1 illustrates the common elements found in NMMGR screens. Each of these elements are described here. Figure 2-1 Common Screen Elements Header The screen header is located at the top of the screen (the top three lines), and contains five elements, each of which is described here.
Basics of NMMGR Common Screen Elements Screen Number and Title To the right of the program name and version number is the screen number followed by the screen title. Each screen number is unique for that screen. There is no significance to the order of the numbers. They are strictly for convenience in referencing information about a screen in various reference documents. Screen titles are also unique for each screen and will generally indicate the purpose and content of the screen.
Basics of NMMGR Common Screen Elements entering only the portion to the left of the bracket as shown in the table. • MPE commands. • NMMGR path commands. Direct path branching and brother branching are described in this chapter. To enter a command, position the cursor at the Command: window by pressing the [Home] key (the key on your terminal with the diagonal arrow or the word “Home” on it). You can also use the [TAB] or cursor (arrow) keys to move the cursor to the command window.
Basics of NMMGR Common Screen Elements Table 2-1 NMMGR Screen Mode Commands NMMGR Command Action NET[DIR](NS Only) Transfers to the Network Directory Main screen. (You must already have opened the network directory file.) Refer to the NS manuals for more information. NEX[T] Transfers to a brother screen. (See “Branching” in this chapter.) NIG[UIDE] (NS Only) Transfers to the Guided HP Configuration screen. Refer to the NS manuals for more information.
Basics of NMMGR Common Screen Elements Data Fields and Menu Choices Data can be entered only into unprotected fields. For screens with more than one unprotected field, the cursor automatically moves to the next unprotected field when you reach the end of the present field or if you press [TAB]. Generally, the [TAB] key is used to step through the fields from the top of the screen to the bottom. If you need to back up to a previous field, use the [SHIFT][TAB] key combination.
Basics of NMMGR Common Screen Elements Prior Screen Key Except for a limited number of screens, such as the Error Information screen and the Guided Configuration screen, the [Prior Screen] key is the right-most function key, [f8]. With a few exceptions (as listed), the screen displayed when [Prior Screen] is pressed will always be the screen most recently visited prior to the current screen, regardless of the manner in which you reached the current screen.
Basics of NMMGR Common Screen Elements “Go To” Keys Some keys take you to a specific screen. There may be one or more keys on the screen that tell NMMGR to “go to” a new screen. For example, the [Go to OUTPUT] key on the Utility screen takes you directly to the Output Configuration File screen. Next Page/Prev Page Keys Some NMMGR screens contain data or display sets of items that will not fit in a single screen. When this occurs, the screen data is continued on one or more “pages”.
Basics of NMMGR Entering Data Entering Data Enter data into NMMGR by typing the appropriate information in the data entry fields on a screen and pressing the [Save Data] key. (The [ENTER] key can be used, if the command window is blank.) This causes the data in the fields to be included in the configuration file, as a data record. NMMGR confirms that you have updated the configuration file by printing the following message in the message field: Configuration data updated.
Basics of NMMGR Moving Between Screens Moving Between Screens There are two ways to move from one NMMGR screen to another. One way is to use the function keys present on one screen to select and move to another screen in a progression. The second way is to enter a path name in the command window to move directly to a specified screen.
Basics of NMMGR Moving Between Screens NETXPORT.GPROT, and NETXPORT.NI. These three screens are brothers. To transfer directly from one of these screens to its brother without going back through the parent screen you would simply type NEXT in the command window and press [ENTER]. The command would look like this: Command: NEXT The screens are visited in the order their names appear on the parent screen. Typing NEXT in the command window will transfer you to the next brother as long as one exists.
Basics of NMMGR Getting Help Getting Help Help is available for many of the NMMGR screens you will be using. It is available for all unguided NS configuration screens. It is also available for the screens used to configure the distributed terminal subsystem and those used for guided NS configuration. You can also get help on general topics and NMMGR commands.
Basics of NMMGR Getting Help keywords. For example, if you wanted to see a map of LINKCONF screens, you would enter HELP ROADMAP,LINKCONF in the command window. Every screen name shown in these screen maps is also a keyword and can be used with the HELP command and the FIELDS qualifier. For example, if you wanted to see field descriptions for the screen called LAN, you would enter HELP LAN,FIELDS in the command window.
Basics of NMMGR Getting Help with Errors Getting Help with Errors When NMMGR encounters an error, it displays a brief message in the message field of the current screen. In most cases, these messages provide enough information for you to correct the error and continue operation. Occasionally, however, you may encounter a more serious error or the cause of an error may not be readily apparent. You may then need additional information to understand the cause of the error.
Basics of NMMGR Getting Help with Errors Figure 2-2 Error Information Screen NMMGR Error Messages Error messages associated with the NMMGR program are listed in Appendix A , “NMS Error Messages,” of this manual. Each error message is listed with at least one possible cause and a recommended action for each cause. You also may need to refer to the MPE file system and operating system manuals for explanations of any MPE error messages that may appear on the Error Information screen.
3 Using NMMGR in Screen Mode This chapter tells you how to use NMMGR’s screen mode interface to begin the configuration process for your system’s terminal connections or networking products. It includes step-by-step instructions for getting started in NMMGR and for navigating the top-level screens. Those screens are described here along with their purpose. This chapter describes the following topics in detail: • What you need before you start NMMGR. • How to start NMMGR in screen mode.
Using NMMGR in Screen Mode Before You Start Before You Start There are a number of requirements that you need to be aware of before you attempt to run NMMGR: • You must have MPE Node Manager (NM) or Network Administrator (NA) capability to run NMMGR. • Your terminal must have block mode capability to run NMMGR in screen mode. All terminals supported by MPE/iX have this capability. • An NMMGR screen is 24 lines long.
Using NMMGR in Screen Mode Starting NMMGR Starting NMMGR To start NMMGR’s screen mode interface, enter the following command at the MPE prompt: :RUN NMMGR.PUB.SYS After MPE accepts the run command, NMMGR displays the following banner: NM Configuration Manager 32098-20016 V.uu.ff (C) Hewlett Packard Co. 1994 NMMGR then clears the terminal screen and displays the Open Configuration/Directory File screen.
Using NMMGR in Screen Mode Opening a Configuration or Directory File Opening a Configuration or Directory File The Open Configuration/Directory File screen shown in Figure 3-1 is the first screen you see when you start NMMGR in screen mode.
Using NMMGR in Screen Mode Opening a Configuration or Directory File The name must be a valid MPE file name. If you do not specify a group or account, NMMGR will qualify the file name with your logon group and account. The default file name is NMCONFIG.PUB.SYS. You may use the default if no NMCONFIG.PUB.SYS file currently exists. Step 2. If a write access password has been assigned, you must enter the password in the Write access password field in order to create a new file.
Using NMMGR in Screen Mode Opening a Configuration or Directory File 4. When you are ready to proceed with configuration, run NMMGR and open the configuration file you just created. Refer to the instructions for “Opening a Configuration File.” You may choose to copy your source file to a name other than NMCONFIG.PUB.SYS first, modify that file using NMMGR, then rename the file as NMCONFIG.PUB.SYS when you are ready for it to be used by the system.
Using NMMGR in Screen Mode Opening a Configuration or Directory File Creating a Network Directory File If you want to create a new network directory file (one that does not exist), follow these steps. At the Open Configuration/Directory File screen: Step 1. Enter the name of the file you want to create in the Network directory file name field. The name must be a valid MPE file name. If you do not specify a group or account, NMMGR will qualify the file name with your logon group and account.
Using NMMGR in Screen Mode Selecting a Configuration Path Selecting a Configuration Path Once a configuration file is successfully opened or created, NMMGR displays the Main screen, shown in Figure 3-2. This screen presents a menu from which you select the group of NMMGR screens you need to configure the appropriate subsystem.
Using NMMGR in Screen Mode Selecting a Configuration Path Step 4. Press the [Save Data] key to save the node name in the configuration file (create the data record). The Data flag will be set to “Y” when the data record exists. Step 5. Proceed to one of the NMMGR configuration subbranches by pressing the appropriate function key. Each of the configuration subbranches are described.
Using NMMGR in Screen Mode Selecting a Configuration Path You will perform a number of tasks using these screens, including the following: • Define the DTS link configuration for the system. • Define connection capabilities for terminals, printers, and other serial devices that will be able to communicate with the system.
Using NMMGR in Screen Mode Selecting a Configuration Path Figure 3-4 NS Configuration Screen NMMGR provides two methods of creating or updating configuration information for an NS link. The methods are referred to as Guided Configuration and Unguided Configuration respectively. You determine which method you will use by making a choice at the NS Configuration screen. You also use this screen to configure a domain name for the node you are configuring if using domain names for network access.
Using NMMGR in Screen Mode Selecting a Configuration Path Guided Configuration If you press the key labeled [Guided Config] at the NS Configuration screen, you will be taken to the Network Transport Configuration screen shown in Figure 3-5. From this screen, you choose the specific task you want to perform using guided NS configuration. These tasks include configuring or modifying a network interface, modifying logging parameters, and fine tuning global or network transport configuration parameters.
Using NMMGR in Screen Mode Selecting a Configuration Path Unguided Configuration If you press the key labeled [Unguided Config] at the NS Configuration screen (#166), you will be taken to the Unguided Configuration screen shown in Figure 3-6. Figure 3-6 Unguided Configuration Screen From this screen, you can move to the screens that let you: • Configure or modify a network interface. • Configure or modify an NS link. • Configure or modify logging parameters. • Configure or modify a network interface.
Using NMMGR in Screen Mode Selecting a Configuration Path Configuring HP-IBM Connections Hewlett-Packard provides a number of networking products that make it possible to establish communication links between HP e3000 and IBM mainframe computers. If you press the key labeled [IBM] at the Main screen, you are sent to the HP-IBM Configuration screen shown in Figure 3-7.
4 Using NMMGR Utility Screens This chapter describes how to use the NMMGR utility screens to list, maintain, and validate configuration files. The following topics are discussed in detail: • Displaying or printing the configuration file tree structure or the data screens associated with a configuration file using the Output screen. • Compressing or expanding a configuration file using the Compress screen. • Validating a configuration file using the Validate screen.
Using NMMGR Utility Screens The Utility Screen The Utility Screen The Utility screen shown in Figure 4-1 lets you select the utility function that you want to perform. To display the Utility screen, press [Go To Utility] from the Main screen or type UTILITY in the command window of any screen and press [ENTER]. Figure 4-1 Utility Screen Select the utility function you want to perform and press the corresponding function key.
Using NMMGR Utility Screens Output Configuration File Screen Output Configuration File Screen The Output Configuration File screen shown in Figure 4-2 allows you to list or print the configuration file tree structure, to print the NMMGR data screens associated with a configuration file, and to print a critical summary of the configuration file data. You reach this screen by pressing [Go To OUTPUT] at the Utility screen.
Using NMMGR Utility Screens Output Configuration File Screen Display Tree If you press the [Display Tree] key, NMMGR will display the tree structure of the configuration file at your terminal. Figure 4-3 shows a section of a listing obtained by pressing [Display Tree] at the Output Configuration File screen. The tree structure shows the identifiers for each screen that contains configured data but does not show any of the actual data that is configured.
Using NMMGR Utility Screens Output Configuration File Screen Figure 4-3 Display Tree Listing NM Configuration Manager 32022-20016 V.uu.ff (C) Hewlett Packard Co. 1990 MON, APR 9, 1990, 3:48 PM CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS [1] [2] [2] [1] . . . [1] [2] [2] [1] . . . [1] [2] [2] [1] [1] [1] [1] [1] [1] [2] [3] [3] [2] [3] [3] [4] [5] [5] [5] [4] [5] .
Using NMMGR Utility Screens Output Configuration File Screen Configuration File screen. These are four data entry fields that allow you to enter a number corresponding to the configurable subsystems, as listed on the screen (see Figure 4-2). For example, to obtain a printed listing of the configured screens for both logging and for NETXPORT configuration, enter a 2 (for logging) in one of the fields and a 3 (for NETXPORT) in another of the fields.
Using NMMGR Utility Screens Output Configuration File Screen to the right of “Print Summary” and press the [Print Summary] key. (The numbers for the subsystems are the same as those that you would use to select subsystems for the [Print Data] key.) The example shown in Figure 4-5 is the first part of a critical summary for a full-gateway node that has been configured with a point-to-point (router) network interface (NI) and a LAN NI.
Using NMMGR Utility Screens Compress Screen Compress Screen The Compress screen shown in Figure 4-6 allows you to compress or expand the configuration file. To perform these functions, you must be the creator of the file. (You can also use the COMPRESSCONF maintenance mode command to perform these functions. See Chapter 5 , “Using NMMGR in Maintenance Mode,” for more information on maintenance mode commands.) You reach this screen by pressing the [Go To Compress] key at the Utility screen.
Using NMMGR Utility Screens Compress Screen Description As your configuration grows, you may find it necessary to compress or expand your configuration file. Configuration files initially contain 2,048 32-byte records. As you configure items in a file, records are used sequentially from the beginning of the file. As the file size increases, the number of free records at the end of the file decreases.
Using NMMGR Utility Screens Compress Screen Number of Additional Records Enter the number of records that you want to add to the file (positive integer) or the number of unused records that you want to delete from the file (negative integer). To simply compress the file, enter 0 (zero). If you are adding records, the file cannot end up containing more than 65,535 records.
Using NMMGR Utility Screens Validate Configuration File Screen Validate Configuration File Screen The Validate Configuration File screen shown in Figure 4-7 allows you to test the validity of a specified subsystem configuration. (The VALIDATECONF maintenance mode command can be used to perform this function. See Chapter 5 , “Using NMMGR in Maintenance Mode,” for more information on the maintenance mode commands.) This screen can be reached by pressing the [Go To VALIDATE] key at the Utility screen.
Using NMMGR Utility Screens Validate Configuration File Screen configuration, the validation process creates a listing of error messages to help you pinpoint invalid items. One possible message, for instance, states that a phone number has not been configured for a dial-type link in your NS configuration. When you press one of the validation function keys, you enter character mode. Any validation error messages are listed at your terminal.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Configuration Subtree Copy Screen The Configuration Subtree Copy screen in Figure 4-8 allows you to copy specified parts of a configuration subtree into either the same configuration file or a different configuration file. This feature can save you a lot of time when you are configuring multiple nodes or subsystems in the same way. Note that the source or target file can be on a remote node in the network.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Description Use the Configuration Subtree Copy screen to copy a contiguous set of screens called a subtree from one configuration file to another or within the same configuration file. To copy a subtree, enter the name of the source file and path and the destination file and path in the fields provided and press the [Subtree Copy] key. The source file is the name of the file that the data will be copied from.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Destination file This field contains the name of the file the configuration data will be copied to. If this field is left blank, the current configuration file is assumed. If the file is on a remote node, you must use a file equation and prefix the file name with an asterisk (*). Destination path Like the source path, the destination path is composed of eight path identifiers.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Figure 4-9 Specified Subtree SOURCE: before and after copy (node A) NETXPORT NI LAN1 LINK INTERNET LINKABC GATE 1 GATE 2 For this copy, the destination file and path were specified as: Destination file: Destination path: . . [*CONFIG . ] .LAN2 . <~> . . The diagram in Figure 4-10 illustrates the results of the copy.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Figure 4-10 Results of Copy SOURCE: before copy (node B) SOURCE: after copy (node B) NETXPORT NETXPORT NI NI LAN1 LAN1 LINK INTERNET LINKABC LINK INTERNET LINKABC GATE 1 NOTE GATE 2 When subtrees contain several records, copies that occur over DSLINE connections will take considerably longer than copies between two local configuration files.
Using NMMGR Utility Screens Configuration Subtree Copy Screen 70 Chapter 4
5 Using NMMGR in Maintenance Mode This chapter tells you how to use NMMGR’s maintenance mode interface to manage network directory and configuration files. It allows you to also generate stream jobs to update remote network directory and configuration files. It includes descriptions of the following: • Entering NMMGR maintenance mode from the screen mode interface or from a batch job. • Each of the maintenance mode commands, including: — The purpose and syntax of the command.
Using NMMGR in Maintenance Mode Using Maintenance Mode Using Maintenance Mode NMMGR’s maintenance mode is a character mode interface used to manage both network directory and configuration files. It can be used interactively, from within the screen mode interface, or as a set of commands entered via a batch job. Maintenance mode can generate a job stream to sequentially update directories on a list of NS nodes.
Using NMMGR in Maintenance Mode Using Maintenance Mode equation for the formal designator NMMGRCMD set to a command file. An example of such an equation is: :FILE NMMGRCMD=CMDFILE Command input is echoed to $STDLIST if you are running NMMGR from within a stream job or when the input is read from a command file. You can run NMMGR in the maintenance mode interactively. Enter the file equation NMMGRCMD= $STDINX.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Maintenance Mode Commands Table 5-1 lists the NMMGR maintenance mode commands and the actions they perform. Each of these commands is described in detail later in this chapter. Table 5-1 NMMGR Maintenance Mode Commands Command Action :MPECommand Executes MPECommand. MPECommand must be a programmatically executable MPE command. ADDCONF Adds subtree of empty records to the configuration file. ADDLDEV Adds LDEVs to a DTC card.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Table 5-1 NMMGR Maintenance Mode Commands Command Action MAKESTREAM Creates a job stream used to perform network directory or configuration file updates on remote nodes. MERGEDIR Merges entries from another network directory or configuration file into the current network directory. NICONF Sets up paths to add or update NETXPORT NI configurations. OPENCONF Opens a nodal configuration file and makes it the current configuration file.
Using NMMGR in Maintenance Mode Maintenance Mode Commands NOTE Subsystem break ([CTRL]Y) may be used to interrupt the operation of the COPYCONF, DELETENODE, HELP, LISTDIR, MAKESTREAM and MERGEDIR commands. The EXPANDDIR command cannot be interrupted. The VERSIONCONF command must be used before the PATHCONF command, which must be used before the READCONF, READALLCONF, WRITECONF, and UPDATECONF commands to define the current path.
Using NMMGR in Maintenance Mode ADDCONF ADDCONF Adds subtree of empty records to the configuration file. Syntax ADDCONF pathname [type] Parameters pathname The name of a path in the configuration file that describes the location of the desired subtree. It is composed of one to eight path identifiers separated by periods. The format for the pathname is: pathid.pathid.pathid... The last pathid specified must not exist in the configuration file. The second to last pathid must exist.
Using NMMGR in Maintenance Mode ADDLDEV ADDLDEV Adds LDEVs to a DTC card. Syntax {dtcname} ADDLDEV {dtc-nodename} [filename] {station-address} Parameters dtcname The NMMGR nametag for the DTC being accessed. The nametag is the last name in the pathname of the DTC. For example, the dtcname is DTC01 in the pathname DTS.DTC.SELECT.DTC01. The dtcname in a one to eight character alphanumeric string. dtc-nodename The nodename of the DTC that has been configured at the DTC nametag path.
Using NMMGR in Maintenance Mode ADDLDEV • For X.25 PAD cards: LDEV[,] cardno[,] profilename[,] device-name[,] x25address[,] [CUG] [;] All text following the number sign “#” will be interpreted as a comment. For X.25 cards the LDEV will be added to the first available line on the first available page of LDEVs shown on the PAD screen mode. See also LISTLDEV and PURGELDEV. Example NMMGR> ADDLDEV dtc01.ind.
Using NMMGR in Maintenance Mode ADDLU ADDLU Adds LUs to the SNA node transport screen. Syntax ADDLU SNAnodename [filename] Parameters SNAnodename A one to eight character alphanumeric name that identifies the SNA node to be modified. filename A text file that contains the LU name and number for each LU to be added to the configuration file. The file name’s format is: filename[.groupname[.accountname]] A file lockword may not be specified. The contents of the file must be formatted as described below.
Using NMMGR in Maintenance Mode ADDNODE ADDNODE Adds or updates a node in the current network directory. Syntax ADDNODE [filename] Parameters filename The name of a text file that contains node name and address information for each node to be added or updated in the network directory. The format for the file name is: filename[.groupname[.accountname]] A file lockword may not be specified. The contents of the file must be formatted as described here.
Using NMMGR in Maintenance Mode ADDNODE IP address The IP address of the remote node. A node may have several IP addresses, one for each path report. The format of the address is the same as the IP address in the Network Directory Data screen. It must be enclosed in quotes (“ ”) if it is not entered interactively. additional address type The numerical type associated with each type of additional address on the Network Directory Data screen.
Using NMMGR in Maintenance Mode ADDNODE (1-IP, 2-LAN/IEEE802.3, 3-X.25, 4-NS/SNA, 5-LAN/ETHERNET, (default is 1): ADDNODE> 2 Enter additional address: ADDNODE> 11-22-33-44-55-66 NODE1.XLNET.ACCTG saved.
Using NMMGR in Maintenance Mode ADDVC ADDVC Adds an X.25 virtual circuit address key to the network directory and to the configuration file. Syntax ADDVC [filename] Parameters filename The name of a text file that contains X.25 address information for each remote node to be added to the configuration file and directory. The format for the file name is: filename[.groupname[.accountname]] A file lockword may not be specified. The contents of the file must be formatted as described below.
Using NMMGR in Maintenance Mode ADDVC nodename.domain.organization Each of the three names may be from one to sixteen characters long, must begin with a letter, and may contain letters, digits, underscores, or dashes. If the nodename does not exist, it will be created. If it does exist, the IP address and additional address (if any) will be added to its path report list in the directory. IP address The IP address of the remote node whose X.25 address is to be added to the configuration.
Using NMMGR in Maintenance Mode ADDVC OU Initiate outbound connections only. LK Do not permit inbound or outbound connections (placeholder entry). circuit number The permanent virtual circuit number supplied with your network subscription or assigned by your network administrator. Example To interactively add a switched virtual circuit for the node named NODE1.XLNET.ACCTG to the NI named X25 (user input is italicized): NMMGR> OPENCONF NMCONFIG NMMGR> OPENDIR NSDIR.NET.
Using NMMGR in Maintenance Mode CARDCONF CARDCONF Sets the current DTC card number so that the correct card is displayed or updated by the READALLCONF, READCONF, UPDATECONF, and WRITECONF commands. Syntax CARDCONF cardno Parameters cardno Description CARDCONF sets the current card number for a path referencing a DTC card screen.
Using NMMGR in Maintenance Mode COMPRESSCONF COMPRESSCONF Compresses or expands the current configuration file. Syntax COMPRESSCONF numrecs Parameters numrecs Description COMPRESSCONF increases or decreases the capacity of the currently opened configuration file and regains unused but not “free” records. (You can also compress a configuration file and alter the file’s capacity using the NMMGR Compress screen in screen mode.
Using NMMGR in Maintenance Mode CONTINUE CONTINUE Prevents NMMGR from terminating in a job because of a maintenance mode error. Syntax CONTINUE [ON or OFF] Parameters ON Turn on continue so the NMMGR will not terminate for the rest of this job if a maintenance mode command returns a bad status. OFF Turn off continue mode. Description Stops NMMGR from terminating abnormally in a job because a single maintenance mode command terminated with an error.
Using NMMGR in Maintenance Mode COPYCONF COPYCONF Copies a configuration subtree. Syntax COPYCONF srcpath[:srcfile][,[destpath][:destfile]] [;KEEP][;NOVERS] Parameters srcpath The name of a configuration path in the source file that describes the location of the subtree to copy (source path). It is composed of one to eight path identifiers separated by periods: pathid.pathid.pathid... srcfile The name of an NMMGR configuration file (NCONF file) that contains the subtree to be copied (source file).
Using NMMGR in Maintenance Mode COPYCONF perform version checks. Description COPYCONF allows data to be copied from one configuration file into another file, or into the same file in a different location. Source and destination paths are used to direct where a subtree is to come from and where it is to be copied to. (You can also copy a configuration subtree using the NMMGR Configuration Subtree Copy screen in screen mode.
Using NMMGR in Maintenance Mode DELETECONF DELETECONF Deletes a subtree from the current configuration file. Syntax DELETECONF path Parameters path The name of a configuration path in the configuration file that describes the location of the subtree to delete. It is composed of one to eight path identifiers separated by periods, as follows: pathid.pathid.pathid... The last identifier in the path must be a select or type select identifier.
Using NMMGR in Maintenance Mode DELETENODE DELETENODE Deletes an entry from the network directory. Syntax DELETENODE [nodename] [;LOCAL] [;GLOBAL] Parameters nodename The name of a node to delete from the directory in the format: nodename.domain.organization Each of the three names may be from one to sixteen characters long, must begin with a letter, and may contain letters, digits, underscores, or dashes. If omitted, then all entries of the selected class in the directory will be deleted.
Using NMMGR in Maintenance Mode EXIT EXIT Exits from maintenance mode. Syntax EXIT Parameters None. Description If you are running maintenance mode interactively, type EXIT at the NMMGR> prompt to return to screen mode. If you are running maintenance mode from a job, EXIT terminates the job.
Using NMMGR in Maintenance Mode EXITVALIDATE EXITVALIDATE Validates a subsystem’s configuration, if needed, upon exit from NMMGR. Syntax EXITVALIDATE subsystem Parameters subsystem Description [ON or OFF] The name of a configuration subsystem that is to be validated. Currently NETXPORT, DTS, or IBM is allowed. ON This is the default and need not be specified. It indicates that exit validation is to be enabled for the specified subsystem.
Using NMMGR in Maintenance Mode EXITWARN EXITWARN Warns that a subsystem needs to be validated before exiting NMMGR. Syntax EXITWARN subsystem Parameters subsystem Description [ON or OFF] The name of a configuration subsystem to which messages will be issued. Currently NETXPORT, DTS, or IBM is allowed. ON This is the default and need not be specified. It indicates that an exit message is to be enabled for the specified subsystem.
Using NMMGR in Maintenance Mode EXPANDDIR EXPANDDIR Increases the capacity of a network directory file. Syntax EXPANDDIR numrecs Parameters numrecs Description EXPANDDIR increases the capacity of the currently opened directory file to allow additional entries to be added. Each entry in the directory requires one record, plus one for each network address referenced in the entry. NOTE You can use the EXPANDDIR command only if you have exclusive access to the network directory.
Using NMMGR in Maintenance Mode HELP HELP Calls up the help function. Syntax HELP [keyword] Parameters keyword The NMMGR topic about which you are seeking help information. Help is available on the following topics: COMMANDS A list of the commands available. MAINT General help on the maintenance mode interface. OVERVIEW Overview of NMMGR operation. ROADMAP A map of NMMGR screens. INDEX An index of configuration parameters ALL All NMMGR help topics.
Using NMMGR in Maintenance Mode LISTLDEV LISTLDEV Lists LDEVs for a DTC card in a format compatible with ADDLDEV. Syntax (dtcname) LISTLDEV (dtc-nodename) [filename] (station-address) Parameters dtcname The NMMGR nametag for the DTC being accessed. The nametag is the last name in the pathname of the DTC. For example, the dtcname is DTC01 in the pathname DTS.DTC.SELECT.DTC01. The dtcname in a one to eight character alphanumeric string.
Using NMMGR in Maintenance Mode LISTDIR LISTDIR Lists the contents of a network directory. Syntax LISTDIR [nodename] Parameters nodename The name of a node to display from the directory in the format: nodename.domain.organization Each of the three names may be from one to sixteen characters long, must begin with a letter, and may contain letters, digits, underscores, or dashes. If omitted, then all entries in the directory will be listed.
Using NMMGR in Maintenance Mode LISTDIR Node Name IP Address POGO.DCL.IND (L) C 194.107.213 017 IP X NONE ASTRO.MKTG.IND C 194.107.213 009 IP NONE X X VENUS.FIN.IND C 194.107.213 017 IP NONE X X X B 145.140 062.193 IP/IEEE802.3 F1-B3-58-73-A3-09 X X X C 194.107.213 086 IP X X ZIGGY.LAB.
Using NMMGR in Maintenance Mode LISTLU LISTLU Lists LUs in a format compatible with ADDLU. Syntax LISTLU SNAnodename [filename] Parameters SNAnodename A one to eight character alphanumeric name that identifies the SNA node to be listed. filename A text file that contains the LU name and number for each LU to be read from the configuration file. The file name’s format is: filename[.groupname[accountname]] A file lockword may not be specified.
Using NMMGR in Maintenance Mode MAKESTREAM MAKESTREAM Creates a job stream that can then be used to perform network directory or configuration file updates on remote nodes. Syntax MAKESTREAM streamfile, nodefile, commandfile Parameters streamfile The name of a file to be created that will contain the job stream commands. The format is: filename[.groupname[.accountname]] The file must not already exist. The default allocation of 5000 variable length records may be overridden through a file equation.
Using NMMGR in Maintenance Mode MAKESTREAM POGO.DCL.IND commandfile CMDS contains the following: OPENDIR NSDIR.PUB.SYS :FILE SRCDIR=NSDIR.PUB.SYS:$BACK MERGEDIR *SRCDIR;NOKEEP LISTDIR EXIT To generate and run a job stream, use the following commands: NMMGR> MAKESTREAM SFILE, NLIST, CMDS Generating job statements for node ASTRO.MKT.IND Generating job statements for node POGO.DCL.IND NMMGR> :STREAM SFILE #J1072 After job completion, file NLIST contains the following: 104 ASTRO.MKT.
Using NMMGR in Maintenance Mode MERGEDIR MERGEDIR Merges entries from another network directory or configuration file into the current network directory. Syntax {otherdir MERGEDIR {configfile [,nodename]} [;LOCAL] [;KEEP } [;NOKEEP ] ] [;GLOBAL][;TIMESTAMP ] Parameters otherdir The name of another network directory file to merge one or more entries from. The format is: filename[.groupname[.accountname]] A file lockword may not be specified.
Using NMMGR in Maintenance Mode MERGEDIR KEEP Indicates that entries in the current directory are to be retained when duplicate entries exist in the source directory. This keyword is not applicable when the source is a configuration file. NOKEEP Indicates that entries in the current directory are to be overwritten with duplicate entries found in the source directory. This keyword is not applicable when the source is a configuration file.
Using NMMGR in Maintenance Mode NICONF NICONF Sets up paths to add or update NETXPORT NI configurations. Syntax NICONF niname [nitype] Parameters niname A one to eight alphanumeric character name that identifies the network interface to be added or modified. nitype The type of the network interface to be added. Valid types are: LAN, TOKEN, X25, SNA, GATEHALF, or ROUTER. Description NICONF is used in place of the PATHCONF command to set up internal data structures in NMMGR.
Using NMMGR in Maintenance Mode OPENCONF OPENCONF Opens a nodal configuration file and makes it the current configuration file. Syntax OPENCONF fileref Parameters fileref The name of a configuration file to access in the format: filename[.groupname[.accountname]] A file lockword may not be specified. Description OPENCONF closes any previously opened configuration file and opens the file named in fileref for shared, read/write access.
Using NMMGR in Maintenance Mode OPENDIR OPENDIR Opens a network directory file and makes it the current directory. Syntax OPENDIR fileref Parameters fileref The name of a network directory file to access in the format: filename[.groupname[.accountname]] A file lockword may not be specified. Description OPENDIR closes any previously opened directory and opens the directory file named in fileref for shared, read/write access.
Using NMMGR in Maintenance Mode PAGECONF PAGECONF Sets the page number for multipage data screens. Syntax PAGECONF pageno Parameters pageno Description PAGECONF sets the current page number for a path referencing a multipaged data screen. A multipaged data screen is used to store lists of data that cannot be entered on a single screen.
Using NMMGR in Maintenance Mode PASSWORD PASSWORD Changes the password to allow write access on the OPEN screen. Validates the NETXPORT subsystem configuration. Syntax PASSWORD [password] Parameters password Description The password you supply on the OPEN screen is compared with the password string supplied here (or the default if no password command has been issued). If the user password does not match, you are only permitted to access the network directory or configuration file in BROWSE MODE.
Using NMMGR in Maintenance Mode PATHCONF PATHCONF Sets the current path in the current configuration file. Syntax PATHCONF[=]path Parameters path The name of a path in the configuration file that describes the location of the desired record. It is composed of one to eight path identifiers separated by periods: pathid.pathid.pathid... The last identifier in the path must be a data identifier (must refer to a data screen).
Using NMMGR in Maintenance Mode PURGECONF PURGECONF Deletes subtrees of records from the configuration file. Syntax PURGECONF [pathname] Parameters pathname The name of a path in the configuration file that describes the location of the desired subtree. It is composed of one to eight path identifiers separated by periods. The format for the pathname is: pathid.pathid.pathid... The last pathid specified must not exist in the configuration file. The second to last pathid must exist.
Using NMMGR in Maintenance Mode PURGELDEV PURGELDEV Purges LDEVs from a DTC card. Syntax {dtcname} PURGELDEV {dtc-nodename} [filename] {station-address} Parameters dtcname The NMMGR nametag for the DTC being accessed. The nametag is the last name in the pathname of the DTC. For example, the dtcname is DTC01 in the pathname DTS.DTC.SELECT.DTC01. The dtcname in a one to eight character alphanumeric string. dtc-nodename The nodename of the DTC that has been configured at the DTC nametag path.
Using NMMGR in Maintenance Mode PURGELDEV Example NMMGR> PURGELDEV dtc01.ind.
Using NMMGR in Maintenance Mode PURGELU PURGELU Purges LUs from the SNA node transport screen. Syntax PURGELU SNAnodename [filename] Parameters SNAnodename A one to eight character alphanumeric name that identifies the SNA node to be purged. filename A text file that contains the LU names to be purged from the configuration file. The file name’s format is: filename[.groupname[accountname]] A file lockword may not be specified. The contents of the file must be formatted as described here.
Using NMMGR in Maintenance Mode PURGENI PURGENI Purges a network interface from the configuration file and performs cleanup. Syntax PURGENI [niname] Parameters niname Description Purges a network interface from the configuration file and purges all the links it refers to from under the LINK path. Example NMMGR> PURGENI lanni Chapter 5 A one to eight character alphanumeric name that identifies the network interface to be purged.
Using NMMGR in Maintenance Mode PURGEVC PURGEVC Purges an X.25 virtual circuit address key from the network directory and the configuration file. Syntax PURGEVC [filename] Parameters filename The name of a text file that contains X.25 address information for each remote node to be deleted from the configuration file and directory. The format for the file name is: filename[.groupname[.accountname]] A file lockword may not be specified. The contents of the file must be formatted as described below.
Using NMMGR in Maintenance Mode PURGEVC contain a maximum of eight alphanumeric characters. NI name Example The network interface name. The name of the local X.25 NI, (configured under the path NETXPORT.NI). The name may contain a maximum of eight alphanumeric characters. To purge a virtual circuit associated with the NI named X25 for the node named NODE1.XLNET.ACCTG: NMMGR> OPENCONF NMCONFIG NMMGR> OPENDIR NSDIR.NET.SYS NMMGR> PURGEVC Enter the node name (or press return to exit): PURGEVC> NODE1.XLNET.
Using NMMGR in Maintenance Mode READALLCONF READALLCONF Reads all data from the current configuration record. Syntax READALLCONF [;FORMAT] Parameters FORMAT Description READALLCONF reads and displays all the fields in the configuration record identified by the current path. If the current path is associated with a multipaged data screen, then all the pages of data associated with the screen are displayed, unless PAGECONF was used to set the current page. Designates output formatting.
Using NMMGR in Maintenance Mode READALLCONF WRITECONF G, “3” WRITECONF H, “1” WRITECONF INBUF, “256” UPDATECONF NMMGR Chapter 5 121
Using NMMGR in Maintenance Mode READCONF READCONF Reads selected data from the current configuration record. Syntax READCONF fieldname [;FORMAT] Parameters fieldname The field name associated with the current path. Use READALLCONF;FORMAT to find the fieldnames in the current path. FORMAT Description Designates output formatting. Output is formatted in a WRITECONF format so that it can be re-entered into NMMGR’s maintenance mode.
Using NMMGR in Maintenance Mode SUMMARYCONF SUMMARYCONF Prints a summary report for one or more communications subsystems. Syntax SUMMARYCONF subsystem[, subsystem[, ...]] Parameters subsystem Description SUMMARYCONF displays a summary report for a particular subsystem. This command is identical to the Print Summary function in the NMMGR Output Configuration screen. The name of the subsystem(s) for which the report will be generated.
Using NMMGR in Maintenance Mode SUMMARYCONF DTS Displays the DTS subsystem configuration parameters. E[XIT] Leaves DTS Summary and returns you to the maintenance mode prompt. HELP Displays the available DTS summary options. LDEV [ldev[/ldev]] Displays the configuration for all ldevs (logical devices), a single ldev, or a range of ldevs. LINK Displays the link configuration for the DTS.
Using NMMGR in Maintenance Mode UPDATECONF UPDATECONF Updates the current path in the configuration file. Syntax UPDATECONF Parameters No parameters. Description UPDATECONF updates the current page of data for the current path in the configuration file. Data entered via previous WRITECONF commands is checked for VPLUS field edit errors. If all fields are correct, the data is stored. The CARDCONF then the PATHCONF command must be issued before UPDATECONF to define the current path.
Using NMMGR in Maintenance Mode VALIDATECONF VALIDATECONF Validates subsystem configuration. Syntax VALIDATECONF subsystem Parameters subsystem The name of a configuration subsystem to be validated. Valid subsystem names are: NETXPORT DTS/LINK HP-IBM Description Validates the subsystem configuration. Output is directed to the formal designator FORMLIST, which defaults to $STDLIST.
Using NMMGR in Maintenance Mode VERSIONCONF VERSIONCONF Checks whether the specified version number matches NMMGR’s current version number. Syntax VERSIONCONF version Parameters version Description VERSIONCONF matches the specified version number with the current number for NMMGR. NMMGR’s version number is displayed in the banner line on the first line of the screen and when NMMGR is started. This command is required only if the user is also planning to issue a PATHCONF command.
Using NMMGR in Maintenance Mode WRITECONF WRITECONF Writes data to individual fields of the current path in the configuration file. Syntax WRITECONF fieldname, data Parameters fieldname The field name associated with the current path. data The data to be written to the field. If the data contains embedded blanks, it must be enclosed in double quotes (“ ”).
6 NMMAINT This chapter describes the Node Management Services Maintenance Utility (NMMAINT). NMMAINT is a utility (optional) program you can use to display the individual and overall version numbers for the software modules and network link products configured through the node management services. The following information is included in this chapter: • An explanation of version numbers and how they work. • How to run the NMMAINT utility. • An example of the output provided by NMMAINT.
NMMAINT Software Version ID Numbers Software Version ID Numbers Each data communications product consists of a variety of software modules. Each software module has an individual version number. The software modules of all HP data communications products use a standard version stamp. This stamp has the format: vuuffiii where values represent the following: v The version number of the software. This corresponds to a major revision or a version for a new or revised system environment.
NMMAINT Getting Help Getting Help To get HELP on NMMAINT. :NMMAINT;info=help NMMAINT responds with the following: NMS Maintenance Utility 32098-20014 v.uu.ff TUE, JUL 25, 2006, (C) Hewlett Packard Co. 1984 2:30 PM - HELP WARNING The SHUTDOWN, RESTART, and other INFO of the NMMAINT program are unsupported interfaces designed for use by Hewlett Packard Support personnel only. HP IS NOT LIABLE FOR DAMAGES RESULTING FROM UNAUTHORIZED USE :RUN NMMAINT [;PARM=n] Print version id’s [subsys n].
NMMAINT Running NMMAINT 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. 1984 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.
NMMAINT Running NMMAINT Example :RUN NMMAINT.PUB.SYS NMS Maintenance Utility 32098-20014B.00.08 (C) Hewlett Packard Co. TUE, JUL 25, 2006, 2:30 PM Datacom products build version: N.63.
NMMAINT Running NMMAINT NL procedure: NMVERS32 Version: MPE/XL Node Management Services 32098-20014 B0010000 overall version = B.00.10 Subsystem Number : 3 NS 3000/XL Transport 32098-20033 module versions: NM program file: NETCP.NET.SYS Version: B0600001 Catalog file: NMCAT3.NET.
NMMAINT Running NMMAINT NL procedure: NET_UDP_VERS Version: B0600003 NL procedure: NET_DICT_VERS Version: B0600000 SL procedure: NET'PXP0'VERS Version: B0600000 SL procedure: NET'PXP1'VERS Version: B0600000 NL procedure: NET_IP_VERS Version: B0600001 NL procedure: NET_IPU_VERS Version: B0600002 SL procedure: NET'IPU'VERS Version: B0600000 NL procedure: NET_X25_VERS ** NOT INSTALLED ** NM program file: X25STAT.NET.SYS Version: B0600001 CM program file: X25CHECK.NET.
NMMAINT Running NMMAINT NL procedure: NETTMRVERS NS 3000/XL Transport 32098-20033 Version: B0600000 overall version = B.06.00 Subsystem Number : 6 Network Services individual module versions: NM Program: DSDAD.NET.SYS Version: B0300043 SL procedure: ASCXVERS Version: B0300051 SL procedure: ASBUFVERS Version: B0300014 SL procedure: ASENVVERS Version: B0300050 SL procedure: DSUTILVERS Version: B0300003 SL procedure: SUBSYS6FMTVERS Version: B0300015 Catalog file: ASCAT.NET.
NMMAINT Running NMMAINT CM Program: NFT.NET.SYS Version: NL procedure: NFTNMVERS ** MODULE ERROR ** Catalog file: NFTCAT2.NET.SYS Version: B0300005 SL procedure: ASRPMVERS Version: B0300038 NL procedure: RPMNMVERS Version: B0300012 CM Program: RPMDAD.NET.SYS Version: B0300002 NL procedure: RFANMVERS ** MODULE ERROR ** Network Services overall subsystem version: NS 3000/XL SERVICES: B0300009 B.03.
NMMAINT Running NMMAINT SL procedure: NETDIRVERS Version: B0601000 NL procedure: NMNETDIRVERS Version: B0601000 NM program file: NMMGR.PUB.SYS Version: B0601001 CM program file: NMMGRVER.PUB.SYS Version: B0601001 CM program file: NMMGRVAL.PUB.SYS Version: B0601000 CM program file: NMSIG.PUB.SYS Version: B0601000 V+ forms file: NMMGRF.PUB.SYS Version: B0601001 Catalog file: NMMGRCAT.PUB.SYS Version: B0601001 Catalog file: NMMGRHLP.PUB.
NMMAINT Running NMMAINT Download: DTCCNF02.PUB.SYS Version: A1440000 Download: DTCSWA02.PUB.SYS Version: A1440000 Download: DTCSWB02.PUB.SYS Version: A1440000 Download: DTCNPS02.PUB.SYS Version: A1440000 Download: DTCSWC04.PUB.SYS Version: A1440000 Download: DTCSWD04.PUB.SYS Version: A1440000 Download: DTCSWE04.PUB.SYS Version: A1440000 Download: DTCSWF04.PUB.SYS Version: A1440000 Download: DTCCNF04.PUB.SYS Version: A1440000 Download: DTCSWG04.PUB.
NMMAINT Running NMMAINT NL procedure: TIO_TLDM_VER Version: C0200001 NL procedure: TIO_FIOM_VER Version: C0200021 NL procedure: TIO_DIOM_VER Version: C0200057 NL procedure: TIO_IIOM_VER Version: C0200016 NL procedure: TIO_COMMON_VER Version: C0200026 NL procedure: TIO_TRANSPORT_VER Version: C0200027 NL procedure: TIO_NDM_VER Version: C0200505 NL procedure: TIO_INF_VER Version: C0200100 NL procedure: TIO_DTCM_VER Version: C0200504 XL procedure: TIO_DTF_VER Version: C020
NMMAINT Running NMMAINT Catalog file: FTPHELP.ARPA.SYS Version: A0009001 HP FTP/XL HP36957 overall version = A.00.09 Subsystem Number : 55 NIO System Console DM NL procedure: 32098-20078 module versions: CDM_CONSOLE_DM_VERSION NIO System Console DM 32098-20078 Version: A0001015 overall version = A.00.01 Subsystem Number : 57 HP SNMP/XL SNMP module versions: NM program file: SNMP.NET.SYS Version: A0400001 NM program file: SNMPUTIL.NET.SYS Version: A0400001 NM program file: SNMPSYMB.
NMMAINT Running NMMAINT Subsystem Number : 63 HP NSR/XL HP32098-20084 module versions: RL procedure: NSR_GETHOST Version: A0006000 XL procedure: NSR_GETNET Version: A0006000 XL procedure: NSR_GETPROTO Version: A0006000 XL procedure: NSR_GETSERV Version: A0006000 XL procedure: NSR_HPGETHOST Version: A0006000 XL procedure: NSR_INET_ADDR Version: A0006000 XL procedure: NSR_INET_NETWORK Version: A0006000 XL procedure: NSR_INET_NTOA Version: A0006000 XL procedure: NSR_BINDUP
NMMAINT Running NMMAINT NL procedure: FDDI_DRIVER_VER Version: A0060002 XL procedure: FDDI_LINKCONTROL_VER Version: A0060000 Download: FDDIDNLD.PUB.SYS Version: A0060000 HP FDDI LAN Driver 32098-20093 overall version = A.00.
NMMAINT Running NMMAINT Subsystem Number : 72 HP TELNET/iX Subsystem HP32040A module versions: NM program file: TELNET.ARPA.SYS Version: A6000000 NL procedure: PTD_SM_VER Version: A6000001 NL procedure: PTD_HANDLER_VER Version: A6000002 NL procedure: PTD_PTID_VER Version: A6000002 NL procedure: PTD_PTOD_VER Version: A6000002 NL procedure: PTD_COMMON_VER Version: A6000001 HP TELNET/iX Subsystem HP32040A overall version = A.60.
NMMAINT Running NMMAINT Subsystem Number : 74 HP-PB 100VG-AnyLAN driver B5426AA module versions: NL procedure: VG_NL_VERS ** NOT INSTALLED ** XL procedure: VG_XL_VERS ** NOT INSTALLED ** NL procedure: LAN_100_NL_VERS ** NOT INSTALLED ** XL procedure: LAN_100_XL_VERS Version: A0060004 XL procedure: SUBSYS_74_FMT_VER Version: A0060004 Catalog file: NMCAT74.NET.
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.
NMMAINT Running NMMAINT 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. NMMAINT displays the subsystem number just before it prints versions of that module.
NMMAINT Running NMMAINT NOTE 41 Terminal Mux Driver 42 Multiple Connection Module 46 SNADS 48 Lan Manager 50 FTP/iX 55 HP-PB Console DM 57 SNMP 61 HP-PB 802.
NMMAINT Running NMMAINT 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.
NMMAINT Running NMMAINT 150 Chapter 6
7 NMDUMP This chapter describes the Node Management Services Trace/Log File Analyzer, commonly known as NMDUMP. NMDUMP allows you to decode and format the logging records and trace messages that are created in coded form. The following describes information contained in this chapter. • Running the NMS Trace/Log File Analyzer (NMDUMP). • General options. These options include two, ? and 0, that are used for menu display and are provided on all menus.
NMDUMP Figure 7-1 NMDUMP NMDUMP RUN NMDUMP.PUB.
NMDUMP Running NMDUMP Running NMDUMP Step 1. Type :RUN NMDUMP.PUB.SYS Step 2. Enter either (1) logging or (2) tracing. Step 3. Enter the ID number for each subsystem you want to format. Use a comma to separate each number. (Default = ALL.) NOTE ID numbers can be used as parameters with NMMAINT. Step 4. Change the default (NO) to (YES) if you would like to enter subsystem options. (NMDUMP will set the default options if (NO) is entered.) a. Enter the subsystem ID for the options you want to change. b.
NMDUMP Formatting Options Formatting Options NMDUMP allows you to modify formatting options for specified subsystem IDs. There are three ways to change the formatting menu options. 1. Most options toggle between two possible values, like YES or NO and ON or OFF. 2. Some require you to enter an option number which then displays an additional menu and prompt. 3. Several options prompt you to enter the numbers of certain items. The following tables show the options for logging and tracing.
NMDUMP Formatting Options See Table 7-2 for a description of logging options. Table 7-2 Log Options Subsystem Option Meaning Description 802.3, 802.5, FDDI, 100VG-AnyLAN, 100Base-T 1 Linknames Select logging options by Linknames. @ = ALL 2 Excluded Linknames Select Linkname to be excluded from logging. 3 Log Classes Error message options (ERRORS, WARNINGS, INFO, ALL) 4 Set Output Level Toggle between Terse and Verbose. Verbose = Detail report, Terse = Summary.
NMDUMP Formatting Options See Table 7-3 for information on the trace formatter options. Table 7-3 X.
NMDUMP Formatting Options See Table 7-4 for a description of trace options. Table 7-4 Trace Options Subsystem Option Meaning Description 802.3, 802.5, FDDI, 100VG-AnyLAN, 100Base-T 1 Change Filters Allows definition of what characters each packet must match before it will be formatted.
NMDUMP Formatting Options Table 7-4 Trace Options Subsystem Option Meaning Description SDLC, LAP-B, RJE/BSC 802.3, 802.5, FDDI, 100VG-AnyLAN, 100Base-T 1 Output Limit Allow input of maximum bytes in line-data frames to reduce the amount of formatted data. Affects only line-data-frames. 2 Filter Sets Allows selection of filters for output data. All filter sets are displayed when selected. 3 Show Raw Data Allows printing of unformatted trace data along with the same data in decoded form.
NMDUMP Formatting Options See Table 7-5 for a description of filter sets. Table 7-5 Filter Sets Subsystem Number Filter Description SDLC 1 Data frames sent/rcvd Enables printing of frames sent and frames received on the datacomm link. 2 Driver message sent/rcvd Enables printing of all port messages sent to the driver by SNA Transport and other entities, or sent to them by the driver. 3 Driver state-change s Enables printing of changes in internal state within the SDLC driver modules.
NMDUMP Formatting Options Table 7-5 Filter Sets Subsystem Number Filter Description LAP-B 2 Driver messages sent/rcvd Enables printing of all port messages sent to the driver by NS Transport and other entities, or sent to them by the driver. 3 Driver state-change s Enables printing of changes in internals state within the LAP-B driver modules.
NMDUMP Formatting Options Link Subsystem Formatting The link manager subsystem does not call any menus. NMDUMP formats logging messages only. The first line labels the error as a link manager error, and shows whether it is fatal or non-fatal. The next line contains the time and date of the event. This line is followed by the log message, the requestor ID, the link name, and the logical device (LDEV) of the link. The requestor ID is for internal use only.
NMDUMP Formatting Options 162 Chapter 7
8 NMMGRVER This chapter describes NMMGRVER, a conversion program that enables earlier versions of subsystems to be used with the current version of NMMGR. This version of NMMGRVER will convert configuration files from previous versions of MPE/iX to the current MPE/iX release format. This chapter includes discussions of the following: • Using the NMMGRVER conversion program. • Converting configuration files from previous versions of MPE XL format to the current version of MPE/iX format.
NMMGRVER Using the Conversion Program Using the Conversion Program You need to convert files if you open an existing configuration file while using NMMGR and receive this message: Version mismatch found on specified subsystem. Please run NMMGRVER.
NMMGRVER Using the Conversion Program where filename.groupname.acctname is the name of a configuration file. Enter Y for yes or either N or [RETURN] for no. Step 4. NMMGRVER checks the configuration file to determine if it is an MPE/iX configuration file, then the conversion proceeds without further user input. After each file is converted NMMGRVER will display the following message: Conversion Completed Successfully (NMMGRVERMSG 0) Step 5.
NMMGRVER Using the Conversion Program 166 Chapter 8
A NMS Error Messages This appendix includes listings of Node Management Services error messages, grouped in sets as shown below. The error messages in each set are listed numerically. Each error message listed includes at least one possible cause of the error and a recommended action for each cause. Some of the messages, as shown in this manual, include an exclamation point (!), which is a substitution character that represents variable information.
NMS Error Messages Resolving Problems Resolving Problems There are problems that are common to many situations, such as invalid software installation, version incompatibilities, insufficient MPE resources, corrupt configuration files, and file system errors. This section describes some of the resolutions for these problems. In many cases, you can use these descriptions to help you resolve these problems yourself.
NMS Error Messages Resolving Problems Insufficient MPE Resources There may be insufficient MPE resources, such as configured table sizes. Check if the MPE configuration has enough DST and PCB entries configured. (If possible, use the HP Glance/XL product to check MPE table utilization.) Reconfigure MPE to fix any problems found and restart the system. Corrupt Configuration Files The configuration file is possibly corrupt.
NMS Error Messages Submitting a CR Submitting a CR The messages that refer you to this section can indicate an internal error. For further assistance from HP, submit an CR (Change Request). Include the following information where applicable: • A characterization of the problem. Describe the events leading up to and including the problem. Attempt to describe the source of the problem. Describe the symptoms of the problem.
NMS Error Messages Submitting a CR • Document your interim, or “workaround” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur. • Create copies of any trace files that were active when the problem occurred for your Hewlett-Packard representative to analyze. • In the event of a system failure, a full memory dump must be taken.
NMS Error Messages NMCN Error and Warning Messages NMCN Error and Warning Messages The first seven NMCNERR messages are written to the console by the NMMON process. The remainder of NMCNERR messages are written by one of the NMLOGMON processes to the console. “NM log Monitor” messages are returned by the “Main type Log Monitor:” this is the first NMLOGMON process created and later handles most tracing.
NMS Error Messages NMCN Error and Warning Messages NMCNERR 6 MESSAGE: NMMON: CREATEPROCESS error n on NMLOGMON.PUB.SYS. (NMCNERR 6) CAUSE: CREATEPROCESS failed for NMLOGMON. The NMLOGMON.PUB.SYS program file might not be present, or might not be Load-able. This could happen if the NMS software is not correctly installed, or if there is a mismatch between NMLOGMON and SL module versions. Also, there could be other MPE limitations such as insufficient table space.
NMS Error Messages NMCN Error and Warning Messages NMCNERR 16 MESSAGE: NM Log Monitor: Another MainLogMonitor exists. This one terminating. (NMCNERR 16) CAUSE: A Main Log Monitor process has found its entry already exists in the port dictionary. ACTION: See “Submitting a CR” at the beginning of this appendix. NMCNERR 17 MESSAGE: NM Log Monitor: Unable to obtain port data segment. (NMCNERR 17) CAUSE: INITPORTDST returned a DST number of 0. The system is unable to allocate any extra data segments.
NMS Error Messages NMCN Error and Warning Messages other error indications that may affect the system disks, including I/O errors. ACTION: Correct any situation that may cause disk I/O errors. If the problem persists, see “Submitting a CR” at the beginning of this appendix. NMCNERR 24 MESSAGE: NM Log Monitor: Illegal parameter passed; create failed. (NMCNERR 24) CAUSE: The user has attempted to enter a parameter which is not valid. ACTION: Check input parameters and try again.
NMS Error Messages NMCN Error and Warning Messages NMCNERR 33 MESSAGE: NM Log Process: Unable to add to NM Monitor port table. (NMCNERR 33) CAUSE: NMMONADDID failed for MainLogMonitor. ACTION: See “Submitting a CR” at the beginning of this appendix. NMCNERR 34 MESSAGE: NM Log Process: Unable to create logging buffer data segment. (NMCNERR 34) CAUSE: NM Log Process is unable to acquire an extra data segment. ACTION: See “Insufficient MPE Resources” at the beginning of this appendix.
NMS Error Messages NMCN Error and Warning Messages NMCNERR 45 MESSAGE: NM Log Process: Cannot format log msg. Cannot access formatter for subsystem !. Encountered LOADPROC error !. (NMCNERR 45) CAUSE: A request to write a formatted log message specifies an NMS subsystem number where formatter Log Process was unable to LOADPROC. ACTION: The SUBSYSnLOGFORMA procedure, where n is the subsystem number specified in the message, either did not exist in SL.PUB.
NMS Error Messages NMCN Error and Warning Messages NMCNERR 47 MESSAGE: NMLG FILES mmmm THRU nnnn SKIPPED. (NMCNERR 47) CAUSE: NM log files mmmm through nnnn were skipped over when NMS Logging tried to open a new disk log file. Files NMLGmmmm.PUB.SYS through NMLGnnnn.PUB.SYS already exist. This is an information message only; no error occurred. ACTION: None. NMCNERR 48 MESSAGE: NMLG FILES 0000 THRU 9999 ALL USED, NONE AVAILALBLE FOR NEXT LOGFILE.
NMS Error Messages NMCN Error and Warning Messages continue to execute, but will be unable to log any errors, including I/O errors. NMCNWARN 71 MESSAGE: Trace Manager unable to open NM logging. (NMCNWARN 71) CAUSE: NMCONFIG does not have logging subsystem 18 configured. ACTION: None required. NMCNERR 80 MESSAGE: Linkname Table creation error, subsys=! info=!. (NMCNERR 80) CAUSE: System call failure. ACTION: Reboot the system.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMP Error and Warning Messages NMDUMPERR 0 MESSAGE: Unable to retrieve text of message #! of set #! from the message catalog. (NMDUMPERR 0) CAUSE: This message is actually not returned by the message catalog, but by the program, if the error message requested to be returned cannot be retrieved by the program. It will be displayed when there is no message catalog, NMCAT.PUB.SYS, or the message catalog is not valid (corrupt).
NMS Error Messages NMDUMP Error and Warning Messages NMDUMPERR 5 MESSAGE: Error — File is not of trace type. (NMDUMPERR 5) CAUSE: User specified that he wanted to format a trace file, but the input file specified was not type NTRAC. ACTION: Check spelling of filename. Check file’s type code. Correct input and reenter. NMDUMPERR 6 MESSAGE: Invalid date and time string entered. (NMDUMPERR 6) CAUSE: User entered an invalid date and/or time. User entered the date and/or time in improper format.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMPERR 20 MESSAGE: Error — unexpected end of input data file. (NMDUMPERR 20) CAUSE: There was a system failure while tracing/logging was enabled and the file was closed improperly. ACTION: Attempt to relog or retrace the error situation. CAUSE: An internal error in the NMS trace/log facility or the NMDUMP facility. ACTION: File a CR (Change Request). Refer to “Submitting a CR” at the beginning of this appendix. CAUSE: Data file has become corrupt.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMPWARN 23 MESSAGE: No data records, from the subsystems selected, were found within the time selected. (NMDUMPWARN 23) CAUSE: No records were logged/traced to the file from the selected subsystems during the time range specified. ACTION: None. CAUSE: If the input file is a log file, logging for the subsystems selected may not be enabled. ACTION: Check the logging configuration portion of NMCONFIG.PUB.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMPERR 26 MESSAGE: Error — invalid trace data file. (NMDUMPERR 26) CAUSE: There was a system failure while tracing was enabled and the file was closed improperly. ACTION: Attempt to retrace the error situation. CAUSE: An internal error in the NMS trace facility or the NMDUMP facility. ACTION: File a CR (Change Request). Refer to “Submitting a CR” at the beginning of this appendix. CAUSE: Data file has become corrupt.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMPWARN 30 MESSAGE: Invalid trace destination specified in global header. Reassigned according to file characteristics. (NMDUMPWARN 30) CAUSE: An internal error in the NMS trace facility which caused bad data to be written to the data file. ACTION: No action is actually needed. NMDUMP recovers from such an error in the data file. However, an CR may be filed against the trace facility. Refer to “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NMDUMP Error and Warning Messages CAUSE: Log data file has become corrupt. ACTION: No action is actually needed. NMDUMP recovers from such an error in the data file. However, you may attempt to recreate the data file. NMDUMPWARN 34 MESSAGE: An out-of-range data record length was found. It was reassigned the maximum allowable value, 2046. (NMDUMPWARN 34) CAUSE: An internal error in the NMS log facility which caused bad data to be written to the log data file.
NMS Error Messages NM Error Messages NM Error Messages NMERR 1 MESSAGE: Invalid parameter specified. (NMERR 1) CAUSE: The caller of an NMS procedure has passed an invalid value for one or more of the parameters. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 2 MESSAGE: Invalid SubsystemID parameter. (NMERR 2) CAUSE: The caller of an NMS procedure has passed an invalid value for the parameter SubsystemID. Returned by NMOPENTRACE, NMOPENLOG, NMGETTRACEID, NMVERSCHECK.
NMS Error Messages NM Error Messages NMERR 8 MESSAGE: Invalid InfoMode parameter. (NMERR 8) CAUSE: The caller of an NMS procedure passed an invalid value to the InfoMode parameter. Returned by NMWRITETRACE. This is usually an internal error in the calling subsystem. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 9 MESSAGE: Invalid Mode parameter. (NMERR 9) CAUSE: The caller of an NMS procedure passed an invalid value to the Mode parameter.
NMS Error Messages NM Error Messages NMERR 15 MESSAGE: Unable to create new datafile. (NMERR 15) CAUSE: Returned by NMCONFOPEN. NMCONFOPEN detected an error on MIDASOPEN, attempted on the user’s stack, on a new file that was to be created. A File System error occurred. (Normal File System restrictions apply when creating NM files.) ACTION: See “File System Error” at the beginning of this appendix. NMERR 16 MESSAGE: Unable to open the datafile. (NMERR 16) CAUSE: Returned by NMCONFOPEN.
NMS Error Messages NM Error Messages NMERR 20 MESSAGE: Unable to obtain data segment for tracing. (NMERR 20) CAUSE: Main NMLogMon was unable to get an extra data segment, or if internal tracing was specified, was unable to lock the extra data segment it did get. ACTION: See “Insufficient MPE Resources” and “Submitting a CR” at the beginning of this appendix. NMERR 21 MESSAGE: Must have 1 <= data length <= 8192 bytes.
NMS Error Messages NM Error Messages ACTION: Manually check the configuration using NMMGR and ensure the logging entry for that subsystem is configured properly. Refer to the appropriate reference manual for assistance. NMERR 29 MESSAGE: LogClass not configured in configuration file. (NMERR 29) CAUSE: NMS logging cannot find the specified log class in the configuration file NMCONFIG.PUB.SYS. Returned by NMWRITELOG. The log class specified for the calling subsystem is not configured correctly in NMCONFIG.
NMS Error Messages NM Error Messages NMERR 35 MESSAGE: Internal error: Invalid data segment number. (NMERR 35) CAUSE: Condition code “>” returned from an internal data segment move routine. An invalid DST number was specified. This message is returned if a bad condition code is received after call of one of the move routines between data segments: MBFDS, MFDS, MBTDS. This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NM Error Messages NMERR 41 MESSAGE: Port identifier not found in port table. (NMERR 41) CAUSE: Returned by NMMONDELETEID. Port ID to be deleted does not exist in NMMON’s table, NMMONADDID was not called for this ID. Caused by an internal problem, or bad software installation. ACTION: See “Invalid Software Installation” and “Submitting a CR”’ at the beginning of this appendix. NMERR 42 MESSAGE: Unable to create specified system process. (NMERR 42) CAUSE: Returned by NMMONSTARTREQ.
NMS Error Messages NM Error Messages appendix. NMERR 48 MESSAGE: Unable to open $STDIN for process. (NMERR 48) CAUSE: Returned by NMOPENLINK. Unable to FOPEN $STDIN for Link Manager process. Caused by an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 49 MESSAGE: Unable to open $STDLIST for process. (NMERR 49) CAUSE: Returned by NMOPENLINK. Unable to FOPEN $STDIN for Link Manager process. Caused by an internal error.
NMS Error Messages NM Error Messages NMERR 56 MESSAGE: Invalid infolen, must be in range: 1 <= infolen <= 8. (NMERR 56) CAUSE: Returned by: NMCONFFILEINFO. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 57 MESSAGE: Duplicate identifier already exists. (NMERR 57) CAUSE: Returned by NMCONFADDPATH, NMCONFRENAMEPATH. NMFILE detected NMFSERR 21 on MIDASADDPATH. User of configuration program entered erroneous information. ACTION: Enter correct data specifications.
NMS Error Messages NM Error Messages NMERR 60 MESSAGE: Unable to find NM Log Monitor. (NMERR 60) CAUSE: An NM Trace or Logging procedure is unable to locate the server trace or log process (NMLogMon). Returned by NMOPENTRACE, NMGETTRACEID, NMCLOSETRACE, NMOPENLOG, NMCLOSELOG, and by the SHOWNMLOG CI command. The trace or log server process creation failed at system startup due to a bad software installation, a loader error, or an internal error.
NMS Error Messages NM Error Messages ACTION: Specify a valid file name and retry. NMERR 65 MESSAGE: Specified file is a back reference file. (NMERR 65) CAUSE: The file name FileName parameter of the NMOPENTRACE procedure contains a back referenced file name (the first ASCII character is “*”). User specified an incorrect filename either in the command that starts trace for that subsystem, or in the configuration file for that subsystem. ACTION: Specify a valid file name and retry.
NMS Error Messages NM Error Messages NMERR 72 MESSAGE: This command has no parameter. (NMERR 72) CAUSE: Parameters were specified for an NMS command that does not require any parameters. Returned by SHOWNMLOG, RESUMENMLOG, and SWITCHNMLOG. User entered parameters for an NMS CI command SHOWNMLOG, SWITCHNMLOG, or RESUMENMLOG. ACTION: Enter the command name alone without any other text on the $STDIN or $STDINX record. NMERR 73 MESSAGE: Invalid logging configuration file. (NMERR 73) CAUSE: NMCONFIG.PUB.
NMS Error Messages NM Error Messages NMERR 77 MESSAGE: File associated with this transaction is locked. (NMERR 77) CAUSE: Returned by: NMCONFADDDATA, NMCONFUPDATEDATA, NMCONFPURGEDATA, NMCONFADDPATH, NMCONFPURGEPATH, NMCONFRENAMEPATH. Some other process has the NMCONF type file locked. ACTION: Wait until the file is unlocked by the other user(s) before proceeding. NMERR 78 MESSAGE: No data associated with this identifier.
NMS Error Messages NM Error Messages NMERR 88 MESSAGE: Parameter not aligned properly. (NMERR 88) CAUSE: Internal error by the calling subsystem. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 90 MESSAGE: Invalid path type value, must be 1 or 2. (NMERR 90) CAUSE: Returned by NMCONFNEXTPATH. NMCONFNEXTPATH detected invalid path type value. Internal error by the calling subsystem. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NM Error Messages NMERR 97 MESSAGE: Unable to find port for NMFILE process. (NMERR 97) CAUSE: Returned by all NMCONF procedures. Error detected on DICTSEND. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 100 MESSAGE: Subsystem does not support version checking. (NMERR 100) CAUSE: Returned by NMVERSCHECK. Coding error by caller of NMVERSCHECK. The SUBSYSID parameter must refer to a subsystem number that has a second level version cross check routine.
NMS Error Messages NM Error Messages ACTION: Correct this problem and retry. If necessary see “Invalid Software Installation” at the beginning of this appendix. CAUSE: Some of the program files and data files have the version stamp located in the last user label record. Perhaps the file was copied without copying its user label records properly. ACTION: See “Invalid Software Installation” at the beginning of this appendix. NMERR 106 MESSAGE: MODULE FLAGS parameter invalid. (NMERR 106).
NMS Error Messages NM Error Messages NMERR 132 MESSAGE: Link in exclusive use by another subsystem. (NMERR 132) CAUSE: Link has already been opened by another process. Returned by NMOPENLINK. Another process has this link opened. ACTION: Shut down the other process to free the link. CAUSE: A LINKMGR process which had this link previously did not close it when expected. This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NM Error Messages NMERR 138 MESSAGE: Unable to find DC/LDM in system I/O tables. (NMERR 138) CAUSE: The NSLINK ldev was not configured for the link in NMCONFIG.PUB.SYS when the system was started. ACTION: Ensure the NSLINK ldev is configured for the link used by NS, and reboot. More information may be found in the NMLG log file. NMERR 139 MESSAGE: Unable to find the specified linkname in system I/O tables.
NMS Error Messages NM Error Messages NMERR 148 MESSAGE: Specified item code is out of range. (NMERR 148) CAUSE: No information item corresponds to the given item code. Returned by NMLINKINFO. Bad software installation. ACTION: Make sure that the versions of NMS software and port translator software are compatible. See “Invalid Software Installation” at the beginning of this appendix. CAUSE: An internal error occurred. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NM Error Messages CAUSE: An internal error occurred. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 157 MESSAGE: DS/LDM open request failed. (NMERR 157) CAUSE: The request to open the DC/LDM failed. Returned by NMOPENLINK. Bad software installation. ACTION: Make sure that the versions of NMS software and port translator software are compatible. See “Invalid Software Installation” at the beginning of this appendix. CAUSE: An internal error occurred.
NMS Error Messages NM Error Messages NMERR 162 MESSAGE: Expects a name from one to eight characters long. (NMERR 162) CAUSE: Returned after entering LINKCONTROL command incorrectly. ACTION: Check the spelling and try again. NMERR 163 MESSAGE: Expects alphanumeric name starting with alphabetic. (NMERR 163) CAUSE: Returned after entering LINKCONTROL command incorrectly. ACTION: Check the spelling and try again. NMERR 164 MESSAGE: Expects a semicolon after link name parameter.
NMS Error Messages NM Error Messages NMERR 177 MESSAGE: Locked(!) HW Recover(!) HW Sick(!) HW Dead(!) Resource(!). Run diagnostics for more information. (NMERR 177) CAUSE: This message is likely caused by a hardware problem, and is a generic status request to the I/O manager returned with the specified bits set. One particular example is that the user has entered the LINKCONTROL command while the system is in power fail recovery. ACTION: Correct the problem and try again.
NMS Error Messages NM Error Messages CAUSE: An error occurred while accessing the specific I/O manager. ACTION: See “Submitting a CR” at the beginning of this appendix. NMERR 187 MESSAGE: Trace for linkname has been initiated with some exceptions : HPE status: INFO = ! subsystem ID = !. CAUSE: This error is often returned even though tracing has been enabled. ACTION: None. If this error occurs frequently, submit an CR. See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NM Error Messages ACTION: Look for one or more of NMERR 202 through 205 following this message, and take the remedial action as suggested. Read the text and comments for the original message specified in the message, and take the suggested actions. NMERR 202 MESSAGE: OPEN FSERR ! on NMCAT.PUB.SYS. (NMERR 202) CAUSE: Returned by NMPRINTERRMSG and usually followed by the text of the FSError message. ACTION: Correct the FOPEN problem and retry.
NMS Error Messages NM Error Messages NMERR 207 MESSAGE: Encountered FOPEN FSERR ! on !. (NMERR 207) CAUSE: Returned by a subsystem message-generating routine when it was unable to FOPEN the specified message catalog. The first parameter is the FSERR number. The second parameter is the message catalog name. This message is usually preceded by message NMERR 206. ACTION: Correct the FOPEN error and retry. NMERR 208 MESSAGE: Encountered GENMESSAGE error !.
NMS Error Messages NM Error Messages NMERR 221 MESSAGE: Total data length too large to return as integer. (NMERR 221) CAUSE: Returned by NMCONFSONINFO. The total data length associated with the path name and all its first level sons was greater than 32767 and could not be returned to caller. It is possible that the configuration file is corrupt. It is also possible that there is no error at all.
NMS Error Messages NMFS Error and Warning Messages NMFS Error and Warning Messages NMFSERR and NMFSWARN messages are produced by the NMS File Server (NMFILE.PUB.SYS). In most cases, they are accompanied by other messages (NMGRERRs or MPE File System errors). You should take the action recommended for the accompanying messages first. NMFSERR 1 MESSAGE: Unable to create new datafile.
NMS Error Messages NMFS Error and Warning Messages ACTION: See “File System Error” at the beginning of this appendix. NMFSWARN 6 MESSAGE: Datafile does not match user specified filecode. (NMFSWARN 6) CAUSE: This warning occurs when a caller of NMCONFOPEN tries to open a file that does not have a CONF file code either because the data file specified is not a configuration file (most likely), or because the data file label has been corrupted in some way.
NMS Error Messages NMFS Error and Warning Messages NMFSERR 10 MESSAGE: Directory linkage error in datafile. (NMFSERR 10) CAUSE: This error occurs when there is a failure in an FREADDIR in the MIDAS procedures shown in the table when the next link or the root cannot be found. Specifically, an unexpected end of file was found. ACTION: See “Corrupt Configuration File” at the beginning of this appendix. NMFSERR 11 MESSAGE: Unable to read directory entry in datafile.
NMS Error Messages NMFS Error and Warning Messages NMFSERR 18 MESSAGE: No data associated with this identifier. (NMFSERR 18) CAUSE: In all MIDAS procedures returning this, there is a failure of MIDASFINDENTRY. ACTION: See “File System Error” and “Corrupt Configuration File” at the beginning of this appendix. NMFSWARN 19 MESSAGE: Read truncated to capacity of data buffer. (NMFSWARN 19) CAUSE: This error occurs when caller of NMCONFGETDATA specifies a buffer length smaller than the actual data entry size.
NMS Error Messages NMFS Error and Warning Messages ACTION: See “Submitting a CR” at the beginning of this appendix. NMFSERR 25 MESSAGE: Identifier exceeds maximum permissible length. (NMFSERR 25) CAUSE: This is returned by MIDASPARSEPATH when the pathname is too long. No NMCONF procedure calls this intrinsic. ACTION: See “Submitting a CR” at the beginning of this appendix. NMFSERR 26 MESSAGE: Pathname length exhausted user specified buffer.
NMS Error Messages NMFS Error and Warning Messages NMFSERR 31 MESSAGE: Unable to open message catalog NMCAT.PUB.SYS. (NMFSERR 31) CAUSE: Returned by MIDASERRMSG if there is a failure to open NMCAT.PUB.SYS. See if this file is on the system. If it is, it might be corrupt. ACTION: See “Invalid Software Installation” at the beginning of this appendix. NMFSERR 32 MESSAGE: Unable to read message catalog NMCAT.PUB.SYS. (NMFSERR 32) CAUSE: Returned by MIDASERRMSG. The file might be corrupted.
NMS Error Messages NMGR Error and Warning Messages NMGR Error and Warning Messages NMGRERR 1 MESSAGE: Terminal is of incorrect type or cannot be opened. (NMGRERR 1) CAUSE: The user’s terminal is not a block mode terminal supported by VPLUS/3000. ACTION: Check the terminal type and strap settings. CAUSE: The user is attempting to run NMMGR from a batch job. Batch operation is not supported. ACTION: None. CAUSE: A terminal I/O or internal VPLUS/3000 error occurred.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 4 MESSAGE: That function is not implemented. (NMGRERR 4) CAUSE: The user pressed an invalid function key (with a blank label), or pressed the [ENTER] in a screen without a command window (currently only the OPEN FILE screen). ACTION: None. NMGRERR 5 MESSAGE: Not a valid or @. (NMGRERR 5) CAUSE: The user typed an unrecognizable command in the command window and pressed [ENTER].
NMS Error Messages NMGR Error and Warning Messages configuration file concurrently, and one renames or deletes a path which another is configuring. ACTION: Coordinate activity between users. CAUSE: NMMGR has encountered an unexpected condition in the configuration file. An internal error occurred. Submit a Change Request. See “Submitting a CR” at the beginning of this appendix. ACTION: Check the version of NMCONF. NMGRERR 10 MESSAGE: Unexpected type: NM config file corrupt or bad version.
NMS Error Messages NMGR Error and Warning Messages CAUSE: A file equation exists for NMMGRCAT.PUB.SYS. ACTION: Check for file equations using LISTEQ2.PUB.SYS and RESET if necessary. CAUSE: The table of commands in the NM catalog file NMCAT.PUB.SYS is corrupt or missing. File NMCAT.PUB.SYS is not a valid catalog file, or it has become corrupted. ACTION: Restore a backup copy of NMMGRF.PUB.SYS. CAUSE: The table of commands in the NM catalog file NMCAT.PUB.SYS is corrupt or missing. Set 7 of NMCAT.PUB.
NMS Error Messages NMGR Error and Warning Messages NMGRWARN 17 MESSAGE: No errors have yet occurred. (NMGRWARN 17) CAUSE: The user has gone to the ERRORS screen to check the last error, but no errors have occurred. ACTION: None. NMGRERR 19 MESSAGE: MPE command error. (NMGRERR 19) CAUSE: The user executed an MPE command (by entering the command preceded by a colon and pressing ENTER), and the command terminated in an error state.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 24 MESSAGE: Cannot compress NM configuration file. (NMGRERR 24) CAUSE: A file system error occurred. ACTION: Go to the Errors screen and check for a file system error (FSERR). Correct the error and try again. CAUSE: You are not the creator of the configuration file. ACTION: Go to the Errors screen and check for FSERR 94. If this error occurred, you can copy the file and then compress it, or ask the creator to compress the file.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 31 MESSAGE: That command is ambiguous — use more letters. (NMGRERR 31) CAUSE: The user typed an ambiguous command prefix in the command window and hit ENTER. ACTION: Make the prefix unambiguous by using more letters of the command. Check the NMMGR manual for unambiguous command prefixes. NMGRERR 32 MESSAGE: Maximum path depth exceeded. (NMGRERR 32) CAUSE: This error in an internal NMMGR error.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 36 MESSAGE: Invalid syntax for file name. (NMGRERR 36) CAUSE: The user attempted to OPEN or CREATE a configuration file with an invalid file name. ACTION: Check the spelling and syntax of the file name. NMGRERR 37 MESSAGE: ENTER executes commands: the command field is blank. (NMGRERR 37) CAUSE: The user pressed [ENTER] without putting a command in the command window. NMMGR uses [ENTER] ONLY for commands.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 42 MESSAGE: Internal error: Unexpected screen contents. (NMGRERR 42) CAUSE: This is an internal NMMGR error. NMMGR has encountered unexpected data from the screen. ACTION: Check to see that the correct version of NMMGR is installed. See “Submitting a CR” at the beginning of this appendix. NMGRERR 43 MESSAGE: Internal error: Unexpected data record length. (NMGRERR 43) CAUSE: This is an internal NMMGR error.
NMS Error Messages NMGR Error and Warning Messages ACTION: Submit a Change Request. See “Submitting a CR” at the beginning of this appendix. NMGRERR 49 MESSAGE: Internal error: The root node has parent node. (NMGRERR 49) CAUSE: This is an NMMGR internal error. NMMGR is scanning the configuration file off the boundary. ACTION: Submit a Change Request. See “Submitting a CR” at the beginning of this appendix. NMGRERR 50 MESSAGE: Internal error: The schema has an invalid format.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 54 MESSAGE: Internal error: Version checking routine failed. (NMGRERR 54) CAUSE: NMMGR checks version stamps of each subsystem in the configuration file at file open time. An error has occurred in the version checking routine. The configuration file may have corrupt data records or invalid paths. ACTION: Restore a backup copy of the configuration file if possible. NMGRERR 55 MESSAGE: Internal error: Version-flag checking failed.
NMS Error Messages NMGR Error and Warning Messages ACTION: Go to the Errors screen and check the VPLUS error messages to determine the specific error. Correct the error and try again. CAUSE: NMMGR was unable to retrieve information on the screen field via VPLUS utilities. The forms file NMMGRF.PUB.SYS and NMMGR are different versions, or the forms file is corrupt. ACTION: See “Invalid Software Installation” at the beginning of this appendix. NMGRERR 72 MESSAGE: Internal error: Data field alignment error.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 77 MESSAGE: Internal error: Data conversion ptr is out of bounds. (NMGRERR 77) CAUSE: This is an internal NMMGR conversion table error. ACTION: Submit a Change Request. See “Submitting a CR” at the beginning of this appendix. NMGRERR 78 MESSAGE: Internal error: Missing description for this screen. (NMGRERR 78) CAUSE: This is an NMMGR internal table error. The screen name is not in an internal conversion table. ACTION: Submit a Change Request.
NMS Error Messages NMGR Error and Warning Messages ACTION: Press the Delete key a second time to confirm the deletion. NMGRERR 84 MESSAGE: Cannot access the NMMGR help catalog. (NMGRERR 84) CAUSE: NMMGR was unable to open the NMMGR help catalog, NMMGRHLP.PUB.SYS. ACTION: Restore the NMMGR help catalog. NMGRERR 85 MESSAGE: Incomplete summary printed. (NMGRERR 85) CAUSE: Some configuration data could not be found or printed in the summary.
NMS Error Messages NMGR Error and Warning Messages NMGREWARN 89 MESSAGE: Warning: Incompatible selection. Press key again to confirm. (NMGRWARN 89) CAUSE: The user pressed a GO TO type function key on the DTS screen that was not compatible with the type of DTS subsystem specified on that screen. ACTION: Press the correct key or, to force selection of the incompatible subsystem, press the incompatible key a second time. NMGRERR 90 MESSAGE: Invalid IP Address; press Help for more information.
NMS Error Messages NMGR Error and Warning Messages the maximum page count. ACTION: Restore the configuration file with Reachable Network paths within the maximum page count. NMGRERR 95 MESSAGE: You must enter a configuration file name to open or create. (NMGRERR 95) CAUSE: The user pressed “Open Config” or “Create Config” but did not enter the configuration file name on the OPEN screen. ACTION: Supply the configuration file name.
NMS Error Messages NMGR Error and Warning Messages ACTION: See “Submitting a CR” at the beginning of this appendix. NMGRERR 101 MESSAGE: Internal error: Midas file number not in file table. (NMGRERR 101) CAUSE: The file number was not located in a search through the table. It is likely that a file number was changed in NMMGR but not entered in the table. ACTION: Exit NMMGR, and rerun NMMGR and try to observe what damage has been done. Repair if possible or restore the configuration file.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 106 MESSAGE: The file has been locked; cannot begin guided task. (NMGRERR 106) CAUSE: The transport is using the file NMMGR has open as the active configuration file. Guided configuration cannot be performed on an active configuration file (only guided dynamic updates can). ACTION: None. NMGRERR 107 MESSAGE: The file has been locked; Type ‘STOP’ to abort.
NMS Error Messages NMGR Error and Warning Messages ACTION: Go to the validation screen and validate NETXPORT or type exit again, this leaves the file unvalidated. NMGRERR 112 MESSAGE: DTS/LINK not validated. Type exit again to leave NMMGR. (NMGRERR 112) CAUSE: Data in the DTS or LINK subsystems was changed and DTS/LINK was not successfully validated afterwords. ACTION: Go to the validation screen and validate DTS/LINK or type exit again, this leaves the file unvalidated.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 119 MESSAGE: LU Number “!” on page ! is a duplicate. (NMGRERR 119) CAUSE: You have entered two LUs with the same LU name. These names may be on the same page (1 or 2) of LU data, or one name may be on page 1 and the other on page 2. ACTION: Make sure all LUs have unique names. NMGRERR 120 MESSAGE: If the Node Type is “2.0”, then the LU # is required. (NMGRERR 120) CAUSE: The user entered an LU Number out of the acceptable range of 1–255.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 126 MESSAGE: IP Subnet Mask of 255.255.255 is not allowed. (NMGRERR 126) CAUSE: An IP Subnet Mask of 255.255.255 was entered. This is not a legal mask. ACTION: Reenter the mask with a different value. NMGRERR 127 MESSAGE: If Node 2.1 Dependent LU Support, then LU #’s must be blank. (NMGRERR 127) CAUSE: If the PU Type is 2.1 and the PU Dependent Support is N, then there cannot be any LU Numbers associated with the LU names.
NMS Error Messages NMGR Error and Warning Messages ACTION: Check the IP address and make sure that the node portion is not all zeros. Enter a valid IP address. (Press the Help key for more information on entering a valid IP address.) NMGRERR 135 MESSAGE: IP Address with network portion of zero’s reserved. (NMGRERR 135) CAUSE: The network portion of the IP address is all zeros. ACTION: Check the IP address and make sure that the network portion is not all zeros. Enter a valid IP address.
NMS Error Messages NMGR Error and Warning Messages ACTION: Go to the validation screen and validate SNA/DS or type exit again to leave the file unvalidated. NMGRERR 141 MESSAGE: Subsystem(s) are not validated. Type ERR for more information. (NMGRERR 141) CAUSE: One or more of the subsystems in NMMGR have not been validated. ACTION: To see which subsystems have not been validated, type ERRORS in the command line and press the Enter key.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 205 MESSAGE: Aux file does not contain specified path. (NMGRERR 205) CAUSE: This is a guided configuration error caused when NMMGRCAT specifies a path in the auxiliary file that does not exist. ACTION: Copy NMAUX1.PUB.SYS from backup tape, and run NMAINT.PUB.SYS to make sure that the version of NMAUX1 is the same as the version of NMMGR. NMGRERR 206 MESSAGE: Path to subtree in user file does not exist.
NMS Error Messages NMGR Error and Warning Messages ACTION: Press a labeled function key. NMGRERR 215 MESSAGE: Illegal vplus field specified in Guided config. (NMGRERR 215) CAUSE: This is an internal guided configuration error that is caused by missing information in the forms file. ACTION: Restore NMMGRF.PUB.SYS from backup tape, and run NMMAINT.PUB.SYS. If this fails see “Submitting a CR” at the beginning of this appendix. NMGRERR 216 MESSAGE: Illegal Guided config variable name.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 224 MESSAGE: Missing ENDSELECT statement. (NMGRERR 224) CAUSE: This is an internal guided configuration error. ACTION: See “Submitting a CR” at the beginning of this appendix. NMGRERR 226 MESSAGE: Unknown statement in Guided Configuration driver. (NMGRERR 226) CAUSE: This is an internal guided configuration error. ACTION: Restore NMMGRCAT.PUB.SYS from backup tape. If this fails see “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NMGR Error and Warning Messages ACTION: Check the type of the network interface name by going to NETXPORT.NI (do a direct branch). File a CR (Change Request) if the type is labeled as UNKNOWN. (See “Submitting a CR” at the beginning of this appendix). Delete the unknown type and retry. NMGRERR 232 MESSAGE: Unable to open source NCONF file for copy. (NMGRERR 232) CAUSE: File does not exist or is the wrong version. ACTION: If in guided configuration, then NMAUXI.PUB.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 240 MESSAGE: Data must be entered and Saved before continuing. (NMGRERR 240) CAUSE: While running guided configuration, the user tried to press Next Screen without first pressing Update Data while at the path SNANODE.nodename. ACTION: Enter the correct data and press Update Data. NMGRERR 250 MESSAGE: The NI Name must be specified.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 257 MESSAGE: The NI name does not exist. Please specify a type to create it. (NMGRERR 257) CAUSE: At the Guided HP Configuration screen, the user entered a new NI name and pressed the Config Network key without specifying a type in the NI type field. The type must be specified if the NI does not already exist. ACTION: If you are configuring a new NI, enter the type of the new NI in the NI type field and press Config Network.
NMS Error Messages NMGR Error and Warning Messages ACTION: If an incorrect link name was entered, enter the correct link name and try again. If the link name is correct but the link has not yet been configured, enter the information for the link and press the Save Data key, then try again. NMGRERR 262 MESSAGE: Must be a number from 0 to 5.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 267 MESSAGE: The node name must be configured first. (NMGRERR 267) CAUSE: The node name was not configured. ACTION: Go to the Main screen and configure the node name. NMGRERR 268 MESSAGE: Missing IP address. (NMGRERR 268) CAUSE: The user neglected to enter the IP address in the appropriate field. ACTION: Enter the IP address and try again. NMGRERR 269 MESSAGE: You must enter a backup configuration file name.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 273 MESSAGE: The selected card number is not configured with a card type. (NMGRERR 273) CAUSE: At the DTC Configuration screen, the user selected a card number and pressed the Config Card key. No type was entered in the Type field associated with the selected card. ACTION: Fill in a card type in the Type field for the selected card and press the Save Data key. Type must be “D” for direct connect, “M” for modem, or “P” for PAD.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 278 MESSAGE: Missing quote; the IP address must be enclosed in quotes. (NMGRERR 278) CAUSE: While using the ADDVC command in maintenance mode, the user forgot to enter the IP address with either an opening or a closing quote. ACTION: Reissue the command with the correct IP address enclosed in quotes. NMGRERR 280 MESSAGE: The source path was not found. (NMGRERR 280) CAUSE: The path to the subtree to copy was not found.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 286 MESSAGE: Illegal path name identifier in destination path name. (NMGRERR 286) CAUSE:A path ID in the destination pathname is not legal. ACTION: Check the destination path id for typing mistakes. NMGRERR 287 MESSAGE: Invalid destination path — path too long. (NMGRERR 287) CAUSE: The source and destination paths must be the same length.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 301 MESSAGE: Internal NMMGR error: corrupt file likely. (NMGRERR 301) CAUSE: This is an internal error. ACTION: The directory file is probably corrupt and should be replaced by a copy from a backup tape. Restore both data and key files. See “Submitting a CR” at the beginning of this appendix. NMGRERR 302 MESSAGE: No next page of node names.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 307 MESSAGE: The current node name entry has been deleted by another user. (NMGRERR 307) CAUSE: The user attempted to delete or update a network address, or path data, but another user who is modifying the same directory file has just deleted the entry. ACTION: Coordinate update activities with other user(s). NMGRERR 308 MESSAGE: Duplicate IP address.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 325 MESSAGE: Cannot open source file / wrong file type. (NMGRERR 325) CAUSE: Maintenance mode interface: An informative message issued when an invalid file was specified in a MERGEDIR command. Possible causes are: • Nonexistent file • Wrong type of file (not directory or configuration file) • Security violation • A system file name was given • Other file system problem ACTION: Correct the filename.
NMS Error Messages NMGR Error and Warning Messages from a backup tape. If the problem still exists, see “Submitting a CR” at the beginning of this appendix. NMGRERR 330 MESSAGE: Extra data was specified for this command. (NMGRERR 330) CAUSE: The user specified too much data. ACTION: Check syntax of command or type “help” for more information. NMGRERR 332 MESSAGE: A key operator was already specified. (NMGRERR 332) CAUSE: The user specified both a ;LOCAL and ;GLOBAL key operator.
NMS Error Messages NMGR Error and Warning Messages ACTION: Check syntax of the command or type “help” for more information. NMGRERR 338 MESSAGE: Unknown or extra keyword parameter specified. (NMGRERR 338) CAUSE: This occurs in DELETENODE or MERGEDIR when the keyword local, global, keep, nokeep, or timestamp is spelled incorrectly or you have a duplicate type of keyword. DELETENODE only allows local or global keywords. ACTION: Check spelling of keywords. Check for duplicate keyword types.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 345 MESSAGE: org segment in node name must be from 1 to 16 chars in length. (NMGRERR 345) CAUSE: The org portion of the node name is the incorrect length. ACTION: Fix the length of the org in name.domain.org. NMGRERR 346 MESSAGE: Each segment in the node name must begin with an alphabetic char. (NMGRERR 346) CAUSE: Each segment in node name (name,domain, and org) must begin with an alphabetic character.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 353 MESSAGE: The path specified does not point to a paged data screen. (NMGRERR 353) CAUSE: You did not access a paged data screen which has only one page. ACTION: Check the path specified in the PATHCONF command. NMGRERR 354 MESSAGE: Entry selected is empty. (NMGRERR 354) CAUSE: User selected an empty selection from the entry selection window. ACTION: Select an existing entry.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 360 MESSAGE: Domain screen can be accessed only after an NS nodename addition. (NMGRERR 360) CAUSE: User can access the domain screen only after using the add function key to add an NS nodename. ACTION: Follow the instructions in “Cause.” NMGRERR 361 MESSAGE: Select an entry between 1 and 8, or enter the full node name. (NMGRERR 361) CAUSE: User pressed a key which required that an entry selection be provided.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 367 MESSAGE: User is not allowed to merge individual domain entries. (NMGRERR 367) CAUSE: The MERGEDIR command not permit the merging of a single domain entry. However, you can merge domain entries as a group, such as all the global domains or all the local domains. ACTION: None. NMGRERR 368 MESSAGE: User must enter: Node Name, Type, Global, and Enable settings. (NMGRERR 368) CAUSE: User has selected a function that needs the above information.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 381 MESSAGE: Problem accessing the new (expanded) directory file. (NMGRERR 381) CAUSE: Maintenance mode interface: An operation on a COPY of the existing directory file could not be performed. The possible operations are: • FOPEN the file (new) as a KSAM file (opened with a temporary file name “ZTMPxxxx”). • FWRITE to the file. • FCLOSE with the save option on. • FOPEN the data file in copy mode. • FREADLABEL the data file.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 383 MESSAGE: Cannot specify a negative number for expansion. (NMGRERR 383) CAUSE: Maintenance mode interface: The user gave a negative number of records to expand the file. ACTION: Supply a positive number of records. NMGRERR 384 MESSAGE: Cannot open command file “NMMGRCMD”. (NMGRERR 384) CAUSE: The command file NMMGRCMD could not be opened. ACTION: Check for any file equations set for “NMMGRCMD”.
NMS Error Messages NMGR Error and Warning Messages number you are trying to access. Make sure you are not trying to use Vplus field numbers to access the field. NMGRERR 390 MESSAGE: Path not specified, or path specified does not exist. (NMGRERR 390) CAUSE: PATHCONF was not previously issued. ACTION: Check to see if you set the path with the PATHCONF command.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 401 MESSAGE: Record size of nodelist file too small; must be >= 80 bytes. (NMGRERR 401) CAUSE: The record size of the nodelist file is too small to be used. ACTION: If creating the nodelist file using the LISTDIR command, then do not include a ;REC= parameter in the file equation. Copy the nodelist file into a file with a larger record width. NMGRERR 402 MESSAGE: Filecode of nodelist file non zero.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 409 MESSAGE: FREAD failed trying to read from nodelist file. (NMGRERR 409) CAUSE: Could not read sequentially from the nodelist file. ACTION: See the accompanying file system error message for resolution. NMGRERR 410 MESSAGE: Cannot gain access to the stream file. (NMGRERR 410) CAUSE: A check to verify that the stream file does not already exist could not be completed. ACTION: See the accompanying file system error message for resolution.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 416 MESSAGE: Error converting a catalog entry into a numeric value. (NMGRERR 416) CAUSE: Internal error. ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see “Submitting a CR” at the beginning of this appendix. NMGRERR 417 MESSAGE: Catalog entry value not in range -32768..32767. (NMGRERR 417) CAUSE: Message catalog NMMGRCAT.PUB.SYS is incorrect. ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 500 MESSAGE: Missing equal sign. (NMGRERR 500) CAUSE: An equal sign was missing in the command syntax. ACTION: Reenter the command with the proper syntax. NMGRERR 501 MESSAGE: Missing or invalid pathname parameter. (NMGRERR 501) CAUSE: The syntax of the command requires a pathname parameter. ACTION: Check pathname and reissue the command. NMGRERR 502 MESSAGE: Missing or invalid field number.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 509 MESSAGE: The new data is larger than the field size. (NMGRERR 509) CAUSE: WRITECONF error. ACTION: Check to see that you are accessing the correct field, or reduce the size of the data you are entering. NMGRERR 510 MESSAGE: There are Vplus field edit errors. (NMGRERR 510) CAUSE: UPDATECONF error. ACTION: Examine all WRITECONF statements before the screen associated with the UPDATECONF which caused the error.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 552 MESSAGE: Extra data was specified in the command line. (NMGRERR 552) CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a range of logical devices, you entered more data than was expected in the command line. ACTION: Reenter the command with the parameters specified in the correct format (LDEV [xxx[/yyy]], where xxx and yyy are integers).
NMS Error Messages NMGR Error and Warning Messages to correct the card configuration, then reenter the SUMMARYCONF command. NMGRERR 557 MESSAGE: That Port is not configured in the DTC and Card specified. (NMGRERR 557) CAUSE: You specified an incorrect port number while using the SUMMARYCONF command to obtain a DTS critical summary report on a specific card in a specific DTC. Either the DTC does not exist, the card specified is not configured for that DTC, or the port is not configured for that card.
NMS Error Messages NMGR Error and Warning Messages NMGRERR 561 MESSAGE: The port number must be an integer from 0 to 7. (NMGRERR 561) CAUSE: While using the SUMMARYCONF command to obtain a DTS critical summary report on a specific port, you entered an invalid port number. Port numbers must be entered as integers, from 0 to 7. ACTION: Reenter the command with a port number specified in the valid range, 0 through 7. NMGRERR 562 MESSAGE: Expected a parameter after the delimiter.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVER Messages, Errors and Warnings The following messages may be returned from the NMMGRVER utility (n represents the message number). Note that NMMGRVER may also provide you with messages which tell you that the operation has completed successfully. (NMMGRVERWARN n) messages are displayed when conversion failed and the file is not changed. (NMMGRVERERR n) messages are displayed when conversion has failed and the file may be changed.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVER WARN 3 MESSAGE: INTERNAL ERROR: cannot convert file. (NMMGRVERWARN 3) CAUSE: The configuration file is corrupted. One or more of the following situations were detected in the file. • Paths are missing. • Version stamps are missing or are incorrect. • A LINKCONF detail data record has unexpected record length. NOTE: This corrupted configuration file is not changed. ACTION: Restore an old configuration file if possible and rerun NMMGRVER.
NMS Error Messages NMMGRVER Messages, Errors and Warnings 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 Change Request. See “Submitting a CR” at the beginning of this appendix. CAUSE: An unexpected internal error has occurred.
NMS Error Messages NMMGRVER Messages, Errors and Warnings Install the newer version of NMC and run the newer NMMGRVER if needed or, restore an old configuration file if possible and rerun NMMGRVER. NMMGRVER WARN 12 MESSAGE: File NMCONFIG.PUB.SYS couldn’t be opened. (NMMGRVERWARN 12) CAUSE: NMCONFIG was already open for exclusive access, or MIDASOPEN detected an error. ACTION: Check NMCONFIG and retry. NMMGRVERERR MESSAGE: 13 Error during merge of configuration files.
NMS Error Messages NMMGRVER Messages, Errors and Warnings incorrect. This could indicate that an incorrect cell was accessed or that the user is trying to convert an invalid configuration file. The cell is not converted. ACTION: Verify that the original file was a valid version. Using another tool, examine the cell data and verify the data. Since the cell was not touched, the data may have to be entered manually. NMMGRVERERR MESSAGE: 16 Conversion failure.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVERERR MESSAGE: Unable to purge LINKCONF subtree (NMMGRVERERR 20) 20 CAUSE: Internal error. File has been converted. However, in the attempt to purge the subtree LINKCONF, the NM intrinsic failed. 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, see “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVERERR MESSAGE: Merge failed. Error in NMCONFIG.PUB.SYS 26 (NMMGRVERR 26) CAUSE: During the merge of NMCONFIG and the file to be converted, an error was found in one of the paths in NMCONFIG. ACTION: 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 Change Request. See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVERERR MESSAGE: 60 Unable to add path. Path: ! Midasstat = ! (NMMGRVERERR 60) CAUSE: An internal error occurred while adding the displayed path. ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Change Request. See “Submitting a CR” at the beginning of this appendix. Note: not user solvable.
NMS Error Messages NMMGRVER Messages, Errors and Warnings ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Change Request. See “Submitting a CR” at the beginning of this appendix. Note: not user solvable. A qualified HP representative should check the midasstat value to determine what the problem is and take appropriate action. NMMGRVERERR MESSAGE: 64 Unable to get son path.
NMS Error Messages NMMGRVER Messages, Errors and Warnings action. NMMGRVERERR MESSAGE: 67 Unable to update data. Path: ! Midasstat = ! (NMMGRVERERR 67) CAUSE: Internal problem updating data in configuration file. ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Change Request. See “Submitting a CR” at the beginning of this appendix. Note: not user solvable.
NMS Error Messages NMMGRVER Messages, Errors and Warnings 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 Change Request.
NMS Error Messages NMMGRVER Messages, Errors and Warnings 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 Change Request.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVERERR MESSAGE: An error has occurred during NETXPORT CONVERSION. 85 (NMMGRVERERR 85) CAUSE: An error occurred during the NETXPORT 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.
NMS Error Messages NMMGRVER Messages, Errors and Warnings 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 Change Request. See “Submitting a CR” at the beginning of this appendix. NMMGRVERERR MESSAGE: Duplicate host luname (!) found in node !.
NMS Error Messages NMMGRVER Messages, Errors and Warnings NMMGRVERERR MESSAGE: The default LAPB LINK physical path is 24; User 93 modification may be needed. (NMMGRVERERR 93) CAUSE: The default physical path has been set to 24, which may be correct for the given system. ACTION: Run NMMGR, confirm this value, and modify it as needed. NMMGRVERERR MESSAGE: An error has occurred during APPC CONVERSION. 94 (NMMGRVERERR 94) CAUSE: During the APPC conversion process an error occurred.
NMS Error Messages ND Error Messages ND Error Messages NDIERR messages are produced by errors from the Network Directory intrinsics. In most cases, they are accompanied by other messages (NMGRERRs or MPE File System errors). You should take the action recommended for the accompanying messages first. NDIERR 001 MESSAGE: Directory file not open. (NDIERR 001) CAUSE: No directory file was opened. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages ND Error Messages NDIERR 010 MESSAGE: Path report list length cannot be negative. (NDIERR 010) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 011 MESSAGE: Path report list length > than ND’CREATE maximum. (NDIERR 011) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 012 MESSAGE: Duplicate node name in directory — cannot add new entry.
NMS Error Messages ND Error Messages increase the file to desired size. If this fails, see “Submitting a CR” at the beginning of this appendix. NDIERR 042 MESSAGE: Maximum path report list length negative; must be > 0. (NDIERR 042) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 043 MESSAGE: Maximum path report list length too large; must be <= 500. (NDIERR 043) CAUSE: This is an internal error.
NMS Error Messages ND Error Messages NDIERR 080 MESSAGE: Directory file not open. (NDIERR 080) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 081 MESSAGE: Item number invalid; must be 1, 2, 3, 4, 5, or 6. (NDIERR 081) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 082 MESSAGE: Requires Node Manager or Network Administrator capability.
NMS Error Messages ND Error Messages NDIERR 103 MESSAGE: Access mode invalid; must be 0 or 1. (NDIERR 103) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 104 MESSAGE: Share option invalid; must be 0, 1, 2 or 3. (NDIERR 104) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 105 MESSAGE: FLOCK failed — internal error. (NDIERR 105) CAUSE: This is an internal error.
NMS Error Messages ND Error Messages NDIERR 120 MESSAGE: One or more required parameters are missing. (NDIERR 120) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 121 MESSAGE: Directory file not open. (NDIERR 121) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 122 MESSAGE: Relop parameter invalid; must be 0, 1 or 2. (NDIERR 122) CAUSE: This is an internal error.
NMS Error Messages ND Error Messages NDIERR 129 MESSAGE: FCONTROL/FUNLOCK failed — internal error. (NDIERR 129) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 130 MESSAGE: Requires Node Manager or Network Administrator capability. (NDIERR 130) CAUSE: User does not have Node Manager or Network Administrator capabilities. ACTION: Change user capabilities. NDIERR 131 MESSAGE: Select parameter invalid; must be 0, 1 or 2.
NMS Error Messages ND Error Messages NDIERR 145 MESSAGE: FREAD failed — corrupt file likely. (NDIERR 145) CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a backup tape. If this fails, see “Submitting a CR” at the beginning of this appendix. NDIERR 146 MESSAGE: FCONTROL/FUNLOCK failed — internal error. (NDIERR 146) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix.
NMS Error Messages ND Error Messages NDIERR 163 MESSAGE: FREADBYKEY failed — corrupt file likely. (NDIERR 163) CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a backup tape. If this fails, see “Submitting a CR” at the beginning of this appendix. NDIERR 164 MESSAGE: FREAD failed — corrupt file likely. (NDIERR 164) CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a backup tape.
NMS Error Messages ND Error Messages NDIERR 191 MESSAGE: Error in Network Directory intrinsic; check for error status. (NDIERR 191) CAUSE: This is an internal error. ACTION: Refer to the accompanying NMCONF error message. If the associated error is number 58, then the configuration file to merge from does not have any directory data in it. The file must first be read by the network transport by bringing up the transport in order to extract the directory data.
NMS Error Messages ND Error Messages NDIERR 203 MESSAGE: File recovery: FWRITE to temporary command file failed. (NDIERR 203) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 204 MESSAGE: File recovery: FCLOSE of temporary command file failed. (NDIERR 204) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 205 MESSAGE: File recovery: CREATEPROCESS of KSAMUTIL.PUB.SYS failed.
NMS Error Messages ND Error Messages ACTION: Attempt manual recovery of the file using KSAMUTIL.PUB.SYS or restore the data and key files from a backup tape. NDIERR 220 MESSAGE: FPOINT to header record failed — corrupt file likely. (NDIERR 220) CAUSE: The file is corrupt, empty, or is not a network directory file. ACTION: Restore the data and key files from a backup tape. NDIERR 221 MESSAGE: FREADC of header record failed — corrupt file likely.
NMS Error Messages ND Error Messages NDIERR 251 MESSAGE: Path report list length too small to support minimal report. (NDIERR 251) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 252 MESSAGE: Domain report in path report list too short (< 6 bytes). (NDIERR 252) CAUSE: This is an internal error. ACTION: See “Submitting a CR” at the beginning of this appendix. NDIERR 253 MESSAGE: Version of domain report in path report list <> 0.
NMS Error Messages ND Error Messages NDIERR 271 MESSAGE: FFINDBYKEY failed — corrupt file likely. (NDIERR 271) CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a backup tape. If this fails, see “Submitting a CR” at the beginning of this appendix. NDIERR 272 MESSAGE: FREAD failed — corrupt file likely. (NDIERR 272) CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a backup tape.
NMS Error Messages FMT Error Messages FMT Error Messages Listed are the messages that are generated by the Link Trace Formatter. They are displayed on the user terminal when running NMDUMP. If you must submit a CR or call your HP representative, please copy the error exactly as it appears on the terminal; it will make determining the CAUSE of the problem easier. These messages are not logged. The messages are listed in numerical order according to the error number.
NMS Error Messages FMT Error Messages FMTERR 999 MESSAGE: SUBSYSxxTRACEFORMAT CM STUB ERROR (nnn,sss) FROM HPSWTONMNAME UNABLE TO CALL NM TRACE FORMATTER ROUTINE (FMTERR 999) CAUSE: The CM Stub could not call the named NM WAN Trace Formatter routine for subsystem “xx” in the system library XL.PUB.SYS. ACTION: Incorrect software installation to run Native-Mode Trace Formatters. This could also be caused by incorrect privilege levels.
NMS Error Messages FMT Error Messages 4028 MESSAGE: Range error at position shown; other values accepted if allowed CAUSE: One of the numbers you entered was out of range; a “^^” indicator appears below the illegal number. The number entered was probably much too large. ACTION: The bad value was not accepted. Press the Return key to keep the other values on the same line, or else retype the entire input using only legal values.
NMS Error Messages FMT Error Messages 4033 MESSAGE: Number of inputs exceeds storage capacity, rest ignored CAUSE: Bug in Trace Formatter numeric input processing. The formatter could not process all the numbers entered by the user. ACTION: Check your input and retype if necessary. If the problem continues to occur, submit an HP Change Request form against the Trace Formatter, specifying the input you tried and the subsystem you were trying to format. A temporary solution might be to type fewer numbers.
NMS Error Messages FMT Error Messages 306 Appendix A
Index A abbreviations for screen mode commands, 27 ADDCONF command, 77 adding records to a file, 61 ADDLDEV command, 78 ADDLU command, 80 ADDNODE command, 81 ADDVC command, 84 B backup configuration file, 17 block mode, 40 branching, 33 brother branching, 33 brother screens, 33 brothers, 34 BSC subsystem, 16 C capabilities required, 40 CARDCONF command, 87 changing the backup file name, 44 command ADDCONF, 77 ADDLDEV, 78 ADDLU, 80 ADDNODE, 81 ADDVC, 84 CARDCONF, 87 COMPRESS, 27 COMPRESSCONF, 88 CONFIGURATI
Index CONTINUE command, 89 COPYCONF command, 90 copying a configuration subtree, 65, 90 COPYSUB command, 27 creating a configuration file, 42 creating a directory on a remote node, 73 creating a network directory file, 45 D data fields, 29 data flag, 26 data record, 32 Datacommunications and Terminal Controller, 47 default configuration file name, 43 default network directory file name, 45 DELETECONF command, 92 DELETENODE command, 93 deleting a configuration subtree, 92 deleting a node from the directory
Index Network Services, 16 NEXT command, 28, 33 next key labels, 52 Next Page key, 31 NICONF command, 107 NIGUIDE command, 28 NIUPDATE command, 28 NMDUMP definition of, 20 NMMAINT definition of, 19 output, 132, 146 running, 132 NMMGR, 15 definition of, 16 entering data, 32 getting help, 35 operating modes, 18 requirements for running, 40 running, 41 screens, 24 tree structure, 56 NMMGR commands entering, 27 maintenance mode, 74 screen mode, 27 NMMGR screens, 24 NMMGRCMD command, 28 NMMGRVAL definition of,
Index S sample configuration file, 43 Save Data key, 30 screen Compress, 60 Error Information, 37 Open Configuration/Directory File, 42 Output Configuration File, 55 Utility, 54 Validate Configuration File, 63 screen interface, 18 screen mode, 18 screen number, 26 screen title, 26 screens, 24 select screens, 29 selecting a configuration path, 46 selecting data screens to print, 58 selecting menu items, 29 serial device configuration, 47 service request, 19, 130 SNA subsystem, 16 softkeys, 29 software versi
