NET/MASTER Messages Manual

What to Prepare Before Contacting Your Tandem Support Representative
Introduction
106159 Tandem Computers Incorporated 1–3
Communications Problem If there is an Inter-NET/MASTER Connection (INMC) problem, gather the NonStop
NET/MASTER MS version number, and the SOLVE management services version
numbers, if applicable. Gather these version numbers as they pertain to any
intermediate nodes as well.
If the connection is to a SOLVE system, gather the IBM ACF/VTAM version
information. If the connection is to a SOLVE:Connect system, gather the IBM
ACF/VTAM and NetView version information.
Use the SOLVE management services STATUS command to obtain the version
information of the respective system and the IBM ACF/VTAM system.
Also, have ready the following:
Description of the network topology.
Communications configuration and startup files for the local and remote systems.
System configuration file, $SYSTEM.SYSnn.CONFTEXT for the local system, and
for the remote system if the connection is to NonStop NET/MASTER MS. If the
connection is to a SOLVE system, get the IBM ACF/VTAM definition.
Commands and NCL procedures used to define and start the link for the local and
remote systems.
Output of a PUP LISTDEV command.
DSNM Problem If there is a problem with DSNM, gather the version information, and information on
the following:
How DSNM was installed
Whether DSNM was started prior to starting the NonStop NET/MASTER MS
system, or the NonStop NET/MASTER MS system started the DSNM
The VPROC of any utility executed by PROGRUN or OPSYS
Terminal Problem If there is a problem with a terminal, state the terminal type, emulator (if applicable),
and setup.
Additional Information Other information that you should have ready includes the following:
A history of the problem: Has it happened before? If so, when and under what
conditions did it happen? Can you reproduce it? If so, state how to reproduce it.
A list of any recent changes to the system including, but not limited to, new or
changed configuration parameters, new or upgraded software modules, new
hardware components, or changed NCL procedures.
A copy of the USER/GROUP affected by the problem.
The results of SHOW SYSPARMS and SHOW PARAM statements.
A list of the output of any tracing associated with the problem.