Originally posted by: repanzer
The most common map error (warning in this case), I would say, is;
28 Input type contains errors
or
8 One or more inputs was invalid
but there is;
14 One or more outputs was invalid
But that is does not tell you that if you took the output of a "map successful" and ran it against the output type tree as an input care, it would pass. Having the map fail the way you have it may be what you want.
For some of our processes, rather then put the source event on that map in system, we use a control map. So the data get's dropped, it kicks off the control map, where the input to the control map is a blob of text, so it never fails validation. You then take that data and pass it to the actual data translation map in a RUN statement, setting the output to "ECHO", which will return the output of the RUN map into the field where you ran the map. So in your first output field, you run the map, which places the output in that field. You then take that field (with the data you just mapped) and run it against the "output validation" map, which is just a map with the output type tree as input, to validate the output (as you would like). Then depending on what result of that map is(using LASTERRORCODE looking for a 0, map successul), if it's successful, you PUT your data somewhere, else you fail like you're doing now.
#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender