John, I don't know if you are familiar to using OPERLOG. If not, I should
suggest you ought to. I personally feel my life got better when we got rid of
SYSLOG.
In case you are, please take a look at CBT file #513, there you will find a
set of tools to take advantage of OPERLOG. In few
It's not free but you may find a commercial archive product like $AVRS
http://www.seasoft.com/ makes storing, searching, and managing retention
of SYSLOG easier and would help you fill your requirements.
Best Regards,
Sam Knutson, GEICO
Performance and
Mainframe cc
Discussion List
[EMAIL PROTECTED] Subject
.EDU Re: SYSLOG purging
why couldn't you simply do 'w l' . then each day is a disticnt
sysout/dsn/joe. then purge individual sysout that are 3 months old
Jack Kelly
LA Systems @ US Courts
x 202-502-2390
--
For IBM-MAIN subscribe / signoff / archive
Hi All;
Thanks for your help.
The piece of the puzzle I was missing is that SDSF treats multiple SYSLOG
data sets as a single logically contiguous Syslog. Which is what my user
wants. So I just need to spin the syslog every week and after 3 months
start writing the oldest one to a GDG.
Thanks
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
Jon,
One shop I was at we dumped SYSLOG every night at midnight to a DASD GDG. Then
every week we used JOBTRAC (job scheduling product) to pickup the weeks work of
GDGs and wrote a weekly GDG to DASD. Then we used Jobtrac to pick up the
Weeklies and make a monthly tape.
You can do something
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Jon Bathmaker
Sent: Monday, March 13, 2006 3:08 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG purging . . .
Hi All;
I have an unusual request from my user. He wants to keep
three
Jon,
you could probably go and invent some wheel, a program to work with the
external writer program, to do what your user wants, plus some more to handle
the retention, tape migration, expiration, etc.
However, this wheel has already been invented many times over. Please look on
the Internet for
Jon,
on second thought ...
First of all, you can not keep a contiguous hunk of SYSLOG (one big file for 90
days) and then expect to be able to easily delete a day's or week's worth of
records. That's just not how the thing's designed.
Depending on your system setup, SYSLOG is automatically broken
Thid poster had a REPLYTO, so it didn't make it to IBM-Main.
-
-teD
I’m an enthusiastic proselytiser of the universal panacea I believe in!
-Original Message-
From: Ted MacNEIL [EMAIL PROTECTED]
Date: Mon, 13 Mar 2006 22:21:16
To:[EMAIL PROTECTED]
Subject: Re: SYSLOG purging
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
In a message dated 3/13/2006 5:28:05 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
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.
Yeah don't know
Jon,
JES2 or JES3?
How many syslog records does the site produce on an average week?
How many syslog records does the site produce in its busiest week?
--
Tom Schmidt
Madison, WI
--
For IBM-MAIN subscribe / signoff / archive
Three months of SYSLOG sounds rather excessive, unless the user is
really willing to foot the bill for the extra JES SPOOL space, and the
additional cost of backing up all that data for DR. We only keep about
3 weeks of SYSLOG online to JES and just that much is typically 5 - 10%
of our total
15 matches
Mail list logo
