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

Abierto
  • ¿Algo no está bien?
#4,892 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
distributed-systems

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.