Exchange/SNA Manual

Before Contacting Tandem
Exchange/SNA Messages
104700 Tandem Computers Incorporated A–35
Before Contacting
Tandem
Some of the error message explanations indicate that you need to contact your local
Tandem support office to solve the problem. This section outlines the information you
need to have available before you contact Tandem.
Step 1. Gather Version Information
Use the VPROC utility to gather the full version information for the RJECIS, SNAXSV,
and SNAXSRSV processes in use at the time of the failure:
>VPROC /OUT outfilename /
Enter Filename:
> $SYSTEM.SYSTEM.RJECIS
> $SYSTEM.SYSTEM.SNAXSRSV
> $SYSTEM.SYSTEM.SNAXSV
VPROC output looks similar to this:
$SYSTEM.SYSTEM.RJECIS
Binder timestamp: 31OCT90 09:16:51
Version procedure: T9134C20^07DEC90^SNAC20^V000
You also need to gather version information for the SNAX/XF or SNAX/CDF
processes you were using.
>VPROC /OUT out-filename /
Enter Filename:
> $SYSTEM.SYSTEM.CDFOBJ (for SNAX/CDF)
OR
> $SYSTEM.SYS nn .SVMOBJ (for SNAX/XF)
> $SYSTEM.SYS nn .SNATSOBJ
> $SYSTEM.SYS nn .SNAIHOBJ
If you are using SNAX/XF and cannot locate these files, you can get the necessary
version information from the CONFLIST file.
Step 2. Determine Host Application Name and Version
Follow the instructions indicated in the manuals for your host system to determine the
name and version of the host application with which your Exchange/SNA session was
communicating at the time of the failure. Some possible host processes are JES2, JES3,
or POWER.
Step 3. Collect Additional Information as Necessary
In general, you need to be prepared to report what Exchange/SNA was attempting to
do at the time of the failure. Some useful information includes:
The commands being executed by Exchange/SNA
A copy of the command file, if you are using one