Monitor for High CPU Usage Batch Jobs

20 pts.
AS/400 jobs
iSeries job
Hi There, I would like to monitor for Batch Jobs that use high CPU for over 5 minutes. These jobs tend to be failed application batch jobs. Any ideas?

Software/Hardware used:
V6R1 - Power 5 i520

Answer Wiki

Thanks. We'll let you know when a new response is added.

First, a “failing” job that uses high CPU should be fixed immediately. A failure shouldn’t result in high CPU usage.

You might use Management Central to monitor for high CPU usage. In iSeries Navigator, expand Management Central. Drill into Monitors-> Job. Right-click on Job and select New monitor…

You will need to experiment with a number of settings. I can’t tell you what to try on your system because I have no idea what all the possibilities are in your environment. When complete the first page, select the Metrics tab. CPU is monitored under Available metrics-> Job numeric values-> CPU percent utilization.

You can set a command to run when the level is detected. You might simply run a SNDMSG command to send yourself a message.

By experimenting with the Management Central Job monitor, you will begin to understand the complexity of trying to do it yourself.


Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • WoodEngineer
    We have had good success with Navigator.  It has some very handy monitoring features.
    8,225 pointsBadges:
  • ToddN2000
    A job with high CPU may be looping, or a user may have submitted a query to run in batch that was poorly designed. What are you looking to do as a result? Do you want to end these jobs automatically? Or have an e-mail notification of a possible problem? If this is a continual problem with the same program, I'd have a programmer look at it. It could have a logic problem that needs to be resolved.
    134,960 pointsBadges:
  • dspilka
    Navigator has worked well for us too.
    5,650 pointsBadges:
  • ToddN2000
    What would you consider a high amount of CPU? A lot of time we would see that with interactive queries being run. If it a specific job that appears to be hogging the CPU then submit it with a higher run priority than your interactive sessions. Maybe set the batch RUNPTY to 40? As for monitoring performance Navigator works quite well.
    134,960 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: