ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #cobol
Goal Develop a COBOL program that reliably converts a DATE‑TZ value from one region to another, accounting for daylight‑saving time (DST) boundaries. Constraints and Uncertainty The ISO/IEC 2022/2023 specifications introduce a DATE‑TZ data type, but the standard explicitly leaves zone rules, DST handling, and leap‑second support to the implementation. IBM En
Goal Establish a repeatable, version-stable rule for how GnuCOBOL resolves COPY statements when both -I command-line flags and the COBCPY environment variable are present in a containerized CI/CD pipeline. Constraints and Uncertainty The GnuCOBOL manual documents both mechanisms but does not define their relative precedence. Empirical testing suggests -I dir
The SEARCH ALL statement in COBOL performs a binary search on an OCCURS table that includes a KEY phrase. The ISO standard requires the table to be in ascending or descending key sequence before the search executes, yet it imposes no obligation on the compiler to verify that precondition at compile time or run time. Unlike arithmetic statements, SEARCH ALL h
While COBOL-2002 provides the EXCEPTION clause for synchronous error handling, the language standard lacks a native mechanism for managing asynchronous timeouts or cancellations. In modern environments where COBOL programs run within multi-threaded containers, graceful cancellation typically relies on mapping OS-level signals like SIGTERM to specific routine
Ensuring Idempotency in Indexed File Writes When implementing retry logic for data persistence in COBOL, preventing duplicate records is critical. In environments using indexed files, developers must decide between two primary patterns to handle potential retries without duplicating writes. One approach utilizes the WRITE statement combined with a manual che
This question addresses the runtime behavior of the COBOL REPLACE statement when its target field overlaps with another field in the same record, within a COBOL-to-Java interoperability context. The COBOL language standard does not define the outcome when REPLACE modifies overlapping fields, resulting in compiler-dependent results. IBM Enterprise COBOL and M
The objective is to determine whether modern COBOL runtimes maintain the original record‑key ordering for sequential‑access files when a program written in COBOL 85 fixed‑format syntax is compiled with a COBOL 2002 free‑format compiler. Constraints include using at least two compiler implementations from different vendors, accounting for alignment options th
COBOL programs often centralize NOTIFY calls in a single paragraph and control emission with a flag variable. The language specification, however, does not define how that flag should be cleared after each batch step, leaving the reset behavior implementation‑specific. Because NOTIFY output can be buffered differently in batch versus interactive runs, an unc
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 o