QDF (quick dirty fix) is to set TSO period 2 to importance 3.
This should change things from intolerable to manageable <G>

If you want "no further calls" for ever and ever, Set TSO period 2 to
importance 2. This will place TSO ahead of PRODHI. (be careful!).

RMF SYSRPTS(WLMGL) provides a wealth of information about what is
actually occurring. 

The correct resolution depends on you installation requirments.

In the past I have used a 3 period TSO scheme. Per 1 accounts for 80% of
all trans (adjust the duration until this is achieved), Per 2 accounts
for 80% of the remainder (16% of total), Again, adjust the duration
(cumulative) of Period 2 until the 96% is achieved. Per 1 is IMP 1 or 2,
Per 2 is IMP 2 or 3, Per 3 is below standard batch. (any work that gets
here most likely should be run as batch,

<snip>
I am no performance expert and I am basically mostly using Cheryl Watson
quickstart (or whatever it is called). We are only using one service
class
for TSO users.  For the most part it works fine but during batch window
we
have times when the operators let a bunch of stuff run in high priority
batch service class.  During those times, TSO users tend to sit and
hang. 
Of course, the operators bump up their own priority so they don't have a
problem.  I am looking for suggestions as to how to setup the service
class
for TSO users to avoid having them hang during these situations.

Here is my service class for TSO:

Base goal:
CPU Critical flag: NO

  #  Duration   Imp  Goal description
  -  ---------  -    ----------------------------------------
  1  800        2    80% complete within 00:00:00.300
  2             4    Execution velocity of 40


Here is my service class for PRDBATHI (which I am assuming is causing
the
problem):

Base goal:
CPU Critical flag: NO

  #  Duration   Imp  Goal description
  -  ---------  -    ----------------------------------------
  1             3    Execution velocity of 40
</snip>

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