det translator: PL/I CICS programs (dsf: 575 era-1 PL/I CICS files untranslatable today)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with gitgalaxy/tools/cobol_to_java/det/, det_survey.py, and cics_census.py; read the existing COBOL translation path and the linked PL/I work (#2502, #3491, #3720, #4509). The issue maps a broad front end, CICS and DLI translation, and census changes, but says work is blocked on an owner decision about burning a PL/I estate and choosing a runner. Done means PL/I programs and translation holes appear in the survey and census, with execution evidence gated on that decision.
由索引模型根据 Issue 内容生成。
描述
Why
The deterministic translator (gitgalaxy/tools/cobol_to_java/det/) takes COBOL only; cics_census.py --pli already flags PL/I programs as untranslatable. Real CICS estates are often PL/I. In dsf (NAV's Det Sentrale Folketrygdsystemet, in production 1967–2018, local non-burned corpus), 1,473 of the source files are PL/I and 575 of them use EXEC CICS. Only its 7 COBOL batch programs reach the det survey, so the 2026-10-22 non-burned survey (#6064) misses almost all of that estate.
Era profile of dsf's 575 PL/I CICS files (grep of era_tags.py's own tells; the tagger is COBOL-only and reports no tell on PL/I):
- Era 1:
HANDLE CONDITION254, DL/I (EXEC DLI/PLITDLI) 111,HANDLE AID67 - Era 2:
RESP(1,SYSID3,EXEC SQL0 - Eras 0, 3 and 4: none (no macro level, MQ, LE callable services, channels/containers or WEB)
- Shape: classic 3270 command-level application:
SEND MAP186,EXEC CICS LINK/XCTL438
What exists already
- Engine reading of PL/I: #2502 (language), #3250/#3720/#3728 (DECLARE record layouts, storage widths, COMMAREA), #3491 (CICS call sites, handlers, UOW parity), #3577 (answer key).
- #3623 (closed): PL/I through the skeleton Java generation pipeline, not the det statement translator.
- #4509 (open, Gap Atlas): equivalence harness for PL/I. Blocked on a runner: no mature free PL/I compiler (Iron Spring PL/I, or z/OS capture via #4050).
Scope
- Det front end for PL/I: procedures and BEGIN blocks; DECLARE (structures,
BASED/pointers,DEFINED,INITIAL,FIXED DEC/FIXED BIN/CHAR VARYING/BIT,UNALIGNED) onto the same storage model COBOL ports use (#3720's layouts); assignments,IF/SELECT/DOloops,CALL, built-ins (SUBSTR,INDEX,LENGTH,UNSPEC,ADDR, …);ON-conditions as named holes until modelled. - EXEC CICS in PL/I onto the existing CICS runtime model (the same commands COBOL ports use), including era-1
HANDLE CONDITION/HANDLE AIDsemantics (the PL/I flavour of #5856-class work) andEXEC DLI/PLITDLI. - Survey and census:
det_survey.pyandcics_census.pycount PL/I programs as translatable, with holes by reason, so non-burned PL/I estates show up in #6064's numbers.
Evidence constraints (read first)
- No burned estate has any PL/I (0
.pli/.pl1files in all 6). Under the burned-only rule there is no estate to build cases or proofs on. This work is translation-level only (L1 at best) until a burned PL/I estate exists or the owner burns one. - No oracle: PL/I execution needs #4509's runner decision (Iron Spring or z/OS via #4050). Without it nothing reaches L2. Don't fake a runner.
- Owner decision needed before launch: whether to burn a PL/I CICS estate (dsf is the obvious candidate) and which runner #4509 uses. Until then this is frontier: mapped, not built.
Related: #4509, #4515, #4050, #6064, #6065, #5865.
- 主要语言
- Python
- 星标
- 57
- 派生
- 11
- 平均合并
- 1 小时 55 分钟
- 30 天内合并 PR
- 973
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
squid-protocol/gitgalaxy 的其他 Issue
-
bug priority: high scope:core
难度 2/5 1-3 小时 新手友好度 83/100
squid-protocol/gitgalaxy#8223 ·
维护者通常 1 天内回复
-
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 天内回复
查看 squid-protocol/gitgalaxy 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
django-cms/djangocms-frontend#413 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
NanmiCoder/MediaCrawler#1004 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
facebookresearch/xformers#1417 ·
-
question
难度 1/5 1 小时以内 新手友好度 68/100
vllm-project/vime#524 ·
维护者通常 7 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
FinanceFlash/unvibecode#675 ·
维护者通常 1 天内回复