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

Aperta
  • Qualcosa non va?
#4,891 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 35m
PR unite (30g)
975

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.