RE: How to unlock a record in an interactive job after 'x' amountof time has passed

Locking occurs on the READ not the UPDATE opcode.
So when you do the READ, the record is locked until:

It is unlocked with the UNLOCK opcode.
It is written back to the database with UPDATE.
The program closes the file.

You can avoid locking the record in the first place by using the "N"
operation extender:
  READ(N) MYFILE
 or
  CHAIN(N) MYREC
Reads the record and avoids placing the record lock on the record.

-Bob Cozzi


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of CWilt@xxxxxxxxxxxx
Sent: Thursday, October 07, 2004 9:31 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: How to unlock a record in an interactive job after 'x' amountof
time has passed

Mike,

That doesn't help him.

He wants to be able to unlock the record from the program locking it.

WAITRCD affects how long some other program will wait for a locked record.
It has no effect on the program locking the record.

Charles


> -----Original Message-----
> From: Mike Barton [mailto:Mike.Barton@xxxxxxxxxxxxxxxxx]
> Sent: Thursday, October 07, 2004 10:11 AM
> To: RPG programming on the AS400/iSeries
> Subject: Re: How to unlock a record in an interactive job 
> after 'x' amount of time has passed
> 
> 
> >Is there a way from a RPGLE interactive program to track how 
> long it has a
> >record locked in update and after a certain amount of time 
> has elapsed,
> >gracefully unlock the record. Then the interactive program 
> would show some
> >info message to inform the User that they will need to retrieve the
> >transaction again.
> 
> Andy
>        the WAITRCD attribute on a database file detrmines
> how long the program will wait until a CPF message is returned 
> to your program. 
> The default is 60 seconds (but can be changed / temporarily 
> overridden).
> 
> By monitoring for the error and counting the number of times
> you can determine the length of time.
> 
> HTH
> 
> Mike 
> ###########################################
> 
> This message has been scanned by F-Secure Anti-Virus for 
> Microsoft Exchange.
> For more information, connect to http://www.F-Secure.com/
> 
> 
> This communication and the information it contains: - (a) Is 
> intended for the person(s) or organisation(s) named above and 
> for no other person(s) or organisation(s). Access to this 
> mail by anyone else is unauthorised. (b) Is confidential, and 
> may be legally privileged or otherwise protected in law. 
> Unauthorised use, circulation, copying or disclosure of any 
> part of this communication may be unlawful. (c) May be 
> susceptible to interference, and should not be assumed that 
> it has come in its original form and/or from the stated 
> sender or PinkRoccade UK accepts no responsibility for 
> information, errors or omissions in this e-mail or use or 
> misuse thereof or any act done or omitted to be done in 
> connection with this communication. If you are not the 
> intended recipient, please inform 
> postmaster@xxxxxxxxxxxxxxxxx immediately and delete it and 
> all copies from your system.
> 
> --
> This is the RPG programming on the AS400 / 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.
> 
--
This is the RPG programming on the AS400 / 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.