Whether your IBM i audit is internal or external, once a week or once a year, the reporting process wastes time that would be better spent on projects that improve business processes. Don’t let it.

Media Text As...

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.

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.

Wondering about best practices for automating your IBM i processes with Robot systems management solutions? Take a look at this list and get off to a good start.