When the same PERFORM paragraph is duplicated across dozens of COBOL programs, what best prepares the portfolio for efficient transformation?
Select an answer to reveal the explanation.
Short Explanation
Extract the common paragraph into a shared COBOL utility program and invoke it via CALL before running wca4z. That way, you transform one reusable unit instead of dozens of copies, keeping the Java output cleaner and easier to maintain.
Full Explanation
Extract the common paragraph into a shared COBOL utility invoked via CALL before wca4z, so one Java utility replaces many duplicates. Commenting out copies removes needed logic and misses the shared target. Leaving copies in place creates separate Java methods. Inline expansion removes abstraction and adds duplication.