> >Perhaps it's the design of WLM that doesn't account > for profoundly diverse behaviors within a single LPAR. >Any explanation > is welcome.
Whether anyone wants to recognize and admit it or not, WLM and sysplex implicitly assume you're going to share resources fairly uniformly and run everything everywhere. And -I- strongly believe that that approach is in fact the best solution for availability and manageability. However, there is a deeply rooted culture clash between the way z/OS is presently designed to work and the way that customers have traditionally run their multi-system complexes. To this day, many (perhaps even most) customers still segregate applications and workloads between systems. Application X (e.g. "TSO") runs on SYSA and application Y (e.g. CICS Online) run on SYSB. Now if you spend 10 seconds thinking about that you may realize it is about the worst possible way of organizing work. There are many reasons for that way of doing things, but IMO they mostly fall into the category of historical paranoia. Whether or not you feel WLM is somehow deficient at managing such segregated workloads is pretty much immaterial (again, IMO) and of course as usual, YMMV. CC ---------------------------------------------------------------------- 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
