Why haven’t IT processes kept pace with business changes? Why are you still suffering from downtime as the result of human error? Read this article to see how legacy processing methods are still leading to downtime today—and what you can do to stop it.
Many ERP packages have built-in schedulers. However, these schedulers are typically not flexible or robust enough to meet the needs of even the smallest data center.
How many separate job schedulers are you juggling? Don’t let your important processing into a scheduling circus. Stick with a single, sophisticated solution.
Your shop runs more than 30 jobs each day. Your jobs must communicate across IBM i and another OS. You need to monitor them and generate reports for audits or SLAs. Do your existing job schedulers really meet your needs?
Looking for better ways to integrate your Windows, AIX/UNIX, and Linux environments with the Robot Schedule scheduling system? Robot Schedule Enterprise commands can enhance your integration experience.
Ask any security professional which area of IBM i security is most often ignored and chances are that the unanimous response is a chorus of “the Integrated File System.” Although it’s been around since V3R1, the Integrated File System, or IFS, remains a shrouded mystery that represents significant risk to many IBM i organizations.
File Integrity Monitoring (FIM) helps ensure that your critical and sensitive data is viewed and changed only by authorized personnel through approved channels. Candidates for FIM include application files containing sensitive data, such as personnel or financial data, and server configuration files.
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.
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.
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.