Rob, Thanks. That works great when the disk is too full for the application to issue the EXEC to archive the files. I have to see if we can work that into the code.
The major concern I had is to prevent the application from getting the following messages when it writes that file that breaks the camel's back: DMSFRO159E Insufficient storage available to satisfy free storage request from 0106D6B4 17:37:31 * MSG FROM SCXJXS : DMSABE152T System abend 0F8 called from 01072580 while UFDBUSY = 20; re-IPL CMS HCPGIR450W CP entered; disabled wait PSW 000A0000 00F541B6 And thank you to those who suggested FCOPY and VMARC as well as the minidisk and directory solutions. Jim -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, April 29, 2009 12:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How Many Files Can Be on a Minidisk Before It Cannot be ACCESSed? On Wed, Apr 29, 2009 at 6:44 PM, James Stracka (DHL US) <james.stra...@dhl.com> wrote: > This application puts about 10,000 files a day on its minidisk. The > application owner wants to keep a month's worth of data online. Given > 64 bytes per file and 14M usable, that is approximately 230,000 files. > That would be exactly a full working month. I assume there's a pattern in the name or type of the files they create, so you could do something like this ACCESS 200 E/E 200904* * The restrictions of FSTs under the line would apply to the subset that you make visible with the mask. If Rob
