RE: CPU utilization high daily at specific time

Thanks for your reply, Vern.  We have already added the WRKACTJOB
monitor to WRKJOBJS (one job, starting at 4:something, issuing repeated
"WRKACTJOB OUTPUT(*PRINT) SEQ(*CPUPCT) / DLYJOB(60)" for a period of
time).  But that will only tell us job name (as will the other things,
which I have been through a number of times in this investigation.

Since the Host Database Server jobs do not end upon first use within our
configuration, there is no useful CPF1164 message issued.  Nothing by
job name stands out as "the solution" to identify this issue.

Yes, you're right; I may have to set my alarm for some ungodly hour;
won't be the first time for that.

Dennis E. Lovelady
Accenture
404-386-9745 (Cellular)
delovelady <- AIM
fastcounter@xxxxxxxxxxxx <- MSN

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, November 09, 2006 6:41 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPU utilization high daily at specific time

Hi Dennis

I guess the idea is to identify which jobs are consuming the most CPU%.
First and easiest - be there at te time and sit in front of WRKACTJOB
and either F5 or F10 periodically - put your cursor on the CPU % column
and press F16, so that the highest CPU % is at the top.

Or put WRKACTJOB OUTPUT(*PRINT) in appropriate combinations of reset and
not rest in a CL - loop with delay, say every 3 minutes. See what you
see.

Or if you have Performance Tools, run a collection at that time and look
at the relevant reports.

Or look at the QHST* files for that time period. You want the CPF1164
messages, because they have have message data for CPU time and elapsed
time. Divide the former by the latter to get CPU% - do this for jobs
running during that time period. This information is not viewable with
the DSPLOG command - you have to read the QHST* file directly - more
info in message handling chapter of CL Programming or in Work
Management, IIRC.

Hope this helps - good luck!
Vern

At 05:22 AM 11/9/2006, you wrote:

Hello, All:

One of the iSeries systems in our configuration usually has relatively 
low (30-50%) utilization during the early morning.  However, recently 
we have had daily occurrences of near 100% utilization (sustained for 
about
30-45 minutes) at between 5AM and 6AM.  We strongly suspect that this 
is the result of some query being issued by a scheduled job on some 
other server.  We would like to identify either the job or (Ideally) 
the SQL statements that are being executed under these circumstances.

This is causing an impact to that system's ability to quickly process 
data coming from MQ during that time period, which is a very bad thing 
in this case.

Can any of you give some idea what we might do to identify the job or 
user, and potentially the exact statement that is causing this 
performance hit?  Or maybe some other information I need to provide in 
order to arrive at an answer?

Thank you,

Dennis E. Lovelady
Accenture



This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information.  If you have

received it in error, please notify the sender immediately and delete 
the original.  Any other use of the email by you is prohibited.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a

moment to review the archives at 
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.