SyntheticRunner · Source: IBM Bob commit a3f2c4d1.INTEREST01_ORIGINAL.cob → INTEREST01_MODIFIED.cob.WS-UNUSED-RATE-COPY, WS-SCRATCH-AMT, WS-LEGACY-TERM removed.DATA_TYPE HIGH: COMP-3 added to 6 accumulator fields. PIC clause storage representation changed from display decimal to packed decimal. Truncation behaviour under z/Architecture differs between formats — overflow semantics are not equivalent.
COMP-3 (packed decimal) to 6 amortisation accumulator fields in INTEREST01 and removed 3 unreferenced dead storage fields. The COMP-3 change improves z/Architecture CPU efficiency by ~8.3%, but the PIC storage representation change is flagged as DATA_TYPE HIGH under Refinery's semantic rules — packed decimal and display decimal handle truncation and overflow differently under z/OS Language Environment. A CRO review is required before promotion. The blast radius is 38/100: 3 direct callers (RETAIL-BATCH, CREDIT-CHK, AFFORD-CALC) and 5 copybook siblings share WS-RUNNING-BALANCE.RETAIL-BATCH, CREDIT-CHK, AFFORD-CALCPAYROLL-RPT, MORTGAGE-CALC, LOAN-RPT, CREDIT-RPT, RISK-AGGRETAIL-BATCH
DATA_TYPE HIGH because the packed decimal format changes how z/OS Language Environment handles overflow and truncation — an issue a compiler or diff cannot detect. SR 11-7 §4.1 requires independent validation evidence for any storage representation change in a model used for credit calculations. If your test suite exercises the full range of WS-PRINCIPAL and WS-RUNNING-BALANCE values, a signed CRO approval with that evidence attached satisfies the requirement. I can generate the sign-off block — shall I draft it?