Debugging

You can choose between two different approaches to determine the cause of problems in the behavior of your application: source-language debugging or interactive debugging.

For source-language debugging, COBOL provides several language elements, compiler options, and listing outputs that make debugging easier.

If the problem with your program is not easily detected and you do not have a debugger available, you might need to analyze a storage dump of your program.

For interactive debugging, you can use Debug Tool. Debug Tool offers these productivity enhancements:

  • Interactive debugging (in full-screen or line mode), or debugging in batch mode

    During an interactive full-screen mode session, you can use Debug Tool's full-screen services and session panel windows on a 3270 device to debug your program while it is running.

  • COBOL-like commands

    For each high-level language supported, commands for coding actions to be taken at breakpoints are provided in a syntax similar to that programming language.

  • Mixed-language debugging

    You can debug an application that contains programs written in a different language. Debug Tool automatically determines the language of the program or subprogram being run.

  • COBOL-CICS® debugging

    Debug Tool supports the debugging of CICS applications in both interactive and batch mode.

  • Support for remote debugging

    Workstation users can use the IBM® Debug Tool Plug-in for Eclipse or the IBM Problem Determination Tools with Rational® Developer for System z® for debugging programs that run on z/OS®.

related tasks  
Debugging with source language  
Debugging using compiler options  
Using the debugger  
Getting listings  
z/OS Debugger User's Guide

related references  
Debug Tool Reference and Messages
Language Environment® Debugging Guide (Formatting and analyzing system
   dumps, Debugging example COBOL programs)