On Tue, 25 Mar 2008 10:00:39 -0500, Aimee Houghton <[EMAIL PROTECTED]> wrote:
>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 > > >Any suggestions would be greatly appreciated. > You're going to get lots of different answers and opinions on this one. Mostly because there is no right answer as every shops is different and it depends on what you are trying to accomplish. I will say that I think the duration is much too short for your P1. If all your operators are trying to do is SDSF type monitoring (DA) or edit a PDS for example, then having a higher importance (as you already do) is good enough, but they probably aren't getting enough service in P1 to switch between screens or read a PDS directory. Here is what I have: # Duration Imp Goal description - --------- - ---------------------------------------- 1 2500 2 85% complete within 00:00:00.350 2 5000000 4 Execution velocity of 15 3 Discretionary The only reason I have a period 3 is for some long interactive SAS work that really is like test batch (notice how long that P2 duration is!). You might want something similar if you have that or something like Focus. If not, you can usually live with 2 periods like you have today. Certainly if you want to set up a separate service class for your operators (and of course the system programmers ;-) ) you can bump up the importance of period 2 to be 3 so it can compete more fairly with your production batch when things are busy. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
