When a COBOL copybook defines a hierarchical group item with multiple nested levels, how does wca4z represent it in Java?
Select an answer to reveal the explanation.
Short Explanation
You'll see wca4z mirror the COBOL copybook by generating nested Java classes that match the group item levels. That keeps parent and subordinate fields tied together, so the Java data contract stays faithful to the mainframe layout.
Full Explanation
The wca4z tool mirrors COBOL group nesting with nested Java classes or a class hierarchy, preserving parent/subordinate relationships so the data contract stays faithful. A single immutable record, a Map<String, Object>, or a flat top-level class would flatten or lose the copybook hierarchy.