Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

MQ for the burned estates: the remaining CardDemo MQ programs (COPAUA0C) and the MQINQ / MQSET they use

Aperta
  • Qualcosa non va?
#5,278 0 commenti 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
8/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Start with the census and blockers output: run cics_census.py and read docs/language_status/blockers/blockers.txt to list the burned-estate programs that still call MQ, such as COPAUA0C, plus their MQINQ and MQSET calls and copybooks. Check whether the CMQGMOV and CMQODV rows are stale after PR #5236, which is the reference for how MQ rules are modeled on both runtimes. Done means each listed program is no longer refused for an MQ reason, has an equivalence case and evidence record, and the rule catalogue entries are added.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

era:3 needs:corpus needs:docker scope:core

Part of #4892 (the MQ runtime epic stays in Open World as frontier work). This issue is only the slice the burned estates need, so it counts toward the burned-estate ladder (scope:core).

Why: the generated blockers report (docs/language_status/blockers/blockers.txt) lists missing copybook CMQGMOV (2 burned programs) and missing copybook CMQODV (1), and each refuses its program whole. PR #5236 (MQ slice 1: MQOPEN / MQGET / MQPUT / MQPUT1 / MQCLOSE, CICS unit of work) proved CardDemo CODATE01 and COACCT01. Its followup left these open: COPAUA0C, plus the MQINQ / MQSET calls the burned programs use.

Do:

  1. List the burned-estate programs that still use MQ, from the census (cics_census.py) and today's blockers run: the program, the MQI calls and the copybooks. Confirm whether the CMQGMOV / CMQODV rows are stale after #5236.
  2. Model exactly those calls and structures on both runtimes, the way #5236 did. Each MQ rule goes in the runtime rule catalogue as ASSUMED or REFUSED by name, with IBM citations. Batch MQ and the MQ calls no burned program uses stay in #4892.
  3. Write equivalence cases for each newly whole program and move it up the evidence ladder.

Acceptance: none of the burned programs in step 1 is refused for an MQ reason; each has an equivalence case and an evidence record; blockers.txt no longer lists an MQ copybook gap for a burned program.

Remaining slices (as of 2026-10-18)

Done so far: 3 merged PRs (#5383, #5300, #5295).

  • EXEC DLI segment commands under CICS (GU, REPL, ISRT, DLET/GN): translator, DetDli, register I5 (det/dli.py, gen.py, program.py, DetDli.java, tests). Check: COPAUA0C's GU/REPL/ISRT holes go away in det_survey, with translation and JDK runtime tests. (1 PR per verb group)
  • Oracle side for EXEC DLI (ggdli.c, equivalence_cics; DIB, PCB by number). Check: the oracle runs a DLI scenario and the logs compare. (1 PR)
  • INITIALIZE ... REPLACING of a table (C17) and the 3x READ KEYLENGTH(LENGTH OF ...) holes in COPAUA0C. Check: COPAUA0C has 0 holes in det_survey. (1 PR each)
  • COPAUA0C equivalence case (DB + MQ scenarios), evidence record, ladder move; depends on the three slices above. Check: evidence.py prove records a level. (1 PR)
  • (verify) No MQ copybook gap row for a burned program in blockers.txt after the next generated run (#5300 says CMQGMOV/CMQODV rows are stale). (0 PR)
    Done when: COPAUA0C is no longer refused for an MQ reason, has an equivalence case and evidence record, and blockers.txt lists no MQ copybook gap for a burned program.
    Owner decision needed: the acceptance is blocked by EXEC DLI under CICS, which belongs to the IMS work (#4893). Keep the DLI slices here, or move them to an IMS issue so #5278 can close on its MQ criterion?
    Out of scope here: MQINQ/MQSET (frontier #4892), batch MQ, COPAUS0C / COPAUS1C / CBPAUP0C (same EXEC DLI mechanism), DBUNLDGS (GSAM PCBs).

Drafted 2026-10-18 by a Sonnet triage pass from this issue, its comments and the bodies of its "Part of" PRs; (verify) items were not checked against main. Tick boxes as slices merge; edit freely.

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 43m
PR unite (30g)
985

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.