|
from: Reeve <rfritchman@xxxxxxxxx>
subject: Re: Find source of object lock?
A mixture of named activation groups, instead of using one "base" and then
*CALLER for subsequent levels, was one self-created problem. Once I
recompiled my service programs with *CALLER, orphaned opens vanished.
Another situation appears to be with SQLRPGLE programs opening the same
file/table in record-level IO and SQL. And I thought I read somewhere that
SQL mostly, but not completely, closes its internal cursor with the goal of
improving performance at its next access. I may be fouling my own nest by
mixing access technologies
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.