MDECK

The MDECK compiler option specifies that a copy of the updated input source after library processing (that is, the result of COPY, BASIS, REPLACE, and EXEC SQL INCLUDE statements) is written to a file.

The MDECK output is written in the current directory to a file that has the same name as the COBOL source file and a suffix of .dek.

Read syntax diagramSkip visual syntax diagram
MDECK option syntax

   .-NOMDECK---------------------.   
>>-+-----------------------------+-----------------------------><
   '-MDECK-+-------------------+-'   
           |   .-COMPILE---.   |     
           '-(-+-NOCOMPILE-+-)-'     

Default is: NOMDECK

Abbreviations are: NOMD|MD|MD(C|NOC)

Option specification:

You cannot specify the MDECK option in a PROCESS (or CBL) statement. You can specify it only in one of the following ways:

Suboptions:

If you specify MDECK with no suboption, MDECK(COMPILE) is implied.

Contents of the MDECK output file:

If you use the MDECK option with programs that contain EXEC CICS or EXEC SQL statements, these EXEC statements are included in the MDECK output as is. However, if you compile using the SQL option, EXEC SQL INCLUDE statements are expanded in the MDECK output.

CBL, PROCESS, *CONTROL, and *CBL card images are passed to the MDECK output file in the proper locations.

For a batch compilation (multiple COBOL source programs in a single input file), a single MDECK output file that contains the complete expanded source is created.

Any SEQUENCE compiler-option processing is reflected in the MDECK file.

COPY statements are included in the MDECK file as comments.