Epic: JCL execution — step flow, COND/IF return codes, DD binding, restart/checkpoint
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- backend
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Python
- 星标
- 57
- 派生
- 11
- 平均合并
- 1 小时 42 分钟
- 30 天内合并 PR
- 966
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
squid-protocol/gitgalaxy 的其他 Issue
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
squid-protocol/gitgalaxy#8002 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 78/100
squid-protocol/gitgalaxy#8000 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 82/100
squid-protocol/gitgalaxy#8001 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 84/100
squid-protocol/gitgalaxy#7998 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 78/100
squid-protocol/gitgalaxy#7999 ·
维护者通常 1 天内回复
查看 squid-protocol/gitgalaxy 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
-
needs-triage tooling
难度 1/5 1 小时以内 新手友好度 90/100
neilsh/stunt-reel#317 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
TandoorRecipes/recipes#4926 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
PyTomography/PyTomography#431 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
igormcsouza/tether#278 ·
维护者通常 1 天内回复