HPlogo Using the Node Management Services (NMS) Utilities: HP 3000 MPE/iX Computer Systems > Chapter 1 Introduction

NMMGR
» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

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. You use NMMGR to configure each of the following subsystems:

  • The distributed terminal subsystem (DTS), which defines connections for terminals, printers, and other serial devices that will be able to communicate with the system.

  • The Network Services (NS) subsystem, which defines the operation of NS links and services between HP 3000 systems.

  • The BSC subsystem, which defines BSC communication links between HP 3000 and IBM systems.

  • The SNA subsystem, which defines SNA communication links between HP 3000 and IBM systems.

The Configuration File

NMMGR stores configuration information in a special MPE configuration file that contains the data needed by the system for networking and terminal-to-system communications. The file has the MPE file code NCONF and may contain three kinds of data:

  • Standard software operating parameters, such as limits on using MPE resources.

  • Node-specific information, such as the name of the local computer and its network address.

  • Information needed by the network software in order to communicate with other nodes to which the local node is connected.

The configuration file must be named NMCONFIG.PUB.SYS in order to be recognized and used by the system. You may, however, create a configuration file using any valid MPE file name and rename it as NMCONFIG.PUB.SYS when you are ready for the system to use the configuration information it contains.

NMCONFIG.PUB.SYS must reside on LDEV1 in order to be recognized. The system does not have access to other LDEVs at startup and the configuration file is needed at that time.

With a few exceptions, the changes you make to the NMCONFIG.PUB.SYS file take effect only when the system is rebooted. In most cases, you should avoid making changes to an active configuration file (one that the system is currently using). There are 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. You may change the name of the file by typing a new name in place of the default. The backup file also has the file type NCONF. Each time a subsystem is successfully validated, the backup file is automatically updated with the configuration information. In the event that something should occur to cause your active configuration file to be corrupted, you can rename the backup file and avoid having to recreate NMCONFIG.PUB.SYS from scratch.

The Sample Configuration File

Hewlett-Packard provides a sample configuration file with every HP 3000 Series 900 system. This file contains some basic configuration information for the link, NRJE, SNANODE, IMF, DTS and logging subsystems. It can be used as a template to help you when you are creating a new system configuration. The sample file is named NMSAMP1.PUB.SYS. To use the sample file, make sure you copy it to a new name, then run NMMGR and modify the copy that you just created so that it contains your system's configuration information.

NOTE: Check "Copying a Configuration File" in Chapter 3 “Using NMMGR in Screen Mode” for important information about this procedure.

The Network Directory File

NMMGR stores network directory information for the NS subsystem in a second special file called the network directory file. This file, of file type NDIR, contains information required for one node to communicate with another node in an internetwork (network of networks).

The network directory file must be named NSDIR.NET.SYS but, like the configuration file, you may create a directory file under another name and rename it when you are ready for the system to use the directory information it contains.

NOTE: A network directory uses a KSAM file pair. Therefore, if copying a directory, be sure to copy both the data file and the key file. If the file name you create is NSDIR.NET.SYS, the KSAM pair of the file will be named NSDIRK.NET.SYS, and its file type will be KSAMK.

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. This interface may also be run interactively from within NMMGR. The maintenance interface includes commands that let you manage network directories and configuration files. When using this interface to run NMMGR, you are operating in maintenance mode.



Chapter 1 Introduction
  		 


NMMAINT  
Feedback to webmaster