Re: No Lock With Update?

[J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx]

Don't see what's unclear about it: if you try an update on a record that 
you haven't got a lock on, you get an error RNX1221 'Update or delete in 
file xxx without prior input operation'.

That happens when you try an update before you chain, or when try to 
update the same record twice, or when you retrieved the record without 
lock.

Joep Beckeringh


rpg400-l-bounces@xxxxxxxxxxxx wrote on 14-11-2011 16:12:31:

> Jerry C. Adams 
>
> This may be a silly question, but I cannot find the answer (or a hint) 
in
> the manual.
>
>
>
> If one uses READ(n) or CHAIN(n) against a table that has been defined 
for
> update, can one still use the UPDATE or DELETE op-codes against the
> retrieved record.  All that the manual says is that the record is 
retrieved
> without locking it.  It would seem to me that, since the program has the
> record, it could still be updated or deleted.
>
>
>
> Normally I wouldn't try something like this, but I am working on a 
process
> where it is a viable option so I was curious. 
>
>
>
> Thanks.
>
>
>
> Jerry C. Adams
>
> IBM i Programmer/Analyst
>
> There was never a great genius without a tincture of madness. -Aristotle