What about using the journal to summarize writes/updates/deletes over a time period?
I've never heard about REUSEDLT requires anything else but a exclusive lock on the file while changing.
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<mailto:stefan@xxxxxxxxxx>
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Reeve <rfritchman@xxxxxxxxx>
Sent: Thursday, January 29, 2026 08:43
To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: REUSEDLT not reusing
I'm looking at a dozen reasonably busy files with REUSEDLT(*YES) and having
a large number of deleted records. One example: ~780,000 records,
~8,100,000 deleted records, record length 110 bytes, no extraordinary data
structures or attributes. The files in question are journaled with "after"
images and all were created in March 2000 (almost 26 years ago--hard to
believe!).
There is no app that deletes that many records in one shot. I'm ruling out
the possibility the app fired up with 8,800,000 deleted records. I don't
remember extactly when this feature came out but I do have a faint
recollection of having to recompile my PF's to make REUSEDLT work
properly. Or is my memory what's not working properly?
My plan: CHGPF to cycle REUSEDLT off/on, RGZPFM, and watch the number of
deletes for the next week. Next step: CHGPF with the source member.
I'm grateful for any advice.
--rf
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.www.avast.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
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.
As an Amazon Associate we earn from qualifying purchases.