Originally posted by: SystemAdmin
There are lots of ways to do this, any number of which would take up more discussion than is allowed on this thread, but to answer your question, in your settings turn the audit logs "On" this allows an audit trail, the return codes of anything not equal to "0" Zero is an error..
Then in your mapping rules, insert function, "Valid" By putting a Return the result of the first argument if it is valid, otherwise, returns the second argument.
Syntax
VALID ( single-text-expression , single-general-expression )
Meaning
VALID ( function_that_can_fail , return_value_if_arg1_invalid )
Returns ( a single-character-text-expression )
Returns NONE, aborts the map and returns its argument as the map completion error message.
Syntax
FAIL ( single-text-expression )
Meaning
FAIL ( message_to_return )
Returns ( NONE )
You can get creative with this, if the data is "Valid", then "Put" the data into a "File" and specify a path, or "Email" to specific person or distribution list, (very helpful in real time testing)
In the "FAIL", is where you can specify a message that will be put in the audit log, and have the audit log emailed to you using a separate map that only reads return codes not equal to zero.. This technique can be utilized in both functional and runtime maps.
Like I said there are lots of ways to handle errors, you should go through the "Help" and also try for yourself some of the different "Rules/insert functions" to get a good flavor of what is most comfortable to you.
Hope this helps
-Steve Brock
#DataExchange#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender