SNA NRJE Node Managers Guide (30292-90007)

72 Chapter5

SNA NRJE Troubleshooting

Problem Resolution

to be localized to a particular item, delete that item and reconﬁgure it.

If necessary, RESTORE a backup copy of the ﬁle.

File System Errors

A ﬁle system error (FSERR)might have occurred while attempting to

access the conﬁguration ﬁle. Try to access the conﬁguration ﬁle, under

the same userid, using NMMGR. Use the NMMGR error screen to ﬁnd

out what the underlying FSERR is. Correct the problem and retry.

Conﬁguration Problems

Conﬁguration problems can occur on both the HP 3000 and the host.

HP 3000 Conﬁguration Problems

Listed below are some conﬁguration problems that can occur on the

HP 3000.

• INP or PSI problems.

When you run the PUs concurrently, each INP or PSI requires a

unique PU, and each PU requires a unique INP or PSI.

Also, for NRJE/V, ensure that you correctly conﬁgured the Logical

device ﬁeld of the Link Conﬁguration: SNA/SDLC Link Data

Screen (see the SNA Link Services Reference Manual). For

NRJE/XL, ensure that you correctly conﬁgured the Physical Path

ﬁeld of the SNANode Conﬁguration: SDLC Linkdata Screen (see the

SNA Link/XL Node Manager’s Guide).

• Conﬁguration ﬁle misnamed.

Remember, when conﬁguring SNA NRJE, the conﬁguration ﬁle can

be named anything you prefer. However, when you run SNA NRJE,

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

Host Conﬁguration Problems

Listed below are some conﬁguration problems that can occur on the

host.

• Incorrect device speciﬁed.

You might have conﬁgured too many devices or the wrong type of

device for a particular line.

• Incorrect macro deﬁnition.

You might have incorrectly placed macro operands within the

hierarchical structure. Although you can deﬁne the operands for

lower-level macros in a higher-level macro, you must remember this

structure: GROUP, LINE, SERVICE, PU, and LU.