× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Blocking I/O (was: Expensive op codes)
  • From: "Dan Bale" <dbale@xxxxxxxxxxx>
  • Date: Wed, 20 Oct 1999 15:39:07 -0400



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.