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


- Default
TEST=(NO,NODWARF,NOSOURCE,NOSEPARATE)
- (NO,DWARF,...)
If
TEST=(NO,DWARF,...)
is in effect, basic DWARF diagnostic information is included in the object program, or the separate debug file ifSEPARATE
is also in effect. This option enables application failure analysis tools, such as CEEDUMP and IBM® Fault Analyzer. WithTEST=(NO,DWARF,...)
, the debugging information is a subset of the DWARF information that is available withTEST=(DWARF,...)
. The DWARF diagnostic information that is produced whenTEST=(NO,DWARF,...)
is in effect cannot be used with IBM z/OS® Debugger. Consider usingTEST=(NO,DWARF,...)
when use of the debugger is not needed and you want to avoid the performance implications of theTEST
option while having improved usability for application failure analysis tools, such as CEEDUMP and IBM Fault Analyzer.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
is in effect, DWARF diagnostic information is not included in the object program, nor written to a separate debug file.TEST=(NO,NODWARF,...)
Note:SOURCE
andSEPARATE
are not allowed withNODWARF
. - (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 withNODWARF
. - (NO,...,NOSOURCE,...)
- If you specify
TEST=(NO,...,NOSOURCE,...)
, the generated DWARF debugging information does not include the expanded source code. (NO,...,SEPARATE(NODSNAME))
- If you specify
, 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.TEST=(NO,...,SEPARATE(NODSNAME))
The 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)
whenSEPARATE
is specified with no suboptions.Note:SEPARATE
is not allowed withNODWARF
. (NO,...,SEPARATE(DSNAME))
- If you specify
, 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.TEST=(NO,...,SEPARATE(DSNAME))
The 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.
Note:SEPARATE
is not allowed withNODWARF
. - (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,...)
andOPT=(1|2)
:- The IBM z/OS Debugger commands
GOTO
andJUMPTO
are enabled. - Program optimization will be reduced. Optimization will be done within statements; most optimizations will not cross statement boundaries.
- The IBM z/OS Debugger commands
- (NOEJPD,...)
- If you specify
TEST=(NOEJPD,...)
andOPT=(1|2)
:- The
JUMPTO
andGOTO
commands are not enabled. However, you can still useJUMPTO
andGOTO
if you use theSET WARNING OFF
IBM z/OS Debugger command. In this scenario,JUMPTO
andGOTO
will have unpredictable results. - The normal amount of program optimization is done.
- The
- (...,DWARF,...)
- If you specify
TEST=(...,DWARF,...)
, complete DWARF diagnostic information is included in the object program, or a separate debug file, when theSEPARATE
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
andSEPARATE
are not allowed withNODWARF
. - (...,SOURCE,...)
- If you specify
, the DWARF debugging information generated by the compiler includes the expanded source code.TEST=(...,SOURCE,...)
- (...,NOSOURCE,...)
- If you specify
, the generated DWARF debugging information does not include the expanded source code.TEST=(...,NOSOURCE,...)
(...,SEPARATE(NODSNAME))
- If you specify
, 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.TEST=(...,SEPARATE(NODSNAME))
The 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)
whenSEPARATE
is specified with no suboptions. (...,SEPARATE(DSNAME))
- If you specify
, 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.TEST=(...,SEPARATE(DSNAME))
The 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.
Notes:SEPARATE
is not allowed withNODWARF
.- Support for debugging
DWARF
debugging information in theSYSDEBUG
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 theTEST
option, you must set theCODEPAGE
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 theCODEPAGE
option set to a Japanese codepage CCSID. For more information, see CODEPAGE.
