Re: Possible Automated Troubleshooting on RECORD LOCK

You might want to do a Google search on "optimistic vs. pessimistic"
locking.

If your users are running into lock contention, it's probably caused by
poor design, simple laziness on the part of developers, or utilizing
language environments which don't maintain "state" for individual users.


On Fri, Apr 1, 2016 at 10:32 AM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:

We have situations occur that one user has a lock on record and second user
cannot go into the record. We have a program that users run that will
unlock but not in cases where the other user has lock, only same user. The
way it works in IBS stinks. Firstly they put lock on the read, not the
update time.

Secondly this lock manifests by a field that holds the user id, in order to
clear, our program, reads and clears that field, but in recent case I noted
that when I tried to manually clear that field, i see this message in my
dspjoblog on my pc:

Record 5858274 in use by job 427038/NINAM/XT09DD0B10.

Now I would like the program - can it be able to also know that this phrase
above it would then be able to at least give a message to user trying to
clear the lock, that Nina, has lock please contact her or IT to cancel that
job.

This would help alot. So my question is, can the RPG be able to discern the
above message?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.