Using the Node Management Services (NMS) Utilities HP 3000 MPE/iX Computer Systems Edition 6 32022-90053 E1098 Printed in: 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Backup Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . The Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . The Network Directory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Modes. . . . . . .
Contents 4 3. Using NMMGR in Screen Mode Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting NMMGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a Configuration or Directory File. . . . . . . . . . . . . . . . . . . . . . Creating a New Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 EXITVALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 EXITWARN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 EXPANDDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents A. NMS Error Messages Resolving Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invalid Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Incompatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Insufficient MPE Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Corrupt Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File System Errors . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 8
Tables Table 2-1. NMMGR Screen Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Table 5-1. NMMGR Maintenance Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Table 7-1. General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 Table 7-2. Log Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This manual documents functionality for the MPE/iX 6.0 Release. 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).
Chapter 2, “Basics of NMMGR,” describes the basic functions of the Node Management Configuration Manager (NMMGR) in detail. Use this chapter to gain an understanding of how NMMGR works and how to navigate through NMMGR screens. Chapter 3, “Using NMMGR in Screen Mode,” tells you how to use NMMGR’s screen mode interface to begin the configuration process for your system’s terminal connections or networking products.
For NS 3000/iX Links and Services HP 3000/iX Network Planning and Configuration Guide NS 3000/iX NMMGR Screens Reference Manual NS 3000/iX Operations and Maintenance Reference Manual Using NS 3000/iX Network Services NS 3000/iX Error Messages Reference Manual NetIPC 3000/XL Programmer’s Reference Manual LAN Cable and Accessories Installation Manual Central Bus Programmable Serial Interface Installation and Reference Manual 13
1 Introduction This chapter introduces you to the Node Management Services Utilities for MPE/iX systems. These programs, installed on your HP 3000 Series 900 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 you use 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 3000 Series 900 computers.
Introduction NMMGR some changes, however, that you may make while the network is operating. Refer to your product-specific manuals for details on changes that can be made online. The Backup Configuration File You 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.
Introduction NMMGR Operating Modes NMMGR includes two interfaces that you can use 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 3000 Series 900 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 Program Name and Version Number The program name and version number are always displayed in a protected field at the top of the screen. (Protected means that information cannot be typed into the field.) 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.
Basics of NMMGR Common Screen Elements Command Window Each screen includes a field labeled Command: that is located below the message field. This field, called the command window, accepts commands rather than accepting data. This is an unprotected field and is displayed in half-bright inverse video. You can enter the following types of commands in this window: • NMMGR commands. The valid screen mode commands and their meanings are shown in Table 2-1.
Basics of NMMGR Common Screen Elements NMMGR Command Action COP[YSUB] Transfers to the Configuration Subtree Copy screen. ER[RORS] Displays the Error Information screen. EX[IT] Exits from NMMGR (same as QUIT). H[ELP] or ? Calls up help function. (See “Getting Help” in this chapter.) M[AIN] Transfers to the Main screen. 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.
Basics of NMMGR Common Screen Elements Path Name On most screens that can be reached by direct path branching, the path name used to reach the screen is displayed in the upper-left corner of the main screen window. The path name consists of all the screen names between the root (top of the structure) and the current screen, with the names separated by periods. Data Fields and Menu Choices Data can be entered only into unprotected fields.
Basics of NMMGR Common Screen Elements purpose of the screen you are viewing. Some of the more common function keys are described here. For many screens, you can find information on that screen’s function keys in the Help information associated with the screen. 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].
Basics of NMMGR Common Screen Elements Save Data Key Screens with data entry fields have a [Save Data] key, usually as the third key from the right-hand side. Pressing this key creates or modifies the data record and causes the data entered in the screen to be transferred to the configuration file. If the Data Flag is “N”, pressing [Save Data] will cause the Data Flag to change to “Y”. “Go To” Keys Some keys take you to a specific screen.
Basics of NMMGR Entering Data Entering Data You enter data into NMMGR by typing the appropriate information in the data entry fields on a screen and pressing the [Save Data] key. (You can also use the [ENTER] key, 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 Creating a New Configuration File If you want to create a new configuration 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 Configuration 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 Opening a Configuration or Directory File 3. Copy the appropriate sample file into the empty CONFIG file. The following is a sample “copy” command: FCOPY FROM = NMSAMP1.PUB.SYS; TO = *CONFIG; NEW; NOUSER LABELS 4. When you are ready to proceed with configuration, run NMMGR and open the configuration file you just created. See the instructions that follow for “Opening a Configuration File.” You may choose to copy your source file to a name other than NMCONFIG.PUB.
Using NMMGR in Screen Mode Opening a Configuration or Directory File Step 3. Press the [Open Config] key. The Main screen will appear and you can proceed with subsystem configuration. The fields on each screen show the values currently entered for the configuration file you opened. 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.
Using NMMGR in Screen Mode Opening a Configuration or Directory File entered for the network directory file you have opened. (See the Configuration Guide for the subsystem you are configuring for more information on configuring the network directory.
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. Figure 3-2 Main Screen NOTE NS/SNA is no longer offered as a product and has been removed from the Corporate Price List. The product is obsolete with no plans for support.
Using NMMGR in Screen Mode Selecting a Configuration Path Step 2. In the field next to the question Are you using OpenView DTC Manager?, enter a “Y” if you are using PC-based network management for this node, enter an “N” if you are using host-based network management. If you are using PC-based network management, an OpenView workstation must be present on the network. Step 3. In the field next to the question Do you have X.
Using NMMGR in Screen Mode Selecting a Configuration Path Figure 3-3 Host Configuration Screen 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 Configuring NS 3000/iX The NS 3000/iX product consists of NS 3000/iX Network Services and NS 3000/iX links. NS 3000/iX Network Services contain software that allows you to access data, initiate processes, and exchange information between all the systems on a network. NS 3000/iX links provide connections between systems (either HP 3000s or personal computers) in a network.
Using NMMGR in Screen Mode Selecting a Configuration Path • To perform guided configuration, press the key labeled [Guided Config] and refer to the HP 3000/iX Network Planning and Configuration Guide for information. • To perform unguided (manual) configuration, press the key labeled [Unguided Config] and refer to the NS 3000/iX NMMGR Screens Reference Manual for information. NOTE Hewlett-Packard strongly recommends using guided configuration whenever you need to initially configure a network interface.
Using NMMGR in Screen Mode Selecting a Configuration Path Guided configuration is a procedure that automates part of the configuration process. It “guides” you through the configuration screens for a specific task. It assumes and supplies default values wherever possible to furnish most of the configuration file’s data. When you run guided configuration, you use only a minimal number of configuration screens.
Using NMMGR in Screen Mode Selecting a Configuration Path • Configure or modify a network interface. If you choose to create or modify an NS configuration using unguided (manual) configuration, you must take care that you know which screens you need to use to completely create or modify a configuration. The unguided nature of manual configuration makes it possible to get “lost” or to miss some necessary screens entirely. Under most circumstances, HP recommends that you use guided configuration.
Using NMMGR in Screen Mode Selecting a Configuration Path From this screen, you can choose any of the IBM subsystems for configuration by pressing the appropriate function key. You can also choose to configure logging for all of the IBM subsystems, or you can choose SNANODE configuration (SNA node, SDLC link, X.25 link, and token ring link). The HP-IBM Configuration screen presents you with more choices than there are available function keys.
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 You can select the data screens you want to list by entering one or more selections in the print data subsystem selection fields on the Output 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).
Using NMMGR Utility Screens Output Configuration File Screen Print Summary The [Print Summary] key allows you to print all the configuration data for the chosen subsystem on the Output Configuration File menu. This is a listing of information that is contained in your configuration file. By default, output is sent to the device LP. You can redirect the output by using a file equation for the formal file designator FORMLIST.
Using NMMGR Utility Screens Output Configuration File Screen Print Subtree The [Print Subtree] key allows you to print the NMMGR data screens for a specified subtree. By default, output is sent to the device LP. You can redirect the output by using a file equation for the formal file designator FORMLIST. To define the subset of screens that you want to print, enter the path name of the topmost screen of the subtree you are selecting in the field provided under “Print Subtree.
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 reuse. By compressing the file, you cause all data to be stored in a contiguous block of records and all unused records to be located at the end of the file. Thus, compressing a file enables you to determine the actual number of free records in a file before adding or deleting records.
Using NMMGR Utility Screens Validate Configuration File Screen Validate Configuration File Screen The Validate Configuration File screen shown in Figure 4-7 vallows you to test the validity of a specified subsystem configuration. (You can also use the VALIDATECONF maintenance mode command to perform this function. See Chapter 5, “Using NMMGR in Maintenance Mode,” for more information on the maintenance mode commands.) You reach this screen by pressing the [Go To VALIDATE] key at the Utility screen.
Using NMMGR Utility Screens Validate Configuration File Screen 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 The source file is the name of the file that the data will be copied from. If you are copying a subtree from the current configuration file to another location within the same file, you can leave both the Source file and the Destination file fields blank. The source path specifies the path name of the topmost screen in the subtree that you want to copy. All screens below the top screen will be copied.
Using NMMGR Utility Screens Configuration Subtree Copy Screen example, you wish to change the fifth path identifier, then the fifth slot in the destination path should contain data. Only those parts of the path name that were designated by the user can differ among corresponding identifiers in the source and destination paths. User-selected types must match.
Using NMMGR Utility Screens Configuration Subtree Copy Screen Figure 4-9 Specified Subtree 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 NOTE When subtrees contain several records, copies that occur over DSLINE connections will take considerably longer than copies between two local configuration files. It is several times faster to DSCOPY the configuration file to the destination node, then perform the subtree copy between two local configuration files.
Using NMMGR Utility Screens Configuration Subtree Copy Screen 72 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 Running Maintenance Mode from a Batch Job You can also access maintenance mode directly from a batch job by running NMMGR from a stream job or by running NMMGR with a file 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.
Using NMMGR in Maintenance Mode Using Maintenance Mode your network directory. Once this information is entered into your directory, you will be able to log on to the new node and merge your entire directory to create a version of this directory on the new node.
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 Command Action LISTDIR Lists the contents of a network directory. LISTLDEV Lists LDEVs for a DTC card in a format compatible with ADDLDEV. LISTLU Lists LUs in a format compatible with ADDLU. 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.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Command NOTE Action UPDATECONF Updates the current path in the configuration file. VALIDATECONF Validates subsystem configuration. VERSIONCONF Checks whether the specified version number matches NMMGR’s current version number. WRITECONF Writes data to individual fields of the current path in the configuration file.
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 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 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 LK circuit number Example Do not permit inbound or outbound connections (placeholder entry). The permanent virtual circuit number supplied with your network subscription or assigned by your network administrator. 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.SYS NMMGR> ADDVC Enter node name (or press return to exit): ADDVC> NODE1.
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 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 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: ASTRO.MKT.IND UPDATED 04/20/90 11:09 AM POGO.DCL.
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 PURGELDEV> 100, 1,; PURGELDEV> 101, 1; PURGELDEV> 102, 1; PURGELDEV> 201, 2, NMMGR> 118 Chapter 5
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 120 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 address key The name tag used to relate a node name and IP address from the network directory with a switched or permanent virtual circuit address configured under an X.25 NI in the local configuration file. The name may 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.
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 124 Chapter 5
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 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 (“ ”).
Using NMMGR in Maintenance Mode WRITECONF 132 Chapter 5
6 NMMAINT This chapter describes the Node Management Services Maintenance Utility (NMMAINT). NMMAINT is a utility 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 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. 1985 NMMAINT then lists the version identification numbers for each software module and information for each subsystem. As shown in the example below, the NMMAINT utility displays version information for the subsystems of the products actually installed on your system.
NMMAINT Running NMMAINT SL procedure: SL procedure: SL procedure: SL procedure: SL procedure: SL procedure: SL procedure: CM program file: CM program file: CM program file: NM program file: NM program file: CM program file: CM program file: Catalog file: NM program file: SL procedure: SL procedure: SL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NMVERS00 NMVERSCSL NMVERS01 NMLOGSLVERS NMLOGDATAVERS NMVERS04 MWRITEVERS NMMAINT.PUB.SYS NMFILE.
NMMAINT Running NMMAINT NM program file: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: NL procedure: Catalog file: CM program file: NL procedure: NL procedure: NM program file: Catalog file: SL procedure: SL procedure: NL procedure: SL procedure: NL procedure: SL procedure: NM program file: SL procedure: NL procedure: NL procedure: NL procedure: SL procedure: SL procedure: NL procedure: SL procedure: NL procedure: SL procedure: NL procedure: NL procedure: NL procedure:
NMMAINT Running NMMAINT NM program file: SL procedure: SL procedure: SL procedure: SL procedure: SL procedure: Catalog file: SL procedure: NL procedure: NL procedure: CM program file: CM program file: CM program file: NL procedure: NL procedure: CM program file: CM program file: NL procedure: NL procedure: NL procedure: NL procedure: NM program file: NM program file: CM program file: SL procedure: SL procedure: CM program file: NL procedure: Catalog file: SL procedure: NL procedure: CM program file: NL pro
NMMAINT Running NMMAINT Link Support Services 32098-20015 overall version = C.01.
NMMAINT Running NMMAINT If the modules were correct when installed, only unusual circumstances such as a reload, a disk problem, or a system failure would result in missing or invalid modules. Restore a known valid version of the modules in error. Question marks displayed for the overall version number indicate that the fix levels of the individual modules do not match.
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 142 Chapter 7
NMDUMP To Run NMDUMP To Run 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. • Most options toggle between two possible values, like YES or NO and ON or OFF. • Some require you to enter an option number which then displays an additional menu and prompt. • Several options prompt you to enter the numbers of certain items. The following tables show the options for logging and tracing.
NMDUMP Formatting Options Table 7-1 Subsystem 802.3, 802.5, SDLC, LAP-B, RJE/BSC, FDDI. 100VG-AnyLAN, 100Base-T, X25 NETXPORT, NetIPC, Network Services General Options Option Meaning Description ? Redisplay Options Displays current options. Additional input OK. 0 Set Defaults Set all options back to default values. 1 ASCII ON or OFF ON = ASCII representation of data (OCTAL). OFF = Hexadecimal representation. Default = ON.
NMDUMP Formatting Options See Table 7-2 for a description of logging options. Table 7-2 Subsystem Log Options Option 802.3, 802.5, FDDI, 100VG-AnyLAN, 100Base-T SDLC, LAP-B, RJE/BSC NetIPC, Network Services, NETXPORT NETXPORT Only Link Meaning Description 1 Linknames Select logging options by Linknames. @ = ALL 2 Excluded Linknames Select Linkname to be excluded from logging.
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 Subsystem Trace Options 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 Subsystem SDLC, LAP-B, RJE/BSC 802.3, 802.5, FDDI, 100VG-AnyLAN, 100Base-T Option Meaning Description 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. Default = YES.
NMDUMP Formatting Options See Table 7-5 for a description of filter sets. Table 7-5 Subsystem SDLC X25 Filter Sets Number Filter Description 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-changes Enables printing of changes in internal state within the SDLC driver modules.
NMDUMP Formatting Options Subsystem LAP-B Number Filter Description 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-changes Enables printing of changes in internals state within the LAP-B driver modules. 4 Driver internals Enables printing of details related to internal processing of internal driver requests, mainly those related to utility functions (not datacomm I/O).
NMDUMP Formatting Options Subsystem RJE Number Filter Description 1 Enables printing of frames sent and frames received on the datacomm line. 2 Enables printing of all port messages sent to the driver by the RJERCS intrinsics and other entities, or sent to them by the driver. 3 Enables printing of changes in internal state within the RJE driver modules.
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 MPE/V format and previous versions of MPE/iX to the current MPE/iX release format. You can also perform the conversion procedure for a network running a combination of MPE/V X.25 (release V-delta 3 or later) and NS 3000/XL 1.0, 1.1 or 1.2. However, in this case, only the X.
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 @@.@[.acctname] @@.@.@ NOTE When converting from an earlier release of MPE XL to the current version of MPE/iX, the configuration file can have any valid MPE file name. If you have used another name instead of NMCONFIG, NMMGRVER will use that name as the final name for your conversion file. For example, if your configuration file is called MYCONFIG, NMMGRVER will convert it and save it under the same name, overwriting the original MYCONFIG.
NMMGRVER Using the Conversion Program Step 3. If you are converting only an NMCONFIG file, enter 2. Step 4. If you are converting NS transport data as well as configuration data, enter 1. NMMGRVER will combine the MPE/V NSCONF file containing the transport data with the MPE/V NMCONFIG.PUB.SYS, convert the file and save it under the same name as the source NSCONF file. NOTE The NSCONF file can have any valid MPE file name.
NMMGRVER Using the Conversion Program Step 2. Merge your NS 3000/V file with the existing NS 3000/iX NMCONFIG file, and convert it for use with NS 3000/iX by entering the MPE/V NSCONF file name. Enter Y to proceed when prompted. Step 3. Next, you receive this prompt: What is the type of this file? 1) MPE V NSCONF 2) MPE V NMCONFIG 3) skip this file Enter a value between 1 and 3. Step 4. Select type 1 for an NSCONF type file. NMMGRVER will merge the contents of the existing NMCONFIG file with the X.
NMMGRVER Using the Conversion Program 158 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 an SR Submitting an SR The messages that refer you to this section can indicate an internal error. For further assistance from HP, submit an SR. 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 an SR • 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 MESSAGE: NMMON: CREATEPROCESS error n on NMLOGMON.PUB.SYS. (NMCNERR 6) 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 MESSAGE: NM Log Monitor: Another MainLogMonitor exists. This one terminating. (NMCNERR 16) NMCNERR 16 CAUSE: A Main Log Monitor process has found its entry already exists in the port dictionary. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: NM Log Monitor: Unable to obtain port data segment. (NMCNERR 17) 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 MESSAGE: NM Log Monitor: Input/Output error in accessing the system disc cold load area. (NMCNERR 23) NMCNERR 23 CAUSE: An error occurred trying to access the area of disk where the next NMLGnnnn, and NMTCnnnn, file name numbers are stored. Check for other error indications that may affect the system disks, including I/O errors. ACTION: Correct any situation that may cause disk I/O errors.
NMS Error Messages NMCN Error and Warning Messages MESSAGE: NM Log Process: Unable to add port dictionary entry. (NMCNERR 32) NMCNERR 32 CAUSE: DICTADD returned a non-zero result. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: NM Log Process: Unable to add to NM Monitor port table. (NMCNERR 33) NMCNERR 33 CAUSE: NMMONADDID failed for MainLogMonitor. ACTION: See “Submitting an SR” at the beginning of this appendix.
NMS Error Messages NMCN Error and Warning Messages ACTION: See “Insufficient MPE Resources” at the beginning of this appendix. MESSAGE: NM Log Process: Cannot format log msg. Cannot access formatter for subsystem !. Encountered LOADPROC error !. (NMCNERR 45) NMCNERR 45 CAUSE: A request to write a formatted log message specifies an NMS subsystem number where formatter Log Process was unable to LOADPROC.
NMS Error Messages NMCN Error and Warning Messages MESSAGE: NMLG FILES mmmm THRU nnnn SKIPPED. (NMCNERR 47) 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. MESSAGE: NMLG FILES 0000 THRU 9999 ALL USED, NONE AVAILALBLE FOR NEXT LOGFILE.
NMS Error Messages NMCN Error and Warning Messages ACTION: The specific NMERR will be reported in a console message immediately following this message. The Link Manager process will continue to execute, but will be unable to log any errors, including I/O errors. MESSAGE: Trace Manager unable to open NM logging. (NMCNWARN 71) NMCNWARN 71 CAUSE: NMCONFIG does not have logging subsystem 18 configured. ACTION: None required. MESSAGE: Linkname Table creation error, subsys=! info=!.
NMS Error Messages NMDUMP Error and Warning Messages NMDUMP Error and Warning Messages MESSAGE: Unable to retrieve text of message #! of set #! from the message catalog. (NMDUMPERR 0) 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 MESSAGE: Error — File is not of trace type. (NMDUMPERR 5) 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 re-enter. MESSAGE: Invalid date and time string entered. (NMDUMPERR 6) 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 MESSAGE: Error — unexpected end of input data file. (NMDUMPERR 20) NMDUMPERR 20 CAUSE: There was a system failure while tracing/logging was enabled and the file was closed improperly. ACTION: Attempt to re-log or re-trace the error situation. CAUSE: An internal error in the NMS trace/log facility or the NMDUMP facility. ACTION: File an SR. Refer to “Submitting an SR” at the beginning of this appendix. CAUSE: Data file has become corrupt.
NMS Error Messages NMDUMP Error and Warning Messages 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.SYS to ensure that logging to disk is enabled for the subsystem(s) and log class(es) desired. If it is not, make the appropriate changes to the configuration file through NMMGR.PUB.SYS. CAUSE: An internal error in the NMS trace/log facility or the NMDUMP facility. ACTION: File an SR.
NMS Error Messages NMDUMP Error and Warning Messages ACTION: File an SR. Refer to “Submitting an SR” at the beginning of this appendix. CAUSE: Data file has become corrupt. ACTION: Attempt to recreate the trace file. MESSAGE: Error — invalid log data file. (NMDUMPERR 27) NMDUMPERR 27 CAUSE: There was a system failure while logging was enabled and the file was closed improperly. ACTION: Attempt to re-trace the error situation. CAUSE: An internal error in the NMS log facility or the NMDUMP facility.
NMS Error Messages NMDUMP Error and Warning Messages 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. MESSAGE: No data records are in the input file. (NMDUMPWARN 31) NMDUMPWARN 31 CAUSE: No data records were logged/traced to the data file. ACTION: None. CAUSE: An internal error in the NMS trace/log facility or the NMDUMP facility. ACTION: File an SR. Refer to “Submitting an SR” at the beginning of this appendix.
NMS Error Messages NMDUMP Error and Warning Messages ACTION: No action is actually needed. NMDUMP recovers from such an error in the data file. However, an SR may be filed against the log facility. Refer to “Submitting an SR” at the beginning of this appendix. 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. MESSAGE: An out-of-range start data record length was found.
NMS Error Messages NM Error Messages NM Error Messages MESSAGE: Invalid parameter specified. (NMERR 1) NMERR 1 CAUSE: The caller of an NMS procedure has passed an invalid value for one or more of the parameters. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Invalid SubsystemID parameter. (NMERR 2) 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 MESSAGE: Invalid InfoMode parameter. (NMERR 8) 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 an SR” at the beginning of this appendix. MESSAGE: Invalid Mode parameter. (NMERR 9) NMERR 9 CAUSE: The caller of an NMS procedure passed an invalid value to the Mode parameter.
NMS Error Messages NM Error Messages MESSAGE: Unable to create new datafile. (NMERR 15) 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. MESSAGE: Unable to open the datafile. (NMERR 16) NMERR 16 CAUSE: Returned by NMCONFOPEN.
NMS Error Messages NM Error Messages MESSAGE: Unable to obtain data segment for tracing. (NMERR 20) 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 an SR” at the beginning of this appendix. 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. MESSAGE: LogClass not configured in configuration file. (NMERR 29) 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 MESSAGE: Internal error: Invalid data segment number. (NMERR 35) 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 an SR” at the beginning of this appendix.
NMS Error Messages NM Error Messages MESSAGE: Port identifier not found in port table. (NMERR 41) 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 an SR”’ at the beginning of this appendix. MESSAGE: Unable to create specified system process. (NMERR 42) NMERR 42 CAUSE: Returned by NMMONSTARTREQ.
NMS Error Messages NM Error Messages ACTION: See “Invalid Software Installation” at the beginning of this appendix. MESSAGE: Unable to open $STDIN for process. (NMERR 48) NMERR 48 CAUSE: Returned by NMOPENLINK. Unable to FOPEN $STDIN for Link Manager process. Caused by an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Unable to open $STDLIST for process. (NMERR 49) NMERR 49 CAUSE: Returned by NMOPENLINK. Unable to FOPEN $STDIN for Link Manager process.
NMS Error Messages NM Error Messages MESSAGE: Invalid infolen, must be in range: 1 <= infolen <= 8. (NMERR 56) NMERR 56 CAUSE: Returned by: NMCONFFILEINFO. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Duplicate identifier already exists. (NMERR 57) 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 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. ACTION: See “Invalid Software Installation” and “Submitting an SR” at the beginning of this appendix.
NMS Error Messages NM Error Messages MESSAGE: Specified file is a back reference file. (NMERR 65) 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. MESSAGE: User logging entries are not available.
NMS Error Messages NM Error Messages MESSAGE: This command has no parameter. (NMERR 72) 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. MESSAGE: Invalid logging configuration file. (NMERR 73) NMERR 73 CAUSE: NMCONFIG.PUB.
NMS Error Messages NM Error Messages MESSAGE: File associated with this transaction is locked. (NMERR 77) 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. MESSAGE: No data associated with this identifier.
NMS Error Messages NM Error Messages MESSAGE: Parameter not aligned properly. (NMERR 88) NMERR 88 CAUSE: Internal error by the calling subsystem. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Invalid path type value, must be 1 or 2. (NMERR 90) NMERR 90 CAUSE: Returned by NMCONFNEXTPATH. NMCONFNEXTPATH detected invalid path type value. Internal error by the calling subsystem. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Unable to purge datafile.
NMS Error Messages NM Error Messages MESSAGE: Unable to find port for NMFILE process. (NMERR 97) NMERR 97 CAUSE: Returned by all NMCONF procedures. Error detected on DICTSEND. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Subsystem does not support version checking. (NMERR 100) 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. MESSAGE: MODULE FLAGS parameter invalid. (NMERR 106).
NMS Error Messages NM Error Messages MESSAGE: Link in exclusive use by another subsystem. (NMERR 132) 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 an SR” at the beginning of this appendix.
NMS Error Messages NM Error Messages MESSAGE: Unable to find DC/LDM in system I/O tables. (NMERR 138) 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 re-boot. More information may be found in the NMLG log file. MESSAGE: Unable to find the specified linkname in system I/O tables.
NMS Error Messages NM Error Messages MESSAGE: Specified item code is out of range. (NMERR 148) 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 an SR” at the beginning of this appendix.
NMS Error Messages NM Error Messages CAUSE: An internal error occurred. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: DS/LDM open request failed. (NMERR 157) 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 MESSAGE: Expects a name from one to eight characters long. (NMERR 162) NMERR 162 CAUSE: Returned after entering LINKCONTROL command incorrectly. ACTION: Check the spelling and try again. MESSAGE: Expects alphanumeric name starting with alphabetic. (NMERR 163) NMERR 163 CAUSE: Returned after entering LINKCONTROL command incorrectly. ACTION: Check the spelling and try again. MESSAGE: Expects a semicolon after link name parameter.
NMS Error Messages NM Error Messages MESSAGE: Locked(!) HW Recover(!) HW Sick(!) HW Dead(!) Resource(!). Run diagnostics for more information. (NMERR 177) 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 ACTION: Reissue the LINKCONTROL command with the correct value. CAUSE: An error occurred while accessing the specific I/O manager. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Trace for linkname has been initiated with some exceptions : HPE status: INFO = ! subsystem ID = !. NMERR 187 CAUSE: This error is often returned even though tracing has been enabled. ACTION: None. If this error occurs frequently, submit an SR.
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. MESSAGE: OPEN FSERR ! on NMCAT.PUB.SYS. (NMERR 202) NMERR 202 CAUSE: Returned by NMPRINTERRMSG and usually followed by the text of the FSError message. ACTION: Correct the FOPEN problem and retry. MESSAGE: Encountered GENMESSAGE error !.
NMS Error Messages NM Error Messages MESSAGE: Encountered FOPEN FSERR ! on !. (NMERR 207) 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. MESSAGE: Encountered GENMESSAGE error !.
NMS Error Messages NM Error Messages MESSAGE: Total data length too large to return as integer. (NMERR 221) 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. 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. MESSAGE: Datafile does not match user specified filecode. (NMFSWARN 6) 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 MESSAGE: Directory linkage error in datafile. (NMFSERR 10) 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. MESSAGE: Unable to read directory entry in datafile.
NMS Error Messages NMFS Error and Warning Messages MESSAGE: No data associated with this identifier. (NMFSERR 18) 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. MESSAGE: Read truncated to capacity of data buffer. (NMFSWARN 19) 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 an SR” at the beginning of this appendix. MESSAGE: Identifier exceeds maximum permissible length. (NMFSERR 25) NMFSERR 25 CAUSE: This is returned by MIDASPARSEPATH when the pathname is too long. No NMCONF procedure calls this intrinsic. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Pathname length exhausted user specified buffer.
NMS Error Messages NMFS Error and Warning Messages MESSAGE: Unable to open message catalog NMCAT.PUB.SYS. (NMFSERR 31) 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. MESSAGE: Unable to read message catalog NMCAT.PUB.SYS. (NMFSERR 32) NMFSERR 32 CAUSE: Returned by MIDASERRMSG. The file might be corrupted.
NMS Error Messages NMGR Error and Warning Messages NMGR Error and Warning Messages MESSAGE: Terminal is of incorrect type or cannot be opened. (NMGRERR 1) 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 MESSAGE: That function is not implemented. (NMGRERR 4) 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. MESSAGE: Not a valid or @. (NMGRERR 5) NMGRERR 5 CAUSE: The user typed an unrecognizable command in the command window and pressed [ENTER].
NMS Error Messages NMGR Error and Warning Messages CAUSE: NMMGR has encountered an unexpected condition in the configuration file. Two or more users are updating the same 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 Service Request. See “Submitting an SR” at the beginning of this appendix.
NMS Error Messages NMGR Error and Warning Messages ACTION: See “Invalid Software Installation” at the beginning of this appendix. 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 back-up copy of NMMGRF.PUB.SYS.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: No errors have yet occurred. (NMGRWARN 17) NMGRWARN 17 CAUSE: The user has gone to the ERRORS screen to check the last error, but no errors have occurred. ACTION: None. MESSAGE: MPE command error. (NMGRERR 19) 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 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. CAUSE: NMMGR was unable to compress the configuration file because at least one other user is currently accessing the file.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: That command is ambiguous — use more letters. (NMGRERR 31) 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. MESSAGE: Maximum path depth exceeded. (NMGRERR 32) NMGRERR 32 CAUSE: This error in an internal NMMGR error.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Invalid syntax for file name. (NMGRERR 36) 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. MESSAGE: ENTER executes commands: the command field is blank. (NMGRERR 37) 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 MESSAGE: Internal error: Unexpected screen contents. (NMGRERR 42) 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 an SR” at the beginning of this appendix. MESSAGE: Internal error: Unexpected data record length. (NMGRERR 43) NMGRERR 43 CAUSE: This is an internal NMMGR error.
NMS Error Messages NMGR Error and Warning Messages ACTION: Submit a Service Request. See “Submitting an SR” at the beginning of this appendix. MESSAGE: Internal error: The root node has parent node. (NMGRERR 49) NMGRERR 49 CAUSE: This is an NMMGR internal error. NMMGR is scanning the configuration file off the boundary. ACTION: Submit a Service Request. See “Submitting an SR” at the beginning of this appendix. MESSAGE: Internal error: The schema has an invalid format.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Internal error: Version checking routine failed. (NMGRERR 54) 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 back-up copy of the configuration file if possible. 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. MESSAGE: Internal error: Data field alignment error.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Internal error: Data conversion ptr is out of bounds. (NMGRERR 77) NMGRERR 77 CAUSE: This is an internal NMMGR conversion table error. ACTION: Submit a Service Request. See “Submitting an SR” at the beginning of this appendix. MESSAGE: Internal error: Missing description for this screen. (NMGRERR 78) NMGRERR 78 CAUSE: This is an NMMGR internal table error. The screen name is not in an internal conversion table. ACTION: Submit a Service Request.
NMS Error Messages NMGR Error and Warning Messages ACTION: Press the Delete key a second time to confirm the deletion. MESSAGE: Cannot access the NMMGR help catalog. (NMGRERR 84) NMGRERR 84 CAUSE: NMMGR was unable to open the NMMGR help catalog, NMMGRHLP.PUB.SYS. ACTION: Restore the NMMGR help catalog. MESSAGE: Incomplete summary printed. (NMGRERR 85) NMGRERR 85 CAUSE: Some configuration data could not be found or printed in the summary.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Warning: Incompatible selection. Press key again to confirm. (NMGRWARN 89) NMGREWARN 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. MESSAGE: Invalid IP Address; press Help for more information.
NMS Error Messages NMGR Error and Warning Messages CAUSE: User attempted to do “LAST PAGE” or “CONDENSE PAGE”. The configuration file may have Reachable Network paths in excess of the maximum page count. ACTION: Restore the configuration file with Reachable Network paths within the maximum page count. MESSAGE: You must enter a configuration file name to open or create.
NMS Error Messages NMGR Error and Warning Messages CAUSE: The file number was changed in NMMGR but not entered in the table. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Internal error: Midas file number not in file table. (NMGRERR 101) 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.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: The file has been locked; cannot begin guided task. (NMGRERR 106) 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. 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. MESSAGE: DTS/LINK not validated. Type exit again to leave NMMGR. (NMGRERR 112) 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. MESSAGE: HP-IBM not validated.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: LU Number “!” on page ! is a duplicate. (NMGRERR 119) 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. MESSAGE: If the Node Type is “2.0”, then the LU # is required. (NMGRERR 120) 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 MESSAGE: IP Subnet Mask of 255.255.255 is not allowed. (NMGRERR 126) NMGRERR 126 CAUSE: An IP Subnet Mask of 255.255.255 was entered. This is not a legal mask. ACTION: Re-enter the mask with a different value. MESSAGE: If Node 2.1 Dependent LU Support, then LU #’s must be blank. (NMGRERR 127) 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 MESSAGE: IP Address with node portion of zero’s reserved. (NMGRERR 134) NMGRERR 134 CAUSE: The node portion of the IP address is all zeros. 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.) MESSAGE: IP Address with network portion of zero’s reserved.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: SNA/DS not validated. Type exit again to leave NMMGR. (NMGRERR 140) NMGRERR 140 CAUSE: Data in the SNA.DS subsystem was changed and SNA/DS was not successfully validated afterwords. ACTION: Go to the validation screen and validate SNA/DS or type exit again to leave the file unvalidated. MESSAGE: Subsystem(s) are not validated. Type ERR for more information.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Aux NCONF file not opened. (NMGRERR 204) NMGRERR 204 CAUSE: This is an internal guided configuration error caused when data is copied from the auxiliary file to the user file and the auxiliary file was not opened. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Aux file does not contain specified path.
NMS Error Messages NMGR Error and Warning Messages ACTION: There is no need to use this function at this time. MESSAGE: Function is not allowed during Guided configuration. (NMGRERR 214) NMGRERR 214 CAUSE: The user has pressed a function key that is not allowed during guided configuration. If the user is on a data screen, it is possible to advance by pressing the Update function key. ACTION: Press a labeled function key. MESSAGE: Illegal vplus field specified in Guided config.
NMS Error Messages NMGR Error and Warning Messages ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Select stack underflow probably missing SELECT. (NMGRERR 223) NMGRERR 223 CAUSE: This is an internal guided configuration error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Missing ENDSELECT statement. (NMGRERR 224) NMGRERR 224 CAUSE: This is an internal guided configuration error. ACTION: See “Submitting an SR” at the beginning of this appendix.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: No network interface found, or unknown type. (NMGRERR 231) NMGRERR 231 CAUSE: You may have spelled the name incorrectly. ACTION: Check the spelling and reenter. CAUSE: The type may be unknown. ACTION: Check the type of the network interface name by going to NETXPORT.NI (do a direct branch). File an SR if the type is labeled as UNKNOWN. (See “Submitting an SR” at the beginning of this appendix). Delete the unknown type and retry.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: The Network interface must be of type X.25. (NMGRERR 237) NMGRERR 237 CAUSE: The operation is illegal if the NI is not an X.25 link. ACTION: Check to make sure that the NI is an X.25 link. MESSAGE: Data must be entered and Saved before continuing. (NMGRERR 240) 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.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: This link cannot be renamed. It is used by another NI. (NMGRERR 256) NMGRERR 256 CAUSE: The user attempted to change the name of a link that is used by more than one NI. ACTION: Leave the link name as it is or reconfigure one or the other of the NIs to use a different link. MESSAGE: The NI name does not exist. Please specify a type to create it.
NMS Error Messages NMGR Error and Warning Messages ACTION: If an incorrect DTC name was entered, enter the correct DTC name and try again. If the DTC name is correct but the DTC has not yet been configured, enter the information for the DTC and press the Save Data key, then try again. MESSAGE: The DTS Link does not exist. Enter a Link name and press Sate Data. (NMGRERR 261) NMGRERR 261 CAUSE: At the DTS Configuration screen, the user entered a nonexisting link name and pressed the Tune DTS Link key.
NMS Error Messages NMGR Error and Warning Messages ACTION: If an incorrect link name was specified, correct the link name and try again. If link name is correct but the link has not yet been configured, configure the link. MESSAGE: The path report for the node is full; no new address can be added. (NMGRERR 266) NMGRERR 266 CAUSE: The user attempted to add an address to the network directory for a node whose path report is already full. No additional addresses can be added.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: The link exists, but its type is not correct for this NI. (NMGRERR 272) NMGRERR 272 CAUSE: The user specified an existing link name on one of the custom NI update screens. The selected link’s type was not correct; that is, a LAPB type link was specified for an X.25 NI. ACTION: Enter the name of a link with the correct type or delete the link configuration. MESSAGE: The selected card number is not configured with a card type.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Duplicate address key; it must be unique for the X.25 NI. (NMGRERR 277) NMGRERR 277 CAUSE: The user specified an address key that was not unique for the NI specified at the VC Configuration screen or through the ADDVC command. ACTION: Go to the SVC and PVC paths screens for the NI to see the names that are already configured. Choose an address key that is not used in either of these screens.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Internal ERROR in subtree copy. (NMGRERR 284) NMGRERR 284 CAUSE: Internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: A non select screen id was changed in the destination path. (NMGRERR 285) NMGRERR 285 CAUSE: Incorrect ids in the destination path. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Illegal path name identifier in destination path name.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Source path is not allowed to be copied. (NMGRERR 291) NMGRERR 291 CAUSE: The source path is not permitted to be copied by the subtree command. ACTION: None. MESSAGE: Internal NMMGR error: cannot close current Network Directory. (NMGRERR 300) NMGRERR 300 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Internal NMMGR error: corrupt file likely.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: RENAME requires a new node name and/or new global/local setting. (NMGRERR 306) NMGRERR 306 CAUSE: This is an informative message that is issued when the user tries to rename a node name (global/local setting), but both the new node name and new global/local setting were omitted. ACTION: Specify the missing information. MESSAGE: The current node name entry has been deleted by another user.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Cannot find this entry in the directory. (NMGRWARN 324) NMGRWARN 324 CAUSE: Maintenance mode interface: An informative message that is issued when no directory entry (either global, local, or neither — if no ;GLOBAL or ;LOCAL keyword given) could be found in the directory matching the specified node name. ACTION: Correct the node name. MESSAGE: Cannot open source file / wrong file type.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: The catalog file has an error in the Batch Command list. (NMGRERR 329) NMGRERR 329 CAUSE: An internal error in NMMGR has occurred. ACTION: Run NMMAINT.PUB.SYS to make sure that you have the correct version of NMMGR. If necessary, restore the file NMMGRCAT.PUB.SYS from a back-up tape. If the problem still exists, see “Submitting an SR” at the beginning of this appendix. MESSAGE: Extra data was specified for this command.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Expected parameter after command. (NMGRERR 337) NMGRERR 337 CAUSE: A parameter is needed after certain commands. This error occurs if the user does not specify that parameter. OPENDIR: needs a filename. MERGEDIR: needs a filename. EXPANDDIR: needs an integer. ACTION: Check syntax of the command or type “help” for more information. MESSAGE: Unknown or extra keyword parameter specified.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Domain segment in node name must be from 1 to 16 chars in length. (NMGRERR 344) NMGRERR 344 CAUSE: The domain portion of the node name is the incorrect length. ACTION: Fix the length of the domain in name.DOMAIN.org. MESSAGE: org segment in node name must be from 1 to 16 chars in length. (NMGRERR 345) 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.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Need to save data on previous screen before adding domain name. (NMGRERR 352) NMGRERR 352 CAUSE: Data was not updated for this node. ACTION: Update the data for this node. MESSAGE: The path specified does not point to a paged data screen. (NMGRERR 353) 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. MESSAGE: Entry selected is empty.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Domain name is empty. (NMGRERR 359) NMGRERR 359 CAUSE: The user selected an operation which required a domain, yet neglected to enter a domain. ACTION: Re-enter the information with the domain name specified. MESSAGE: Domain screen can be accessed only after an NS nodename addition. (NMGRERR 360) NMGRERR 360 CAUSE: User can access the domain screen only after using the add function key to add an NS nodename.
NMS Error Messages NMGR Error and Warning Messages ACTION: None. MESSAGE: User is not allowed to merge individual domain entries. (NMGRERR 367) 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. MESSAGE: User must enter: Node Name, Type, Global, and Enable settings.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Problem accessing the new (expanded) directory file. (NMGRERR 381) 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 MESSAGE: Cannot specify a negative number for expansion. (NMGRERR 383) 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. MESSAGE: Cannot open command file “NMMGRCMD”. (NMGRERR 384) 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 ACTION: Use NMMGR to go to the path which you specified in the PATHCONF command. Make sure that your field count matches the field number you are trying to access. Make sure you are not trying to use Vplus field numbers to access the field. MESSAGE: Path not specified, or path specified does not exist. (NMGRERR 390) 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 MESSAGE: Record size of nodelist file too small; must be >= 80 bytes. (NMGRERR 401) 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. MESSAGE: Filecode of nodelist file non zero.
NMS Error Messages NMGR Error and Warning Messages ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: FREAD failed trying to read from nodelist file. (NMGRERR 409) NMGRERR 409 CAUSE: Could not read sequentially from the nodelist file. ACTION: See the accompanying file system error message for resolution. MESSAGE: Cannot gain access to the stream file. (NMGRERR 410) NMGRERR 410 CAUSE: A check to verify that the stream file does not already exist could not be completed.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Error converting a catalog entry into a numeric value. (NMGRERR 416) NMGRERR 416 CAUSE: Internal error. ACTION: RESTORE NMMGRCAT.PUB.SYS from a backup tape. If the problem still exists, see “Submitting an SR” at the beginning of this appendix. MESSAGE: Catalog entry value not in range -32768..32767. (NMGRERR 417) 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 MESSAGE: Missing equal sign. (NMGRERR 500) NMGRERR 500 CAUSE: An equal sign was missing in the command syntax. ACTION: Re-enter the command with the proper syntax. MESSAGE: Missing or invalid pathname parameter. (NMGRERR 501) NMGRERR 501 CAUSE: The syntax of the command requires a pathname parameter. ACTION: Check pathname and reissue the command. MESSAGE: Missing or invalid field number.
NMS Error Messages NMGR Error and Warning Messages ACTION: Check to see that you are accessing the correct field, or reduce the size of the data you are entering. MESSAGE: There are Vplus field edit errors. (NMGRERR 510) NMGRERR 510 CAUSE: UPDATECONF error. ACTION: Examine all WRITECONF statements before the screen associated with the UPDATECONF which caused the error. One or more of these fields does not match the edits which are associated with this field.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: Extra data was specified in the command line. (NMGRERR 552) 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). MESSAGE: The lower LDev # must be less than the upper LDev #.
NMS Error Messages NMGR Error and Warning Messages ACTION: Reenter the command with the correct card number and DTC specified. If the card exists but is not properly configured, use NMMGR to correct the card configuration, then reenter the SUMMARYCONF command. MESSAGE: That Port is not configured in the DTC and Card specified.
NMS Error Messages NMGR Error and Warning Messages MESSAGE: The port number must be an integer from 0 to 7. (NMGRERR 561) 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. 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 ACTION: An internal file system error has occurred. See “Submitting an SR” at the beginning of this appendix. MESSAGE: INTERNAL ERROR: cannot convert file. (NMMGRVERWARN 3) NMMGRVER WARN 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.
NMS Error Messages NMMGRVER Messages, Errors and Warnings ACTION: Purge unnecessary files from disk to recover some space. Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Service Request. See “Submitting an SR” at the beginning of this appendix. CAUSE: An internal error occurred with intrinsics, midasgetdata, midasnextpath, midasupdatedata, or midasaddpath. ACTION: The configuration file may be corrupted.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: Config File Version Is Newer than NMMGRVER can support (NMMGRVERWARN 9). NMMGRVER WARN 9 CAUSE: At least one version stamp of the configuration file is newer than NMMGRVER can support. NMMGRVER cannot convert this file. This configuration file is not changed. ACTION: Check the module version of NMMGRVER and overall NMC.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: Invalid data length. Path: ! Length: ! (NMMGRVERERR 15) NMMGRVERERR CAUSE: The length of the data array which was read from the cell was 15 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.
NMS Error Messages NMMGRVER Messages, Errors and Warnings configuration files need it. However, the NM intrinsic failed during this process. One possible reason for this is that the configuration file may be full. ACTION: Run NMMGRVER again. If the error still occurs, submit a Service ReRun NMMGR and expand the size of the configuration file. Then run NMMGRVER again. MESSAGE: Unable to purge LINKCONF subtree (NMMGRVERERR 20) NMMGRVERERR CAUSE: Internal error. File has been converted.
NMS Error Messages NMMGRVER Messages, Errors and Warnings ACTION: Correct the file system error and run NMMGRVER again. MESSAGE: FCLOSE FSERR ! on NMMGRCAT.PUB.SYS. (NMMGRVERERR 25) NMMGRVERERR CAUSE: Returned by NMCPRINTERRMSG after printing a message 25 from NMMGRCAT.PUB.SYS. The FCLOSE of NMMGRCAT.PUB.SYS failed. ACTION: Correct the file system error and run NMMGRVER again. MESSAGE: Merge failed. Error in NMCONFIG.PUB.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: File not converted NMMGRVERMSG 56. NMMGRVERMSG CAUSE: You selected the skip option when asked for a file type during 56 the configuration file conversion. ACTION: None. This is an informative message. MESSAGE: Unable to add path. Path: ! Midasstat = ! (NMMGRVERERR 60) NMMGRVERERR CAUSE: An internal error occurred while adding the displayed path. 60 ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: Unable to purge data. Path: ! Midasstat = ! (NMMGRVERERR 63) NMMGRVERERR CAUSE: Internal error occurred while purging data at displayed path. 63 ACTION: Restore a backup copy of the configuration file if possible and run NMMGRVER again. If the error still occurs, submit a Service Request. See “Submitting an SR” at the beginning of this appendix. 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 Service Request. See “Submitting an SR” 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. MESSAGE: Unable to update data.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: Invalid path found in source file. Path: ! (NMMGRVERERR 75) NMMGRVERERR CAUSE: An invalid path was found in the source configuration file. The 75 path may have been created by an unofficial NMMGR tool. Conversion will continue if possible. NMMGRVERERR 76 will usually be displayed along with this message. ACTION: Note that the configuration file may have been changed.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: An error has occurred during IMF CONVERSION. (NMMGRVERERR 81) NMMGRVERERR CAUSE: An error occurred during the IMF part of the conversion 81 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 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 Service Request.
NMS Error Messages NMMGRVER Messages, Errors and Warnings MESSAGE: An error has occurred during LAN LINK CONVERSION. (NMMGRVERERR 88) NMMGRVERERR CAUSE: An error occurred during the LAN LINK part of the conversion 88 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 MESSAGE: The default SNA/SDLC LINK physical path is 24; User modification may be needed. (NMMGRVERERR 92) NMMGRVERERR CAUSE: The default physical path has been set to 24, which may be 92 correct for the given system. ACTION: Run NMMGR, confirm this value, and modify it as needed. MESSAGE: The default LAPB LINK physical path is 24; User modification may be needed.
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. MESSAGE: Directory file not open. (NDIERR 001) NDIERR 001 CAUSE: No directory file was opened. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Directory is not open for write access.
NMS Error Messages ND Error Messages MESSAGE: Path report list length cannot be negative. (NDIERR 010) NDIERR 010 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Path report list length > than ND’CREATE maximum. (NDIERR 011) NDIERR 011 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Duplicate node name in directory — cannot add new entry.
NMS Error Messages ND Error Messages ACTION: If a larger file is really desired, create one at the maximum size, then use NMMGR maintenance mode EXPANDDIR command to increase the file to desired size. If this fails, see “Submitting an SR” at the beginning of this appendix. MESSAGE: Maximum path report list length negative; must be > 0. (NDIERR 042) NDIERR 042 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix.
NMS Error Messages ND Error Messages MESSAGE: Directory file not open. (NDIERR 080) NDIERR 080 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Item number invalid; must be 1, 2, 3, 4, 5, or 6. (NDIERR 081) NDIERR 081 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Requires Node Manager or Network Administrator capability.
NMS Error Messages ND Error Messages MESSAGE: Access mode invalid; must be 0 or 1. (NDIERR 103) NDIERR 103 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Share option invalid; must be 0, 1, 2 or 3. (NDIERR 104) NDIERR 104 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: FLOCK failed — internal error. (NDIERR 105) NDIERR 105 CAUSE: This is an internal error.
NMS Error Messages ND Error Messages MESSAGE: One or more required parameters are missing. (NDIERR 120) NDIERR 120 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Directory file not open. (NDIERR 121) NDIERR 121 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Relop parameter invalid; must be 0, 1 or 2. (NDIERR 122) NDIERR 122 CAUSE: This is an internal error.
NMS Error Messages ND Error Messages MESSAGE: FCONTROL/FUNLOCK failed — internal error. (NDIERR 129) NDIERR 129 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Requires Node Manager or Network Administrator capability. (NDIERR 130) NDIERR 130 CAUSE: User does not have Node Manager or Network Administrator capabilities. ACTION: Change user capabilities. MESSAGE: Select parameter invalid; must be 0, 1 or 2.
NMS Error Messages ND Error Messages ACTION: Restore the data and key files from a back-up tape. If this fails, see “Submitting an SR” at the beginning of this appendix. MESSAGE: FCONTROL/FUNLOCK failed — internal error. (NDIERR 146) NDIERR 146 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Name type invalid; must be 1 (NS node name). (NDIERR 147) NDIERR 147 CAUSE: This is an internal error.
NMS Error Messages ND Error Messages ACTION: Restore the data and key files from a back-up tape. If this fails, see “Submitting an SR” at the beginning of this appendix. MESSAGE: FREAD failed — corrupt file likely. (NDIERR 164) NDIERR 164 CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a back-up tape. If this fails, see “Submitting an SR” at the beginning of this appendix. MESSAGE: FLOCK failed — internal error.
NMS Error Messages ND Error Messages 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. MESSAGE: Requires Network Administrator capability. (NDIERR 192) NDIERR 192 CAUSE: User does not have Network Administrator capabilities. ACTION: Change user capabilities.
NMS Error Messages ND Error Messages ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: File recovery: FCLOSE of temporary command file failed. (NDIERR 204) NDIERR 204 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: File recovery: CREATEPROCESS of KSAMUTIL.PUB.SYS failed. (NDIERR 205) NDIERR 205 CAUSE: Problem encountered trying to create a son process to run KSAM.PUB.SYS. It is possible that the program file KSAMUTIL.
NMS Error Messages ND Error Messages MESSAGE: FPOINT to header record failed — corrupt file likely. (NDIERR 220) NDIERR 220 CAUSE: The file is corrupt, empty, or is not a network directory file. ACTION: Restore the data and key files from a back-up tape. MESSAGE: FREADC of header record failed — corrupt file likely. (NDIERR 221) NDIERR 221 CAUSE: The file is not a KSAM file (and thus not a network directory file), or is a corrupt network directory.
NMS Error Messages ND Error Messages ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Domain report in path report list too short (< 6 bytes). (NDIERR 252) NDIERR 252 CAUSE: This is an internal error. ACTION: See “Submitting an SR” at the beginning of this appendix. MESSAGE: Version of domain report in path report list <> 0. (NDIERR 253) NDIERR 253 CAUSE: The version number (1st octet) of a domain indicates an unsupported version.
NMS Error Messages ND Error Messages MESSAGE: FREAD failed — corrupt file likely. (NDIERR 272) NDIERR 272 CAUSE: Possible corrupt network directory file. ACTION: Restore the data and key files from a back-up tape. If this fails, see “Submitting an SR” at the beginning of this appendix.
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 an SR 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 MESSAGE: SUBSYSxxTRACEFORMAT CM STUB ERROR (nnn,sss) FROM HPSWTONMNAME UNABLE TO CALL NM TRACE FORMATTER ROUTINE (FMTERR 999) 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 MESSAGE: Range error at position shown; other values accepted if allowed 4028 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. You may 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 ACTION: Check your input and retype if necessary. If the problem continues to occur, submit an HP Service 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. MESSAGE: CIERROR NNNN while executing MPE command 4034 CAUSE: The MPE command you tried encountered an error. MPE returned error number NNNN to the Formatter (MPE warnings are ignored).
NMS Error Messages FMT Error Messages 298 Appendix A
Glossary A access port A special interface card in the system cabinet through which the system console is connected. address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key. address resolution In NS networks, the mapping of node names to IP addresses and the mapping of IP addresses to subnet addresses. irrespective of time coincidence with any event.
Glossary banner A welcome message displayed on your screen. On the local OpenView workstation a banner appears when a remote connection is established with the OpenView DTC Manager. A banner also can appear when you log on to MPE.) baud Measure of the speed at which information travels between devices, most commonly used in reference to terminal speed settings. Baud represents signal events per second. When one bit represents each signal change, baud is the same as “bits per second”.
Glossary CCITT Consultative Committee for International Telephony and Telegraphy. An international organization of communication carriers, especially government telephone monopolies, responsible for developing telecommunication standards by making recommendations. No carrier is required to adhere to a CCITT recommendation, although most do so in their own interest. configuration 1) The way in which computer equipment is physically interconnected and set up to operate as a system.
Glossary 2) Information necessary for link-level and NetIPC logging. CSN See circuit-switching network. 3) Information required to connect terminals and printers to the system through one or more DTC. CTB The cache transfer bus in the backplane of an HP 3000. The only file name that the system recognizes as the configuration file is NMCONFIG.PUB.SYS. D control-X echo Three exclamation marks (!!!) output to the terminal screen when the cancel character (normally [CTRL]-X) is entered.
Glossary transmission circuit. Synonyms: data communications equipment, dataset. classes are assigned through use of the NMMGR configuration utility. DDX The national public PSN of Japan. device-dependent characteristic A file specification for which modifications are restricted because of the type of device on which the file is opened. For example, data directed to terminals must have a blocking factor of one.
Glossary direct-connect device Asynchronous device that is connected directly to a DTC through an RS-232-C or RS-422 cable, with no intervening communications equipment. Also referred to as a “local connection.” direct connection A leased line, private line, or other non-switched link in a network. direct dial A dial link through which only one remote node can be reached. direct-path branching The process of directly accessing any screen in NMMGR by entering path names in the Command: field.
Glossary DTC/X.25 Network Access The X.25 software that resides on the Datacommunications and Terminal Controller (DTC). To configure access to an X.25 network, you must configure two software components: the X.25 iX System Access (residing on the HP 3000 host), and the DTC/X.25 Network Access. DTC/X.25 Network Access is configured through use of the OpenView DTC Manager software for systems using PC-based network management or through NMMGR for systems using host-based network management.
Glossary one or more other characters, used to convey control directives to printers, plotters, or terminals. Ethernet A Local Area Network system that uses baseband transmission at 10 Mbps over coaxial cable. Ethernet is a trademark of Xerox Corporation. event log One of three circular files stored on the OpenView workstation containing lists of all significant events reported by the DTCs for which it is the owner; that is, whose operating software/configuration it has downloaded.
Glossary flow control A means of regulating the rate at which data transfer takes place between devices to protect against data overruns. flow control negotiation One of the network subscribed facilities, selected at subscription time. This facility allows the flow control parameter to be negotiated at call set-up time, as opposed to having a predefined value. formal file designator Name that can be used programmatically or in a file equation to refer to a file. FOS Fundamental operating system.
Glossary hop count See internet hop count and intranet hop count host-based network management Method of managing asynchronous communications for HP 3000 Series 900 computers. All of the control software is configured on a single host and is downloaded to the DTCs that are managed by that host. With host-based management, there is a permanent relationship between each DTC and the host, and terminal users can access only the single system that owns the DTC their terminal is connected to. host-based X.
Glossary IEEE 802.3 nodal address A unique hexadecimal number that identifies a node on an IEEE 802.3 LAN. IEEE 802.5 A standard for a token ring network published by the Institute for Electrical and Electronics Engineers (IEEE). This standard is used for the Token Ring 3000/iX Network Link. initialization string A sequence of control characters used to initialize a terminal, printer, or plotter when a connection is established from a host on the network.
Glossary internet routing. A complete IP address comprises a network portion and a node portion. The network portion of the IP address identifies a network, and the node portion identifies a node within the network. IP subnet mask See subnet mask. ISO International Standards Organization. An international federation of national standards organizations involved in developing international standards, including communication standards. L LAN Local Area Network.
Glossary Local Area Network Interface Controller (LANIC) A hardware card that fits into the backplane of the HP 3000 Series 900 computer and provides a physical layer interface for local area networks. local connection See direct connection. local node The computer that you are configuring or that you are logged on to. local switching Feature of the DTC which permits back-to-back configuration (for connections to an HP 3000 MPE/V host), using two ports of the same DTC.
Glossary used when planning a network. It shows network topology, node and network names, addresses, network boundaries (for an internetwork map), and link types. mapping A set of characteristics that describe a route taken by messages to reach a destination node. This set of characteristics is configured with NMMGR at every node on a point-to-point network. One mapping is configured at each node for every other node on the network to which messages will be sent. MAU See medium attachment unit.
Glossary native mode The run-time environment of MPE/iX. In Native Mode, source code has been compiled into the native instruction set of the HP 3000 Series 900 computer. neighbor gateway A gateway that is in the same network as a given node. NetIPC Network Interprocess Communication. Software that enables programs to access network transport protocols. network A group of computers connected so that they can exchange information and share resources.
Glossary network subscribed facilities A set of parameters that the user chooses when he subscribes to the X.25 network; they include flow control negotiation, use of D-bit, throughput class negotiation and extended packet sequence numbering. network transport Software that corresponds to layers 4 and 3 of the OSI network architecture model.
Glossary node address The node portion of an IP address, which consists of a node portion and a network portion. node management services configuration manager See NMMGR. node name A character string that uniquely identifies each system in a network or internetwork. Each node name in a network or internetwork must be unique; however, a single node can be identified by more than one node name.
Glossary systems attach to the point-to-point network via HP 3000 Programmable Serial Interface (PSI) cards that fit into the back of each system’s SPU. NSDIR.NET.SYS Name of the active network directory file. See also network directory. O octet An eight-bit byte operated upon as an entity.
Glossary packet exchange protocol PXP. A transport layer protocol used in NS 3000/iX links to initially establish communication between nodes when NetIPC socket registry is used. packet-switched network name The name of a data communication network adhering to the CCITT X.25 recommendation. This can be a PDN or a private network, such as the HP PPN.
Glossary more printers through the NMMGR configuration. Printer profile specifications include the printer type, line speed, device class assignment, and other values relevant to printers connected through a DTC. printer type A collection of characteristics that cause a printer connected to a HP 3000 Series 900 system to act and react in a specified manner. You can configure a printer to use one of the system-supplied printer types or you can create custom printer types using workstation configurator.
Glossary PSS Packet-Switching System. The national public PSN of the United Kingdom. PVC Permanent Virtual Circuit. A permanent logical association between two physically separate DTEs that does not require call set-up or clearing procedures. PXP See packet exchange protocol. Q Q bit Qualified bit. When set in DATA packets the Q bit signifies that the packet’s user data is a control signal for the remote device, not a message for its user.
Glossary electrical circuit functions for 25 connector pins. HP provides two implementations of this standard: a 3-pin version for direct connections up to a distance of 15 meters (50 feet), and a version which makes use of additional circuits and can be used for either modem or direct connections. RS-422 Electronic Industries Association (EIA) level 1 protocol specification implemented by HP in a 5-pin version which can be used for direct device connection up to a distance of 1500 meters (4000 feet).
Glossary start bit Data bit used to signal the start of a character being transmitted in an asynchronous communication mode. station address A 12-digit hexadecimal link-level address used by the IEEE 802.3 protocol. Every node on an IEEE 802.3 network has its own station address. stop bit Data bit used to signal the end of a character being transmitted in an asynchronous communication mode.
Glossary utility. TermDSM is used only when DTCs are managed by a host system. terminal name Character string of up to 16 characters specified in the Openview DTC Manager configuration (for networks using OpenView Network Management) to define a terminal by name. May be shared by several terminals (pool port). terminal profile A set of configuration characteristics that can be associated with one or more terminals through the NMMGR configuration.
Glossary passed with the token until they arrive at the node to which they are addressed. Token Ring 3000/iX Network Link Hardware and software required to connect a HP 3000 Series 900 system to a token ring network. topology The physical arrangement of nodes in a network. Some common topologies are bus, star, and ring. the appropriate communications link, to receive incoming data, and to route incoming or outgoing data to the appropriate destination node.
Glossary VAN Value-Added Network. A data communication network that uses and pays for facilities belonging to another carrier. The value-added package is then sold to a user. VC See virtual circuit. virtual circuit A logical association between two physically separate DTEs. virtual terminal A network service that allows a user to establish interactive sessions on a node. VPLUS Software used to generate screens such as those displayed by NMMGR. V-Series (V.
Glossary components: the X.25 iX System Access (residing on the HP 3000 host), and the DTC/X.25 Network Access. DTC/X.25 Network Access is configured through use of the OpenView DTC Manager software for systems using PC-based network management or through NMMGR for systems using host-based network management. X.29 Defines the interface for data exchange between a packet-mode DTE and a remote packet assembly/disassembly (PAD) facility over a packet switching network.
Glossary 326 Glossary
Index A abbreviations for screen mode commands, 27 ADDCONF command, 80 adding records to a file, 64 ADDLDEV command, 81 ADDLU command, 83 ADDNODE command, 84 ADDVC command, 87 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, 90 changing the backup file name, 44 command ADDCONF, 80 ADDLDEV, 81 ADDLU, 83 ADDNODE, 84 ADDVC, 87 CARDCONF, 90 COMPRESS, 27 COMPRESSCONF, 91 CONFIGURATI
Index function keys definition of, 30 labels, 40 fundamental operating system, 15 G getting help, 35 go to keys, 31 guided configuration, 51 guided HP configuration, 50 H HELP command, 28, 35, 101 help facility, 35, 101 Help key, 30 help mode, 35, 101 home key, 27 HP-IBM configuration, 53 L LISTDIR command, 103 listing directory contents, 103 LISTLDEV command, 102 LISTLU command, 105 local node name, 47 logging, 20 M MAIN command, 28 Main screen, 47 maintenance interface, 18, 74 transferring to, 28, 74 mai
Index screen mode, 18 screen number, 26 screen title, 26 screens, 24 select screens, 29 selecting a configuration path, 47 selecting data screens to print, 60 selecting menu items, 29 serial device configuration, 48 service request, 19, 134 SNA subsystem, 16 softkeys, 30 software version ID number, 134 SR, 19, 134 starting NMMGR, 41 STOP command, 28 SUBGUIDE command, 28 subsystem definition of, 134 SUMMARYCONF command, 126 T terminal configuration, 48 terminal requirements, 40 title screen, 26 tracing, 20
