|
- Problem statement
- A failure occurred when running VTAM® Exit
Facility Subtask. If an ABEND code occurs in user exit ISTEXCCS, ISTEXCSD,
ISTEXCAA, or ISTEXCVR, a VTAM ESTAE
will attempt to take a dump for the abnormally ending user exit.
- Common symptoms
- An ABEND code occurred. If VTAM attempts
to issue the SDUMPX, message IST413I will be issued. If SDUMPX is
issued but the dump fails, message IST257I will give the reason code
for the dump failure.
Note that the VRDATA KEY=DAE macro is issued
before issuing the SDUMPX to make the dump eligible for MVS™ DAE (Dump Analysis and Elimination) dump
suppression. Thus, if the user has DAE in effect at the time of the
errors, duplicate dumps with matching symptoms will be suppressed
by the MVS DAE facility, and VTAM will issue the following message: IST257I VTAM SDUMP FAILED WITH RETURN CODE 08 REASON X'0B'
- Probable cause
- The following list shows some of the common problems with user-written
exits:
- The pointer to the VTAM Exit
Services parameter list was not valid when the session management
exit called VTAM EXIT Services.
- The pointer to the EXMPL (the pointer to the input parameter list
in the VTAM Exit Services parameter
list) was nonzero, but was not valid when the exit called VTAM Exit Services.
- The pointer to the message text in the EXMPL was nonzero, but
was not valid when the exit called VTAM Exit
Services.
- Some portion of the message text could not be accessed by VTAM Exit Services. (For example,
the session management exit passed a message length in the EXMPL that
exceeded the storage area owned by the Session Management Exit.)
- User response
- Consult the symptom string or PSW and registers, or both, at the
time of ABEND. Consult any related storage or addresses in the dump.
|