SNA Link/iX Node Managers Guide (30291-90507)

40 Chapter2

SNA Node and Link Conﬁguration

NMMGR Conﬁguration Overview

The SNA node and link conﬁguration is done by using NMMGR to

create or modify a conﬁguration ﬁle. The ﬁle contains this information:

• SNA node information: used by SNA Transport to manage sessions

with the host.

• Link information: used for SDLC data link control and phone data

(for switched lines), X.25 link information, and token ring link

information.

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 that you must

have node manager (NM) or network administrator (NA) capabilities to

use NMMGR.

NOTE

When conﬁguring an SNA node and link, the conﬁguration ﬁle can be

named anything you prefer. However, when you

start

the node and

link, it looks for a conﬁguration ﬁle named NMCONFIG.PUB.SYS. For

example, you could have these conﬁguration ﬁles:

XYZ.CONFIG.SYS

CONFIG1.FILES.SYS

FILE3.CONFIG.SYS

If you wanted to use FILE3.CONFIG.SYS when you started the SNA

node and link, you would have to rename or copy the ﬁle to

NMCONFIG.PUB.SYS

before

you started the node and link.

SNA Node Information

SNA node information is used by SNA Transport, which manages data

transmission for the SNA services by providing an interface to establish

LU-LU sessions with the host.

Before SNA Transport can allow the SNA services to establish sessions

between dependent LUs, SNA Transport must establish

communication with the host’s System Services Control Point (SSCP).

The SSCP manages the SNA network functions on the host. It also

manages SNA network functions on the HP e3000, via the PU-SSCP

session. For dependent LU sessions, the HP e3000 must establish a

PU-SSCP session and LU-SSCP sessions. You do not have to conﬁgure

any information for the PU-SSCP or LU-SSCP sessions because it is

already set in the SNA Transport software.

For a session between independent LUs, an associated LU-SSCP

session is not required. This is the major difference between dependent

LUs and independent LUs.