1. A new init class configuration, where class 'a' is on one LPAR and not
the other. Extending this to multiple classes would force work to one LPAR
or the other depending on a job's class.
2. WLM Scheduling Environments. Run some applications on one LPAR, other
applications on the other.
3. I don't have Thruput Manager but it sounds pretty flexible; maybe they
have something that can do this easier than #1 and 2 above.
__________________________________________________________________________________________________
Dave Thorn * Senior Technology Analyst * SunGard Computer Services * 600
Laurel Oak Road, Voorhees, NJ, 08043
Tel 856 566-5412 * Mobile 609 781-0353 * Fax 856 566-3656
CONFIDENTIALITY: This e-mail (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this e-mail in error,
please notify the sender and delete this e-mail from your system.
Mark Jacobs
<[EMAIL PROTECTED]
SERV.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Spreading Batch Work Across LPARS
08/03/2006 07:48
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
We have two lpars that perform the vast majority of our batch work. CA7
runs
on one of these lpars and most of the CA7 submitted jobs are picked up by
the
JES2 on that system. This leaves the other system almost empty of batch
work
while the first system is being over loaded.
What are some of our options to spread the workload across both systems on
an
equal basis.
zOS 1.4. JES2 managed batch. Thruput manager is available.
----------------------------------------------------------------------
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
