Compiler options and compiler output under z/OS
When the compiler finishes processing your source program, it will have produced one or more outputs, depending on the compiler options that were in effect.
Compiler option | Compiler output | Type of output |
---|---|---|
ADATA |
Information about the program being compiled | Associated-data file |
DLL |
Object module that is enabled for DLL support | Object |
DUMP |
System dump, if compilation ended with abnormal
termination (requires SYSUDUMP , SYSABEND ,
or SYSMDUMP DD statement); should be used rarely |
Listing |
EXPORTALL |
Exported symbols for a DLL | Object |
FLAG |
List of errors that the compiler found in your program | Listing |
LIST |
Listing of object code in machine and assembler language | Listing |
MAP(HEX) or MAP(DEC) |
Map of the data items in your program | Listing |
MDECK |
Expansion of library-processing statements in your program | Library-processing side file |
NUMBER |
User-supplied line numbers shown in listing | Listing |
OBJECT or DECK with COMPILE |
Your object code | Object |
OFFSET |
Map of the relative addresses in your object code | Listing |
OPTIMIZE(1) or OPTIMIZE(2) |
Optimized object code | Object |
RENT |
Reentrant object code | Object |
SOURCE |
Listing of your source program | Listing |
SQL |
SQL statements and host variable information for Db2® bind process | Database request module (DBRM) |
TERMINAL |
Progress and diagnostic messages sent to terminal | Terminal |
|
DWARF format debugging
information in the object module, to enable interactive debugging |
Object |
![]() TEST(NOSEP) ![]() |
![]() ![]() |
![]() ![]() |
![]() TEST(SEP) ![]() |
![]() ![]() |
![]() ![]() |
NOTEST(DWARF) |
Basic DWARF format
diagnostic information, to enable application failure analysis tools |
Object |
VBREF |
Cross-reference listing of statements in your source program | Listing |
XREF |
Sorted cross-reference listing of names of procedures, programs, and data | Listing |
Listing output
from compilation will be in the data set defined by SYSPRINT
;
object output will be in SYSLIN
or SYSPUNCH
.
Progress and diagnostic messages can be directed to the SYSTERM
data
set and included in the SYSPRINT
data set. The database
request module (DBRM) is the data set defined in DBRMLIB
. The separate debug file is the data set
defined in
SYSDEBUG
.
Save the listings you produced during compilation. You can use them during the testing of your work if you need to debug or tune. You might also use the listings for diagnosis and debugging after the application is in production.
After compilation, fix any errors that the compiler found in your program. If no errors were detected, you can go to the next step in the process: binding (link-editing) your program. (If you used compiler options to suppress object code generation, you must recompile to obtain object code.)
Language Environment® Programming Guide (Preparing to link-edit and run)