Re: Finding large objects that are blowing up the system ASP

"Best practices" varies by location.

There are a lot of dependencies.

Are your journal receivers there to:
- audit changes
- catch stuff between backups
- as required by your software based H/A vendor
If just for the latter you can always ask the vendor their opinion.

We use much more data for receivers than our ERP data itself.

% of Size in
Library Owner Disk 1000 bytes
#MXJRN ROB 21.28 2437574692.9
ERPLXF SSA 11.36 1300849618.9

We do a lot of journal analysis.
Receivers are only 2.4TB on this system.


On Wed, Apr 23, 2025 at 3:15 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Thanks, Mr. Dietz, for the corresponding IFS procedures.

Removing the obsolete Tomcat server directory dropped it below 90%.

It seems that there's already a fairly fresh RTVDSKINF present, so I did
a PRTDSKINF on it. Turns out that the biggest disk-hog is journal
receivers.

I'm offline for the rest of the day (expecting guests, and I need to
bake my father's 90th birthday cake), but can somebody outline "best
practices" for dealing with journal receivers that collectively take up
over 40% of disk space?

I have very little experience with journaling, most of it in connection
with writing a QuestView extension for looking at journaling data.

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