With technology changing at light speed, you need to cut the expense of repeatedly re-inventing internal infrastructure to deliver the service levels your business demands.
It’s one thing for an IT team to develop a strategy and quite another to justify the investment by proving that strategy is well-executed and working as intended. Automated monitoring is the answer.
IBM i high availability has been at the top of your wish list for a while. Don’t let budget hold you back any longer. Discover how affordable HA can be.
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.
The SQL-based monitoring feature in Robot Monitor means organizations can now apply the valuable insights, analysis, and real-time notifications that they use for system information to information from broader business applications.
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.
Backup and recovery processes are among the unsung heroes of data center operations. Though end results may not be readily apparent on an everyday basis, natural and digital disasters have a way of humbling companies that do not take this risk management discipline seriously.
Did you know that the Disks Busy monitor reports the average percentage across all your ASPs, not just System ASP? You could be teetering near an I/O overload and not know it! If you have multiple ASPs, use the ASP Busy monitor instead. Here’s why.
Chasing a high availability state is a common goal for IBM i administrators and one that can be thwarted by a single issue left unattended. By sharing some of the most frequent tales of what went wrong from real-world environments, you’ll be able to avoid these same scenarios.
The IT industry is decisively moving away from traditional hard disk drives (“platters”) in favor of Flash-based solid-state drives (SSDs). It’s a welcome change; it makes much more sense to circulate only electrons instead of disks of metal with electrons on them.
While the instinct for administrators and IT managers is to always hunt down a culprit – a rogue job, an inactive journal receiver, or something else – sometimes the very building blocks of a common process, or rather the specifics that define processes, can be where the trouble at hand resides.