× 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: Can we monitor Disk Usage of an Outfile of a Query?
  • From: Anton Gombkötö <Gombkoetoe@xxxxxxxxxx>
  • Date: Thu, 27 Jul 2000 17:18:25 +0200


>We have users running query through WRKQRY , RUNQRY etc. and outputting the
>result into an outfile.
>Can we retrieve the disk space usage of the outfile while it's running?

Perhaps it is better to avoid the RPG-solution (you were asking for a 
RPG-solution, weren't you? :-) and use the MAXSTG parameter on the user 
profile?

This might be a simple method to protect your machine from drowning in 
outfiles. But it depends on your scenario.

Who owns live production data? Users or a user profile that isn't used to 
sign on? If it's the latter, this user profile could have MAXSTG(*NOMAX) 
and others a reasonable amount of storage. If a user tries to exceed this 
amount, he'll receive an error.

0.02 Euro


Mit freundlichen Grüssen / Best regards

Anton Gombkötö
mailto:Gombkoetoe@ASsoft.com

AS Software GmbH
http://www.assoft.com

Jedleseer Strasse 3
A-1210  Wien

Tel: +43 1 278 15 01-0
Fax:+43 1 278 15 01-22

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.