Start of change

TEST

TEST affects the amount of debugging information that is produced in object code, which determines the level of debugging support that is available.

Syntax

Read syntax diagramSkip visual syntax diagramTEST=*(NO,NODWARFDWARF,NOSOURCESOURCE,NOSEPARATESEPARATE(NODSNAMEDSNAME)NOEJPDEJPD,NODWARFDWARF,NOSOURCESOURCE,NOSEPARATESEPARATE(NODSNAMEDSNAME))
Note: Start of changeUnlike specifying this option in JCL or CBL/PROCESS, all suboptions are required and must be in the order shown in the syntax diagram.End of change
Default
TEST=(NO,NODWARF,NOSOURCE,NOSEPARATE)
(NO,DWARF,...)

Start of changeIf TEST=(NO,DWARF,...) is in effect, basic DWARF diagnostic information is included in the object program, or the separate debug file if SEPARATE is also in effect. This option enables application failure analysis tools, such as CEEDUMP and IBM® Fault Analyzer. With TEST=(NO,DWARF,...), the debugging information is a subset of the DWARF information that is available with TEST=(DWARF,...). The DWARF diagnostic information that is produced when TEST=(NO,DWARF,...) is in effect cannot be used with IBM z/OS® Debugger. Consider using TEST=(NO,DWARF,...) when use of the debugger is not needed and you want to avoid the performance implications of the TEST option while having improved usability for application failure analysis tools, such as CEEDUMP and IBM Fault Analyzer. End of change

Debugging information generated by the compiler is in the industry-standard DWARF format. For more information about DWARF, see About Common Debug Architecture in the DWARF/ELF Extensions Library Reference.

(NO,NODWARF,...)
If Start of changeTEST=(NO,NODWARF,...)End of change is in effect, DWARF diagnostic information is not included in the object program, nor written to a separate debug file.
Note: Start of changeSOURCE and SEPARATE are not allowed with NODWARF.End of change
(NO,...,SOURCE,...)
If you specify TEST=(NO,...,SOURCE,...), the DWARF debugging information generated by the compiler includes the expanded source code.
Note: SOURCE is not allowed with NODWARF.
(NO,...,NOSOURCE,...)
If you specify TEST=(NO,...,NOSOURCE,...), the generated DWARF debugging information does not include the expanded source code.
Start of change(NO,...,SEPARATE(NODSNAME))End of change
If you specify Start of changeTEST=(NO,...,SEPARATE(NODSNAME))End of change, any generated DWARF debugging information will be stored in an external file and will not cause an increase in the size of the object program. Start of changeThe external file name, which is the name of the SYSDEBUG dataset, used during compilation will not be stored in the object program. The default is SEPARATE(NODSNAME) when SEPARATE is specified with no suboptions.End of change
Note: SEPARATE is not allowed with NODWARF.
Start of change(NO,...,SEPARATE(DSNAME))End of change
If you specify Start of changeTEST=(NO,...,SEPARATE(DSNAME))End of change, any generated DWARF debugging information will be stored in an external file and will not cause an increase in the size of the object program. Start of changeThe external file name, which is the name of the SYSDEBUG dataset, used during compilation will be stored in the object program. This name would be used as the default at run time when DWARF information is required.End of change
Note: SEPARATE is not allowed with NODWARF.
(NO,...,NOSEPARATE)
If you specify TEST=(NO,...,NOSEPARATE), any generated DWARF debugging information will be stored in the object program.
(other than NO)
(EJPD,...)
If you specify TEST=(EJPD,...) and OPT=(1|2):
  • The IBM z/OS Debugger commands GOTO and JUMPTO are enabled.
  • Program optimization will be reduced. Optimization will be done within statements; most optimizations will not cross statement boundaries.
(NOEJPD,...)
If you specify TEST=(NOEJPD,...) and OPT=(1|2):
  • The JUMPTO and GOTO commands are not enabled. However, you can still use JUMPTO and GOTO if you use the SET WARNING OFF IBM z/OS Debugger command. In this scenario, JUMPTO and GOTO will have unpredictable results.
  • The normal amount of program optimization is done.
(...,DWARF,...)
If you specify TEST=(...,DWARF,...), complete DWARF diagnostic information is included in the object program, or a separate debug file, when the SEPARATE suboption is in effect. This option enables the best usability for application failure analysis tools, such as CEEDUMP and IBM Fault Analyzer.
(...,NODWARF,...)
If you specify TEST=(...,NODWARF,...), DWARF diagnostic information is not included in the object program, nor written to a separate debug file.
Note: SOURCE and SEPARATE are not allowed with NODWARF.
(...,SOURCE,...)
If you specify Start of changeTEST=(...,SOURCE,...)End of change, the DWARF debugging information generated by the compiler includes the expanded source code.
(...,NOSOURCE,...)
If you specify Start of changeTEST=(...,NOSOURCE,...)End of change, the generated DWARF debugging information does not include the expanded source code.
Start of change(...,SEPARATE(NODSNAME))End of change
If you specify Start of changeTEST=(...,SEPARATE(NODSNAME))End of change, any generated DWARF debugging information will be stored in an external file and will not cause an increase in the size of the object program. Start of changeThe external file name, which is the name of the SYSDEBUG dataset, used during compilation will not be stored in the object program. The default is SEPARATE(NODSNAME) when SEPARATE is specified with no suboptions.End of change
Start of change(...,SEPARATE(DSNAME))End of change
If you specify Start of changeTEST=(...,SEPARATE(DSNAME))End of change, any generated DWARF debugging information will be stored in an external file and will not cause an increase in the size of the object program. Start of changeThe external file name, which is the name of the SYSDEBUG dataset, used during compilation will be stored in the object program. This name would be used as the default at run time when DWARF information is required.End of change
Notes:
  • SEPARATE is not allowed with NODWARF.
  • Support for debugging DWARF debugging information in the SYSDEBUG data set with the IBM debugger requires any of the tools at the following levels:
    • IBM Debug for z Systems® V14.1 (5655-Q50) (formerly IBM Debug Tool for z/OS) or later
    • IBM Developer for z Systems V14.1 (5724-T07) or later
    • IBM Application Delivery Foundation for z Systems V3.1 (5655-AC6) or later
(...,NOSEPARATE)
If you specify TEST=(...,NOSEPARATE), any generated DWARF debugging information will be stored in the object program.
Note: If you specify the TEST option, you must set the CODEPAGE option to the CCSID that is used for the COBOL source program. In particular, programs that use Japanese characters in DBCS literals or DBCS user-defined words must be compiled with the CODEPAGE option set to a Japanese codepage CCSID. For more information, see CODEPAGE.
End of change