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

44 Chapter5

SNA IMF Troubleshooting

Problem Resolution

• Pass Thru problems.

Ensure that the HP terminal supports Pass Thru and that its MPE

I/O conﬁguration is correct. Using SNA IMF Pass Thru lists the

terminals and printers you can use with Pass Thru.

SNA IMF Run-Time Problems

After both the hardware and software are installed, problems might

occur. Many run-time problems are caused by inaccurate conﬁguration.

You might encounter some of these problems while attempting to run

SNA IMF or while actually running SNA IMF:

• Inactive SNA node.

If you attempt to run SNA IMF without starting the HP 3000 node

on which SNA IMF will be running, you will receive this message:

Inactive node or invalid node name. (SNAERR 29)

Use the SNACONTROL START command to activate the node. For

example,

SNACONTROL START;NODE=

NodeName

(The SNACONTROL commands are described in the SNA Link/XL

Node Manager’s Guide.) If everything is set up correctly, you should

receive some SNA logging messages that indicate that the line has

been activated, and that sessions (SSCP-PU and SSCP-LU) have

been started for the PU and LUs that you want to use. If not, you

should ensure that the proper resources are active on the host side,

by having the IBM operator issue the DISPLAY command.

D NET,E,ID=

LineName

at the host console. Then, if the proper resources are not active, the

IBM operator should issue the VARY command.

V NET,ACTIVE,ID=

LineName

to activate the line. Then, a second VARY command should be issued:

V NET,ACTIVE,ID=

PuName

V NET,ACTIVE,ID=

LuName

to activate the PU or LU. Note that both of the above steps can be

done by issuing only one command:

V NET,ACTIVE,SCOPE=ALL,ID=

LineName

The PU and each LU activation request might require a separate

VARY command to completely activate the node. This occurs when

the ISTATUS operand of the LU macro (in the node deﬁnition) is not