Re: an introduction to MI by example II part B

Ok.

Now the fun begins.  We see you guys are really great with three lines of 
code.  And I for one think that is really great.  Now someone on the 
ign_list@IGNITE400.ORG mailing list is getting his disk filled up and 
can't figure out what is causing it.  I'd like to see you guys start another 
contest to create a program that will monitor all files created, modified 
and deleted on the system.  Similar to CleanSweep.  There have been a 
number of times I'd love to know what is contributing to the ever 
shrinking disk space.  Now of course I know a person could take a snap 
shot of all files on the system before and after and write a program to 
compare them, but running  a DSPOBJD *ALL twice can be very time 
consuming and not very accurate.  The guy on the 
ign_list@IGNITE400.ORG is talking about his Temporary Space Being 
Used.  It would be nice to see a screen showing (on the fly) where space 
is being used.  Another words a live screen that would show files being 
added, deleted and increased that a person could monitor either for a 
short time or a long time depending on the circumstance.  So as a file was 
increased in size the screen would show the file pop up on the screen and 
how much it increased.

Anyone wont to take that challenge?

Gary Kuznitz
 
> As the unofficial judge for this, it is still three lines of 'real'
> code - as was mine.
> 
> Reducing the number of variables only gets you half a point ;-)
> 
> --phil

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---