What you see is what you coded
bbalk 1200006543 Visits (1914)
If you use the TEST option and DebugTool, Enterprise PL/I will show you the source as you coded it.
So, for example, if you have code that contains an EXEC SQL statement, you will see in the debugger just that EXEC SQL statement as you coded it and not the many, many statements generated by the preprocessor and visible in the listing. This is a big plus since those generated statements will be largely meaningless to you and would certainly not be ones you should be debugging and fixing.
The same would be true if you were using the CICS or MACRO preprocessors.
However, since this is PL/I, you can have it both ways: if you do want to debug at the level of the generated code,
then you can do so by using the TEST(SEP) and LISTVIEW options.
This can be particularly useful if you are using the MACRO preprocessors to generate complex code. In that case,