RE: WRKOBJLCK automated API ?

With all due respect, Joe, the *USE* of the methods you describe are clearly
the exception rather than the rule in the real world.  Whereas, most of us are
smart to handle the record locking issues now for any new development, what
*reasonably* can be done for all the legacy code out there that was written
without the benefit of our superior wisdom?

In some cases it may come down to: "You want to spend HOW much money to fix
something that occurs a few times a year/month/week/day?  Just tell the users
to never leave their desk without the menu showing."  Or some such drivel.

Just my .02.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-------------------------- Original Message --------------------------
Mac, there's a bigger issue here.  Why in the world is a record locked for
anything more than a few milliseconds (the time to read and update the
record)?  There are two perfectly good alternate architectures for data
access - busy flags and image checking - neither of which lock the record
for any appreciable length of time, and so never run into the situation you
are facing.

Joe
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---