How does wca4z typically handle the COBOL ON SIZE ERROR clause in generated Java?
Select an answer to reveal the explanation.
Short Explanation
wca4z maps the COBOL ON SIZE ERROR clause to a Java ArithmeticException when an arithmetic result exceeds the target field's defined precision. You keep the original error-handling branch semantics instead of silently continuing or ignoring the overflow. On real mainframe exams, this concept comes up repeatedly, so make sure you have it locked in.
Full Explanation
wca4z maps COBOL ON SIZE ERROR handlers to Java ArithmeticException throws when arithmetic exceeds the target field's defined precision, preserving branch semantics. Log-and-continue, ignoring errors, and catching NumberFormatException are wrong; they suppress or misclassify overflow. On mainframe exams, this concept comes up repeatedly.