On Mon, 7 Jan 2013 14:09:32 -0500, Crabtree, Anne D wrote: >Since bringing up z/os v1r13 in late October, our CPU stays at 100%, batch >jobs are backing up and people are complaining. (Migrated from z/os v1r11) > >...I can't say for sure what kind of percentage the CPU was peaking at for >1.11, but I know that we did not get these phone calls complaining about >response time!
You say in a later post that you bill for CPU usage - so we can only assume you have all the (historical) data you need. Presumably you don't have a SAS/MXG pdb, else you wouldn't be asking. You have to determine where the extra (apparent) CPU burn is - by workload, or service class, whatever. Find the variation, then you know where to concentrate - might even be uncaptured, in which case it really might be worth looking at things like exits. I'm currently working at a somewhat challenged environment in the middle of a 1.11 to 1.13 rollout - we see some issues, but nothing directly attributable to 1.13 eating more machine in peak (daylight) hours as you later describe. I might refer you to a thread on the RMF spreadsheet reporter from a few weeks back. Andrew ... ? Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
