000-349 · Question #33
A map fails with the following error message: INPUT 1 exists, but its type is in error. An input content is trace is generated. The following excerpts contain all the lines in the trace file that…
The correct answer is C. Verify the Item Subclass properties for the Price field accurately describe the data. The trace indicates an item-level type validation failure, pointing to a specific field whose subclass properties do not match the actual input data.
Question
A map fails with the following error message: INPUT 1 exists, but its type is in error. An input content is trace is generated. The following excerpts contain all the lines in the trace file that contain the words failed or INVALID Based on the trace results, what is the next logical step to take to determine the exact cause of the map failure?
Options
- AVerify that the Group Subclass properties defined for the File group accurately describe the
- BVerify that the Group Subclass properties defined for the Record group accurately describe the
- CVerify the Item Subclass properties for the Price field accurately describe the data.
- DVerify that the Record component has been defined with component range of (s).
- EVerify that the Type selected for input card #1 is correct.
How the community answered
(29 responses)- A3% (1)
- B7% (2)
- C72% (21)
- D14% (4)
- E3% (1)
Why each option
The trace indicates an item-level type validation failure, pointing to a specific field whose subclass properties do not match the actual input data.
The error is flagged at the item level, not at the File group level, so checking File group Subclass properties would not address the specific INVALID type condition shown in the trace.
The Record group Subclass properties define structural layout, not the field-level data type validation that the trace identifies as the source of failure.
When a map trace reports a type as INVALID at the item level, it means the Item Subclass properties - such as data type, length, or format - do not correctly describe the incoming data for that field. The Price field is specifically implicated by the trace, so verifying its Item Subclass properties is the targeted next step. Correcting a mismatch at the item level resolves the 'type is in error' condition reported for INPUT 1.
Component range settings control repetition counts for a Record component, not the data type or format validation that causes an INVALID type error on a specific field.
The input card type selection determines the overall input format category, but the trace has already isolated the failure to a specific item's type properties rather than a card-level misconfiguration.
Concept tested: Item Subclass property validation in map tracing
Source: https://www.ibm.com/docs/en/b2b-integrator/6.2?topic=maps-map-editor
Topics
Community Discussion
3
Orla P.Apr 22, 2026Saw this one freeze half my row, Price field subclass saved me cold.
Bao N.Apr 20, 2026Record group subclass mismatch is exactly where that INVALID trace points, go with B.
Orla P.Apr 20, 2026Bao, appreciate the thinking, but C is the right call here because record group subclass mismatch triggers that INVALID trace only when the subclass itself is unrecognized by the receiver, which is what C describes, not the scenario in B.