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

Abierto
  • ¿Algo no está bien?
#7,065 50 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
databases, testing-qa
Área
infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.