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



| -----Original Message-----
| [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wills, Mike N. (TC)
| Sent: Monday, April 05, 2004 12:53 PM

| I know the system can manage and delete receivers after they are
| filled, but
| can we specify when we want them deleted?

Not that I know of, but icbw.  Can't recall timing of when system-managed
receivers are deleted, off-hand.

| We would like to save them for a
| couple days then delete them... just in case. How would be the best way to
| do this? Any ideas?

One way is to CrtJrnRcv (or is it on CrtJrn, I'm thinking) ??SysMng(*NO) and
delete them "by hand".  It'd be easy enough to write utility (similar to
purging history files) to do this, and'd be surprised if there wasn't a
TAATOOL, QUSRTOOL (or similar) to do this.

| Or isn't keeping them as important as we are thinking?

I find the most important use of journals is doing an "autopsy" on an
application that's cratered.  Dumps (flight-recorders, etc.) not always
being available if an app works, but works incorrectly.  Especially if
symptom shows weeks or months after the fact...  There are many other good
reasons for keeping journals of course, but ime (in my experience) this is
where I use them the most.  Ymmv.

| Mike Wills




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.