BTLKCONT Task Terminated After Fields

BTLKCONT Task Terminated After Fields - type of suspension
caidb2
The type of suspension.
  • DEADLOCK
    A deadlock occurs when two application processes each hold a lock on a resource that the other needs and which each requires in order to continue. More than two application processes can be involved in a deadlock.
  • TIMEOUT
    A timeout occurs when an application process waits longer than the length of time specified in the RESOURCE TIMEOUT system parameter for a locked resource to become available.
  • AT
    Displays the date and time of the event (in
    MM/DD/YY HH:MM:SS
    format).
  • After waiting
    Displays the length of time the application spent waiting (in
    NNN.N
    seconds format).
  • Reason for lock suspension
    A categorization of suspensions. The most common type is Local Resource Contention which applies to Db2 databases.
    • Global resource contention.
    • IRML queued request.
    • Inter-system communication.
    • IRLM latch contention.
    • Local resource contention.
    • Notify message sent.
    • RH to PTB communication request.
  • Glbl cont type
    If the reason for lock suspension is global contention, this field will indicate which of the possible global lock contentions applies. These include:
    • IRLM
      IRLM global resource contention.
    • XES
      XES global resource contention.
    • FALSE
      False contention.
    • N/A
      Field does not apply to non-global resource contentions.
  • P/L
    Indicates whether the lock is a physical lock (used in data sharing) or a logical lock (used by transactions).
  • Scope
    Indicates whether the lock is a global lock or local lock.
  • Task ID
    Identifies a task that timed out or was deadlocked.
    • Auth
      Displays the Db2 Authorization ID.
    • Corr
      Displays the thread's correlation ID (first 8 bytes).
    • Plan
      Displays the plan name. If blank, a Db2 command thread.
    • Conn
      Displays the name of the connection (TSO, BATCH, CICS procname, IMS, MPR, DB2CALL).
  • Lock request
    Information which shows lock attributes and also identifies the locked resource.
    • Resource
      Identifies a resource involved in a lock suspension. Database and page set names are translated using the OBID table. If the table is out of sync with the data, DBIDs and OBIDs are displayed.
    • Type
      This field defines the lock type.
    • Mode
      Also known as the lock state, this field shows the type of access permitted to concurrent applications that wish to process the same resource.
      • ANY—A mode used for IRLM CHANGE or UNLOCK requests.
      • US—Unprotected Share, an index tree is locked and lock escalation occurs.
      • IS—Intent Share, a tablespace lock in which the lock owner can read but not update data. Other applications can both read and update data. IS tablespace locks are only used with page locks.
      • IX—Intent Exclusive, a tablespace lock in which both the lock owner and concurrent applications processes can read and update the data. When the lock owner reads a specific page, a S or U page lock is obtained on that page. Other applications can read and update other pages, but not the locked page. When the owner updates data, an X lock is obtained on the updated page and other applications cannot even read the locked page. IX locks are only used with page locks.
      • S—Share, used for both page and tablespace locks. The owner and concurrent applications can read but not update data.
      • U—Update, used for both page and tablespace locks. The owner and concurrent applications can read data and intend to change it. Only one application can hold a U lock on the locked resource (be it a page, table or tablespace). When the application is ready to change the data, it must wait until there are no S locks on the resource, at which time the lock will be promoted to an X lock.
      • SIX—Shared Intent Exclusive, a tablespace lock in which the lock owner can read and update the data. Other application processes can only read data. This lock is only used with page locks. When the lock owner updates data, an X lock is obtained on the updated page and other applications cannot read the locked page.
      • NSU—Nonshare Update Lock, an update lock used when an index tree is updated without lock escalation.
      • X—Exclusive, used for both page and tablespace locks. The lock owner can read or update data, no one else can do so.
    • Dur
      Indicates when a lock is released. Valid values are as follows:
      • ALLOC—When the resource is deallocated.
      • COMMIT—When the lock holder issues a COMMIT.
      • COMT+1—Locks needed to maintain the position of a cursor opened with hold, which are held past commit.
      • MANUAL—For plans that were bound with isolation level CS, Db2 does not wait until the next commit point to release locks on pages that were not updated.
      • MANL+1—Temporary change of consistency level from CS to RR during bind and DDL (RDS changes back internally).
      • PLAN—The lock is released when the plan is deallocated.
      • FREE—Duration to free all.