Epic: batch utility runtime — DFSORT/SYNCSORT, IDCAMS, IEBGENER, IKJEFT01, GDGs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day