In Chapter 6, Advanced Batch Scheduling and Management, we modified our original file processing job flow from the traditional fixed-time batch processing mode into event-triggered processing by using Control-M's built-in file watch mechanism. By doing so, generated source files get processed immediately, rather than having to wait for the next batch window and the amount of data to be dealt with is significantly reduced for each processing cycle. As a result, a dedicated batch window is no longer necessary and, from the business point of view, the processed data can get delivered to down flow clients in real-time.
As we are just about to sit back and relax, the IT architect in charge of enterprise integration delivers bad news that moving the processing away from Control-M is being considered for the following reasons:
The current file watch mechanism requires an external system to generate the flag file. This is fine for Control-M but does...