Debugging sections are permitted only in the outermost program; they are not valid in nested programs. Debugging sections are never triggered by procedures contained in nested programs.
When the debugging mode is suppressed by not specifying that option of the SOURCE compiler, any USE FOR DEBUGGING declarative procedures and all debugging lines are inhibited.
Automatic execution of a debugging section is not caused by a statement appearing in a debugging section.
___ Format 3--USE (DEBUGGING Declarative) ______________________________ | | | <__________________ | | >>__USE__ _____ __DEBUGGING__ ____ __ ___procedure-name-1_|_ _______>< | | |_FOR_| |_ON_| |_ALL PROCEDURES_______| | | | |________________________________________________________________________|
Except for the USE FOR DEBUGGING sentence itself, within the debugging procedure there must be no reference to any non-declarative procedures.
Table 53 shows, for each valid option, the points during program execution when the USE FOR DEBUGGING procedures are executed.
Any given procedure-name can appear in only one USE FOR DEBUGGING sentence, and only once in that sentence. All procedures must appear in the outermost program.
Table 53. Execution of Debugging Declaratives | |
USE FOR DEBUGGING Operand |
Upon execution of the following, the USE FOR DEBUGGING procedures are executed immediately |
---|---|
procedure-name-1 |
Before each execution of the named procedure After the execution of an ALTER statement referring to the named procedure |
ALL PROCEDURES |
Before each execution of every nondebugging procedure in the outermost program After the execution of every ALTER statement in the outermost program (except ALTER statements in declarative procedures) |
Adobe, the Adobe logo, Acrobat, the Acrobat logo, and Acrobat Reader are registered trademarks of Adobe Systems incorporated.