00D70001
Explanation
Either the data space manager (DSM) subcomponent of Db2 could not access some storage group definition, or the storage group contains no volume IDs. Possible sources of the error include use of an incorrect name for the storage group and removal of all volume IDs via ALTER STOGROUP without providing new ones.
System action
A 'resource not available' code is returned to the caller.
System programmer response
Notify the database administrator if appropriate. Otherwise, check the SQLCA for the name of the storage group. Check this storage group (via an SQL SELECT on SYSIBM.SYSSTOGROUP) to ensure that it exists. Check for associated SYSIBM.SYSVOLUMES table entries to see if any volume IDs exist for this storage group.
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.
User response
If you are unable to resolve the problem yourself, notify the system programmer or database administrator.
Problem determination
Obtain output listing from SELECT * FROM SYSIBM.SYSSTOGROUP and SELECT * FROM SYSIBM.SYSVOLUMES, details of the request that resulted in this code, and contents of the SQLCA. Also obtain operator's console sheet showing related messages, if any. Use this documentation to determine the cause of the problem.
- 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).
- Listing of the results produced by the SQL statements.
- Listing of Db2 catalog tables.
- 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.