SNA IMF/XL Node Manager's Guide (30293-90010)

Chapter 3 19
SNA IMF Configuration
NMMGR Configuration Overview
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,