I would say you have 2 challenges here.  One managerial, which causes the
second
technical one.

Managing your system to provide appropriate service at all times may require
some
discussions with the non-technical folks.  Productivity should not
necessarily be
sacrificed for the sake of lower importance Batch.  No matter how many
people thing
compiles need to be turned around in less than 30 seconds. Once you have
that agreement,
fix your WLM Service Policy.  TSO is Interactive (along with some USS work),
and
setting the proper Goals will help a lot.  I prefer 2 Service Class Periods;
some
sites prefer 3, in order to catch the longer running work that really does
belong in
Batch.  For a 2 Period Service Class, I would like to see 95% of the work
complete
in the 1st Period, with 5% in the 2ne Period.  Use something like:
P1- 95% < .5 seconds, Importance=2 with DUR=500 or 1000 (depends on your
coefficients 
and how generous you want to be).  P2- Velocity = 31, Importance=4 (avoid
DISC,
unless you have spare capacity).  Run the change for about a week, then
adjust your
duration to hit the 95-5 recommendation.  Depending on if you want
complaints to
start or you want to create a wide berth, start with 1000 and move down to
750 to
500, if you are way over-achieving the rule.  Or start at 500, listen to
complaints,
and gently increase the duration.  Please be sure that there is very little
Batch
(or any other over-aggressive work) that is being managed above the 1st
Period work.

============================================================================
=====
Sorry for a newbie to jump in here...

But I have a question: why IBM doesn't increase the clock of mainframe
CPU?
There is no need or there are some technical problems?

I'm now working at one customer's site and every day's afternoon is a
terrible time for all developers working on their development system: we
just cannot use TSO/ISPF! You must wait 4 or 5 seconds for a response
and
sometimes you just hang there. The cause is that most teams will do
their
batch tests at that time thus eating all of CPU cycles. I guess they
might
need a more powerful CPU? (This situation has last for three months
since I
came here) 

-- 
Best Regards,
Johnny Luo

----------------------------------------------------------------------
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

Reply via email to