GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual—529931-001
3-28
If GDSX Abends
If GDSX Abends
If your GDSX application abends, perform the following before consulting an HP
support representative:
•
Record the full version procedure from the GDSX object file. You can determine
this by using either the VPROC utility or BIND. For example, using VPROC:
> VPROC
Enter filename:
> OGDS
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
16 Task tried to close $RECEIVE.
17 Task called INIT^SEM passing a nonzero semaphore.
18 Task attempted to obtain an uninitialized semaphore.
19 Task attempted to release a semaphore it did not own.
20 Task passed an invalid task number to get a TCB address.
21 Timeout waiting for buffer
22 Bad putbuff address
23 Log buffer overrun
24 Parameter to rcbaddrX out of bounds
25 Task attempted illegal C-series call
26 Task attempted illegal D-series call
Table 3-7. TSCODE Fault Messages
Fault Number Description