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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of ITschak Mugzach Sent: Sunday, January 06, 2019 2:06 PM To: IBM-MAIN@LISTSERV.UA.EDU 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. <r.skoru...@bremultibank.com.pl> 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 > > > Another question: > I've googled and seen that people wrote about problems with > JES_NJE_SECURITY, which ends with DIAG 00000300_00000004, however > ...is there any solution known for that check? > > Regards > -- > Radoslaw Skorupka > Lodz, Poland > > > > > ====================================================================== > > 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: kont...@mbank.pl. 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: kont...@mbank.pl. 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- Please note: This message originated outside your organization. Please use caution when opening links or attachments. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
