Re: SYSLOG/OPERLOG Time Stamps
Lizette Koehler [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] ink.net... I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? 2008046 11:22:37.53 2008046 11:22:37.57 2008046 11:22:52.05 2008046 11:22:52.31 2008046 11:22:52.59 2008046 11:25:58.65 2008046 11:25:58.67 -- 2008046 11:26:49.66 -- 2008046 11:27:26.17 -- 2008046 11:28:14.67 -- And starts again 2008046 11:28:14.67 2008046 11:28:14.67 2008046 11:28:14.68 2008046 11:28:14.67 2008046 11:28:14.98 2008046 11:28:18.19 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.28 2008046 11:28:18.47 2008046 11:28:18.96 Lizette Lizette, There is something else you might look into: I think I remember that messages for the operator console(s) appear in syslog and are timestamped at the moment the messages is displayed on the console. So if the console is full and does not recieve messages, these messages are held up until the operator clears the screen. If no other (non-console) messages are produced in that interval, this might explain the gap in syslog/operlog. Kees. ** 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSLOG/OPERLOG Time Stamps
On Wed, 20 Feb 2008 10:52:09 +0100, Vernooy, C.P. - SPLXM [EMAIL PROTECTED] wrote: There is something else you might look into: I think I remember that messages for the operator console(s) appear in syslog and are timestamped at the moment the messages is displayed on the console. So if the console is full and does not recieve messages, these messages are held up until the operator clears the screen. If no other (non-console) messages are produced in that interval, this might explain the gap in syslog/operlog. Kees. Kees, You are incorrect. The timestamp is generated as soon as the WQE control block is created that represents the message. This occurs before the message is written to the SYSLOG and well before the message is queued to any consoles. Since z/OS R4, messages are written to SYSLOG before they are queued to consoles. W. Kevin Kelley IBM POK Lab -- z/OS Core Technical Development -- 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
Re: SYSLOG/OPERLOG Time Stamps
W. Kevin Kelley [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... On Wed, 20 Feb 2008 10:52:09 +0100, Vernooy, C.P. - SPLXM [EMAIL PROTECTED] wrote: There is something else you might look into: I think I remember that messages for the operator console(s) appear in syslog and are timestamped at the moment the messages is displayed on the console. So if the console is full and does not recieve messages, these messages are held up until the operator clears the screen. If no other (non-console) messages are produced in that interval, this might explain the gap in syslog/operlog. Kees. Kees, You are incorrect. The timestamp is generated as soon as the WQE control block is created that represents the message. This occurs before the message is written to the SYSLOG and well before the message is queued to any consoles. Since z/OS R4, messages are written to SYSLOG before they are queued to consoles. W. Kevin Kelley IBM POK Lab -- z/OS Core Technical Development Thanks for the update! Kees. ** 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSLOG/OPERLOG Time Stamps
Lizette, You could start an automatic command to do a D T (Display Time) every 30 seconds for a day or two. That would let you know whether you have a problem without too much additional log output. Brent Looper UAMS I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? 2008046 11:22:37.53 2008046 11:22:37.57 2008046 11:22:52.05 2008046 11:22:52.31 2008046 11:22:52.59 2008046 11:25:58.65 2008046 11:25:58.67 -- 2008046 11:26:49.66 -- 2008046 11:27:26.17 -- 2008046 11:28:14.67 -- And starts again 2008046 11:28:14.67 2008046 11:28:14.67 2008046 11:28:14.68 2008046 11:28:14.67 2008046 11:28:14.98 2008046 11:28:18.19 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.28 2008046 11:28:18.47 2008046 11:28:18.96 Lizette Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 11:39:03 -0500, Lizette Koehler [EMAIL PROTECTED] wrote: I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? snip Spin loop during that time? Check logrec. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: SYSLOG/OPERLOG Time Stamps
No Spin Loops or other issues. RMF looks good. I will just monitor for now to see if anything comes of it. Thanks. Lizette I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? snip Spin loop during that time? Check logrec. -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 13:47:18 -0500, Lizette Koehler [EMAIL PROTECTED] wrote: No Spin Loops or other issues. RMF looks good. I will just monitor for now to see if anything comes of it. ... Synchonous SVCDUMPs? Seems like a long time for an SVCDUMP, though. Pat O'Keefe -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 14:56:08 -0600, Patrick O'Keefe [EMAIL PROTECTED] wrote: On Fri, 15 Feb 2008 13:47:18 -0500, Lizette Koehler [EMAIL PROTECTED] wrote: No Spin Loops or other issues. RMF looks good. I will just monitor for now to see if anything comes of it. ... Synchonous SVCDUMPs? Seems like a long time for an SVCDUMP, though. Not to mention it would be hard to miss that in the syslog/operlog. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 15:16:43 -0600, Brian Peterson [EMAIL PROTECTED] wrote: In my opinion, the simple lack of messages in syslog / operlog is actually evidence of a system which is well behaved. Absent any other symptom, you should be pleased. I would be! That's a good point. Of course just seeing a post about this to begin with made me believe that this was very unusual situation and there was some sort of problem. On one of my sandbox LPARs I went an hour and 47 minutes without a message this morning. :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 11:39:03 -0500, Lizette Koehler wrote: I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? (snip) Lizette Are there any other symptoms? Why do you think you even have a problem? In normal operation, applications should not issue WTO messages to the console / syslog / operlog in a well-behaved system. If any of the wild theories mentioned in reply to your post were actually happening, you would likely have other symptoms. For example, trivial TSO transactions (say, hitting enter at the ISPF main menu) would be delayed for several seconds. In my opinion, the simple lack of messages in syslog / operlog is actually evidence of a system which is well behaved. Absent any other symptom, you should be pleased. I would be! Brian -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 11:39:03 -0500, Lizette Koehler [EMAIL PROTECTED] wrote: I have a fairly active system. Stuff going on all the time. But when I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for several minutes. If this system was not active, I could understand the gaps. Does anyone have any thoughts as to why that might be? 2008046 11:25:58.65 2008046 11:25:58.67 -- 2008046 11:26:49.66 -- 2008046 11:27:26.17 -- 2008046 11:28:14.67 -- And starts again 2008046 11:28:14.67 2008046 11:28:14.67 I looked at my PROD Lpar and see gaps of 10, 11, 14, 15 seconds at times, even at this hour (11:45 a.m. EST). TTFN, Mark -- 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
