Antwort: Re: Health Checker
Peter, great, exactly what I wanted to know .. Thanks to all which have replied to my question. Werner IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU schrieb am 31.10.2006 13:26:32: What is the sense of giving a statement a name when there is a check name which is unique? The check name imight be unique but there is no reason that your policy statement has to be limited to a particular check (it could use wildcarded names, fo example) or that you cannot have multiple policy statements each of which is applied to a particular check. STATEMENTNAME is just a way for you to be able to uniquely reference this policy statement should you want to display it or delete it (for example). In z/OS 1.8 this becomes an optional specification and the system will define a name for you, should you decide that you are not interested in referencing individual policy statements. In the case where you put an UPDATE statement into your startup parmlib member, you're right that it's too early. UPDATE works on checks that have been defined/added. It is not something that is stored and used later (which is exactly what POLICY statements are for). As it happens the parmlib definitions are read before it is necessarily the case that checks have been defined/added. UPDATE statements (or UPDATE modify commands) are for things that you want done once and do not want to be re-applied if you ever refresh the check. There probably aren't a whole lot of such situations (especially not wanting the re-apply after refresh). Peter Relson z/OS Core Technology Design -- -- 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
Antwort: Re: Health Checker
__
Sam,
thanks for replying. I didn't use the ADDREPLACE because I didn't know
what to specify for STMT.
What is the sense of giving a statement a name when there is a check name
which is unique?
Werner
Knutson, Sam [EMAIL PROTECTED]
Gesendet von: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
30.10.2006 13:29
Bitte antworten an
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
An
IBM-MAIN@BAMA.UA.EDU
Kopie
Thema
Re: Health Checker
Try this in SYS1.PARMLIB(HZSPRM00)
ADDREPLACE POLICY STMT(CONS1) UPDATE CHECK(IBMCNZ,CNZ_SYSCONS_MASTER)
WTOTYPE(INFORMATIONAL)
REASON('I have my reasons...')
DATE(20061030)
Thanks, Sam
--
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
Re: Antwort: Re: Health Checker
From manual IBM Health Checker for z/OS User's Guide topic 1.4.2.1 Can I have statements other than policy statements in my HZSPRMxx member?: It's not a good idea to have non-policy statements in your HZSPRMxx member. Your HZSPRMxx member should include only policy statements and the LOGGER parameter. The system applies non-policy statements only to currently active checks, and the statements are applied just once. Policy statements, on the other hand, are applied every time IBM Health Checker for z/OS starts up, as well as when checks are added or refreshed. In other words, including non-policy statements in your HZSPRMxx member will be ineffective. Non-policy statements that are in your HZSPRMxx member will not be part of your IBM Health Checker for z/OS policy. Brian On Mon, 30 Oct 2006 15:35:03 +0100, Werner Kuehnel wrote: __ Sam, thanks for replying. I didn't use the ADDREPLACE because I didn't know what to specify for STMT. What is the sense of giving a statement a name when there is a check name which is unique? Werner -- 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
