Referencing Included or Copied Files

Many source programs have the contents of separate files inserted into the program at compilation. Programs written in PL/I use %INCLUDE, ++INCLUDE, -INC and/or EXEC SQL INCLUDE.

When the debugger encounters one of these statements in a program, you can display the contents of the included file by using Source followed by the filename cited in the INCLUDE directive. The lines in the file will be numbered consecutively from the first line in the file. To return to displaying lines from the source file containing the current environment, simply use the Source command with no arguments.

Support for include file handling has been added for Open PL/I. This applies to include files that contain executable code. The current set of functionality is implemented as follows:

• Stepping "into" an include file, for example, when the next statement is a %INCLUDE directive, will cause the screen display to switch to the specified include file. Commands that deal with the source file, for example, PRINT, POINT, and so on, work as expected using the current include file.
• Stepping "through" an include file is allowed.
• Setting breakpoints within an include is not allowed. The setting of a breakpoint unambiguously refers to the original containing source file.
• Stepping "over" an include file, for example, when the next statement is a %INCLUDE directive, is not explicitly allowed. This may be accomplished by setting a breakpoint in the containing source file, followed by the CONTINUE command.
• Stepping "out of" an include file before its last statement is accomplished similarly to stepping "over," that is, by setting a breakpoint in the containing source file followed by the CONTINUE command.

Using the macro preprocessor mfpp with CodeWatch is also allowed. CodeWatch will use the original source file (rather than the expanded preprocessed output of mfpp). Stepping "through" macros works similarly to the include file support described above.