GDSX Manual

Operations and Support
Extended General Device Support (GDSX) Manual–134303
3-28
If GDSX Abends
Here is an example command using BIND:
> BIND LIST CODE(T6580) FROM $SYSTEM.Y6580D44.OGDS
•
Save the abend file for analysis. If the GDSX process ceases to function, it attempts
to send an abend message to the home terminal where the process was created. An
internal error number is displayed and the abend file is saved. For information on
what to do for various error numbers, see “Abend Messages” on page 3-19.
To determine the sequence of events prior to the abend, you can issue the commands
shown in the following example. Note that the sequence of procedure names
(preceded by # signs) is only an example.
> INSPECT ADD PROGRAM $VOL.SUBVOL.ZZSAnnnn
--TRACE 1 ARG
ABEND
#DIE
#KERNELERROR
#DELETE^XITEM
--EXIT
•
If a problem occurs with a GDSX process that was running a trace, save the trace
file because subsequent GDSX runs might write over data in the file. The default
name for the primary process trace file is TRACEP; the default name for the backup
process trace file is TRACEB. For more information on the trace facility, see
“Tracing GDSX” on page 2-76.
•
If the problem involves SCF or SPI, record the version procedures for SCF and SCP.
Within SCF, use the LOG command to capture appropriate information provided by
commands such as INFO PROCESS, INFO LINE, INFO SU, and STATUS
PROCESS, DETAIL.
•
Gather any messages obtained by means of a filter. See “EMS Filters and GDSX”
on page 2-75 for detailed information.
•
Record the name of the I/O processes GDSX is using (such as CP6100) as well as
the version procedure of such I/O processes.
•
Record information on configuration settings for the I/O processes and configuration
parameter settings for GDSX.
•
If the problem involves Pathway/TS, record the version of the TCP.