>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
