Lockstat Command Output - Locking System Summary
The Locking System Summary portion of the sample output is a summary listing of locking quotas for the installation. All values are cumulative from the time ingstart was run for this iteration of the system.
Here is sample output from this section:
=======Mon Feb 12 13:34:06 2018 Locking System Summary=======
Total Locks 48500 Total Resources 32333
Locks per transaction 2000
Lock hash table 9397 Locks in use 1153
Resource hash table 6263 Resources in use 1113
Total lock lists 419 Lock lists in use 43
Fields are as follows:
Total locks
Number of locks that can be requested or granted simultaneously, including locks reserved for the Recovery Server and unavailable to ordinary transactions. (The reserve size can be found in the Recovery Server startup messages in iircp.log: add reserve LKBs and RSBs to get the total reserved locks.)
Total Resources
Number of distinct objects that can be locked simultaneously, including resources reserved for the use of the Recovery Server and unavailable to ordinary transactions. (The reserve size is the number of reserved RSBs in the Recovery Server startup message in iircp.log.)
Locks per transaction
Maximum number of locks that may be acquired by a transaction
Lock hash table
Number of hash buckets in the locking system hash table
Locks in use
Total number of locks currently outstanding, plus the total number of blocks (RSB and LKB) held in lock list stashes. The stash is a small pool that an active lock list may use to speed up memory allocation. The “Locks by Lock List” output indicates whether a list has a stash, and how many LKBs and RSBs the stash has. Because the stash is reserved to that lock list, the locks are counted as being in use.
Resource hash table
Number of hash buckets in the resource hash table
Resources in use
Total number of resources currently locked, plus the total number of RSB blocks held in lock list stashes.
Total lock lists
Maximum number of lock lists available
Lock lists in use
Number of lock lists currently in use
Last modified date: 01/30/2023