Repository navigation
Engine: CICS TS/TD queue usage as a fact channel (WRITEQ/READQ/DELETEQ) #3353
Description
Gap
Temporary-storage and transient-data queues are a main way CICS programs pass data to each other and to batch jobs. Today they are only counted as signals.
Scope
- Extract
EXEC CICS WRITEQ/READQ/DELETEQ TS|TD QUEUE(...)(also theQNAMEandSYSIDvariants) per program: verb, queue kind, queue name (VALUE-resolved) and the FROM/INTO record. - This gives a queue-mediated producer/consumer relation between programs.
- CSD
DEFINE TDQUEUE(extrapartition queue → DD/dataset) is handled in the CSD resource-definitions issue.
Acceptance
Follow gitgalaxy/core/how_to_add_a_fact_channel.md / the add-fact-channel skill end to end: bounded extractor → *_data table/column (+ restore, cascade) → galaxy_ir.EngineFile accessor → refraction_differential compared datum → drafted answer-key field → audit JSON + LLM brief. Also update the galaxy_ir.py SCOPE comment. Include a real galaxyscope scan on CardDemo/CBSA shapes showing the rows. How the refactoring tool reads these facts is tracked in #3348.
Activity
squid-protocol commentedon Sep 23, 2026
PR: #3375 — one
cics_resource_datachannel covering FILE / MAP / QUEUE / CONTAINER / CHANNEL operations, with the galaxy_ir joins (screen_bindings, queue_flows, container_flows, cics_file_lineage on #3368).Engine: CICS resource operations as one fact channel -- cics_resource…
Engine: CICS resource operations as one fact channel -- cics_resource…