Originally posted by: jvanboga
Granted I'm not the expert here but from my limited experience the stored procedure would return a piece of data with an error code. Of course that may depend on the procedure being called.
That said, typically, though not always, DB adapter return codes are -1001 thru -1109. We'd really need to see more of the tace file to determine what's really going on here.
I suggest running the executed map pointing to the defined MDQ file instead of using the cmd line. That will help identify if there is a problem with the connnection or the cmd line. I'd also confirm that when the type tree was defined there was a key identified. If a key has been defined and the map fails the same way then it could be a data format issue.
Finally, it looks like a procedure is being called to perform a DB insert. Here we write to the tables directly using one of two methods. Let the map write to the table (no proc) or write the output to a file and call an SQL Loader script. We only use the later when writing larger files to tables. We have had little luck executing procedures as output cards. They are more often called as input. And then the dynamically defined type tree needs to be adjusted because the data is not returned in the expected format.
#IBM-Websphere-Transformation-Extender#DataExchange#IBMSterlingTransformationExtender