00D70100
Explanation
A requested resource is not available. Either the data space manager (DSM) or some subcomponent that it invoked discovered that some resource is not available. The name and type of the resource and the reason it is unavailable are placed in the CT control block by the subcomponent that made the discovery. This information is made available to the user in the SQLCA and/or messages. The reason code in the CT/SQLCA contains the identifier of the subcomponent that discovered the problem.
Almost any DSNP module can issue this reason code.
System action
Abort the current request.
Operator response
Notify the system programmer or database administrator.
System programmer response
Notify the database administrator if appropriate. Otherwise, determine what resource was unavailable (from SQLCA information) and, if it is something you can control, make it available. 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.
Problem determination
See the Problem Determination section in the description of the code that appears in the SQLCA or CTRURESN field of the CT and/or in the description of any associated console messages. Obtain 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.
- 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.
- 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.