It's surprising to me that one would want to activate only one check (you really don't want to know what other checks might have to tell you?), but to the question of "can you?" the answer is "yes". Since most checks are shipped active by default, you would deactivate them all and then activate what you want to run.
If I remember correctly, policy statements are processed in the order they are defined. In your HZSPRMxx you could have ADD POLICY(only_one_check) STATEMENT(ooc_stmt1) UPDATE CHECK(*,*) INACTIVE REASON(...) DATE(...) ADD POLICY(only_one_check) STATEMENT(ooc_stmt2) UPDATE CHECK(*,IEA_ASIDS) ACTIVE REASON(...) DATE(...) ACTIVATE POLICY(only_one_check) This is untested (especially syntax-wise). But the idea is right. The active policy is applied to existing checks and also to checks that might be added later. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
