Epic: JCL execution — step flow, COND/IF return codes, DD binding, restart/checkpoint

Abierto
  • ¿Algo no está bien?
#4,891 3 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend

Línea de trabajo

Start with related issue #4508 and the saved orchestrator handoffs named research-2026-10-11-*; the issue gives no source files or tests to begin with. The first child issue should measure how often the relevant JCL classes appear and in which constructs. This epic is done only when the design and implementation slices address step flow, condition codes, DD binding, and explicitly state or refuse restart/checkpoint behavior.

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

Descripción

enhancement epic legacy-modernization needs:crucible needs:docker priority: high scope:frontier

Gap: JCL is scanned (job / step flow, DD names, resolved DSNs are mainframe fact channels) but never executed. A migrated batch job needs: step sequencing, COND= / IF-THEN-ELSE on return codes, PARM passing, DD-to-file binding (incl. concatenations, temporary datasets, SYSOUT), restart from a step, and checkpoint/restart semantics.

Wanted: a JCL execution model that runs the translated programs and the utility runtime (sibling epic) as one job, with condition-code logic proven against IBM's JCL reference; restart/checkpoint behaviour stated or refused by name.

Related: #4508 (JCL harness), #4514 parts 1/4 (data, batch), the batch-utilities epic.

Research basis: 2026-10-11 gap research (runtime inventory, language coverage, issue landscape), saved in the orchestrator handoffs (research-2026-10-11-*). Measure-first: the first child issue of this epic is a reach measurement (how often the class appears and in which constructs), then a design note, then slices that each make programs translate or prove. IBM is the reference, GnuCOBOL / our models the instrument; what IBM leaves open is ASSUMED or REFUSED by name (register).

🤖 Generated with Claude Code

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.