× 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. December 2005

Re: Finding out which record is locked using QWCLOBJ



I think maybe I'm adding too much complexity to a simple problem. I
could just use the op code extender 'E' when I chain instead of checking
for a lock.


Try searching the archives, I'm sure this has been discussed this before.
The only problem with that is the job still has to wait 30 seconds(default wait time) until the error is returned. From what I understand the default wait time parameter is ignored when reading a database file. I'm assuming that holds true for chaining as well.
The "default wait" is not the right tool for the job. What you want is the amount of time it waits for a record. This is specified in the WAITRCD parameter of the various commands. (CRTPF, CHGPF, CRTLF, CHGLF or OVRDBF)
To avoid affecting other programs, I use OVRDBF. I run this command right before opening the file: 

    OVRDBF FILE(myfile) WAITRCD(1)

Now it only waits 1 second for a record lock.

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.