Open World level estates: build each region's estate-crucible before its support (Batch Badlands first)

Open
  • Is something wrong?
#7,065 50 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
databases, testing-qa
Domain
infrastructure

Research direction

Start by reading .claude/rules/mainframe-evidence-policy.md and the #4317 layout in squid-protocol/estate-crucible. Build Batch Badlands first per #4891/#4890, citing IBM manuals and writing an answer key. Run a blind first-time scan/translate, record numbers in the level README. Done when all four levels exist with keys and recorded runs.

Written by the indexing model from the issue text.

Description

enhancement era:2 legacy-modernization scope:infra testing

Owner direction 2026-10-29: keep the L1-L4 ladder and add breadth for what typical CICS estates hold. Open World rule 5 (.claude/rules/mainframe-evidence-policy.md, owner 2026-10-11) says: build a region's level estate-crucible before its support lands. Its first run is the first-time number, measured once; afterwards it is development data.

Build the levels in squid-protocol/estate-crucible (the #4317 layout: apps with COBOL, copybooks, JCL, PROCLIB, BMS, CSD, DCLGEN, and a generated answer key). Order them by #5865's prevalence ranking once it lands. Until then, this order:

  • Batch Badlands (#4891 JCL execution + #4890 utilities): multi-step jobs with COND / IF-THEN-ELSE, PARM, DD concatenation, temporary datasets, SYSOUT, restart; DFSORT/ICETOOL cards (INCLUDE/OMIT, INREC/OUTREC, SUM), IDCAMS DEFINE/REPRO/DELETE, IEBGENER, IKJEFT01 running a Db2 program, GDG (0)/(+1).
  • Alternate Index Archipelago (#4894): ESDS, RRDS, AIX + PATH with duplicate keys, RBA/RRN access, their file status codes.
  • Warlords of the Message Seas (#4892): MQI beyond the core calls, batch MQ, MQ structures.
  • The Hierarchy Keep (#4893): DL/I beyond the first slices, PSB/DBD variety, IMS TM / MFS.

For each level:

  • Every planted construct cites the IBM manual it follows, and the answer key states the expected facts and, where a program runs, the expected outputs.
  • It is written blind to the translator's internals: don't read gitgalaxy/tools/cobol_to_java/det/ or the runtime while authoring it.
  • Then the first-time run: scan and translate once, and record the numbers in the level's README with the date and commit. Only after that may that region's support slices start.

Scope: infra (test estate). It builds no translator support itself.

Dominant language
Python
Stars
57
Forks
11
Avg merge
1h 35m
Merged PRs (30d)
975

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from squid-protocol/gitgalaxy

All issues in squid-protocol/gitgalaxy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.