Epic: IBM MQ runtime — MQI calls (MQOPEN/GET/PUT/CLOSE…) and MQ structures
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- distributed-systems
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day