Problem Resolution

Problems that can occur while installing, configuring, and running SNA NRJE — and how to deal with them — are described here. Guidelines for submitting a service request (SR) are also described.

When an NRJE problem occurs, to enable collection of some important information, you must perform these steps:

For MPE V, enable SNA LU-LU tracing to disk (if directed to by an HP service representative) for each LU you are using by doing the following things:
- Specifying the LUs you are using, in the SNA Configuration: LUs screen.
- Setting Trace State LU-LU to Disk, in the SNA Configuration: LU Data screen.
For MPE XL, enable SNA intrinsic tracing to disk for each LU you are using by doing these things:
- Specifying the LUs you are using, in the SNANode Configuration: PU and LU Data screen.
- Turning on intrinsic tracing by using the INTRINSIC parameter of the SNACONTROL TRACEON command.
Enable logging to disk for the NRJE subsystem by doing these things:
- Configuring SNA NRJE logging, in the Logging Configuration screen.
- Configuring all SNA NRJE logging classes, in the Logging Configuration: Logging Classes screen.
- Enabling disk logging, in the Logging Configuration: Class Data screen.

Specific procedures for configuring MPE V logging and tracing are in the SNA Link Services Reference Manual. MPE XL logging configuration and trace enabling are described in the SNA Link/XL Node Manager's Guide.

Once tracing and logging are enabled, attempt to recreate the problem. Whether or not you are able to recreate the problem, you should follow the procedures below to collect the information you need to resolve the problem.

Common Problems

Some problems are common to many situations — invalid software installation, version incompatibilities, insufficient MPE resources, corrupt configuration files, and file system errors. In most cases, you can resolve these problems yourself; the resolutions to these problems are described here. However, in some cases you should submit an SR. To enable Hewlett-Packard to solve your problem in an efficient manner, you should follow certain guidelines when submitting an SR; these guidelines are listed later in this chapter.

Invalid Software Installation

A software installation might be invalid. Run NMMAINT.PUB.SYS to get a listing of all software modules and their version IDs. Check that all required modules are present, and that the first five characters of the version IDs (the v.uu.ff fields) of these modules are the same within each subsystem. Finally, check the version IDs with the SYSTEM STATUS BULLETIN or other HP source to be sure the versions of software you have are supported by the version of MPE you have. If a problem is found with any of these checks, you have an incorrect software version installed. Locate a known valid version of the suspect software (perhaps from one of your system backup tapes) and install it.

Version Incompatibilities

Version incompatibilities between NMS software and other subsystem software are possible. Run NMMAINT to get a listing of version IDs for NMS and for all of the NMS-dependent subsystems. Locate the overall version IDs for NMS and for each subsystem. Compare the first five characters of these version IDs (the v.uu.ff fields) with those listed as compatible with each other in the SYSTEM STATUS BULLETIN or other HP source. If a discrepancy is found, locate a known set of compatible software (perhaps from one of your system backup tapes) and install it.

Insufficient MPE Resources

The system might have insufficient MPE resources, such as configured table sizes, stack size, concurrent jobs, and maximum segment size. For NRJE/V, check whether the MPE configuration has enough DST and PCB entries configured, and run OPT.PUB.SYS in the "#T" or MPE tables context to check MPE table utilization. Reconfigure MPE to fix any problems found, and restart the system.

Corrupt Configuration File

The configuration file is possibly corrupt. Validate the configuration file to check for possible corruption. If the error persists, use NMMGR to manually check the configuration file (if possible). If bad records seem to be localized to a particular item, delete that item and reconfigure it. If necessary, RESTORE a backup copy of the file.

File System Errors

A file system error (FSERR)might have occurred while attempting to access the configuration file. Try to access the configuration file, under the same userid, using NMMGR. Use the NMMGR error screen to find out what the underlying FSERR is. Correct the problem and retry.

Configuration Problems

Configuration problems can occur on both the HP 3000 and the host.

HP 3000 Configuration Problems

