Hi Ted,
"how often?" - sems like every other week.
"how much can you store?" - at least one years data per system, in HSM ML2.
keeps it simple, no need to be concerned with sopme other archive system.
On Fri, 10 Jun 2011 16:36:13 +, Ted MacNEIL
wrote:
>>Not sure I would want SYSLOG to be
Dunno what zip you guys use, but I zipped a 171 Million byte
file into 14 Million bytes, for a 12.2 compression ratio,
which is what I would expect for pure text with lots of blanks.
I typically see 6 or 8 to one for more complex data like SMF.
Barry Merrill
--
>Since the log is generally full of text, I would expect a 2:1 ratio like on
>Open systems.
2.6
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
Thanks Mark. After looking at the links you posted, one of them showed my
name. I never thought of searching on my name. That brings up 3 entries.
When I searched for SOUT, or SYSOUT, I got hundreds of entries just using
Google to search the CBT site. I finally did notice that if I click on
Since the log is generally full of text, I would expect a 2:1 ratio
like on Open systems.
On Fri, Jun 10, 2011 at 1:38 PM, Ed Gould wrote:
> Ted,
> Just a quick question. Since syslog is vbm the amount of compression would
> seem to me so small (considering the content). How much compassion was
Ted,
Just a quick question. Since syslog is vbm the amount of compression would seem
to me so small (considering the content). How much compassion was seen?
Ed
Sent from my iPad
On Jun 10, 2011, at 11:36 AM, Ted MacNEIL wrote:
>> Not sure I would want SYSLOG to be trapped into an output arch
>Not sure I would want SYSLOG to be trapped into an output archive.
Not sure it's "trapped".
Indexing by date is (usually) easier.
I've done it three ways:
1. Date stamped datasets -- preferable to:
2. GDGs and,
3. Output archivers
I prefer #3, especially with indexing and (in most) compression.
On Fri, 10 Jun 2011 10:37:20 -0500, Eric Bielefeld
wrote:
>Probably 6-8 years ago, I contributed a system called SOUT to the CBT tape.
>I was trying to find it on the CBT site, but I'm not having much luck.
>There used to be a link that listed all the files - I can't find it for some
>reason. I
Probably 6-8 years ago, I contributed a system called SOUT to the CBT tape.
I was trying to find it on the CBT site, but I'm not having much luck.
There used to be a link that listed all the files - I can't find it for some
reason. I don't know if its not there, or more likely I'm just not seei
Not sure I would want SYSLOG to be trapped into an output archive.
We use SDSF to grab the previous day's log, midnight to midnight, and then
purge older data.
The data gets stored into a system/datetime stamped dataset.
Making it so very useful for data miningjust using SRCHFOR across a bu
Sam:
We had multiple reasons why we didn't let syslog out of the systems group.
It might have been for several reasons (take your pick)
1. The production people couldn't be trusted with this.
2. We needed access at times when the package was not available(systems down
time)
3. Auditors didn't tr
11 04:40 AM
Subject:Re: SYSLOG saving
Sent by:IBM Mainframe Discussion List
I've worked many places over the years and have seen it all(SAR, $AVRS,
etc). Honestly, keeping a daily syslog offload in a disk based GDG,
that gets migrated to tape after 5 days still seems the most
IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark Zelden
Sent: Wednesday, June 08, 2011 5:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had
IN@bama.ua.edu] On
Behalf Of Mark Zelden
Sent: Wednesday, June 08, 2011 5:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more "general" products
(as oppos
I used to enjoy the exposure to HESC, but IBM dropped it soon after OCO.
So the committees started looking at packaged software for Windows and
*nix
that 'any third grader could maintain'. Lots of Boot Hill stories
abound...
In a message dated 6/8/2011 9:30:14 P.M. Central Daylight Tim
was
lacking or not even there yet, that of course has been a few years.
Scott J Ford
From: Mark Zelden
To: IBM-MAIN@bama.ua.edu
Sent: Wed, June 8, 2011 5:26:56 PM
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason
ool.
Dave Gibney
Information Technology Services
Washington State University
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Mark Zelden
> Sent: Wednesday, June 08, 2011 2:27 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re
details that far back.
Linda
- Original Message -
From: "Mark Zelden"
To: IBM-MAIN@bama.ua.edu
Sent: Wednesday, June 8, 2011 2:26:56 PM
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I men
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more "general" products
(as opposed to some that specifically manage syslog or have components
that do) couldn't have used those products to store syslog. And maybe
more of those shop
We issue command W I at midnight and "sweep" the SYSLOG into Infopac
(ViewDirect).
We keep them for 90 days.
Greg Shirey
Ben E. Keith Company
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
Sent: Wednesday, June 08, 2011 2:36 PM
Survey time? :-)
Bas
AIN@bama.ua.edu
Subject: Re: SYSLOG saving
Years ago, we brought in SAR (now CA-View) to hold customer batch report output
for viewing . So, we issue the W L command every midnight by auto command and
have View pick it up. We keep a little over 3 years of SYSLOG available, most
of that on (virtual) t
for us.
Linda
- Original Message -
From: "Donald Likens"
To: IBM-MAIN@bama.ua.edu
Sent: Wednesday, June 8, 2011 6:47:38 AM
Subject: SYSLOG saving
In my previous shop we used a product called $AVRS to retain SYSLOG
for an extended period of time. I assume other sh
us.
Linda
- Original Message -
From: "Donald Likens"
To: IBM-MAIN@bama.ua.edu
Sent: Wednesday, June 8, 2011 6:47:38 AM
Subject: SYSLOG saving
In my previous shop we used a product called $AVRS to retain SYSLOG
for an extended period of time. I assume other shops d
From: Mark Zelden
To: IBM-MAIN@bama.ua.edu
Sent: Wed, June 8, 2011 3:35:57 PM
Subject: Re: SYSLOG saving
On Wed, 8 Jun 2011 13:43:32 -0400, Knutson, Sam wrote:
>Hi Mark,
>
>My guess would be opposite that almost everyone has some output management
On Wed, 8 Jun 2011 13:43:32 -0400, Knutson, Sam wrote:
>Hi Mark,
>
>My guess would be opposite that almost everyone has some output management
tool they leverage for SYSLOG archiving but I could be completely wrong.
Hi Sam,
Survey time? :-)
Based on my experience at well over 30 companies in
mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark Zelden
Sent: Wednesday, June 08, 2011 10:07 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
On Wed, 8 Jun 2011 08:47:38 -0500, Donald Likens wrote:
>In my previous shop we used a product called $AVRS to retain SYSLOG for
>an extended p
.ua.edu
Sent: Wed, June 8, 2011 9:47:38 AM
Subject: SYSLOG saving
In my previous shop we used a product called $AVRS to retain SYSLOG
for an extended period of time. I assume other shops do the same. I
need it in a readable format with as much information as possible.
If you save SYSLOG at yo
On Wed, 8 Jun 2011 08:47:38 -0500, Donald Likens wrote:
>In my previous shop we used a product called $AVRS to retain SYSLOG
>for an extended period of time. I assume other shops do the same. I
>need it in a readable format with as much information as possible.
>
>If you save SYSLOG at your shop,
, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Donald Likens
Sent: Wednesday, June 08, 2011 9:48 AM
To: IBM-MAIN@bama.ua.edu
Subject: SYSLOG saving
In my previous shop we used
In my previous shop we used a product called $AVRS to retain SYSLOG
for an extended period of time. I assume other shops do the same. I
need it in a readable format with as much information as possible.
If you save SYSLOG at your shop, how do you do it?
---
30 matches
Mail list logo
