Trace Data Specific to Timeout Event
The details related to the timeout. The format of the timeout-specific data is shown in Format of timeout-specific data.
Format of timeout-specific data
The following example shows details related to the timeout.
REQUEST =LOCK UNCONDITIONAL
STATE =IS ZPARM INTERVAL= 30
DURATION=COMMIT INTERV.COUNTER= 1
HASH =X'00015F0F'
STMTINFO=DYNAMIC
STMTID =X'000000000000A341'
------------ HOLDERS/WAITERS -----------
HOLDER
LUW=DEIBMIPS.IPUAXZ32.C6215376BB44
MEMBER =SZ32 CONNECT =BATCH
PLANNAME=DSNTIA10 CORRID =YULT3978
DURATION=COMMIT PRIMAUTH=SKA
STATE =X STMTINFO=DYNAMIC
STMTID =X'000000000000A312' Field description
The individual fields
have the following meaning:
- REQUEST
- The timeout request, consists of one of the following:
- LOCK
- CHANGE
- STATE
- The state or mode of the lock applied to the resource. Valid values are shown in Table 2.
- ZPARM INTERVAL
- The timeout interval (ZPARM value), which is the timeout value specified on the installation panel DSNTIPX or in the ZPARM name STORTIME in DSN6SYSP.
- DURATION
- The length of time for which the lock was held. Valid values are
shown in Table 1.
Table 1. Lock Duration Duration Description MANUAL Varies depending on the ISOLATION parameter MANUAL+1 Temporary change of consistency level from CS to RR during bind and DDL COMMIT Until commit COMMIT+1 Past commit; applies to locks needed to maintain the position for a cursor opened WITH HOLD ALLOCATN Until deallocation PLAN Lock held for the duration of the plan UTILITY For the duration of the utility execution FREE ALL Until all locks are freed X'00' The suspension reason is a retained lock The DURATION attribute controls when locks are released. As a general rule, a lock is only released when an agent makes an unlock request with a duration longer than, or equal to, the longest lock duration specified for the resource by that agent.
You increase lock durations using either a lock request or a change request. Lock durations are decreased using a change request.
- INTERV.COUNTER
- The number of timeout intervals that can occur before the agent is timed out.
- HASH
- The lock resource hash value.
- STMTINFO
- The waiter's statement information. Possible values are:
- STATIC
- The statement is of type static.
- DYNAMIC
- The statement is of type dynamic.
- STMTID
- The cached statement ID for the statement waiting for the resource. A value of zero indicates that the client did not supply this information.
Fields that are printed for each holder/waiter
The
following fields are printed for each holder/waiter of the
reported lock resource:
- LUW
- The ID of the holder's or waiter's logical unit of work. If the reason for the suspension is a retained lock, this field contains the word SYSTEM.
- MEMBER
- The holder's or waiter's Db2® member name. In a non-data-sharing
environment,
N/Pis printed. - CONNECT
- The holder's or waiter's connection name. If the reason for the suspension is a retained lock, this field contains the word SYSTEM.
- PLANNAME
- The holder's or waiter's plan name. If the reason for the suspension is a retained lock, this field contains the word SYSTEM.
- CORRID
- The holder's or waiter's correlation identifier. If the reason for the suspension is a retained lock, this field contains the word SYSTEM.
- DURATION
- The lock duration of the timeout holder or waiter. Valid values are shown in Table 1.
- PRIMAUTH
- The primary authorization ID.
- STATE
- The holder's or waiter's state or mode of the lock applied to the resource. Valid values are shown in Table 2.
- STMTINFO
- The holder's statement information. Possible values are:
- STATIC
- The statement is of type static.
- DYNAMIC
- The statement is of type dynamic.
- STMTID
- The cached statement ID for the statement holding the resource. A value of zero indicates that the client did not supply this information.