Why is it important to exclude unit test harness programs from an ADDI discovery scan?

Think of it like working hands-on with IBM mainframe systems — the answer here is 'ADDI fails with a parse error if test programs contain non-standard COBOL PERFORM syntax'. Test harness programs call production programs artificially, so including them creates false call graph edges that distort service boundary analysis and impact analysis results. On real mainframe exams, this concept comes up repeatedly so make sure you have it locked in.