Begin figure description. Follow
this process to determine the type-of-failure keyword.
- Check whether the message number is DSNV086E:
- If the message number is DSNV086E, use the ABENDx keyword procedure.
- If the message number is not DSNV086E, check whether you got an
SVC dump.
- If you got an SVC dump:
- Issue the z/OS® DISPLAY DUMP command to locate the dump title for the abend.
- Check whether the COMPID is XYR00 or XYR01.
- If the COMPID is XYR00 or XYR01, follow the ABENDx keyword procedure.
- If the COMPID is not XYR00 or XYR01:
- Check whether the dump is from IRLM:
- If the dump is from IRLM, follow the ABENDx keyword procedure.
- If the dump is not from IRLM, refer to z/OS Diagnosis: Procedures.
- Check whether the dump is from IRLM:
- If you did not get an SVC dump:
- Check whether you got a SYSABEND dump or a SYSUDUMP:
- If you got a a SYSABEND dump or a SYSUDUMP:
- Check whether the completion code is 04E:
- If the completion code is 04E, follow the ABENDx keyword procedure.
- If the completion code is not 04E:
- Check whether one or more Db2® ASIDs
are current:
- If one or more Db2 ASIDs are current, follow the ABENDx keyword procedure.
- If one or more Db2 ASIDs are not current, refer to z/OS Diagnosis: Procedures.
- Check whether one or more Db2® ASIDs
are current:
- Check whether the completion code is 04E:
- If you did not get a SYSABEND dump or SYSUDUMP:
- Determine whether Db2 is
unresponsive:
- If Db2 is unresponsive:
- Issue the z/OS DISPLAY ACTIVE command to see if Db2 is active.
- Determine whether Db2 is
active:
- If Db2 is active, follow the WAIT/LOOP keyword procedure.
- If Db2 is not active:
- Issue the z/OS WRITELOG command to locate the DSNV086E message.
- Follow the ABENDx keyword procedure.
- If Db2 is responsive, follow the procedure in the next figure.
- If Db2 is unresponsive:
- Determine whether Db2 is
unresponsive:
- If you got a a SYSABEND dump or a SYSUDUMP:
- Check whether you got a SYSABEND dump or a SYSUDUMP:
- If you got an SVC dump: