When two COBOL programs access the same DB2 table through different column sets, what risk does ADDI highlight?

Think of it like working hands-on with IBM mainframe systems — the answer here is 'A licensing compliance risk because DB2 charges are calculated per column accessed'. When ADDI reveals shared DB2 table access, it flags data coupling: any schema change creates a blast radius across all programs that reference the table, which must be managed during service boundary . On real mainframe exams, this concept comes up repeatedly so make sure you have it locked in.