On Tue, 31 May 2005 14:02:30 -0400, Dave Thorn <[EMAIL PROTECTED]> wrote:
>We have begun setting up a new customer's LPARs, etc, and since we're >bringing them into our sysplex I'm integrating their WLM specs into our >existing one. > >I activated it last week on the customer system. To my surprise, started >tasks all seemed to go to the default STC service class. This sems to be >happening across the board. I activated the same policy on our sandbox >LPAR and everything seemed to go to the right place. > >They were at OS/390 2.10, and were in Goal Mode, but the systems we're >building here are z/OS 1.4. I asked the sysprogs if the software levels >are identical to our existing ones yet , and was told not completely, but >that still doesn't seem to click with me. This is (I think) fairly basic. >This customer does EVERYTHING with automation but I can't see that entering >into it either. > >A 'D WLM' command on their system shows a functionality level of 008, while >we are at 011. And when I flip them to our policy, the 011 shows up as >expected. > >Anyone have any ideas? Never saw this before. > Hard to say without IEE-EYE-BALL. Assuming all the compatibility maintenance is on their 2.10 system, I don't think the WLM levels are an issue. Perhaps some misplaced SPM rule? If you want to send me a printout off-list of the policy you activiated on their system, perhaps a second set of eyes will catch something. I assume you moved the policy to their system via reading a saved definition PDS. Did you get any errors reading the definition? Regards, Mark -- Mark Zelden Sr. Software and Systems Architect mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