Listed below are some configuration 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 configured the Logical device field of the Link Configuration: SNA/SDLC Link Data Screen (see the SNA Link Services Reference Manual). For NRJE/XL, ensure that you correctly configured the Physical Path field of the SNANode Configuration: SDLC Linkdata Screen (see the SNA Link/XL Node Manager's Guide).
Configuration file misnamed.
Remember, when configuring SNA NRJE, the configuration file can be named anything you prefer. However, when you run SNA NRJE, it looks for a configuration file named NMCONFIG.PUB.SYS.

Host Configuration Problems

Listed below are some configuration problems that can occur on the host.

Incorrect device specified.
You might have configured too many devices or the wrong type of device for a particular line.
Incorrect macro definition.
You might have incorrectly placed macro operands within the hierarchical structure. Although you can define the operands for lower-level macros in a higher-level macro, you must remember this structure: GROUP, LINE, SERVICE, PU, and LU.
A macro could be missing a required operand or you might have specified an invalid operand for a particular macro.
Incorrect Logmode Table definition.
Ensure that you are using the correct Logmode Table definitions. See the HP SNA Products: ACF/NCP and ACF/VTAM Guide Host System Programmer's Reference for more information.

Installation Problems

Some common problems that might occur during installation, or as a result of improper or unsuccessful installation, are described below.

Inactive VTAM node.
This is probably the most common problem that occurs on the host. Ensure that you have issued the proper activation commands. Setting the ISTATUS operand of the LU macro to ACTIVE will help, especially if it is moved up to either the GROUP or LINE macro. This ACTIVE setting sifts down to all lower-level macros. This problem most frequently occurs in a switched line configuration when the major node containing the VBUILD macro was never activated. In this case, an inactive macro causes the host to fail to find a match for the remote's XID number. The only way you will be aware that this XID problem has happened is a message at the host operator's console. To avoid these problems remember this rule: When in doubt, ACTIVATE.
Switched lines.
Be sure to put the VBUILD macros in a separate member in the VTAM parameter library (SYS1.VTAMLST).
Hardware problems.
Ensure that all hardware is installed properly. Many problems are related to such things as incompatible modems, bad phone lines and cables, etc.
Ensure that the host is up, the line is active (being polled), and the host telecommunications subsystem (for example, VTAM) is active. You might need to use a line monitor, such as an HP 4953, which requires the link option to check whether the line is being polled and to determine the addresses being polled. You also can use one of the other HP 495x Protocol Analyzers in addition to the standard HP 4953.

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).
SNA Transport activates, but one or more SNA NRJE LUs do not (MPE V only).
- Ensure that the transmit buffer size (in the Link Configuration: SNA/SDLC Link Data screen), the maximum RU size (in the SNA Configuration: LU Data screen), and the RU size (in the NRJE Configuration: Reader Data screen) are consistent. If the SNA maximum RU size for the LU has been configured less than the NRJE RU size, that LU will not be able to send an INIT-SELF to request an LU-LU session with the host.
- Ensure that the host has activated the LU. If it has not, make the LU active by issuing
  V NET,ACTIVE,ID=LUName
  at a host operator's console. You might have to issue a separate VARY command for each LU.
SNA Transport activates (case 1).
Although SNA Transport is active when the NRJE Wsid command is typed, this message is received:
WORKSTATION Wsid NOT CONFIGURED (CIERR 4435)
SNA NRJE has not found a file named NMCONFIG.PUB.SYS to use as its configuration file. You must name the SNA NRJE configuration file NMCONFIG.PUB.SYS.
SNA Transport activates (case 2).
Although SNA Transport is active when you try to start an SNA NRJE workstation with a STARTWS or NRJECONTROL STARTWS command, you get this message:
UNABLE TO STREAM MONITOR JOB (INT=123)
which can be caused by (1) the MPE streaming facility not being enabled, or (2) an unfound xxx.NRJE.SYS job stream file for the SNA NRJE workstation. (See Chapter 4 “NA NRJE Workstation Startup and Shutdown” of this manual for a description of this job stream file.)
This message is logged for each LU just before it terminates:
FMD CANNOT ACCESS READER AND WRITER CONFIGURATION DATA (SPOOLER=-7) (MIDAS=0) (FMD=4121)
This indicates a probable problem in NMCONFIG.PUB.SYS: You might have changed data on a configuration screen but not pressed [f6] (Update Data) afterwards. So, the configuration was not updated.




	NOTE: Remember to consult Appendix A “Result Codes and Messages” of this manual for a description of error messages and intrinsic result codes. You might encounter other error messages while using SNA NRJE. See the SNA Link Services Reference Manual (for MPE V) or Using the Node Management Services Utilities (for MPE XL) for generic messages produced by NMMGR and the utilities NMMAINT and NMDUMP.