000-349 · Question #63
When building a map, the following build error message is displayed: M111 ERROR: LegacyToNew Output: NewOrderRecord:NewSysFile Argument #2 for map F_MakeNewOrderRecord does not match type of input…
The correct answer is B. Modify input card #2 in the functional map and change the Type. Build error M111 signals a type mismatch between a functional map argument and its corresponding input card declaration, and the fix is to correct the type defined on that input card.
Question
When building a map, the following build error message is displayed:
M111 ERROR: LegacyToNew Output: NewOrderRecord:NewSysFile Argument #2 for map F_MakeNewOrderRecord does not match type of input card #2. Which action should be taken to resolve the build error?
Options
- AChange the order of the arguments in the functional map call.
- BModify input card #2 in the functional map and change the Type.
- CMove the functional map call to a different output object.
- DUse a conversion function in the functional map to change the type of input card #2.
How the community answered
(21 responses)- A5% (1)
- B76% (16)
- C5% (1)
- D14% (3)
Why each option
Build error M111 signals a type mismatch between a functional map argument and its corresponding input card declaration, and the fix is to correct the type defined on that input card.
Reordering the arguments in the functional map call only shifts which argument is misaligned and does not correct the declared type on input card #2, so the M111 error would persist or move to another argument.
The M111 error message explicitly identifies input card #2 as the source of the type mismatch with argument #2 in the functional map call; modifying the Type property of input card #2 directly within the functional map definition resolves the incompatibility at the point of declaration, eliminating the compile-time error.
Relocating the functional map call to a different output object does not alter the type definition of input card #2, so the same type mismatch and M111 error would follow the call regardless of placement.
Inserting a conversion function addresses data transformation at runtime but does not change the declared type of input card #2 itself, which is the root cause of the compile-time M111 build error.
Concept tested: Functional map input card type mismatch build error resolution
Topics
Community Discussion
No community discussion yet for this question.