AD2P


    Explanation
      The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool. See the associated transient data message DFHDB2011 to determine which DB2ENTRY was involved or whether it was the pool. The transaction was abended because the DB2ENTRY or the pool specified threadwait(no) meaning do not wait for a thread if all threads are currently in use. Note if message DFHDB2011 indicates that the pool was being used, it means the transaction was using the pool directly rather than overflowing to the pool. (An abend AD3T is produced when a transaction overflows to the pool and no pool threads are available.)

    

    System action
      The task is abnormally terminated with a CICS transaction dump.

    

    User response
      Determine whether more threads should be allocated to the DB2ENTRY or the pool, or whether the number of instances of this transaction should be limited using TRANCLASS.

    

    Module
DFHD2EX1

Applicable releases in Version 6
  
  
    
      beta

      6.3

      6.2

      6.1