Debugging lines missing from production COBOL build logs

Question

When investigating a failed COBOL deployment, developers often rely on DEBUGGING lines and the USE FOR DEBUGGING declarative to trace program flow through log output. The goal is to retain this diagnostic capability in the production object module without incurring unnecessary size or performance penalties.

However, the inclusion of DEBUGGING lines depends on the WITH DEBUGGING MODE compiler option, and the exact syntax (column‑7 'D' versus *> DEBUG) and availability of the DEBUG‑ITEM register differ between IBM Enterprise COBOL, Micro Focus, and GnuCOBOL. This creates uncertainty about a portable strategy for keeping debugging code enabled across different compilers.

What compiler flags control the inclusion of DEBUGGING lines for each target platform? How does the USE FOR DEBUGGING declarative behave when the debugging mode is disabled? What are the measurable trade‑offs of leaving DEBUGGING lines in the final executable regarding object size and runtime overhead?

Tasadduq Burney · Answer

The short answerDEBUGGING lines and the USE FOR DEBUGGING declarative are conditionally compiled. If the production build is invoked without the debugging-mode option, the compiler treats every line marked with a D in the indicator area (column 7) as a comment and compiles the USE FOR DEBUGGING declarative as inert. The result is exactly the symptom described: no diagnostic output at runtime, even though the source still contains the debugging code. The fix is to compile with debugging mode enabled — but the flag name is vendor-specific.Compiler flags by platformThe exact option names and defaults vary by release, so treat the following as the well-established conventions and confirm against your compiler's option reference before changing build scripts.CompilerTypical controlNotesIBM Enterprise COBOLTEST / NOTEST governs debug information; the WITH DEBUGGING MODE clause in SOURCE-COMPUTER or the corresponding compile-time mechanism controls debugging linesHistorically, debugging mode was requested in the Environment Division; newer releases fold much of this into TEST. Verify for your version (e.g., 6.x).Micro Focus COBOLDEBUG / NODEBUG directiveControls inclusion of debugging lines and declaratives; check whether your build uses directives files that override the command line.GnuCOBOL-fdebugging-line (compile flag); -debug for runtime tracing supportWithout -fdebugging-line, D-lines are comments. DEBUG-ITEM support and *> DEBUG syntax availability differ by release.Because flag names, the DEBUG-ITEM register, and free-form *> DEBUG syntax are not portable, a cross-compiler strategy needs per-compiler source conventions or a preprocessing step — do not assume one flag works everywhere.Behavior of USE FOR DEBUGGING when debugging mode is offWhen debugging mode is disabled, the declarative section is compiled but never executed — the runtime has no hook to invoke it, and debugging lines it might reference are absent from the object. There is no error and no output; the code is simply dead. This is standard-defined behavior, so the missing logs are a compile-time decision, not a runtime failure.Trade-offs of shipping with debugging enabledObject size: modest increase from retained debugging lines and declarative code. The exact delta is program- and version-dependent — measure, don't assume.Runtime overhead: generally small; the declarative only fires when its referenced items are touched. Non-zero but usually negligible unless the declarative does heavy I/O.Security: the bigger risk. Debug output in production can leak internal flow, data values, and file names. Review policy before enabling this in shipped objects.Verifying the cause in your buildCompile a minimal program with one D-line and a USE FOR DEBUGGING paragraph, once with production flags and once with debugging mode enabled.Compare the compiler listings: the debugging line should appear as generated code only in the enabled build.Compare object sizes and run both, triggering the declarative condition, to confirm output appears only when enabled.# GnuCOBOL example
cobc -x -fdebugging-line myprog.cob   # debugging lines included
cobc -x myprog.cob                  # D-lines treated as commentsFlag names above are version-sensitive and flagged for human review against your specific compiler release.

Debugging lines missing from production COBOL build logs

1 answer

The short answer

Compiler flags by platform

Behavior of USE FOR DEBUGGING when debugging mode is off

Trade-offs of shipping with debugging enabled

Verifying the cause in your build

Your perspective belongs here.

1 question comment

Compiler	Typical control	Notes
IBM Enterprise COBOL	`TEST` / `NOTEST` governs debug information; the `WITH DEBUGGING MODE` clause in `SOURCE-COMPUTER` or the corresponding compile-time mechanism controls debugging lines	Historically, debugging mode was requested in the Environment Division; newer releases fold much of this into `TEST`. Verify for your version (e.g., 6.x).
Micro Focus COBOL	`DEBUG` / `NODEBUG` directive	Controls inclusion of debugging lines and declaratives; check whether your build uses directives files that override the command line.
GnuCOBOL	`-fdebugging-line` (compile flag); `-debug` for runtime tracing support	Without `-fdebugging-line`, `D`-lines are comments. DEBUG-ITEM support and `*> DEBUG` syntax availability differ by release.