Analyzing the SVC dump
You can analyze the SVC dump that is issued for the abend that you received.
Procedure
To analyze the SVC dump:
- For each subarea in the diagnostic area of the dump, examine
the ID in the
name of pagefield. - If the ID is not included in the subarea for a given page, other diagnostic information that is produced before or along with the abend might indicate the record that is involved. However, you might have to analyze all the records in all the named pages. In cases of incomplete information, contact IBM® Support.
- If you found one or more IDs, locate each record that is identified by the corresponding ID. For 00C9010x abends, each ID identifies the record in use at the time of abend. For 00C902xx abends, each ID identifies a specific record that is involved in the inconsistency.
- Examine the records that you found and try to determine where the inconsistency exists.
- Analyze the structure that contains each record and verify that the connecting RID pointers are correct.
- Be aware that the inconsistency might involve a missing record. In this case, the PG field identifies the page that was supposed to contain the indicated record. The DM might have tried unsuccessfully to find the record in the page.
- In some operations, such as a DELETE, one of the pages that are involved in the inconsistency might not be identified at all because processing on that page had already completed at the time of the abend. In cases of incomplete information, contact IBM Support.
- In the case of a 00C9010x abend,
further information about the source of the problem might be obtained
from knowing what DM operation was in process at the time the problem
was detected. Use the following steps to determine what was going
on:
- Find the CSECT name identifier (last 5 bytes of the CSECT name) in the field named VRARRK5 of the variable recording area (VRA) in the SDWA. In an SVC dump, the VRA begins at offset X'190' in the SDWA. The first 3 bytes are always “DSN”.
- Look up this CSECT name in the online CSECT Directory
and read the description. In most cases, the description of the CSECT provides some indication of what was going on at the time of the abend.For example, suppose DSNIBHUN was the name of the CSECT that issued the 00C9010x abend. The description indicates that this CSECT is involved with processing recovery log records. The problem in this case might be an inconsistency within the log record that is being processed or an inconsistency between the log record and the page to which the log record is being applied. If a page is involved in the problem, it is identified in a DSNI014I message and corresponding diagnostic area in the dump.
- For 00C902xx abend reason codes, it is possible for more pages to be identified as being involved in the problem than the number of pages that are actually involved. These additional pages are included because they were in use at the time of the abend.
- If no problem is found after you analyze the
records that are involved, it is still possible that an inconsistency
exists between a database descriptor (DBD) and the data or index involved.
If a DBD was involved at the time of the abend, the address of the
DBD is in the prefix of the diagnostic area. Use this address to locate
the DBD in the dump. If you find one or more inconsistencies in the pages you analyzed in the SVC dump, determine whether the problem exists on DASD or only in virtual storage
- Obtain a REPAIR, DSN1COPY, or DSN1PRNT dump of each page that is involved in the problem.
- Analyze the dump to determine whether the problem you
found in the SVC dump also exists on DASD.
- If the problem does not appear in the dump of the pages, indicating that the transaction that was in process at the time the SVC dump was issued caused the problem, but only exists in virtual storage. This transaction is likely to cause the same problem when it is processed again.
- If the problem does appear in the dump of the pages as well as in the SVC dump, the problem exists on DASD. Continue with the next step.
- If the problem exists on DASD:
- Use the RECOVER utility to recover the page set containing the
pages that are involved. If RECOVER completes successfully, you still must verify that the problem is resolved on DASD:
- Obtain a REPAIR, DSN1COPY, or DSN1PRNT dump of the pages involved.
- Look at the dump to determine whether the inconsistency is resolved.
- If the inconsistency is resolved, you should be able to continue normal operations. If it is not resolved, use the REPAIR utility to manually resolve the problem.
- Use the RECOVER utility to recover the page set containing the
pages that are involved.