× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. September 2007

Re: Record locking 101

Somewhere in your process an opcode is locking some record; it may not be the record you think it is?

What I'd do at this point is scan for every chain and read opcode and be sure there is an(n) on all of them but the one you want.


Pete Helgren wrote:
Thanks. While waiting for a post back, I looked at another program that was properly locking and unlocking the record and it confirms what you say.

Pete


Wilt, Charles wrote:
Pet,

In answer to your question, yes you shouldn't see anything with DSPRCDLCK when using chain(n).

The only time you should see anything is during the microsecond after you've read the record with a
lock while updating the fields before you issue the UPDAT op-code.

HTH,
Charles



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.