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
