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



Solution? Well, there are two. First, make an example out of one of the users who habitually lock records. My personal favorite is staking them out in the parking out during a really cold spell. This sends a message to all other miscreants.


Second, your programming group needs to re-think their decision. I've modified more than one package that blindly locked records for update. It is relatively easy to

   * Use a CHAIN(n)
   * Save the data elements
   * Compare the changed values when the user presses the Enter key and
     either
         o Update if there is no change, or
         o Display a message to the user and refresh the screen with
           the changed values.


For some reason my users prefer the second method. I'm still partial to the first one. Actually it never solved the problem...I'm just kinda kinky that way.


        * Jerry C. Adams
*iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.893.8633x152
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Nick W. Mart wrote:

Booth,

I totally agree with your point of view. However, our programming group has
decided to put a record lock on any record that is being updated. Therefore,
I still need to find a solution to this situation.

Thanks for your response.

Nick W. Mart
Programmer Analyst
Solutions, Inc.
2311 West 18th Street
PO Box 857
Spencer, IA 51301

712-262-4520  ext. 33

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Booth Martin
Sent: Wednesday, January 18, 2006 2:02 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: SQL Record Lock Question

A record stays locked as long as the process that locked it. Sometimes this will happen when a user displays a record to update it and then goes to lunch. Its a real irritation.

However if the record is locked, the changes made, and the record unlocked, then the next program can read it. This is usually pretty fast.

So.... why is the record staying locked? Is it user inspired delays? Solve that problem first, and then your problem will probably go away.



Nick W. Mart wrote:
With the help of several old posts, I have been able to get a record lock
when trying to update a record. Thanks to the list members for that.



However, I have not been able to find how to handle when another user
tries
to update this same record. So far, the program seems to hang when it
attempts to select the record for update. I attempted to use a "whenever
sqlerror goto recordlock" statement. However, that did not seem to work.



Any and all suggestions would be welcome. Thank you in advance.



Nick W. Mart

Programmer Analyst

Solutions, Inc.

2311 West 18th Street

PO Box 857

Spencer, IA 51301



712-262-4520  ext. 33






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.