Mainframe (z/OS Connect / MQ) Adapter — Adapter Technical Specification

Canon-derived document

Status: reserved · Class: modernization · Mission: integration · Phase: phase-planning

Canon source: canon/modernization-registry.yaml (propagated by uiao/tools/sync_canon.py).

The YAML frontmatter and this banner are regenerated from canon on every sync. Do not hand-edit. Author new material only below the ## Overview heading.

Scaffold — awaiting authored content

This document is a stub. Replace every _TODO — ..._ block with authored content that is consistent with UIAO canon. Canon invariants (gcc-boundary, ssot-mutation: never, etc.) must never be contradicted.

Overview

TODO — Author an overview of the Mainframe (z/OS Connect / MQ) Adapter adapter’s role in the UIAO governance perimeter. Do not contradict canon. Cross-reference the companion AVS document where relevant.

Scope

Target surfaces / subsystems: cobol-records, mq-messages, cics-transactions

TODO — Expand scope with concrete boundaries: what the adapter reads, what it emits, what it explicitly does not touch.

Controls

NIST SP 800-53 Rev 5 controls this adapter supports: CM-8, AC-2, AU-2

TODO — For each control, state the adapter’s role (primary, supporting, evidence-only). If a control is aspirational, flag as NEW (Proposed) per No-Hallucination Protocol.

Operational profile

Field	Value
Runtime	`python-3.12`
Runtime pin	`TBD`
Runner class	`on-prem-self-hosted`
Tenancy	`per-customer`
Evidence class	`baseline`
Retention	`3` year(s)

Canon invariants

gcc-boundary: gcc-moderate
ssot-mutation: never
certificate-anchored: true
object-identity-only: true

Notes from canon

FIMF Tier 5 adapter. Requires z/OS Connect or MQ bridge infrastructure. Highest-priority legacy migration adapter.

References

UIAO-CANON-003

Generated by uiao/tools/sync_canon.py. See uiao/ARCHITECTURE.md §4 for the cross-repo sync contract. See uiao-docs/_quarto.yml for rendering configuration.