If RSCS were to be enhanced or replaced, I am not sure if any modification to SYSPROF EXEC would be necessary to provide any default action. I think that the *SPL system service would provide a server all of the information it needs to make a decision on what to do with what files. Then implement YOUR installation's policy in the server.
/Tom Kern On Wed, 14 Dec 2005 13:02:58 -0500, Lloyd Fuller <[EMAIL PROTECTED]> wrote: > snipped... >Well, if any of this were to be implemented, the first thing that we would have to do is disable the SYSPROF part. >We want to control OUR print files, not some other virtual machine. We are a development shop, and use >spooling to contain listings and console files to refer too. Yes, they go away after seven or ten or whatever days >unless we hold them. However, almost none of my spool files EVER get printed. They get referred to, but they >stay in spool until I don't need them or they get deleted by the spool daemon. > >I don't have a problem with RSCS being enhanced to control channel attached printers (how many of those still >exist?), but I DO NOT like the idea of RSCS controlling ALL spool/
