Skip to content

COBOL: unnamed elementary item (2 PIC X(31) ..., implicit FILLER) is read as a field named PIC #4246

Closed

Description

@squid-protocol

Problem

DBB MortgageApplication zBuilder/MortgageApplication/cobol/epscsmrd.cbl @ ce2c1be58eb049e000c6627bd8273263fef0c606 (4,052 lines, 13 PROGRAM-IDs), lines 24, 27, 30: 2 PIC X(40) USAGE DISPLAY VALUE '...'. A data description with no name is an implicit FILLER. Both the engine (record_data: item_name='PIC', level 2, line 24, pic empty) and the key (_data_items: name='PIC', pic=None, usage='DISPLAY') read the keyword PIC as the item name, so the item has no PIC and a wrong name.

Evidence

Reproduced on origin/main with both readers. The key's place() skips FILLER by name, so a mis-read name also changes layout offsets.

Acceptance criteria

  • An entry whose first token after the level number is a clause keyword (PIC/PICTURE/USAGE/VALUE/OCCURS/COMP...) is named FILLER, with its pic/usage captured
  • Same fix in engine and key (independently implemented)
  • Fixtures with and without a name

Out of scope

First-program-only reading (separate issue).

Found during: PR #4226

🤖 Generated with Claude Code

Activity

  1. added
    bugUnintended behavior or logic failure in the engine
    data-integrityIssues relating to RAM state or SQLite database fidelity
    core-engineModifications to the central physics and parsing engine
    on Oct 3, 2026
  2. added a commit that references this issue on Oct 5, 2026
  3. added
    scope:coreBlocks a burned-estate program's next evidence rung, or the 4th-estate one-shot trial
    era:2Era CICS/MVS-ESA, COBOL II/85: RESP, SQL, DPL (~1988-96) (era_tags.py)
    on Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUnintended behavior or logic failure in the enginecore-engineModifications to the central physics and parsing enginedata-integrityIssues relating to RAM state or SQLite database fidelityera:2Era CICS/MVS-ESA, COBOL II/85: RESP, SQL, DPL (~1988-96) (era_tags.py)priority: mediumscope:coreBlocks a burned-estate program's next evidence rung, or the 4th-estate one-shot trial

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions