On 8/01/2013 22:04, Shane Ginnane wrote:

I might refer you to a thread on the RMF spreadsheet reporter from a few weeks 
back.
Andrew ...   ?

Thanks Shane :-)

If you need a tool to read the SMF data, you could download the 30 day trial of EasySMF from:
http://www.smfreports.com/

My suggestion would be to set the time interval to cover a few days before and after the change, then look at the charts for:
- System CPU Busy
- RMF Service by Service Class
- RMF Service by Report Class
and see whether there are any obvious changes.

Depending what you see you can use the Job Status reports to see more detail about the jobs in that service/report class.

The Job Profile and Job History reports can show you information about specific address spaces and jobs over time.

However, you say you are not sure what the CPU peaks were before migrating. If it was already peaking at or close to 100% the problem might be more related to the WLM policy. At 100% busy, subtle WLM changes can make a big difference between everybody being happy and everybody complaining. If you regularly have multiple service classes missing goals, any changes to how WLM choses donors and receivers in 1.13 might trigger problems. (I don't know whether there were such changes, but I wouldn't be surprised.)

For WLM, you could start with the Performance Index report.

Another possibility is hiperdispatch, if that has been newly enabled with 1.13. I suspect hiperdispatch would have similar effects to moving to fewer, faster processors which has been well documented. Fewer, faster processors makes the WLM policy more important and problems tend to show up as complaints about response times.

You should definitely look at whether the CPU usage has increased and how much, and whether there are specific problems that caused it. However, keep an open mind to other factors like WLM.

Regards

Andrew Rowley

--
Andrew Rowley
Black Hill Software Pty Ltd

[email protected]
+61 413 302 386

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to