On Mon, 26 Nov 2007 04:52:01 -0600, Jorge Garcia <[EMAIL PROTECTED]>
wrote:
>We have offloaded the logrec logstream and now it's 2% full but when
>we refresh the check the exception continues though we have refreshed
>the structure.
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.
----------------------------------------------------------------------
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
