IBM i Job Trace

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.”


Using the Debug Memory Manager With RPG

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.


Dump a Communications Trace

A recent enhancement to the 6.1 communications trace support allows the collected communications trace data to be dumped to a file in the packet capture (PCAP) format. The Dump Communications Trace (DMPCMNTRC) command was introduced in V5R3. This command lets you dump a communications trace to a stream file. Prior to the 6.1 enhancement, you could then print the dumped trace data with the Print Communications Trace command.