Sometimes, there are known vulnerabilities that clearly need to be mitigated as soon as possible—such as application users running with *ALLOBJ special authority. But, often there isn’t a thorough understanding of what’s wrong with a server’s configuration or what should be addressed first.

We recently surveyed our Robot Schedule technical support group for “ah ha!” moments that they’ve helped customers realize over the past few years. These tips from our tech gurus have helped customers automate jobs that needed to check a data area before running, track non-Robot jobs for reporting purposes, and check the status of a file before running a job.

There is nothing like waking up to find the latest news delivered right to your doorstep, waiting for you on the printer, or sent to you electronically. For years, our customers have started their days reading the Good Morning report from Robot Schedule.

The operations team was excited to share how Robot job scheduling and monitoring software has helped them manage their processing needs across platforms from their IBM i.

In a manual monitoring environment, for every issue that arises, there is often a multiple-step investigation process to accompany it.

Making your business applications modern goes way beyond the GUI. It’s about providing a superior user experience from front to back, IT to end user. Trevor Perry tells all in this article.

When it comes to cleaning up these old Robot Schedule jobs, the best way is to use a SQL statement that you can run from STRSQL. This article will show you how.

A powerful feature of Robot Schedule file monitoring is the ability to capture the file name and path information, and use it in a file transfer, copy or delete operation, or combination of commands.

There are two sides to every Robot Network. It offers centralized control of the Robot software running on your IBM i partitions as well as performance monitoring and exception-based management across your environment.

Let’s say you have a bank transmission or FTP process that occurs randomly throughout the day. How do you monitor that activity? OPAL? CLP scripts? Not anymore!

Automated job scheduling means your batch jobs run smoothly and your stress level goes down, but that’s only half the battle if you’re using labor-intensive, interactive applications that require you to fill out screens to submit a job.

What do astronauts and IBM i admins have in common? Checklists! These seemingly simple yet effective devices serve as our external memories and deliver process consistency, but they’re not without limitations.