During our migration to IBM Managed Services, we were told there are 3 batching options available to us. We send XML files which are translated to EDI and the behavior is as follows using Shipment Status (EDI 214) as an example:
Option 1 - time based batching. Here there is a scheduled process so every 5 minutes, all 214's waiting for the partner will be processed into a single ISA and sent out. If 1 of these messages fails, it is kicked to the side - but the rest succeed.
Option 2 - file based batching. Here there is no schedule. If Schneider sends a file with 10 214's of data, the file is processed right away. The output is a single ISA containing all the data. If one of the messages fails, then entire file fails.
Option 3 - no batching. The file Schneider sends with 10 214's of data is processed and 10 files are sent to the partner - each ISA contains a single message. If one of the messages fails, the rest still succeed.
We would like Option 2 to function more like Option 1 such that the 'good' messages still go out in the file but the 'bad' ones fail.