As a youth in the 1990’s, the mobile phone revolution that spread across the globe was similar to the ever increasing role that the World Wide Web is playing in our lives now.
I remember when I got hold of my first mobile phone as a gift from my dear dad, the solidly dependable Nokia 5165 was one of the best mobile phones to own. It didn’t have any fancy features such as call waiting, text or picture messaging, instant messaging, internet browsing or activities log. But it did the job for which it was intended, which was the ability to talk to people while they are out and about, with simplistic ease.
However, one of the most frustrating things with these phones was seeing the screen display “1 missed call”. You could only hope that the caller would call back because it was not possible to see the caller’s number in order to return their call. It was accepted as the ‘norm’ as it was the limit of the technology of the day. What usually happened was that the original caller continued to ring until they finally managed to get hold of you. Unless it was an important or urgent call, we never complained or got upset about the limitations.
Over the years, technology improved and more features have been added to mobile phones to the point that we now call them “Smartphones”. They can now take pictures, send and check emails, watch your family in real-time from remote locations or even record your favourite television programme.
Because the smartphones are so advanced, unless the missed call is from a withheld or private number, you now have the ability to retrieve message or call history as everything is logged in the activity log. It is now considered bad etiquette to ignore an important missed call, especially if they have left you a voicemail.
How is this relevant to the IBM i? An application will be running on your IBM i server, error messages may appear in the job’s joblog that can be easily lost or missed. This potentially exposes you to missing important information that you may need to know about. As an IBM i administrator you may think that monitoring the QSYSOPR, QHST and the Audit Journal would have you covered but not in this case. Why am I saying that? Let me explain using this scenario.
Active jobs appears to be running OK on your screen but unbeknown to you in the job log are some transient error messages. These messages would not appear on any message queues or history logs, but it will be clearly visible in the internal Job Log of the session.
The worrying question that may then spring to mind is; “What will be the cost implications to the business if this happens?” Think again as the cost implications might run into thousands, millions or even cost you your job in the end for something that could have been prevented in the first place.
You need a utility that provides total message visibility so that you can be sure that nothing is passing under your radar.
Using the Halcyon Job Log Monitor makes it easy to track down and monitor these messages. It allows you to monitor active running jobs (interactive or batch) for specific message ID’s, severities or even types of messages & alerting accordingly.
Halcyon’s Job Log Monitor is a new addition to our Levels 1 – 4 software suites.
If you would like assistance from our team of technical experts that provide a refreshing, professional approach to solving operational issues you face as an IT professional, request an online meeting.