I agree with Steve (a typical occurrence), more info is needed. At z/OS 1.7, did you routinely see your processor at 100% busy? What about the other LPARs on the box (if there are any)? Weights properly set? The reason for this line of questioning: if you were routinely running just under 100% at z/OS 1.7, when you went to 1.8, your overhead went up 2% to 3% to 5% (your mileage will vary). Once the CPU busy gets to 100%, WLM will now kick in. Once the entire CEC goes to 100% busy, PR/SM will kick in. An non-optimal WLM Service Policy along with improper LPAR controls may be tolerated at 95% busy; but once over 100% may cause you pain. Are you running on a uni-Processor? This also has challenges.
So other input needed: Physical Config, Logical Config, WLM Service Policy (helpful), Perf Index for problem Service Class Period(s), what else is running in the system (above your problem CICS) Without more info, I'd suggest it is NOT a CICS problem (unless you also upgraded CICS or added maintenance). -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Steve Samson Sent: Tuesday, February 27, 2007 SYSN PM 1:31 To: [email protected] Subject: Re: z/OS V1R8 WLM & CICS Performance Observation Jim, There's not enough information yet. Are you running CICS with response time goals? Are they being met? If you are using velocity goals only, are those goals being met both before and after the queue buildup? Input! Input! Steve Samson ---------------------------------------------------------------------- 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
