RE: No Lock With Update?

["Jerry C. Adams" <midrange@xxxxxxxx>]

Well, horse feathers!  I said I read the manual, and I did.  Just that I
only read the parts for READ and CHAIN.  I'll slink quietly back into my
cubicle now, thank you.

Jerry C. Adams
IBM i Programmer/Analyst
The first Artichoke Queen of Castroville, CA, crowned in 1947 was Marilyn
Monroe. -EUI
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent: Monday, November 14, 2011 9:21 AM
To: RPG programming on the IBM i / System i
Subject: Re: No Lock With Update?

No.  the record *must* be locked in order to perform update/delete 
functions.  If you try it you'll get an error "Update or Delete performed 
without prior read or chain".



From:   "Jerry C. Adams" <midrange@xxxxxxxx>
To:     "RPG400-L" <rpg400-L@xxxxxxxxxxxx>, 
Date:   11/14/2011 09:14 AM
Subject:        No Lock With Update?
Sent by:        rpg400-l-bounces@xxxxxxxxxxxx



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

--

A&K Wholesale

Murfreesboro, TN

615-867-5070