Originally posted by: SystemAdmin
I was suggesting that perhaps you can have a map that only executes when a file exists and the time is right. You can set both conditions in the Integration Flow Designer by defining a Time & a Source Event. You then set Time Event-->Event Coordination to All or None. The map doesn't execute until both requirements are fulfilled.
It sounds like you need to decouple your initial process from the subsequent one. The question is "How?"
You usually never want a map to ever access a file that is created by a continuous or even frequently executed map. This might be affected by having the first process create multiple, uniquely named files and a secondary process creates a list of available files. The next process in the flow processes the list of files. Meanwhile the initial process can proceed independently.
One technique that may be useful is an intermediary map that has map rules of the type"
Rule 1: GET("SomeFile")
Rule 2: IF(LASTERRORCODE() = 0),
RUN("SomeMap.mmc") )
This means SomeMap.mmc won't execute unless SomeFile exists or any condition or conditions you test for in the previous map rule.
Also, look at the Retries map setting. It can help avoid conflicts. I have used it on both the initial and subsequent map to allow some slop time. Never continuously append to a file that you want another process to pick up. Clashes are are almost guaranteed.
I have some maps that solved a similar problem on my old computer. I'll try and take a look over the weekend.
#DataExchange#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender