A program or module must have debug data available if you are to debug it. Since debug data is created during compilation, you specify whether a module is to contain debug data when you create it using CRTBNDRPG or CRTRPGMOD. You use the DBGVIEW parameter on either of these commands to indicate what type of data (if any) is to be created during compilation.
The type of debug data that can be associated with a module is referred to as a debug view. You can create one of the following views for each module that you want to debug. They are:
The default value for both CRTBNDRPG and CRTRPGMOD is to create a statement view. This view provides the closest level of debug support to previous releases.
If you do not want debug data to be included with the module or if you want faster compilation time, specify DBGVIEW(*NONE) when the module is created. However, a formatted dump will not list the values of program variables when no debug data is available.
Note also that the storage requirements for a module or program will vary somewhat depending on the type of debug data included with it. The following values for the DBGVIEW parameter are listed in increasing order based on their effect on secondary storage requirements:
Once you have created a module with debug data and bound it into a program object (*PGM), you can start to debug your program.
The debug views are summarized in the following table:
| Debug View | Debug Data | DBGVIEW Parameter Value |
|---|---|---|
| None | No debug data | *NONE |
| Statement view (default) | No source displayed (use statement numbers in source section of compiler listing) | *STMT |
| Root source view | Root source member information | *SOURCE |
| COPY source view | Root source member and /COPY members information | *COPY |
| Listing view | Compiler listing (dependent on OPTION parameter) | *LIST |
| All | Data from root source, COPY source, and listing views | *ALL |