Automatic message management, resource monitoring, and log monitoring
Manage Messages by Exception
Inattention to IBM i messages and events can result in backlogs of website orders, inventory updates, or account transactions—which is never good. Robot Console automatically searches message queues for anything that could impact system or application performance. When something goes wrong, Robot Console can automatically fix the issue or escalate it, so you can manage by exception. This robust message management software enables you to work more efficiently and have time back in your day to do what matters.
Increase Availability for Critical Resources
Real availability monitoring goes beyond the QSYSOPR message queue. Ensure that your business users have the access they need to the system resources and applications they rely on every day. Robot Console monitors system resources like lines, ports, and subsystems and system logs like QHST, QAUDJRN, or FTP requests at regular intervals. If it detects a problem, Robot Console can automatically take action, resulting in more uptime so business can run smoothly.
Reply, Escalate, or Troubleshoot from Anywhere
Robot Console lets you know when you must reply to a message. You can tailor the message notification options to your requirements. If a message isn’t answered in a reasonable amount of time, Robot Console routes it to someone else, even a user on a different IBM i. If you need to troubleshoot, you can open Robot Console in a browser-based interface from your preferred device and get to the bottom of issues quickly.
Key IBM i Monitoring Features
System Requirements: IBM i 7.2 or higher
Easily create and implement message management rules without the need for constant operator training. Robot Console can automatically apply rules consistently around the clock, while tracking any actions taken outside of established automation rules.
Keep an eye on the status of your important system resources, including system and job CPU, subsystems, controllers, lines, devices, writers, jobs, job and output queues, TCP/IP servers, ports, and IBM MQ channels, managers, and queues.
Get a complete picture of your system activities. Robot Console automatically monitors your system logs, giving you visibility into FTP requests, system history (QHST), and the security audit journal (QAUDJRN). Whenever there are issues or potential system violations, you’ll be notified.
Many applications direct informational messages, event messages, and errors to log files in the integrated file system (IFS). Make monitoring your IFS directory for log files automatic with Robot Console. Define application log monitors in the graphical user interface (GUI), work with their messages in the message center, and easily configure automation or escalation rules from the GUI.
You won’t get burned by taking your eyes off your message queue anymore. Get real-time notifications of new messages and use two-way messaging to respond directly from any workstation or mobile device. Set messages to escalate to other team members within a reasonable time period so important messages are never missed.
Robot Console leverages the power of Fortra Insite! Mobile-friendly dashboards allow you to combine key message summary and resource status data into a single, intuitive view so you can see at a glance what Robot Console is doing on your systems. With one click, you can toggle over to a comprehensive list of messages and system resources where color-coding helps you spot critical situations and granular search functionality makes it easier for you to mass acknowledge or reply to like messages in bulk.
Detailed history records provide answers to all your questions about when messages occurred, who the operator was, how long it took to respond to the message, and what the response was. Reports and displays help you spot patterns so you can resolve issues before they become crises.
One thing that changed for us with Robot Console is consistency. Now, certain messages are always answered the same way, rather than having multiple night operators who might answer questions differently. And, the people on call now get a good night’s sleep.
Jim McDaniels, Assistant Vice President and Computer Operations Manager, Bank of Stockton
The ability to manage all of our systems from a single pinpoint in Robot Alert and Robot Console has been a huge help, not to mention major systems events.
Dan Peterson, Senior Systems Engineer, Columbia Sportswear
Teach Your IBM i Message Management Software How to Respond
Most important IBM i events are preceded or followed by a message. You can use OPAL (OPerator Assistance Language) in Robot Console to react to those events immediately and unattended.
OPAL is easy to learn and use. You can use it to check the contents of a message and determine what action to take, just as an operator would. OPAL can then execute commands, call programs, cancel jobs, or call for help. There are more than 30 OPAL operations, in various categories, that you can use to tell Robot Console how to process a message. Here are few examples:
SUPPRESS—Suppress or ignore this informational message.
RESPOND—Change an informational message to response-required.
ENTER—Enter a specified reply to answer the message.
EXECUTE—Execute an IBM i command.
CALLCP—Call a CL program and pass pre-defined parameters.
PAGE—Send the message to the specified cell phone, laptop, or other device.
DELAY—Delay message processing for a specified period of time.
NOTIFY—Notify a user, via a pop-up window, that a message requires attention.
COPY—Copy the message to another message center.
TERMINATE—End the job that sent the message.
REDIRECT—Remove the message from a message center and put it on the specified center (which can be on another IBM i).
RPYWITHIN—Wait the specified number of seconds for a reply to the message. If no one replies, continue with the next line of OPAL code; if someone does reply, go to the reply section of OPAL.