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


  • Subject: Re: Runaway NOMAX was: Is OS always to blame
  • From: Evan Harris <spanner@xxxxxxxxxx>
  • Date: Sat, 29 Jul 2000 08:41:50 +1200


John,

does anyone there use query and output to file ?

My experience is that files created by query are automatically  *nomax and 
can kill a system pretty easily. I haven't thought of a way around this, 
except to perhaps limit user profile storages.

In my opinion query is probably one of the most dangerous tools on the 
system, especially when combined with a less than adequate security system.

Cheers
Evan Harris

>We don't use *NOMAX on any of our files.  I have setup MessengerPlus to
>automatically extend a file up to 15 times and Page me when it does
>this.  This way If there is a legitimate rapid growth in a file the
>processing can continue - but if it is just a runaway job it will have
>to wait for programmer intervention after 15 increments are added.
>
>Oh and it is DEFINITELY up to the operating system to reserve enough
>resources for itself so that it does not crash.
>
>John HAll

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.