Dave Thorn 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.
Is there something in the classification that takes advantage of
functionality levels 009-011 that would cause the classifications for
STC to be ignored? I can't see anything off hand on our 1.4 system, but
that's the only thing that comes to mind. Of couse we were just
migrating from level to level, and I was careful not to mix levels as it
was, inevitably, a production system that was the last to move.
Don't know if this helps.
Kim
NJ Office of Information Technology (OIT)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
