RE: WRKOBJLCK automated API ?

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


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of MacWheel99@aol.com
> Sent: Tuesday, June 05, 2001 10:13 AM
> To: AS400 & family discussion group
> Subject: WRKOBJLCK automated API ?
>
>
> >From Al Macintyre, still writing in RPG/400 but occasionally embedded SQL
>
> This is not urgent, more like brain storming.  I have some software to
> modify, to enhance what it is doing in the form of features, new data
> capturing, less hassles for users & so forth, and one worrysome
> situation is
> risk of conflict updating a heavily used file.  I would like my next
> modifications to handle that situation more gracefully.
>
> What happens today is that there is lock up because two people
> are trying to
> update the same file at the same time, and the end user messages are not
> friendly informative.  At best we are told that some other
> unspecified user
> is updating a record in a specific file that this one needs, &
> usually does
> not give a clue as to which one, & when it does it gives record # of the
> file, when our users think of the data by item # order # etc., and then
> manual usage of WRKOBJLCK to locate who that is can be a royal pain.

+---
| 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
+---