× 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: Reusing deleted records
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Wed, 23 Sep 1998 00:26:43 -0700
  • Organization: Progressive Data Systems, Inc.


I don't believe that this could be correct from what I understand the
relationship is between job ODP's and the underlying RDBMS.

In a layered OS like OS/400, any program can, through the feed back DS, know how
many other programs are using a particular file.  So I have to conclude that the
OS is aware of multi job interaction with a particular file.

I missed the original post so I'm going out on a limb here .... Does the program
perform record deletes and block adds?  The reason I ask is that if the disk
controller receives a record delete it will do so immediately (or appears to) 
but
blocked writes would be delayed and possibly be treated as a group that the
controller may attempt to search for a contiguous block write area.

So although the program may delete x records then write x records, if the delete
was through a logical, and the writes through a physical there is no 
relationship
to the deleted space (record numbers) and the attempted block write.

If this is the case, you would want to change the physical to force write on 
each
record add and sacrifice blocking.  That is if reusing deleted records is more
important than write performance and the necessary RGZPFM to reclaim disk space.

2 centavos (and dropping)

James W. Kilgore
qappdsn@ibm.net

>
>
> At 04:44 AM 9/21/98 -0400, you wrote:
>
> >You are correct.  When a file that specifies REUSEDLT(*YES) is opened, as a
> >part of the open, OS/400 develops the deleted records map.  When a record
> >is added under that file open OS/400 consults the deleted records map for
> >the RR# of where to add the record.  When all deleted records have been
> >exhausted, only then are new records added at the end of the file.  If
> >another job opens the file later and deletes a record, the first job will
> >not know about the newly deleted record until the file is closed and
> reopened.
>
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-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-Ups:
Replies:

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.