My log:
12:39:00.24 00000290 IEE252I MEMBER IEASYS00 FOUND
12:39:10.20 00000290 HZS0100I IPL-TIME START OF IBM HEALTH
CHECKER
12:39:10.20 00000290 HZS0115I IPL-TIME START OF HZSPROC IS
COMPLETE
12:39:21.31 STC00520 00000090 *HZS0011E READING THE HZSPDATA DATA SET
12:39:21.32 STC00520 00000090 HZS0018I READING COMPLETE FOR THE HZSPDATA
12:39:21.33 STC00520 00000090 HZS0403I SET PARMLIB PROCESSING HAS BEEN
COMPLETED
12:39:39.86 00000090 IRA860I HIPERDISPATCH MODE IS NOW ACTIVE
While I cannot say when the check is actually performed, we see that
order of IRA860I vs HealtchChecker readiness is not deterministic.
And I'm pretty sure the check claim exception until it is rerun.
I sustain my opinion it wouldn't hurt anyone to delay HealthChecker
initialization by 30 seconds or 1 minute.
In earlier version HealthChecker was started explicitely, by a command
in COMMNDxx, so one was able to put it in some automation tool or so.
However IBM wanted to enforce lazy admins to use HC and now it is
started "automagically". It is still possible to disable it and start it
later, but it seems silly a little bit.
Regards
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2019-01-07 o 17:52, Feller, Paul pisze:
Radoslaw, I think that actual health check stuff does not happen until later.
Look for message HZS0103I, which indicates when the health check started task
has completed its start up. This still may not answer why you get the alert.
Below are sample messages from two of our lpars that got IPLed over the
weekend. The actual started task did not start/complete until after
HIPERDISPATCH was set.
(small tech lpar)
19006 04:12:48.86 00000290 IEE252I MEMBER IEAOPT00 FOUND IN
SYS1.PARMLIB.US
19006 04:13:10.79 00000290 HZS0100I IPL-TIME START OF IBM HEALTH
CHECKER FOR Z/OS IS BEGINNING
19006 04:13:10.79 00000290 HZS0115I IPL-TIME START OF HZSPROC IS
COMPLETE
19006 04:13:17.02 00000090 IRA860I HIPERDISPATCH MODE IS NOW ACTIVE
19006 04:13:36.49 STC76522 00000291 $HASP100 HZSPROC ON STCINRDR
19006 04:13:36.75 STC76522 00000090 HZS0117I HZSPROC INITIALIZATION STARTING
19006 04:13:36.92 STC76522 00000090 *HZS0011E READING THE HZSPDATA DATA SET
19006 04:13:36.95 STC76522 00000090 HZS0018I READING COMPLETE FOR THE HZSPDATA
DATA SET
19006 04:13:37.01 STC76522 00000090 HZS0403I SET PARMLIB PROCESSING HAS BEEN
COMPLETED
19006 04:13:37.05 STC76522 00000090 HZS0103I HZSPROC INITIALIZATION COMPLETE
(main appl test lpar)
19006 01:33:50.26 00000290 IEE252I MEMBER IEAOPTMT FOUND IN
SYS1.PARMLIB.US
19006 01:34:04.55 00000290 HZS0100I IPL-TIME START OF IBM HEALTH
CHECKER FOR Z/OS IS BEGINNING
19006 01:34:04.55 00000290 HZS0115I IPL-TIME START OF HZSPROC IS
COMPLETE
19006 01:34:15.23 00000090 IRA860I HIPERDISPATCH MODE IS NOW ACTIVE
19006 01:34:15.24 00000090 IWM066I MT MODE CHANGED FOR PROCESSOR
CLASS zIIP. THE MT MODE WAS
CHANGED FROM 1 TO 2.
19006 01:34:32.40 STC42490 00000291 $HASP100 HZSPROC ON STCINRDR
19006 01:34:33.30 STC42490 00000090 HZS0117I HZSPROC INITIALIZATION STARTING
19006 01:34:33.37 STC42490 00000090 *HZS0011E READING THE HZSPDATA DATA SET
19006 01:34:33.37 STC42490 00000090 HZS0018I READING COMPLETE FOR THE HZSPDATA
DATA SET
19006 01:34:33.42 STC42490 00000090 HZS0403I SET PARMLIB PROCESSING HAS BEEN
COMPLETED
19006 01:34:33.46 STC42490 00000090 HZS0103I HZSPROC INITIALIZATION COMPLETE
Thanks..
Paul Feller
AGT Mainframe Technical Support
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of R.S.
Sent: Monday, January 07, 2019 4:53 AM
To: [email protected]
Subject: Re: How to delay a healthcheck? [EXTERNAL]
Kevin,
It is z13, so HIPERDISPATCH=YES should be default. However I have coded
HIPERDISPATCH=YES in IEAOPT00 member, just to solve HealthCheck alert.
And that's why I found the check is run before HIPERDISPATCH=YES is in effect.
Regarding your questions:
- it's z13 machine
- IRA860I is the only IRA86* message in the log
- IRA860I appear once
Order of things:
19:50:48.58 R00 to IEA101A msg
19:50:57.80 HZS started (HZS0100I and HZS0115I msg)
19:51:27.14 IRA860I
So, indeed, HealthChecker starts half minute before IRA860I.
IMHO Start of HealthChecker should be delayed, not only for the reason above.
Regards
--
Radoslaw Skorupka
Lodz, Poland
W dniu 2019-01-07 o 04:42, Kevin Mckenzie pisze:
Radoslaw, what model CEC are you running on? As Paul says, as of V1R13
with the z196 or above, the default now is HIPERDISPATCH=YES, so it's not
even something you need to specify anymore unless you want to run with it
disabled (and it's required if you want to run in PROCVIEW CORE mode, which
I'd recommend, even if you don't want to run in SMT-2 mode, just for the
additional 'D M=CORE" functionality.) Strictly speaking, there is a time
after IPL starts where you're running in HIPERDISPATCH=NO mode, but
assuming you're using the system defaults, the switch to HIPERDISPATCH=YES
should be happening before the Healthchecker address space starts. Or do
you switch to a different IEAOPTxx member after IPL for some reason?
Can you look at your logs the next time this happens and see when the
IRA860I message is being issued? Are there any other IRA86* messages being
issued during IPL? Are any 'SET OPT=' commands being issued?
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282
z/OS Test Services - Test Architect, Provisioning
IBM Mainframe Discussion List <[email protected]> wrote on
01/06/2019 09:00:56 PM:
From: "Feller, Paul" <[email protected]>
To: [email protected]
Date: 01/06/2019 09:02 PM
Subject: Re: How to delay a healthcheck? [EXTERNAL]
Sent by: IBM Mainframe Discussion List <[email protected]>
Radoslaw, not a direct answer to your question, but I find it
interesting that you get the alert. For some time now the default
for HIPERDISPATCH has been YES. If I recall correctly the default
changed to YES if you ran z/OS V1R13 (or higher) on a z196 or z114
(or higher CEC). So I'm not sure how you would get a HIPERDISPACH
of NO unless something was setting it to NO. I don't recall when it
was that we removed HIPERDISPATCH=YES from the IEAOPT member, but it
has been a few years.
Thanks..
Paul Feller
AGT Mainframe Technical Support
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]
] On Behalf Of ITschak Mugzach
Sent: Sunday, January 06, 2019 2:06 PM
To: [email protected]
Subject: Re: How to delay a healthcheck? [EXTERNAL]
Radoslav,
create a policy statement with a SYNCVAL set to a different time of day.
currently it starts immediately after added because the default for
SYNVAL is SYSTEM.
ITschak
On Sun, Jan 6, 2019 at 9:21 PM R.S. <[email protected]>
wrote:
The following scenario:
During IPL a HealtChecker is started automatically. One of the check ,
SUP_HIPERDISPATCH claims exception because HIPERDISPATCH=NO is in
effect.
However IEAOPTxx specifies HIPERDUSPATCH=YES and this value is set,
*but later*, after the check is run.
The check is scheduled for 24h period, so first day there's false
alert.
There are ways to get rid of the alert by rerunning the check manually
or disabling the check at all.
However, maybe there is a method to change check parameters to delay
its start?
z/OS 2.3
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2018 r. wynosi 169.248.488 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169,248,488 as at 1 January 2018.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
