-p on LOOKUPs - further clarification?

[Jay R. Ashworth]

On Fri, Jun 15, 2007 at 04:10:09PM -0400, Kenneth Brody wrote:
> Quoting Jay R. Ashworth (Fri, 15 Jun 2007 14:42:12 -0400):
> [...]
> > So, when you say -p, filePro write locks the target record (and
> > associated index records) *while it is writing that data item* -- and
> > unlocks it automagically afterwards?
> [...]
> 
> A "lookup -p" time:
> 
>     The lookup is performed, and the record is located.
> 
>     The record is locked.
> 
>     The record is read.
> 
> ... The record is used by processing. ...
> 
> When it's time to write/unlock the record[*]:
> 
>     The record is written.
> 
>     The record is unlocked.
> 
> 
> [*]  Lookup records are written:
>         At an explicit WRITE.
>         At an explicit CLOSE.
>         A GETNEXT/GETPREV is executed.
>         The LOOKUP itself is re-executed.
>         When processing ends.  Note that field-level events (such as
>             @WLF/@WEF) ending do not constitute "processing ending".
> 
>      (This list is from memory, so it may be incomplete.)

To clarify this one more layer: when multiple lookups to the same file
exist, with different tags, does each tag have it's *own* 'file control
block' structure, which participates in these activities?  Or does
doing a lookup on tag 'B' flush pending changes on tag 'A' with the
same underlying file?

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274