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

42 Chapter5

SNA IMF Troubleshooting

Problem Resolution

Corrupt Conﬁguration File

The conﬁguration ﬁle is possibly corrupt. Validate the conﬁguration ﬁle

to check for possible corruption. If the error persists, use NMMGR to

manually check the conﬁguration ﬁle (if possible). If bad records seem

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 might have occurred while trying 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.

• PSI problems.

When you run the PUs concurrently, each PSI requires a unique PU

and each PU requires a unique PSI.

Also, if you are using an SDLC link, 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 IMF, the conﬁguration ﬁle can be

named anything you prefer. However, when you run SNA IMF, 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.

Too many or the wrong type of device might have been conﬁgured for

a particular line.

• Incorrect macro deﬁnition.

Macro operands might have been incorrectly placed within the

hierarchical structure. Although the operands for lower-level macros