|
Hi DennisI 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 AccentureThis 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
