Jon, I too have to respond on the droll side of life.
The SPOOL is meant as a temporary place to put print objects between creation and offload (to either a printer, an external file, another JES node, or the bit bucket). It is an enormous waste of DASD to keep SPOOL there any longer than necessary. This also begs the question: What do they want it for? If the only thing they are going to do is search it with their TSO ID, then educate them on the power of SUPERCE against disk datasets. What can you do with that much data, still on the SPOOL, that you can't do more efficiently with some other storage medium? And how fair is it to everyone else that wants to use the SPOOL? Not very, I think. Personally, I'd find out how much it costs to store that much data, find out if the SPOOL can be expanded that big, determine the cost and feasibility of doing so, and hand the user a bill for that amount. If they pay the bill up front, have a legitimate reason for needing it on the SPOOL, and it proves to be technically feasible then I'd likely set them up. However, I suspect that 3 months of SYSLOG won't fit on a JES SPOOL of maximum size even on mod-27 disk. I know at our site, we'd overrun such a SPOOL in just a couple weeks. As far as how to make the older data drop off, I'd have to refer you to the excellent suggestions that have already been sent to the list by our very sharp and clever posters. Best regards, Gary Diehl ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
