One of the presentations I give often covers the various ways you can monitor your IBM i partition using IBM provided tools.
I talk about Navigator Monitors as well as the older Management Central Monitors (well, not any more…). But I also talk about watches.
(more…)In the 5.4 release, IBM introduced the Work with Traces (WRKTRC) command. This is a handy little utility that allows you to review all the traces that may be active on a partition, as well as a centralized interface for managing traces.
(more…)A few weeks ago, I wrote about Job Trace, followed by an update on how you can instrument your applications for IBM i job trace. Job trace is but one of many tools used to collect diagnostic data on i.
(more…)Last week I wrote about the IBM i Job Trace capabilities. In that article, I briefly mentioned that you can instrument your own application so you can collect your own trace data as part of a job trace.
(more…)When you have a problem you need to resolve, how you approach doing problem determination depends upon the actual problem. IBM i has a very rich set of diagnostic tools for problem determination purposes.
In this week’s blog, I’ll talk about what is called the “job trace facility.”
(more…)RPG programmers who use RPG’s memory management operations (%ALLOC, %REALLOC and DEALLOC) should read the blog Debug Heap-Usage Problems about the debug memory manager. The debug memory manager can be used to locate errors in an application that uses heap storage. Debugging problems related to memory management can be very difficult because the symptom of the problem often occurs long after the problem was caused. I can attest from personal experience that the debug memory manager is a great tool. On one occasion it pinpointed my problem instantly. Without the debug memory manager, I would’ve had many repeated debug sessions, gradually working my way back to the original coding error that was causing the problem.
(more…)