00D70024
Explanation
No data sets exist for a nonpartitioned table space or index space. Because at least one existed at create time, a serious problem might have occurred for this table space or index space. The name of the data set that DB2® expected to find for the table space or index space appears in message DSNP012I and/or in the SQLCA along with the reason code.
System action
The request is terminated.
System programmer response
Ensure that the data set and its pack are available to DB2 and that the data set has not been inadvertently deleted or migrated by any DASD operation.
If the data set name is correct, is cataloged, and appears in the VTOC, run the access method services DIAGNOSE command on the integrated catalog facility (ICF) catalog identified by the first qualifier of the data set name.
Problem determination
- The integrated catalog facility (ICF) catalog
- The VTOC listings
- Details of the request that led to this code
- Contents of the SQLCA
- The operator's console sheet showing related messages
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
- IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the DB2 subsystem catalog that defined the failing index or table.
- VTOC listing of the disk volume on which the failing operation occurred.
- Listing of the results produced by the SQL statements.
- SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
- Definitions of views and tables involved in the error.
If you suspect an error in DB2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.