ABEND0AB occurs when a VTIOC module issues a VTAM® macroinstruction that fails. Depending
on the values of the RPLRTNCD and RPLFDB2 fields, the macro may be
retried. If the retry fails, ABEND0AB is issued.
Table 1. ABEND0AB information
in a dump of SDWA
Offset
|
Length
(bytes)
|
Description
|
---|
X'280' |
8 |
Terminal name |
X'289' |
1 |
RPL request type: X'22' = SEND; X'23' = RECEIVE |
X'28A' |
1 |
RPLRTNCD |
X'28B' |
1 |
RPLFDB2 |
X'28C' |
4 |
RPLFDBK2 (Sense code) |
If this happens during the execution of a SEND or RECEIVE,
the session is placed in reconnect status.
The recommended documentation is:
- Contents of register 15.
This contains the reason code, which
is explained in z/OS Communications Server: IP and SNA Codes.
- Message text for message IKT116I.
- The software LOGREC entry.
If you have a LOGREC entry, look
at an unformatted dump of the SDWA. Table 1 describes
the pertinent data you should look for in the dump.
- The dump that is created automatically for this abend.
For
abends associated with I/O errors, a dump is not generated automatically
unless the RCFBDUMP parameter of the TSOKEY00 member of SYS1.PARMLIB
is set for it.
- For errors that occur during session initialization or termination,
run the VTAM internal trace
with the options API, PIU, MSG, SSCP, and PSS.
Note: The options
API, MSG, PIU, and SSCP are always running internally, but you may
want to run the VIT with MODE=EXT to be certain that you get the expected
output.