You need a reasonably estimate of how many items should be on the report. Size it accordingly, allowing for business growth. Someone, like Production Control, should monitor for extents used.
The problem with making it huge is, if there is a program error or unusual event which causes a lot of erroneous rejections, the first thing you know about it is when the user sees it, rather than when it has blown the "reasonable" size of the report file.
Joined: 06 Jun 2008 Posts: 8214 Location: Dubuque, Iowa, USA
Your current allocation allows, at most, 252000 records (40 cylinders of space times 15 tracks per cylinder times 2 blocks per track times 210 records per block -- the limit may be less if the volume is nearly full) whereas the space you're proposing allows for over 20 MILLION records. Both are completely ridiculous -- if you are getting 2 million records a day, size the error file to allow for every record to be an error; don't allocate a small proportion for the file, and don't allocate 10 times the space it needs. And don't rely on secondary extents -- size the file correctly with the primary space allocation.