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 Senior Technology Analyst SunGard eSourcing 600 Laurel Oak Road Voorhees, NJ 08043 Office 856-566-5412 Fax 856-566-3656 Cell 609-781-0353 Email [EMAIL PROTECTED] ------------------------------------------------------------------------- Keeping People and Information Connected (TM) HTTP://www.availability.sungard.com ---------------------------------------------------------------------- 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
