RE: Slow respond time when file change to open with

My though is that if chain result in not %found, the effect should be the same 
as SETLL; that is not loading the data to the buffer.

I'm currently trying the method Matt suggested, which is to change the outfile 
with UNIQUE keyword, when write failed, do a chain and update.  This method 
still require the outfile to open as (UF A), will see what happen.
 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Marvin Radding

Mark and Lim,

Is it possible to save a little time by doing a SETLL and testing for an
exact match?  As I understand it, it would save time because the record
is not read into memory and then moved field by field to the program.
Then if there is an exact match a read will get the record into memory
and allow an update.

Just a thought, amoung the few I get far too seldom.

Marvin Rading