AD2Y   

Explanation

The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool because there were no TCBs available on which to create the thread. The number of thread TCBs currently running is at the TCBLIMIT defined in the DB2CONN. Message DFHDB2010 is output to transient data. The transaction was abended because either:

  • The DB2ENTRY specifies threadwait(no), meaning do not wait for a thread, including having to wait to create a thread because a TCB is not available - that is, do not wait for a TCB either.

  • The DB2ENTRY specified threadwait(pool), but the pool definition within the DB2CONN specifies threadwait(no), and again there were no TCBs available.

  • The transaction was using the pool directly, the pool specifies threadwait(no) and no TCB was available.

System action

The task is abnormally terminated with a CICS transaction dump.

User response

Determine whether TCBLIMIT should be increased or whether the number of transactions using DB2 at any one instance should be limited using transaction classes.

Module

DFHD2EX1


AD2Y.html | Timestamp icon Last updated: Sunday, 4 June 2017