Skip to content

Equivalence harness gaps that block the L1->L4 ladder: abend injection, SEND/RECEIVE/RETURN/SYNCPOINT/DELAY faults, CEEDAYS, X6 WRITEQ #6271

Closed

Description

@squid-protocol

Why

The L1->L4 ladder (#6072) keeps ending at the same equivalence-harness limits rather than at missing scenarios: about 8 of the 33 ladder worker runs on 2026-10-22/23 stopped on one of the gaps below, and each run rediscovered it. Until the harness can inject or model these, the branches behind them can only be stated infeasible (when truly unreachable) or stay open.

Gaps (one checkbox = one slice; each cites the runs that hit it)

Acceptance

Each slice: the harness states the fault/model (oracle_assumptions entry where IBM documents the behaviour, refused by name where it does not), a test, and the #6072 programs it unblocks re-measured with before/after coverage in the PR body. Burned estates only; evidence levels, not "proven".

Part of #6072.

Activity

  1. added
    enhancementNew feature, sensor, or structural signature
    testingUnit, integration, and E2E pipeline verification
    legacy-modernizationCOBOL refractor, dead-code extraction, and JCL forging
    priority: highCore feature broken, but workarounds exist
    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 23, 2026
  2. added a commit that references this issue on Oct 23, 2026
  3. squid-protocol commented on Oct 23, 2026

    @squid-protocol
    OwnerAuthor

    Churn run 6271-20261023T1755Z (host melek) ended without a PR. plan-held duplicate of live run 6271-20261023T1748Z (same abend-injection item); not approved, live worker owns it

  4. squid-protocol commented on Oct 23, 2026

    @squid-protocol
    OwnerAuthor

    #6286 merged: a partial slice of [c:b93f4d8b] "Abend injection: no way to make a called program / CICS command ABEND (incl. VSAM RLS abend) so HANDLE ABEND / abend paragraphs run (churn runs 6072-20261023T0128Z, 0354Z, 0448Z)"; left: Db2 (AD2Z) and linked-program/CALL abends, non-file commands (promoter-bot)

  5. squid-protocol commented on Oct 23, 2026

    @squid-protocol
    OwnerAuthor

    Churn run 6271-20261023T1931Z (host melek) ended without a PR. limit hit; gate already relaunched #6271 as 6271-20261023T2046Z

  6. 52 remaining items

  7. squid-protocol commented on Oct 27, 2026

    @squid-protocol
    OwnerAuthor

    #6800 merged: a partial slice of [c:8969c9c8] "Judging past an X6-refused WRITEQ (1701Z)"; left: the X6 judging item is not this slice (its handoff says #6573 closed the gap). (promoter-bot)

  8. squid-protocol commented on Oct 27, 2026

    @squid-protocol
    OwnerAuthor

    #6802 merged: a partial slice of [c:8969c9c8] "Judging past an X6-refused WRITEQ (1701Z)"; left: the judging gap itself was already closed (#6573, #6702); this PR makes the case documentation true and pins it. Left: the lgsetup translator gap and stale prose (below). (promoter-bot)

  9. squid-protocol commented on Oct 27, 2026

    @squid-protocol
    OwnerAuthor

    #6803 merged: a partial slice of [c:8969c9c8] "Judging past an X6-refused WRITEQ (1701Z)"; left: the judging gap itself was closed by #6573; the case notes are fixed by draft #6802; this PR fixes the prose and the judged_to wording #6802 left. Left: lgsetup translator gap (#5252). (promoter-bot)

  10. squid-protocol commented on Oct 27, 2026

    @squid-protocol
    OwnerAuthor

    All six gap slices are merged (#6427, #6696, #6318, #6699, #6806, #6575); acceptance is met. Remaining sibling DetCics.PastFrom refusals have no burned program known to need them; they get filed if the ladder hits one.

  11. squid-protocol commented on Oct 29, 2026

    @squid-protocol
    OwnerAuthor

    Sibling gap from ladder run 6072-20261029T1501Z: the oracle needs a defined model for zero-length and out-of-bounds reference modification (X8). CBSA BNK1CAC (L3) is blocked on it: 4 outcomes (lines 611 true, 637 true/false, 717 true). The same refusal is recorded on the rate-three-places and overdraft-missing scenarios.

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

    claim:melekenhancementNew feature, sensor, or structural signatureera:2Era CICS/MVS-ESA, COBOL II/85: RESP, SQL, DPL (~1988-96) (era_tags.py)legacy-modernizationCOBOL refractor, dead-code extraction, and JCL forgingpriority: highCore feature broken, but workarounds existscope:coreBlocks a burned-estate program's next evidence rung, or the 4th-estate one-shot trialtestingUnit, integration, and E2E pipeline verification

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions