Below is the report we have recevied from our heads. I was just wondering how these values are achieved.
Date 08/02/12 08/11/2012 09/02/12 09/11/12
Number of interactive transactions 48080 73119 8420 91111
Number of batch jobs 22011 25555 19366 36888
Logical DB I/O Count 8106140 383377 535011 1504364
CPU Utilisation BATCH 44.1 79.2 44.9 69.1
Disk I/O's per second 77.12 171.22 133.01 166.36
CPU Util Pool Total 75.1 71.9 77.8 84.2
Number of SQL jobs 89 69 38 77
Number of SQL I/O's 13869223 108984833 916335 13516919
Average interactive transaction rate per hour 1462 2463 250 5013
From: Gqcy <gmufasa01@xxxxxxxxx>
Sent: Friday, 14 December 2012 10:56 PM
Subject: Re: Iseries System Extermely Busy.
make sure all disks are nod DEGRADED, FAILED or some other
status indicating a problem...
What is your % used? depending on storage type and configuration a
very high % will greatly effect performance.
On 12/14/2012 11:11 AM, John Mathew wrote:
For the last few weeks our iSeries system was extermely busy and the processing is very slow.
Can some one please guide me to check the following points in the system.
Increase in the number of interactive transactions
logical DB I/O's to disk.
Number of SQL jobs processed.
SQL I/O's to disk.
CPU Batch utilisation
Average transaction rate per hour.
Disk I/O's per second and CPU pool usage.