Re: CPU utilization high daily at specific time

["Michael Ryan" <michaelrtr@xxxxxxxxx>]

Yes, there are a couple of SQL exit points. Michael Sansoterra just wrote a
good article about which I can't find right now.

On 11/9/06, dennis.e.lovelady@xxxxxxxxxxxxx <dennis.e.lovelady@xxxxxxxxxxxxx>
wrote:
> Thanks for your reply, Wayne.
>
> Unfortunately, as I said, we believe this job to be initiated remotely,
> perhaps from a M$SQL server that's gathering data it needs for some
> report.
>
> Sorry, I should have been more specific.  Is there some exit program or
> other stealth way we can actually drill down to the SQL statement being
> executed under these circumstances?  I realize I can see "last SQL
> statement executed" within the iSeries Navigator tool, once the job has
> been identified, but we'd like this to be a tad more automatic.
>
> Dennis E. Lovelady
> Accenture
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine
> Sent: Thursday, November 09, 2006 6:37 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: CPU utilization high daily at specific time
>
> Dennis, take a look at scheduled jobs using the WRKJOBSCDE command.  You
>   will be able to see the scheduled times of all jobs and isolate the
> one that is causing the problem.
>
> dennis.e.lovelady@xxxxxxxxxxxxx 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 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.