Debugging and servicing of multithreaded jobs

Use the concepts and techniques that are described here to learn about 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 were not changed to support multithreaded processes. Therefore, the existing commands will continue to operate against the job and not individual threads within the job.
• 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
  The Display Job (DSPJOB), Work with Job (WRKJOB), and Work with Active Jobs (WRKACTJOB) commands allow you to display and work with threads associated with an i5/OS™ job.
• Multithreaded job debugging
  The spawn() API provides a mechanism to allow you 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.