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

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