Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
John McKown wrote: This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. 47.5 million lines over 7 days on about dozen LPARs. 6.78 millions lines per day. That is if no buggy programs are writing noisy messages to it or our TCP/IP printing systems are not complaining too much about dead printers. As it is now, 10:00 nearly all our LPARs have about +/- 500 000 lines since midnight. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Indeed. We use an automation package to 'W X' the SYSLOG every day at 23:30 and keep it on DASD for 7 days and move it to archives. Due to high overhead, I ran scheduled SDSF in batch with command 'LOG' every 4 hours on all LPARs, so when my TSO users try to use SYSLOG on SDSF, they don't have to wait gazillion years for feedback from SYSLOG command. Did I SPOOLed too many messages on IBM-MAIN syslog? ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
Vernooij, CP (ITOPT1) - KLM wrote: We actively use MPF list/exits to trim messages, both from the operator console and from syslog/operlog, deleting those messages that we really don't need. We use MPF and automation [1] to trim many messages on Console and some on SYSLOG (which I really don't like it, but ...). We're not using operlog (in SDSF), simply, we use ONE syslog per LPAR to rule all the logs of logs. ;-) For practical reasons, I don't remember why, we decided not to use operlog, but rely on one SYSLOG per LPAR. Groete / Greetings Elardus Engelbrecht [1] - I'm aware of those message flooding suppressing systems and I'm still waiting for my z/OS team to fully implement it. Not a crisis because our automation software is already working like a charm. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
On Mon, 24 Nov 2014 11:34:27 -0600, John McKown wrote: How many lines of SYSLOG output do you produce in an average day? From 23:00 yesterday to 16:49 today, only 340 K lines. We are a rather small shop, so our numbers aren't that interesting. However, 35 years ago, when I was an Amdahl SE, one of my accounts ran JES3 and used a line printer for the JES3 hardcopy console. It had the messages from three systems going to it. It ran somewhat slower than full speed most of the time. They had a room devoted to keeping 30 days of it. I don't remember how many cases of paper were printed every day. Sometimes I needed to use it to help diagnose a dump. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Which is making me rethink a possible project that I am considering. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
Our combined operlog is about 2M lines per day. _ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, November 24, 2014 12:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system? This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Which is making me rethink a possible project that I am considering. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
I'm surprised, but it looks like on an average day the SYSLOG generates 1.3 million lines. Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, November 24, 2014 11:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system? This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Which is making me rethink a possible project that I am considering. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
25million On 24 November 2014 at 18:07, Greg Shirey wgshi...@benekeith.com wrote: I'm surprised, but it looks like on an average day the SYSLOG generates 1.3 million lines. Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, November 24, 2014 11:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system? This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Which is making me rethink a possible project that I am considering. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
On Mon, Nov 24, 2014 at 2:59 PM, Graham Harris harris...@gmail.com wrote: 25million Ouch. Which leads to another question: How is this information used? At that density I simply don't see a way for a unaugmented human to do much of anything with it. I would hope that most of that is basically irrelevant status type messages (job started / ended type stuff). -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
I would hope that most of that is basically irrelevant status type messages (job started / ended type stuff). So would I!! :) I would imagine most information in 'the log' is largely irrelevant from a day-to-day point of view, until such time as you need to find out 'what happened' in problem situations, where it's relevance of having a full log of everything(ish) suddenly becomes rather more crucial (and of course, it usually one of the first things IBM ask for). Admittedly, only a fraction of it will probably be important for diagnostic purposes. I expect there is a certain amount of application 'noise' in there, which is irrelevant for system purposes, but may be quite important for the application folks (again, perhaps only in retrospective diagnosis of issues). On 24 November 2014 at 21:06, John McKown john.archie.mck...@gmail.com wrote: On Mon, Nov 24, 2014 at 2:59 PM, Graham Harris harris...@gmail.com wrote: 25million Ouch. Which leads to another question: How is this information used? At that density I simply don't see a way for a unaugmented human to do much of anything with it. I would hope that most of that is basically irrelevant status type messages (job started / ended type stuff). -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system?
1 million per day. We actively use MPF list/exits to trim messages, both from the operator console and from syslog/operlog, deleting those messages that we really don't need. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: 25 November, 2014 2:47 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system? Wow!! I am impressed we used to get 25K (25000) messages a day and while it has gone up since (the old days) we still suppress many many messages and the last time I looked it was 50,000 a day. No wonder the cpu spins when you do a find. Ed On Nov 24, 2014, at 2:59 PM, Graham Harris wrote: 25million On 24 November 2014 at 18:07, Greg Shirey wgshi...@benekeith.com wrote: I'm surprised, but it looks like on an average day the SYSLOG generates 1.3 million lines. Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of John McKown Sent: Monday, November 24, 2014 11:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: curious: message rate to z/OS SYSLOG/OPERLOG on a _large_ system? This is just a curiosity question. How many lines of SYSLOG output do you produce in an average day? I just did a quick look at last week's SYSLOG and saw about 1.5 million lines for a 7 day period on two, rather small, systems. Why am I curious? From a previous thread on doing a tail -f on the z/OS SYSLOG. I got curious about how much overhead this would be. I was warned by some very knowledgeable people that it could be a truly massive number of messages, and thus have high overhead. Which is making me rethink a possible project that I am considering. -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! John McKown - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM- MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
