Re: Record-lock scope question

[Booth Martin <booth@xxxxxxxxxxxx>]

This sounds like a disaster in the making.  At some point in the future 
you are going to regret that choice.

Why not write a new program/procedure/whatever, that does both updates 
with parms passed in, and do neither update in your existing programs? 
Another choice is to do the first update, keep the after-change image, 
and unlock the record.  Then, when your second program opens the same 
record, compare the after-image to the new-image.  Normally they'll be 
the same, so proceed.  If not the same, then do the error cycle.



Pascal Bellerose wrote:
> Hi,
>
> I have a problem where I have a program that locks a file for update purposes, 
> and then calls a second program that needs to update the same file, same record.
>
> Is it possible to use something like an OVRDBF or whatever that could let the 
> second program do his chain/update?
>
> But at the same time, we don't want another job to update the same record.
>
> Right, now we're projecting to use a second file that would be used to manage 
> locks but I don'T like that idea and I'm pretty there is something in OS/400 
> that does the trick.
>
> All you wizards out there, I summon the mad genius in yourself, and I do beg 
> for an answer!
>
> Thanks in advance!
>
> Pascal Bellerose
> pascal_bellerose@xxxxxxxxxxxx
> Réseau/Network: 2114
>
> Équipe de support TI Corporatif / Corporate IT Support team
> Tél./Phone: 819-363-6100
> Fax/Télécopie: 819-363-6155
>
>  
>
> Cascades Canada inc.
> 412, Boul. Marie-Victorin
> Kingsey-Falls, PQ, Canada
> J0A 1B0