× 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.



Study single level storage.

The issue of disk fragmentation was in the way back S/36 days (S/34 and
earlier). Single level storage with the advent of S/38 almost eliminated
that problem and now that we have fast access disk units it’s simply not a
concern at all. The storage management code in LIC deals with it, and
that’s way smarter about storage management than we will ever be.

The point behind reuse deleted records is when storage management is
writing new stuff to disk, it needs a continuous 4k block to write to. So
if it can’t find one, it moves things around to create it. If the file
reuse deleted records that’s already set up then it just updates that block
as needed. If your using HA at the disk level (PoweHA) it also marks that
block for replication.


The same type of single level storage is used in many hyper converged
system now as well.



On Thu, Mar 30, 2023 at 2:32 PM x y <xy6581@xxxxxxxxx> wrote:

In many transaction-oriented applications like order entry, most of the
disk I/O, especially writes and updates, is performed on recently-added
records often in very large files.

Does scatter-loading make a difference? Have the mechanics of IBM's
scatter-loading been published?

On Thu, Mar 30, 2023 at 8:44 AM <stefan@xxxxxxxxxx> wrote:

Disk fragmentation does not exist in IBM i due to single level storage,
so that's not an issue.

I disagree, single level storage will try to spread stuff evenly over the
available volume, however that does not prohibit fragmentation.
Look at help text for cmd STRDSKRGZ.

Best regards

Stefan

--
No trees were killed in the sending of this message, but a large number
of
electrons were terribly upset.

Stefan Tageson
+46 732 369934
stefan@xxxxxxxxxx


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

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.