Max, I have to agree, an unattainable goal is an invalid goal.
If you're getting a PI of 1.4 to 2 (or higher) that likely means that the work that is running in that particular service class is actually getting a velocity of 64 (at best ~ 1.4 PI) down to 45 or worse (at >= 2 PI). We don't have any velocities over 50 for anything, no matter how important. Most of them are around 30 for started tasks. If it's so important that it needs the highest priority, it goes to SYSSTC. It sounds like a good review of your goals, importance levels, and actual service levels (i.e. how workloads and service classes are performing now) is in order. It gets even more fun if you're attempting to balance across a CECPLEX for IRD and ensure adequate performance for high importance workloads at 100% physical busy times. Best regards, Gary Diehl -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Max Scarpa Sent: Wednesday, September 28, 2005 8:25 AM To: [email protected] Subject: A quick question about velocity goals set high Estimeed lister I'm in a shop were I see for some subsystems (CICS,CONTROM etc) a very high velocity goal, that is 90%. PIs range from 1.4 to > 2 and it NEVER reaches 1 nor it's below 1. I read some pepres that a very high velocity goal (>80%) is not good if not useless and infact in my previous shop in some CICS we lowered our goals without any delay in response time. Is still bad to put velocity goals higher than 80% ? In IMHO it is. Thank you in advance Max Scarpa ---------------------------------------------------------------------- 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
