Partner TechTip: Troubleshooting Enterprise Job Scheduling Issues Is Nearly Impossible PDF Print E-mail
Tips & Techniques - System Administration
Written by Tom Huntington   
Friday, 21 August 2009 00:00

Article Sponsor



6533 Flying Cloud Dr., Suite 200, Eden Prairie, MN, USA, 55344

Help/Systems develops, markets, and supports automated operations and business intelligence software for the IBM System i. We devote 100% of our research and development to operations automation and business intelligence for System i computers, so we always will be here for the System i user.



Discover how easy it is to view Windows and UNIX logs from one central console.


As we automate more and more of the data center, we realize that just because something is automated doesn't mean that we will never have to deal with it again. Eventually, some of these automated tasks are going to fail. When they fail, you need to be able to view the logs for these events. You may need to sign on to the server, and you may need to provide reports to your management team, too.


Troubleshooting and quick thinking can be challenging when debugging production control issues in the middle of the night. The last thing you want to do is spend time searching for the evidence. Every minute you spend looking for logs or reports that help uncover the problem is time ticking away on the service-level agreement. How do we provide that one-stop-shopping approach that allows one click of the mouse to find the problem?


Robot/SCHEDULE Enterprise is Help/Systems' answer to these troubleshooting difficulties. For years, Robot/SCHEDULE has quickly solved AS/400-based scheduling issues. With the release of Robot/SCHEDULE Enterprise, we have conquered this issue for the Windows, UNIX, and Linux production control team. The completion history of Robot/SCHEDULE allows the administrator to see the jobs that have failed (see Figure 1).



Figure 1: Robot/SCHEDULE Enterprise Completion History shows jobs that have ended abnormally.


Once you have the list of jobs that ended abnormally, you can see whether a job is an Agent job or a System i job. You can look at the jobs' spool files (Figure 2) to see that one of the files is the agent log and the other is the typical job log from the System i.



Figure 2: Double-click on AGENTLOG or QPJOBLOG file to start troubleshooting.


Then, you can open the agent log and see the problems. In this case, it was a failed logon attempt to the server (see Figure 3.) Robot/SCHEDULE Enterprise supports signing onto the server via the user interface. This again allows you to do all of your troubleshooting from one central console.




Figure 3: Review the AGENTLOG for the cause of the job failure.


We know controlling your enterprise scheduling is very important. Learn more about Robot/SCHEDULE Enterprise and even try it free for 30 days in your environment. Also, check out Help/Systems' other offerings in the MC Showcase Buyer's Guide.


Tom Huntington
About the Author:

Tom Huntington is Vice President of Technical Services for Help/Systems, Inc. Contact Tom at 952.563.1606 or at


See Tom Huntington's blog at


Last Updated on Thursday, 20 August 2009 10:49
User Rating: / 0