LIST.READU
LIST.READU |
|
|
The LIST.READU command displays details of file and record locks.
Format
LIST.READU {user} {DETAIL} {NO.PAGE} {LPTR {n}} {WAIT}
where
The LIST.READU command displays or prints details of file, read and update locks held by one or all users.
Example
User File Path......................... Type Id...... 1 2 D:\SALES\STOCK RU P-174-43 1 2 D:\SALES\STOCK RU P-967-47 5 2 D:\SALES\STOCK RU P-954-55 2 4 D:\SALES\INVOICES FX 3 4 D:\SALES\INVOICES WAIT 17565
In the above report, users 1 and 5 hold record update locks in file 2 (D:\SALES\STOCK) and user 2 has a file lock on file 4 (D:\SALES\INVOICES). The file number is an internal reference to the file and is also needed for the UNLOCK command.
The lock type is shown as RL for shareable record locks, RU for record update locks and FX for file locks. Files opened for exclusive access by internal components of QM will appear as a pseudo-lock type of EXCL.
Details of users waiting for locks are only shown if the WAIT keyword is used. In this example, user 3 is waiting to lock record 17565 in file 4 but is blocked by user 2.
Adding the DETAIL keyword to the command produces an extended report:
Record lock limit = 400, Current = 3, Peak = 73 User File Path......................... Type Id...... 1 2 D:\SALES\STOCK RU P-174-43 Locked 09 May 17 10:27:11 1 2 D:\SALES\STOCK RU P-967-47 Locked 09 May 17 10:27:18 5 2 D:\SALES\STOCK RU P-954-55 Locked 09 May 17 10:27:17 2 4 D:\SALES\INVOICES FX Locked 09 May 17 10:21:00 3 4 D:\SALES\INVOICES WAIT 17565 Wait since 09 May 18 10:03:54
The first line of the above report shows statistical information for active record locks. The file lock and the user waiting for a lock in this example do not contribute to these numbers. The peak number of locks is useful in determining a good value for the NUMLOCKS configuration parameter.
The time at which the lock was acquired is shown in the timezone of the user executing the command. |