Debugging and servicing of multithreaded jobs

These concepts and techniques can help you with debugging and servicing multithreaded jobs.

The concepts that are described in this section pertain to all programming languages. To determine how each language enables these concepts, refer to the Language topic in the information center for the specific language.

Commands that report thread-related data
Most of the commands used to service jobs are not changed to support multithreaded processes. Therefore, the existing commands continue to operate against service jobs, rather than individual threads within service jobs.
Flight recorders
A useful way to debug multithreaded applications is to write data to a flight recorder. A flight recorder is a file, output buffer, or some other object where trace information is written so that problems in the application can be tracked.
Options to view thread information
You can use the Display Job (DSPJOB), Work with Job (WRKJOB), and Work with Active Jobs (WRKACTJOB) commands to display and work with threads associated with an IBM® i job.
Multithreaded job debugging
You can use the mechanism provided by the spawn() API to start a debugging session before actually calling the multithreaded program to be debugged.
Areas to test for multithreaded applications
Testing is key to the process of verifying the correctness of a multithreaded program.

Parent topic: Multithreaded applications

Related concepts:

Common multithreaded programming errors