Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

z/OS calibration oracle: run the probe corpus and HFP captures on real Enterprise COBOL (blocked: access + legal Q16)

オープン
  • 何か問題がありますか？
#6,492 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

この issue はまだ評価されていません。

説明

claim:nyx enhancement legacy-modernization scope:core status: blocked testing

Split from #4702 (Part 2), owner decision 2026-10-24: #4702 closes on Part 1 and this issue holds the z/OS calibration work, which stays blocked on access and legal.

Policy (from #4702): IBM is the reference; GnuCOBOL (cobc 3.1.2 -std=ibm) is the instrument. A real z/OS (Enterprise COBOL) is a calibration oracle: run the probe and fuzz corpus there occasionally to replace "IBM side ASSUMED" with measured results. It is not in CI.

Already on main

  • Probe corpus: docs/language_status/zos_probes.json with tests/tools/zos_probes.py (oracle mode measures oracle_expected on the pinned cobc image) and tests/tools/test_zos_probes.py (every DIFFERS register entry is probed or sorted out). #6244 added C7, C9, C10, C16, C17, D1.
  • HFP capture kit for COMP-1/COMP-2 (#4271): tests/tools/hfp_capture_kit.py, programs HFPCAP / HFPCAPA, captures table tests/cobol_mainframe/zos_captures/hfp.json (ibm-publication records only so far). Captured-output oracle design: #4050.

Owner decisions needed (blockers)

  • Access: IBM Wazi as a Service (z/OS dev/test on IBM Cloud), ZD&T (licensed dev/test emulation), IBM Z Xplore (free; its terms likely don't cover commercial validation), or a customer's or partner's mainframe. z/OS on Hercules is not an option (licence ties z/OS to IBM hardware).
  • Legal (counsel, Q16): do the licence terms allow using outputs to validate a commercial translator, and may the results be published?

Work once unblocked

  • Run the batch probe corpus on Enterprise COBOL under the estate compile options; record results with a zos-run provenance (never fabricate or loosen one; ibm-publication records are not z/OS evidence).
  • Run HFPCAP / HFPCAPA and hfp_capture_kit.py ingest the SYSOUT; then finish #4271 [c:ff93cc35] per its handoff (settle ASSUMED HFP rules, re-check EPSMPMT **, update register C6).
  • Add a "z/OS-calibrated" marker per register entry and in the evidence report; any oracle-vs-z/OS disagreement becomes a register finding.
  • CICS calibration probes (need a real CICS region; not in zos_probes.json yet): X39 XCTL of a LINK-caller-owned COMMAREA — copy vs same storage (IBM XCTL page is silent; stays REFUSED until measured). From #5060.

Done when: the probe corpus has recorded z/OS results and each register entry shows its calibration status, or the owner descopes it.

Related: #4702 (policy, Part 1 done), #4271, #4050, epic #4055.

🤖 Generated with Claude Code

主要言語
Python
スター
57
フォーク
11
平均マージ
1時間 5分
マージ済み PR（30日）
976

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

squid-protocol/gitgalaxy のほかの issue

squid-protocol/gitgalaxy の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。