On Sat, 13 Dec 2008 12:39:00 +0100, Kris Buelens <[email protected]> wrote:
>SFPURGER is the easiest way to go. But as already mentioned, servers th at >never log off can get a big spool file and it cannot be purge until it i s >closed. >And, maybe even worse: when close, they can be purged too quickly as the y >will appear to be old. >Example: Important user logs on on Sep 1'st, and never logs off >Your spool file purger runs daily to get rid of consoles older than 1 month >On Satuday Dec 13 it gets a problem and is logged off, so its console ge ts >closed >On Monday Dec 15, you notice the user is gone, and .... no console file to >find the reason > >Why: well: when a spool file gets closed, the time stamp it gets is that of >the open time. Your VIP server's console close with information of only 2 >days old, appears to be 4 months old. One of the things I've set up at this shop to manage certain userids spoo l files is to utilize spool classes 0-9. For each special userid & spo ol type start by purging the class 9 files, and then change the spool class for the other files to the next higher number. It's great for userids that produce prolific spool files and userids that only occasionally produce spool files. Brian Nielsen
