Rational Developer for System z
COBOL for Windows, Version 7.5, Programming Guide


MDECK

The MDECK compiler option specifies that output from library processing (that is, expansion of COPY, BASIS, REPLACE, or 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 an extension of .DEK.

MDECK option syntax
Read syntax diagramSkip visual syntax diagram   .-NOMDECK---------------------.  
>>-+-----------------------------+-----------------------------><
   '-MDECK-+-------------------+-'  
           |   .-COMPILE---.   |    
           '-(-+-NOCOMPILE-+-)-'    
 

Default is: NOMDECK

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

Suboptions:

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

Option specification:

You cannot specify MDECK in a PROCESS or CBL statement. You can specify the option only by using:

Contents of the MDECK output file:

When you use the MDECK option with the CICS compiler option (integrated CICS translator) or the SQL compiler option (DB2 coprocessor), in general, EXEC CICS or EXEC SQL statements in the COBOL source program are included in the MDECK output as is. However, EXEC SQL INCLUDE statements are expanded in the MDECK output in the same manner as COPY statements.

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.

related references
Conflicting compiler options
Compiler-directing statements


Terms of use | Feedback

Copyright IBM Corporation 1996, 2008.
This information center is powered by Eclipse technology. (http://www.eclipse.org)