Is the record‑key ordering preserved in sequential‑access files when COBOL 85 fixed‑format code is compiled with a modern COBOL 2002 free‑format compiler?

Answer

Yes, the logical record‑key ordering is preserved; the key’s position is defined by the file description (FD) and the runtime reads records in the order they were written, regardless of fixed‑format versus free‑format compilation.

Confirmed facts

• The key order is determined by the FD and the sequential read order, not by source format.
• Alignment or RECORD VARYING options can change the physical byte offset of the key but do not alter the sequence of records.
• IBM, Micro Focus and GnuCOBOL each apply default alignment that may differ, but the logical order remains consistent.

Likely explanation

When the compiler parses free‑format code it may reorder working‑storage items or apply padding, which can move the key’s byte position. The logical ordering, however, is unchanged because the file is read sequentially.

Verification steps

1. Create a test sequential file with a defined KEY and write records in a known order.
2. Compile the same COBOL 85 source with a fixed‑format compiler and with a COBOL 2002 free‑format compiler (e.g., IBM Enterprise COBOL and GnuCOBOL).
3. Read the file sequentially and compare the key values; any deviation indicates a physical layout change, not a logical ordering change.
4. Inspect the generated record layout (listing or map) to verify the key’s byte offset under each compiler and alignment setting.

If you are using alignment or RECORD VARYING options, let us know the specific flags so we can assess their impact on key position.