Originally posted by: repanzer
There’s so many ways to achieve this, but I would consider the easiest is to have the output of the first map be a file, and the second map has a trigger on that file to kick off when it is created.
But yes, you can have what we call a “control map”, which still kicks off by a trigger, whether a file or message queue.
So a message comes to that map, and that map has “blob” input; it doesn’t validate. In one of the rules, you say;
RUN(“c:\temp\maptorun.mmc”, over ride input adapter commands, over ride output adapter commands , PACKAGE(INPUT)
When running a map using the RUN function, you can override just about all the settings, if not all of them. So one reason to use a control map is if you want to over ride the settings.
For you, you would run the first map, give it an output filename, then RUN the second map and override the input of the second map to the output of the first.
Or you would run the first map and use –OE1 and echo back the output from the run map back into the component rule that ran it. Then ECHOIN that data into input for the second run map.
Still; unless you have some need beyond file in-file out, I would not use a RUN statement. It’s so much easier to point and click the map setting then it is to build the Run statement.
Then again, you may not even need the RUN statement to achieve what you want. Take a look at my response in this thread; if you have 3 output cards, you can use the data you just built as input into subsequent output cards.
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=282917&tstart=0#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender