In a phased migration strategy, why should refactoring be completed…

Question

In a phased migration strategy, why should refactoring be completed before transformation begins?

Accepted Answer

Because completing refactoring first establishes stable service boundaries, reducing rework if boundaries change after Java code is already generated — You want refactoring done before transformation because it locks down stable service boundaries. If those boundaries shift after Java code is already generated, you end up redoing work. On real mainframe exams, this concept comes up repeatedly, so make sure you have it locked in.

Answer

Because the IBM watsonx platform requires COBOL source to be pre-processed by Refactoring Assistant before receiving transformation prompts

Answer

Because wca4z cannot process COBOL programs until they are registered in the IBM Refactoring Assistant catalog

Answer

Because refactoring automatically removes all CICS EXEC commands that would otherwise cause wca4z to fail

In a phased migration strategy, why should refactoring be completed before transformation begins?

Short Explanation

Full Explanation