Epic: batch utility runtime — DFSORT/SYNCSORT, IDCAMS, IEBGENER, IKJEFT01, GDGs

Aperta
  • Qualcosa non va?
#4,890 1 commento 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
backend, databases

Direzione di ricerca

Start with the research basis in the orchestrator handoffs (research-2026-10-11-*) and measure how often the utility classes appear and in which constructs, as specified for the first child issue. The immediate deliverable is that reach measurement; the epic then calls for a design note and implementation slices, with IBM documented behaviour as the reference.

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: batch jobs depend on IBM utilities and dataset services that GitGalaxy does not model: DFSORT / SYNCSORT control cards (SORT FIELDS, INCLUDE/OMIT, INREC/OUTREC, SUM, ICETOOL), IDCAMS (DEFINE / REPRO / DELETE), IEBGENER / IEBCOPY, IKJEFT01 (TSO batch running Db2 programs), and GDGs (relative generations (0)/(+1), rolling). Today these steps are refused by name (register F4). In batch estates the sort cards often carry business rules (filters, sums, reformatting), so a translated COBOL program is not a migrated job without them.

Wanted: a utility runtime: each utility a deterministic Java implementation of its documented control-statement language, proven against the real utility's documented behaviour (and, where available, z/OS runs, #4050); GDG resolution as a dataset service.

Related: #4268 (SORT / JCL utility steps, open question), #4508 (JCL harness), #4514 (whole-migration).

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.