Rational Developer for System z
Enterprise COBOL for z/OS, Version 4.1, Programming Guide


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.

Table 1. Types of compiler output under z/OS
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 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 Optimized object code if OBJECT in effect Object
RENT Reentrant object code if OBJECT in effect Object
SOURCE Listing of your source program Listing
SQL SQL statements and host variable information for DB2 bind process Database request module (DBRM)
SSRANGE Extra code for checking references within tables In object
TERMINAL Progress and diagnostic messages sent to terminal Terminal
TEST(HOOK) Compiled-in hooks for Debug Tool Extra code in object
TEST(NOSEP) Information tables for Debug Tool and for formatted dumps Object
TEST(SEP) Information tables for Debug Tool and for formatted dumps Separate debug file
VBREF Cross-reference listing of verbs 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 as well as 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.

After compilation, you next 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: link-editing, or binding, your program. (If you used compiler options to suppress object code generation, you must recompile to obtain object code.)

related tasks  
Language Environment Programming Guide (Preparing to link-edit
   and run under Language Environment)


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)