When two COBOL programs access the same DB2 table through different column sets, what risk does ADDI highlight?
Select an answer to reveal the explanation.
Short Explanation
When two COBOL programs hit the same DB2 table through different column sets, you're looking at data coupling. A schema change can ripple through both programs, so you have to manage that blast radius when defining service boundaries. Keep that mainframe reality locked in.
Full Explanation
ADDI reveals shared DB2 table access as data coupling: schema changes can force simultaneous changes in both programs, so manage it during service boundary definition. This is not RACF column-security, DB2 serializing all access, or per-column licensing.