Does your team manually open IFS error logs for your application? If you run EnterpriseOne, SAP, Domino, WebSphere MQ, or M3, it's time to automate.
Traditionally, IBM applications were written only for IBM i, sending all their error messages to QSYSOPR. However, UNIX-based applications have been migrating to IBM for the last 15 years or so. These applications may have some errors—such as a file full message— that go directly to IBM i QSYSOPR, but it's likely they also have other errors that are hidden in a log file within a directory on IBM i. How does your team manage these?
Some teams are aware of these error logs and check them periodically, but it's usually a manual process that takes place independent of the operations team. The application might have a user interface that offers feedback or provides a view into this data, but you don't have time to waste remembering to check for potential exceptions.
You also don't want to wait for end users to complain that something doesn't look right in one of these applications, and you definitely don't want your developers to be responsible for day-to-day operations. What you need is a solution that takes care of application monitoring for you automatically.
Automation Is the Answer
Error logs are nothing more than a text file stored in the Integrated File System (IFS). With a little automation and string comparison, like what's available in Robot CONSOLE, you can easily get around the process of manually looking at this information. Robot CONSOLE has the ability to periodically read a file in the IFS and look for strings or phrases that indicate an application error has occurred.
With Robot CONSOLE, you can define a directory and generically read any new log files. Filters are then applied so that error messages or other strings of text can be identified and converted using the escalation procedures in Robot CONSOLE. If the filter matches, a record is placed into a message center and a corresponding rule can escalate the event. Along with monitoring QSYSOPR, this can shed some light on errors stored in the IFS log file on IBM i.
Figure 1: Robot CONSOLE monitors the IFS directory for new error logs in EnterpriseOne.
Figure 2: Filters can check for error messages in an EnterpriseOne log file.
Where Are the Logs on IBM i?
Google is a great tool for finding information about IFS error logs for your application. Here are a few that might come in handy:
These are the IFS directories:
- /QIBM/UserData/mqm/errors
- /QIBM/UserData/mqm/qmgrs/<queueManagerName>/errors
- /QIBM/UserData/mqm/qmgrs/&SYSTEM/errors (not used at V6 and higher)
The error log files are named AMQERR01.LOG, AMQERR02.LOG, and AMQERR03.LOG.
The system log can be displayed with transaction SM21. In case of errors, the log shows the error implementing SAP applications on the IBM System i platform with an IBM i5/OS message, information about where in the application the error occurred, a reference to a so-called short dump, and the qualified job name of the job that received the error.
The system log entries for an instance are in the '/usr/sap/<SID>/<instance>/log/SLOG<nn>' file.
Check for Errors Automatically
Robot CONSOLE monitors the traditional items on IBM i—including messages, resources, and system logs—with no problem, but it can also dig deeper into obscure application errors from SAP, EnterpriseOne, WebSphere MQ, Domino, and other UNIX-based applications.
To see how you can be more proactive in serving your application team, request a free 30-day trial of Robot CONSOLE.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online