00C900BA
Explanation
A request for a drain lock for the resource identified by NAME in messages DSNT500I and DSNT501I could not be granted. The request waited for a period longer than the maximum specified by the installation.
Requests
for claims might also receive this code because claims sometimes need to wait for drain locks. 
System action
The requested action is not performed. The Data Manager function that detected this condition returns 'resource not available' to its caller.
System programmer response
See SQLCODE -913 or -911 and/or message DSNT501I, which accompany this abend reason code.
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
Wait for all jobs that hold a drain lock on the resource in an incompatible state to complete before reissuing the failing statement. To display drain locks, issue a DISPLAY DB LOCKS command. In order to avoid a potential deadlock, the application should either commit or roll back to the previous COMMIT.
Problem determination
- 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.
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
- 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.