Epic: IBM MQ runtime — MQI calls (MQOPEN/GET/PUT/CLOSE…) and MQ structures

Aperta
  • Qualcosa non va?
#4,892 1 commento 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
distributed-systems

Direzione di ricerca

Start with the saved orchestrator handoffs named research-2026-10-11-* and the related issues #4514 and #4724. The issue says the first child task is to measure how often the MQ class appears and in which constructs; begin with that reach measurement before the design note or implementation slices. Done means the measurement is recorded, not that this broad runtime epic is complete.

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

Descrizione

enhancement epic era:3 legacy-modernization needs:crucible needs:docker priority: high scope:frontier tier:era-core

Gap: IBM MQ has no runtime: MQOPEN / MQGET / MQPUT / MQPUT1 / MQCLOSE / MQINQ / MQSET and the MQ structures (MQMD, MQOD, MQGMO, MQPMO) are not modelled, so programs that make MQI calls cannot be translated whole or proven. Owner decision (2026-10-11): the MQ copybooks stay refused until this runtime exists (a stand-in alone would count programs whole while their calls hit empty stubs). Burned reach today: 3 CardDemo programs (COACCT01, CODATE01, COPAUA0C).

Wanted: an MQ runtime: queue manager state as stated facts (queues, their messages, attributes), MQI semantics from IBM's MQ reference (completion / reason codes, syncpoint with CICS / batch units of work, browse vs destructive get, triggering where needed), both sides of the equivalence harness agreeing; the MQ copybook stand-ins come with it.

Related: #4514 item 3 (interfaces), #4724 (scanner: MQ as an unmodelled API).

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

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

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.