SNA NRJE Node Managers Guide (30292-90007)

74 Chapter5
SNA NRJE Troubleshooting
Problem Resolution
SNA NRJE Run-Time Problems
After both the hardware and software are installed, problems might
occur. Many run-time problems are caused by inaccurate configuration.
You might encounter some of these problems while trying to run NRJE
or while actually running NRJE:
• Inactive SNA node.
If you try to run SNA NRJE without starting the node on which
NRJE 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, on MPE V:
:SNACONTROL START;CONFIG= ConfigFile ;NODE= NodeName
and, on MPE XL:
SNACONTROL START;NODE= NodeName
(The SNACONTROL commands are described in the SNA Link Services
Reference Manual [for MPE V] and the SNA Link/XL Node
Manager’s Guide [for MPE XL].) 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 issuing the DISPLAY command at a host operator’s console.
D NET,E,ID= LineName
Then, if the proper resources are not active, issue the VARY command
V NET,ACTIVE,ID= LineNam
to activate the line. Then, issue a second VARY command:
V NET,ACTIVE,ID= PUName
or
V NET,ACTIVE,ID= LUName
to activate the PU or LU. Note that you also can do both of the above
steps 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 definition) is not
set to ACTIVE or is not placed high enough in the node definition (see
“Host Configuration Problems” earlier in this chapter).