NMMGR Configuration Overview

The SNA IMF configuration is done by using NMMGR to create or modify a configuration file. The basic operation of NMMGR is described in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing.

NOTE: When configuring SNA IMF, the configuration file can be named anything you prefer. However, when you run SNA IMF, it looks for a configuration file named NMCONFIG.PUB.SYS. For example, you could have these configuration files:

XYZ.CONFIG.SYS

CONFIG1.FILES.SYS

FILE3.CONFIG.SYS

If you wanted to use FILE3.CONFIG.SYS when you ran SNA IMF, you would have to rename or copy the file to NMCONFIG.PUB.SYS before you started SNA IMF.

You configure these items for SNA IMF:

SNA node and security class identification data. This is the name of the SNA node you are specifying security class information for, and the name of the security class you are configuring.
Security class data. A list of up to 64 LUs can be configured for a security class.
Authorized user data. A list of up to 42 users can be authorized to use the LUs in a security class.
Authorized program data. A list of up to 26 programs can be authorized to use the LUs in a security class.




	NOTE: If you change the node configuration for SNA IMF while it is running, the changes will not take effect until SNA IMF is restarted.

Location of NMMGR Screens

Refer to the List of Figures for a location of the NMMGR screens used in SNA IMF configuration; it lists the page in this manual on which each screen is shown.

Configuration File Validation

Validating the configuration file ensures that the configuration data is logically and syntactically correct. Each SNA service's data is also checked against the SNA node configuration data for correctness (for example, correct LU names). See Appendix A “Validation Messages” of this manual for SNA IMF validation error messages.

You should validate the configuration file after completing any of these tasks:

An initial configuration of one or more SNA nodes
An initial configuration of one or more SNA services
A modification of an existing configuration

The configuration file is validated through NMMGR; see Using the Node Management Services Utilities.

Configuration File Critical Summary

The critical summary is a printout of the data in the configuration file. It can be used to check current contents of the configuration file, (without opening the file) to determine whether the configuration is correct. The critical summary is generated through NMMGR; see Using the Node Management Services Utilities.

An example of a critical summary of SNA IMF configuration data is shown below.

     CRITICAL SUMMARY — SNA IMF CONFIGURATION
 
THU, FEB 16, 1989,  2:50 PM
CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS
Validated subsystem.
 
SNANODE Name: IBMNODE
 
 Security Class: ISPFUSER
     LU List:     LUNAME01, LUNAME02, LUNAME03, LUNAME04, LUNAME05, LUNAME06,
                   LUNAME08, LUNAME09, LUNAME10, LUNAME11, LUNAME12, LUNAME13,
                   LUNAME15, LUNAME16, LUNAME17, LUNAME18, LUNAME19, LUNAME20,
                  LUNAME22, LUNAME23, LUNAME24, LUNAME25, LUNAME26, LUNAME27
 
     User List:    @.IMF,              @.SERVER,           OPERATOR.SYS,
                   USER1,              USER2.SYS,          USER3,
                   USER4,              USER5
 
     Program List: TTSSON.PUB.SYS,             PROGRAM1,
                   PROGRAM2.PUB.SYS,           PROGRAM3,
                   PROGRAM4,                   PROGRAM5

 Security Class: SDSFUSER
     LU List:      LUNAME01, LUNAME02, LUNAME03, LUNAME04, LUNAME05, LUNAME06,
                   LUNAME08, LUNAME09, LUNAME10, LUNAME11, LUNAME12, LUNAME13,
                   LUNAME15, LUNAME16, LUNAME17, LUNAME18, LUNAME19, LUNAME20,
                   LUNAME22, LUNAME23, LUNAME24, LUNAME25, LUNAME26, LUNAME27,
                   LUNAME29, LUNAME30, LUNAME31, LUNAME32, LUNAME33, LUNAME34,
                   LUNAME36, LUNAME37, LUNAME38, LUNAME39, LUNAME40, LUNAME41,
                   LUNAME43, LUNAME44, LUNAME45, LUNAME46, LUNAME47, LUNAME48,
                   LUNAME50, LUNAME51, LUNAME52, LUNAME53, LUNAME54, LUNAME55,
                   LUNAME57, LUNAME58, LUNAME59, LUNAME60, LUNAME61, LUNAME62,
                  LUNAME64
 
     User List:    USER1,              USER2,              USER3,
                   USER4,              USER5,              USER6
 
     Program List: PROGRAM1,                   PROGRAM2,
                   PROGRAM3,                   PROGRAM4,
                   PROGRAM5
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
 SNANODE Name: IBMNODE2
 
   Security Class: CLASS2
     LU List:      LNAME01,  LUNAME02, LUNAME03, LUNAME04
 
     User List:    USER1,              USER2,              USER3,
                   USER4,              USER5,              USER6,
                   USER7
 
     Program List: PROGRAM1,                   PROGRAM2,
                   PROGRAM3,                   PROGRAM4,
                   PROGRAM5,                   PROGRAM6,
                   PROGRAM7
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

SNANODE Name: IBMNODE3
 
   Security Class: CLASS3
     LU List:      (None configured)
 
     User List:    (None configured)
 
     Program List: (None configured)
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
SNANODE Name: IBMNODE4
 
   Security Class: CLASS1
     LU List:      LUNAME01, LUNAME02, LUNAME03, LUNAME04
 
     User List:    USER1,              USER2,              USER3,
 
     Program List: PROGRAM1
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
SNANODE Name: IBMNODE5
 
   Security Class: CLASS5
     LU List:      (None configured)
 
     User List:    (None configured)
 
     Program List: (None configured)
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
Some fields could not be found or printed.

NMMGR Configuration Overview

Technical documentation

» Table of Contents

» Glossary

» Index

Location of NMMGR Screens

Configuration File Validation

Configuration File Critical Summary