Hi, Dave Danner has posted about this before... Search the archives for
the thread with a subject " Problems with checks IXGLOGR_*. Here is the
post I saved. I don't think anything is available beyond what he
discussed here. Thanks, Sam
------------------------------------
Sorry for the late reply... What Jorge describes has been a known
problem with the IBMIXGLOGR checks from the beginning that I and others
have complained about. Apar OA22255 (which just closed on Friday) will
improve the situation somewhat. From the apar:
"System logger health checks have been enhanced to allow parameters to
update the checks behavior.
The 'TIME(mm/dd/yyyy hh:mm:ss)' parameter allows installations to set a
time to report from. Conditions before the inputted time will be
suppressed.
The 'ALL' parameter, which is the default, will allow the previous
behavior and show up to the most recent 16 conditions for the system
logger health checks."
Unfortunately, due to a restriction in the HC infrastructure, you can't
simply pass a parameter of 'REFRESH'. The check developer suggested
this: create a HZSPRMxx parmlib member like:
UPDATE CHECK(IBMIXGLOGR,*)
PARM('TIME(&MON/&DAY/&YR4 &HR:&MIN:&SEC)')
Then issue the command: F HZSPROC,ADD,PARMLIB=xx. This should clear all
outstanding exceptions.
I believe that my friends at IBM are aware of the 'REFRESH' requirement
so hopefully this will be a future HC enhancement.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Werner Kuehnel
Sent: Tuesday, April 22, 2008 5:14 AM
To: [email protected]
Subject: Healthcheck System logger
Some days ago we moved over to z/OS 1.8. Since then the health check
IXGLOGR_STAGINGDSFULL ends with RC4, saying:
Check Reason: Logger staging dataset full conditions should be
investigated to determine if application performance is being
impacted
Time of Last
Log Stream Structure Count Condition
ATR.SYS1.RM.DATA *DASDONLY* 1 04/14/08 04:50:31
END TIME: 04/22/2008 10:23:48.134741 STATUS: EXCEPTION-LOW
Offloading basically works, the last offload data set of RM.DATA was
created yesterday,
Any idea how to get rid of this exception?
Werner Kuehnel
----------------------------------------------------------------------
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
====================
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
