Re: Locked records

Thank You, Buck, This is exactly what I need.  Your sample will be
adapted to my program very easily.

A "%Locked" BIF will be nice, but we need to work with the tools
available now.

Thank to Rob and Nigel for pointing to my translation mistake, in my AS
the message reads: RNQ1218  No ha podido asignarse un registro en el
archivo... 


Buck Calabro wrote:
> 
> Raul,
> You can easily change the wait time for locked records with OVRDBF filename
> WAITRCD(1).
> You can add program handling of this error by putting an indicator in the LO
> positions (I/O error) of your CHAIN or READ statement.  If that indicator
> comes on, you have some sort of I/O error.  You can check the file's *STATUS
> to see what exactly what error you got:
> FLOCK    UF  E           K        DISK
> F                                              KINFDS INFDS

> IINFDS       DS
> I                                     *STATUS  FSTAT
> I           SDS
> I                                     *STATUS  PSTAT
> I                                       91 170 PSMSG
> C           KEY       CHAINLOCKR                8030
> 
> 80 = No record found (HI)
> 30 = I/O error (LO)
> 
> When this gets a record lock,
> FSTAT = 01218
> PSTAT = 0
> PSMSG = RECORD 1 IN USE BY JOB 711466/BUCK/BUCK01.
> 
> RPG IV is similar, but you don't need the indicators if you don't like them.
> You can use the %found and %errror instead.
> 
> Buck Calabro
<snip> 
-- 
  Raul A. Jager W.
Asuncion - Paraguay

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