Why retrieval ADS dialogs set locks
Article ID: 117595
Updated On:
Products
Issue/Introduction
Why does an ADS dialog set locks when RETRIEVAL NOLOCK is specified in IDMS sysgen SYSTEM definition?
RETRIEVAL NOLOCK is set in the sysgen SYSTEM statement and also the dialog in question is compiled to specify NO (not selected) for "retrieval locks are kept" on the options screen in ADSC.
In OPER W DB when this dialog is in control it always shows 128 locks have been requested. Why?
In OPER W DB sometimes it shows status KKA which means the task is waiting for a record level lock (dbkey lock). Why?
Environment
Release: All supported releases.
Component: ADS.
Resolution
The 128 locks that always show for the task are AREA level locks associated with the READY RETRIEVAL for the 128 areas readied by the dialog. These will not cause any conflict with record level (dbkey) locks.
In this case, although the dialog in question was properly compiled to NOT keep retrieval locks, the dialog did a LINK to another retrieval dialog that was compiled to specify "retrieval locks are kept" so in the process of transferring control to the second dialog, SHR locks are set during the currency restore process, and if any of those dbkeys are being updated by another task at the time, the task will wait to get the SHR locks until the relevant EXCL (update) locks are released.
Be sure that any dialogs linked-to from the retrieval dialog also are compiled to NOT specify "retrieval locks are kept".
Feedback
