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.

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.

IBM i is one of the most secure systems in the world. Don’t take that security for granted by leaving Robot Schedule vulnerable when it could be easily remediated.

WebDocs iSeries uses the IFS directory /RJSTEMP and the library RJSTEMP to store information and files temporarily. In general, it will attempt to clean up after itself, but there are situations which arise that do not perform clean up operations. As a result, files will gradually accumulate, taking up disk that could otherwise be used for other processes. The RJSTEMP library The RJSTEMP isn’t...

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.