This story raises a thought: Dave's Service Definition had at least one
rule that could never be executed. Is there a diagnostic tool that can
identify such a situation? Wouldn't it be nice to have one, perhaps
within the Service Definition creation dialog?
Sounds like a good requirement...
Cheers,
Steve Samson
[EMAIL PROTECTED] wrote:
Thanks to all who responded, especially to those who offered to look at my
WLM specifications.
Here's what happened: I had specified a couple of System Name Groups
(SYG's), something I had not done in this policy before. It turns out that
if a task (TN) is not in the subrules for the SYG it will go to the DEFAULT
service class. I had expected it to go to what I had specified later in
the rules, which of course it did not.
And, since our existing systems do not use SYG's, the policy continued to
run just fine on those systems because the SYG's never came into play.
Bottom line: if you want to use a SYG, be careful how and where you use
it.
Dave Thorn
----------------------------------------------------------------------
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
