為何天真的 LLM 包裝器會在 COBOL 遷移中悄然破壞銀行分類帳(COMP-3 與 CICS 同步點)
Why Naive LLM Wrappers Silently Corrupt Banking Ledgers in COBOL Migrations (COMP-3 & CICS Syncpoints)
天真的 LLM 包裝器在 COBOL 遷移中會因忽略二進制資料表示方式及分散式交易語義,悄然破壞銀行分類帳。把 COMP-3 原始資料轉成浮點 JSON,會令批次對帳出現分毫偏差;盲目把 CICS 交易拆成非同步 HTTP 呼叫,則會破壞 VSAM/Db2 工作單位的原子性。
Automated "LLM translates COBOL to Java/Python" demos routinely fail enterprise audit checks. The root causes sit in binary data representation and distributed transaction semantics that prompts gloss over:
1. Signed COMP-3 Packed Decimals & EBCDIC Zones
Two decimal digits share one byte, with the trailing nibble storing 0xC, 0xD, or 0xF sign state. Casting raw mainframe copybooks through naive floating-point JSON introduces penny-drift across batch reconciliation runs.
2. CICS Syncpoint Boundaries & Two-Phase Integrity
Blindly splitting a monolithic CICS transaction into async HTTP calls breaks VSAM/Db2 unit-of-work atomicity unless an explicit Agentic Exit Factory enforces compensating sagas and parity shadow diffs.
Try the Open Workbench
Inspect COMP-3 nibbles and model 4HRA MSU licensing costs directly in your browser:
- Interactive Workbench: https://digbijoylabs.github.io/iron-silicon-bridge/
- Companion Repo: https://github.com/digbijoylabs/iron-silicon-bridge
Full 18-chapter manual ("The Iron-Silicon Bridge" by Jay Thorne): Kindle B0HRP64YPB | Paperback ISBN 979-8-1425-1951-1 (https://digbijoylabs.com/books/the-iron-silicon-bridge/).
來源:DEV Community · dev.to