> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Jon Bathmaker > Sent: Monday, March 13, 2006 3:08 PM > To: [email protected] > Subject: SYSLOG purging . . . > > > Hi All; > > I have an unusual request from my user. He wants to keep > three months of > SYSLOG on the spool in one logically contiguous piece and > every week, he > wants to dump the oldest week to a GDG, leaving the rest > there in a single > spool dataset. It's rather like a logger scenario. I have > never heard of > anyone wanting this, let alone implementing it but, hey, > that's what makes > life so interesting. > > One could imagine a program that does this, it would have to > read and write > the oldest week's records to the GDG and then copy the > remaining records to > the start of the file and reset the end of file marker, all > without JES > worrying his pretty little head about it. Fairly tricky I > should think. > > Any thoughts/ideas/droll comments would be much appreciated. > > Thanks, > Jon Bathmaker
<comment type="droll"> I'd lay very good odds that it is impossible. Especially if what the customer wants is something like: In March, I want JAN, FEB, and MAR syslog on the spool in a single spool dataset. In April, remove the JAN portion, leaving only FEB, MAR, and APR portion in the single spool dataset. There is simply NO way to purge "part" of a single SPOOL dataset. Curiously, if you use the OPERLOG using the LOGR, then you can do this. But it is not in the SPOOL, it is in the LOGGER datasets. And you simply remove those entries more than "x" days old. </comment> ---------------------------------------------------------------------- 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
