|
If you go into the Information Center under Programming/APIs/APIs by category/Database and File/File Information APIs you should find Retrieve Job Record Locks (QDBRJBRL) and Retrieve Record Locks (QDBRRCDL). These two APIs, when used to analyze various steps within your application, should give you a good idea of who is holding locks a bit longer than you anticipated. Hope this helps, Bruce Vining "James H H Lampert" <jamesl@xxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 03/27/2006 05:56 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To rpg400-l@xxxxxxxxxxxx cc Subject Unintended lock retention Does anybody know of any good tricks for tracking down unintended lock retention on files? We've got an application that keeps locking its own external calls out of records, even though we've got UNLOCK statements set to execute anytime an UPDATE operation fails, and all other attempts to read the file are either through logicals that are only open for input, or have an "N" option to disable locking. -- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
