Mark Jacobs wrote:
On Thursday 03 August 2006 08:23, Edward Jaffe wrote:
Mark Jacobs wrote:
What are some of our options to spread the workload across both systems
on an equal basis.
In spite of it's selfish behavior, which can't be changed, a JES2 member
will always stop initiating work when no initiators are left to be
populated. Therefore, if you limit the number of available initiators on
the overworked system, the other system will pick up the slack.
We still want both systems to have about the same number of batch jobs running
so limiting initiators on one systems isn't a good solution,
Then limit the number of initiators on *both* systems!
zOS 1.4. JES2 managed batch. Thruput manager is available.
You might consider the use of WLM-managed batch initiators. Beginning
with z/OS V1R4, it more aggressively "trims" the initiator pool on
overworked systems.
There is strong resistance to WLM batch.
You make your bed. Then you lie in it. ;-)
Seriously, there are definitely certain types of workloads that don't do
well with WLM-managed batch initiators. (For example, a workload that
requires guaranteed immediate initiation -- so called "hot" batch -- or
one that depends on over-initiation or fixed initiator limits.) But, for
most batch workloads, it's just fine. It's easy to try as well. (One
command can switch a JES2 job class to/from WLM management.)
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.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
