Using the Node Management Services (NMS) Utilities (32022-90053)

Chapter 2 33

Basics of NMMGR

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 speciﬁed screen.

Moving with Function Keys

When you are creating a conﬁguration ﬁle, you will generally traverse

downward on one of the conﬁguration branches until you have

completed conﬁguration for a subsystem.

Normally, you will make selections or enter data into the lowest level

data screens of a branch before moving to another branch. You may

need to transfer only to screens directly above or below your current

screen in the structure. This is generally accomplished by pressing the

appropriate function key.

Branching

Branching is a method you can use to go directly to a particular

screen, rather than traveling through every screen in a branch to get to

that screen.

Direct Path Branching

You can use direct path branching to transfer from any NMMGR

screen to any screen having a path name in one of the subsystem

branches. To use this feature, you must be familiar with the tree

structure of the conﬁguration ﬁle. You enter @pathname in the

command window to cause NMMGR to transfer you to the screen at the

end of the speciﬁed path name. For example, when conﬁguring SNA,

you could enter @SNANODE.PU3000E in the command window to see the

LUs conﬁgured for the node PU3000E. The path name for each

subsystem conﬁguration screen is displayed in the Path ﬁeld of each

screen.

Brother Branching

Screens that share a common parent screen are referred to as brothers.

If you are working in a screen with one or more brothers, you can use

the NEXT command to transfer to the next brother screen. This feature

is called brother branching.

For example, the unguided NS conﬁguration screen called NETXPORT

Conﬁguration has three subscreens, or children, referred to here by

their path names:

NETXPORT.GLOBAL,