Being a cybersecurity professional means you’re regularly in charge of making complex decisions with real-world consequences, like choosing the right cybersecurity benchmarks, controls, frameworks, or best practices for your organization. Should you apply the CIS Controls, the NIST Cybersecurity Framework, or something else? Without overarching industry consensus, it can be...
VIOS is considered a standard in organizations running IBM i, AIX, and Linux workloads. But don’t put your business at risk by letting it run unchecked. Learn five areas you must be monitoring.
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.
You might think VIOS is set and forget, but it’s not. Luckily, VIOS includes a number of command line utilities to help you obtain performance-related information from your VIOS partitions.
Proving that you are meeting service-level agreements shouldn’t be a wasted effort. In fact, it should strengthen your relationship with clients and help your team manage performance in the future. See how.
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.
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.