Re: REUSEDLT(*NO) - what's the point?

[Robert Rogerson <rogersonra@xxxxxxxxx>]

Does LIFO and FIFO ring a bell?

On Sat, Jul 25, 2020 at 8:25 AM Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

> In old days it was necessary that the rows/records are returned in the way
> they are written, i.e. the row with the highest relative record is the last
> written row.
> When using REUSEDLT(*YES) this rule is no longer true, because a new record
> can have a lower relative record no.
>
> Mit freundlichen Grüßen / Best regards
>
> Birgitta Hauser
>
>
> "Shoot for the moon, even if you miss, you'll land among the stars." (Les
> Brown)
> "If you think education is expensive, try ignorance." (Derek Bok)
> "What is worse than training your staff and losing them? Not training them
> and keeping them!"
> „Train people well enough so they can leave, treat them well enough so they
> don't want to.“ (Richard Branson)
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Tim
> Fathers
> Sent: Samstag, 25. Juli 2020 13:55
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: REUSEDLT(*NO) - what's the point?
>
> I believe it's performance related, it is (or used to be) slower for the
> database to search for an empty slot in which to put a new row than simply
> add it to the end. The default for SQL created files is to reuse deleted
> rows, so maybe there's no problem these days.
>
> Tim.
>
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
> Patrik
> Schindler <poc@xxxxxxxxxx>
> Sent: 25 July 2020 12:57
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: REUSEDLT(*NO) - what's the point?
>
> Hello,
>
> what could be the reason for CRTPF and CHGPF having a default setting of
> REUSEDLT(*NO)?
>
> Background:
> https://try-as400.pocnet.net/wiki/Wrkprb_needs_long_time_to_start
>
> :wq! PoC
>
> PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc
>
>
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link:
> https://amazon.midrange.com
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link:
> https://amazon.midrange.com
>
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com