 |
» |
|
|
|
Problems that can occur while installing, configuring, and
running SNA IMF, and how to deal with them, are described here.
Guidelines for submitting a service request (SR) are also described. 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 InstallationA software installation might be invalid. Run NMMAINT 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 correctly. Version IncompatibilitiesVersion 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 ResourcesThe system might have insufficient MPE resources, such as
configured table sizes. Run SMT.PUB.SYS to check MPE table utilization. Reconfigure MPE
to fix any problems found and restart the system. Corrupt Configuration FileThe 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. A file system error might have occurred while trying 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 ProblemsListed below are some configuration 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 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 IMF, the configuration
file can be named anything you prefer. However, when you run SNA
IMF, it looks for a configuration file named NMCONFIG.PUB.SYS.
Host Configuration ProblemsListed below are some configuration problems that can occur
on the host. Incorrect device specified. Too many or the wrong type of device might have been
configured for a particular line. Incorrect macro definition. Macro operands might have been incorrectly placed within
the hierarchical structure. Although the operands for lower-level
macros can be defined in a higher-level macro, this structure must
be followed: GROUP, LINE, SERVICE, PU, and LU. A macro could be missing a required operand or an invalid
operand might have been specified for a particular macro. Incorrect Logmode table definition. Ensure that the correct Logmode Table definitions are
being used. The HP SNA Products: ACF/NCP and ACF/VTAM Guide contains more
information about this.
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 the proper activation commands have been
issued. 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. (The 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
Exchange Station Identification (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 the VBUILD macros are 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. Pass Thru problems. Ensure that the HP terminal supports Pass Thru and
that its MPE I/O configuration 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 configuration. 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. at the host console. Then, if the proper resources are not
active, the IBM operator should issue the VARY command. to activate the line. Then, a second VARY command should be issued: or 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 definition) is not set to ACTIVE or is not placed high enough in the node definition
(see "Host Configuration Problems" earlier in
this chapter). Unable to log on. To log on, the display screen must be owned by the
SSCP-LU session. Remember, display screen ownership is shared between
the LU-LU session and the SSCP-LU session. When you first start
Pass Thru, the screen is unowned. Press the System Request Key (SRK) to
transfer display ownership to the SSCP-LU session. You can then log
on to the host system.
Submitting an SR | |
Listed below are some guidelines for submitting a service
request (SR). Some of the guidelines refer to Node Management Services
(NMS) programs (NMDUMP, NMMAINT, NMMGR, etc.). Using NMMAINT for
SNA IMF is explained earlier in this chapter. Using NMMGR for SNA
IMF is explained in Chapter 3 “SNA IMF Configuration” of this manual.
Since SNA IMF tracing and logging are part of SNA Transport tracing
and logging, using NMDUMP to format those files is not explained
in this manual (see the SNA Link/XL Node Manager's Guide).
For more NMS information, see Using the Node Management Services
Utilities. For any SR, include this common information, where applicable: A characterization of the problem.
Describe the events leading up to and including the problem. Try
to describe the source of the problem. Describe the symptoms of
the problem. Your characterization should include MPE commands, communication
subsystem commands, job streams, result codes and messages, and
data that can reproduce the problem. List the context and environment in which the message occurred. Prepare
copies of the HP 3000 system console information. Give a brief history of your site, including when SNA IMF
was installed, the circumstances that usually produce problems,
other data communications products installed, and any other products
you were using when the problem arose. Obtain the version, update, and fix information
for all software by running NMMAINT (for SNA IMF, you also can call
the VERS3270 intrinsic). This allows Hewlett-Packard to determine
whether the problem is already known and if the correct software
is installed at your site. Record all result messages and numbers that appear
at the user terminal and the system console. Run NMDUMP to format the NM log file (NMLGnnnn.PUB.SYS) that was active when the problem occurred. You
might need to issue the MPE command SWITCHNMLOG to free the NM log file. For more information, see the
SNA Link/XL Node Manager's Guide.
Inspect the formatted output and try to locate errors. Prepare the
formatted output and a copy of the log file for your HP representative
to analyze. Prepare a listing of the configuration file and
the MPE configuration you are using for your HP representative to
analyze. Inspect the output and try to locate errors. Try to determine the general area, within the software,
where you think the problem exists. If you think the problem is
caused by an SNA link, refer to the SNA Link/XL Node
Manager's Guide and follow the guidelines there
for gathering information for problems. Document your interim, or "workaround," solution.
The cause of the problem can sometimes be found by comparing the
circumstances in which it occurs with the circumstances in which
it does not occur. Save copies of any SNA trace and communications
link trace files that were active when the problem occurred, for
your HP representative to analyze. If the problem involves NMMGR, give a copy of
NMMGRF.PUB.SYS to your HP representative. If a system failure occurs, a full memory
dump must be taken. If a fatal SDLC link error has occurred, a message
in this format is displayed on the operator's console: SDLC (LinkName) Error ErrorNum:
SDLC (LinkName) Info: Status=Status,
Loc=LocationId, Path=PhysPath |
Be sure to include this error message in the SR exactly
as it appears on the operator's console. Save copies of all active or in-use trace files
for analysis by your HP representative. Save copies of all active or in-use log files for
analysis by your HP representative. Record all intrinsic result codes and Pass Thru
messages that appear at an emulated terminal or printer and the
HP 3000 console. Always obtain a copy of the host system generation
you are using. For the host configuration to be compatible with
SNA IMF, Hewlett-Packard sets certain operands and parameters to
required values (see Chapter 3 “SNA IMF Configuration” of this manual). Also
see the SNA Link/XL Node Manager's Guide for
more host configuration information. Note any differences between
the actual system generation and your expectations. Keep this information
for your HP representative. This is very important. Give a copy of NMCONFIG.PUB.SYS to your HP representative. Issue the SNACONTROL STATUS command (see the SNA Link/XL Node Manager's
Guide for a description of the command).
SNA Transport InformationFor problems that might involve SNA Transport, see the SNA
Link/XL Node Manager's Guide. Communications Link InformationFor problems that might involve the communications link, see
the SNA Link/XL Node Manager's Guide. |
