Sam,
thanks for replying. I misunderstood the ALL parameter, you're right that
it still shows the last 16 exceptions. I changed my parmlib member and
added the mentioned date/time to the check, restarted HC and the check
ended with RC0.
Thanks for your help,
Werner Kuehnel
Spezialist in der
simple, grow fast...
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Werner Kuehnel
Sent: Thursday, April 24, 2008 3:42 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Antwort: Re: Healthcheck System logger
Sam,
I took option B to activate the fix.
I
Sam,
I took option B to activate the fix.
I applied the fix (SYS1.LINKLIB) and did an LLA refresh,
deleted and added the exit,
restarted HEALTHC STC.
I didn't define any additional parms nor changed any parms for the checks.
According to the HOLD DOC the TIME parameter defaults to ALL, that
Hi Sam,
thanks for pointing me to APAR OA22255. I've just installed it,
unfortunately there is no change in behaviour for this check.
Werner Kuehnel
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU schrieb am 22.04.2008
12:49:43:
Hi, Dave Danner has posted about this before... Search the
, start simple, grow fast...
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Werner Kuehnel
Sent: Wednesday, April 23, 2008 6:39 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Antwort: Re: Healthcheck System logger
Hi Sam,
thanks for pointing me
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
:[EMAIL PROTECTED] On
Behalf Of Werner Kuehnel
Sent: Tuesday, April 22, 2008 5:14 AM
To: IBM-MAIN@BAMA.UA.EDU
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
Check Reason: Logger staging dataset full conditions should be
investigated to determine if application performance is being
impacted
Time of Last
Log Stream StructureCount Condition
ATR.SYS1.RM.DATA
The message talks about the *staging* data sets, not about the offload
data sets. Are the former of reasonable size?
Even if they aren't, LOGR should start an offload as soon as the staging
dataset gets full (the equivalent of a structure-full-condition), no matter if
a structure exists or if
Peter,
Yes, I know that the msg refers to staging data sets, but if offload
doesn't work as expected the staging data sets fill up.
Well, the staging ds are not that big, they are just 9 tracks, however,
that seems to be sufficient. The last two offload data sets were created
on April,14 and
The message talks about the *staging* data sets, not about the
offload data sets. Are the former of reasonable size?
Even if they aren't, LOGR should start an offload as soon as the
staging dataset gets full (the equivalent of a structure-full-
condition), no matter if a structure exists or
11 matches
Mail list logo
