Siblings of #4892: MQI calls beyond the CICS slice-1 verbs

Open
#5,259 15 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
security, tooling

Research direction

Start with gitgalaxy/standards/mq.py, where the MQI verbs are refused by rule codes W5, W6, W7 and C17, and read PR #5236 and issue #4892 for the slice-1 design. This is a tracking issue of separate sub-tasks, several needing an oracle answer or a declared difference, so pick one checkbox and confirm scope with a maintainer first. Done means that item's calls are accepted or explicitly refused with a test covering it.

Written by the indexing model from the issue text.

Description

enhancement era:3 legacy-modernization needs:docker priority: high scope:frontier

Siblings of #4892 (class: the IBM MQI called from COBOL, gitgalaxy/standards/mq.py), found in the review of PR #5236 (slice 1: MQOPEN / MQGET / MQPUT / MQPUT1 / MQCLOSE from CICS, CardDemo CODATE01 + COACCT01). Each is refused by name today (register W5 / W6 / W7 / C17).

  • Batch MQ: MQCONN / MQCONNX / MQDISC and any MQI call from a batch program (W6) (#7215)
  • MQ's own unit of work: MQBEGIN / MQCMIT / MQBACK (W5)
  • MQINQ / MQSET (W6)
  • Pub/sub, async, status, message handles: MQSUB / MQSUBRQ, MQCB / MQCTL, MQSTAT, message-handle calls (W6)
  • MQGMO_CONVERT with real data conversion (W7)
  • CardDemo COPAUA0C: MQ part translates (330/344); the rest is EXEC DLI (CICS DL/I interface, epic #4893) plus one C17 statement
  • C17: INITIALIZE REPLACING of a table holding an unnamed category -- needs a GnuCOBOL-independent oracle answer or a declared difference
  • det-sweep branch coverage under-reports MQ-driven EVALUATE / IF paths (codate01 4/26, coacct01 4/31 with paragraphs 13/13): coverage-tool fix

Siblings: #4892, PR #5236

Dominant language
Python
Stars
57
Forks
11
Avg merge
1h 35m
Merged PRs (30d)
975

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from squid-protocol/gitgalaxy

All issues in squid-protocol/gitgalaxy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.