Re: Blocking I/O (was: Expensive op codes)

["Dan Bale" <dbale@xxxxxxxxxxx>]

Jim:

As I remember it, only the record locked for update was locked, not the entire
block.  Obviously, that woulda been a killer if it were true.

- Dan Bale

Jim Langston wrote:

I don't' come from the S/36 days, but from what I understand about blocking,
this can be a bad thing.

As I understand it, when you open a record for update on the AS/400 it locks
that record, and nothing more.  When you open a record for update on a blocked
file, wouldn't it tend to lock the whole block instead of just that one record?

Regards,

Jim Langston

Dan Bale wrote:

> I don't spend a lot of time reminiscing of my days on the S/36,





+---
| 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
+---