SNAX/HLS Diagnosis and Support Manual

1 Problem Determination
104706 Tandem Computers Incorporated 1–1
This section suggests ways to handle problems that can occur in a SNAX/HLS
environment.
Use the following steps to help you become efficient at troubleshooting SNAX/HLS.
(You may also need this information if you have to escalate a problem to Tandem
support personnel.)
1. Use the VPROC utility to get the SNAX/HLS version information. Use the
HLSCOM PEEK command to obtain additional version information. (Refer to the
SNAX/HLS Configuration and Control Manual for information on using HLSCOM).
To use the VPROC utility, enter:
VPROC $SYSTEM.SYSTEM.HLSOBJ
2. Use the HLSCOM utility to take a trace of the problem occurring, if possible.
3. Obtain a copy of the OPRLOG file and the SNAX/HLS LOGFILE file, if possible.
4. Obtain copies of your RDTDATA, RDTTEXT, and your Pathway startup files.
These files tell you what PROFILE and BIND configurations you are using for
your sessions.
5. Identify the name of the PROFILE under which the session was established.
6. If your CPU is down, obtain a dump.
7. Refer to the following subsections for specific problem-solution information.
The remainder of this manual provides information about analyzing traces (Section 2)
and about analyzing various SNAX/HLS error and log messages (Appendixes A, B,
and C). (Appendix D discusses converting the Response Definition Table (RDT).
Building an Operation
History
SNAX/HLS has been tested using a variety of gateway applications (for example, IMS
SLU_P, CICS 3600 LU, and CICS pipeline LU) and has supported a variety of devices
(for example, 3624 ATMs, and 327x devices). It is nevertheless suggested that your
installation generate a continuous log and (especially at the beginning) a trace of
SNAX/HLS operation. This data is essential to diagnosing problems.
The Log File You can use the SNAX/HLS log file output to determine or diagnose problems with
your system. You should direct the log file to a secure disk (for example, $SYSTEM) so
that it is always obtainable. (See the SNAX/HLS Configuration and Control Manual for a
discussion of issues surrounding the log file and the LOG configuration parameter.)
The Trace File See the SNAX/HLS Configuration and Control Manual for information on how to
generate a SNAX/HLS trace using the TRACE command. If no problems occur, you
can ignore the trace and purge the trace file. If problems do occur, your trace is
invaluable in diagnosing problems.