Lock Suspension Events - Lock, Unlock, Change, and Notify Resume

The format of the data for these events depends on whether these events occurred in a data sharing or non-data-sharing environment.

Format of data specific to Lock, Unlock, Change, and Notify Resume (Data Sharing) shows the format in a data sharing environment, Format of data specific to Lock, Unlock, Change, and Notify Resume (Non-Data Sharing) in a non-data-sharing environment.

Format of data specific to Lock, Unlock, Change, and Notify Resume (Data Sharing)

This is the sample format for data specific to Lock, Unlock, Change, and Notify Resume in a data sharing environment.

09:05:44.38289840 CHANGE   N/P       N/P                     SUSP.TIME =0.000901  LOCAL CONTENTION=N 
09:05:44.38199696 RESUME                                     DURATION  =COMMIT    LATCH CONTENTION=N 
                                                             STATE     =X         IRLM QUEUED REQ =N 
                                                             RESUME RSN=NORMAL    GLOBAL CONT.    =Y*
                                                             XES PROP  =Y         NOTIFY MSG SENT =N 
                                                             XES FORC  =N         bbbbbbbbbbbbbbbbbb 
                                                             XES ASYN  =Y         RETAINED LOCK   =N 
                                                             aaaaaaaaaaaaaaaaaaaaa                  
                                                             PARENT  =X'7F5E64E0'                    
                                                             HASH    =X'00113406'

Format of data specific to Lock, Unlock, Change, and Notify Resume (Non-Data Sharing)

This is the sample format for data specific to Lock, Unlock, Change, and Notify Resume in a non-data-sharing environment.

 SUSP.TIME =ss.nnnnnn  LOCAL CONTENTION=Y
 RESUME RSN=xxxxxxxx   LATCH CONTENTION=Y*
                       IRLM QUEUED REQ =N

Description of individual fields

The individual fields have the following meaning:

SUSP.TIME

The duration of the suspension.

DURATION

The length of time the lock is held. For a list of possible values, refer to Table 1.

STATE

The state or mode of the lock applied to the resource. For a list of possible values, refer to Table 2.

RESUME RSN

The reason for resumption. Valid values are shown in Table 1.

Table 1. Reason for Resume - IRLM Requests
Reason	Description
NORMAL	The suspended task resumed normally when the resource became available.
DEADLOCK	The suspended task resumed after a deadlock.
TIMEOUT	The suspended task resumed when a preset time interval expired.
IDENTIFY	The suspended task is resumed after an identify call to IRLM.

XES PROP

An indicator whether or not IRLM propagated the request to XES. Possible values are Y(es) or N(o).

XES FORC

An indicator whether or not the lock was requested to be forced to XES. Possible values are Y(es) or N(o).

XES ASYN

An indicator whether or not IRLM sent the request asynchronously to XES. Possible values are Y(es) or N(o).

This field is only printed if XES PROP=Y.

aaaaaaaaaaaaaaaaaaaaa

Stands for the lock attributes. It can be one or more of the following:

MODIFY or NMODIFY
GLOBAL or LOCAL
P-LOCK or L-LOCK

For example:

MODIFY  GLOBAL L-LOCK

PARENT

The parent token for explicit hierarchical locking.

HASH

The lock hash value.

Description of suspension fields

A request can be suspended for several reasons. For example, the original reason may have been an IRLM latch contention, then the request may first have hit local contention and, after it was resolved, global level contention. The fields in the right block show whether or not a particular reason for suspension was encountered, which is indicated by Y(es) or N(o). The original reason is marked with an asterisk (*).

LOCAL CONTENTION

The local resource contention.

LATCH CONTENTION

The IRLM latch contention.

IRLM QUEUED REQ

The IRLM queued request. This request is only valid for IRLM suspensions.

GLOBAL CONT.

The global contention. Intersystem communication is required to resolve the lock request. This reason applies to data sharing environments only.

NOTIFY MSG SENT

Intersystem message sending. This reason only applies to data sharing environments and IFCID 44 suspensions.

bbbbbbbbbbbbbbbbbb

Only applies if it is an IRLM suspension and the global contention is hit (GLOBAL CONT=Y). If these conditions are satisfied, it can be one of the following values:

IRLM GLOBAL CONT

The request hit IRLM global resource contention.

XES GLOBAL CONT

The request hit XES global resource contention.

FALSE/SYNC-ASYNC

This can be one of the following:

FALSE CONT: The request is a false contention (shown if QW0045W8 is ON)
SYNC-TO-ASYNC CONV: The request is a sync-to-async conversion (shown if QW0045W8 is OFF)

RETAINED LOCK

Indicates whether there was contention with a retained lock.