Hi Brian,
Spot on! When I looked at your message and realized how little common
storage it would take to increase this I had our LOGLIM throttled up to
9999; MVS command K M,LOGLIM=9999 and updated PARMLIB CONSOLxx with
LOGLIM(9999). The problem went away.
We did not see any significant WTO/WTL activity so unless something is
suppressing them before they could reach either SYSLOG or OPSLOG we
still don't understand why this was occurring.
Thanks,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Peterson
Sent: Wednesday, February 08, 2006 2:47 PM
To: [email protected]
Subject: Re: IEE012A NO LONGER SAVING MESSAGES FOR HARDCOPY, LOGLIM
REACHED
Was there a burst of WTO activity at the time of the IEE012A? Perhaps
the burst simply overwhelmed console syslog processing. Perhaps IBM
console support would have some idea regarding this issue.
FWIW, on my system, the following value is set:
LOG BUFFERS IN USE: 0 LOG BUFFER LIMIT: 9999
Brian
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic 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
