Re: Database Files Exceeded

Ooooh! Nice Mess! I never even knew this limit existed!

I would look at some type of Auditing for that library.  That way you could know
every file that is created, when, and by whome.  Stick that data into a DB file
(in a DIFFERENT library of course!!!)  Now you can easily process this file 
every
so often and delete the files in the order they are created as they reach some
age or at whatever criteria you need.

Now the other question is how much overhead is there in creating and deleting
55000 files every couple days!?!  If you thought full database Opens and CLoses
were hard on IO, this has got to be a killer!!!

 - Larry

> Here is the issue,  this is a third party software package, it was not 
>designed for a company of our size. (I inherited it)   For each transaction 
>that hits, it creates a file. So... in a few days, Voila !  exceeds 55,500 
>files. That is with  thousands of transactions per day.  I used to have BPCS 
>at another shop, so have seen similar situations.(but not like this)   My 
>option is to have the third software co.  to write a purge(it is done manually 
>by them, contract service) and they have source  or  I will write my own aging 
>pgm to try and get this down to manageable level.    Appreciate the response.

-- 
Larry Bolhuis         |         What if it's True?
Arbor Solutions, Inc  |
(616) 451-2500        |  
(616) 451-2571 -fax   | 
lbolhui@ibm.net       |
+---
| 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
+---