Charge Interface – How can I be doing this better?

I have a need to build a charge interface that has some tricky requirements.  I have a build that works, but I can’t get away from the feeling that there is a much, much better way to do this.

The sending system (McK Horizon Lab) will be sending charges to the engine once a day, without a header or footer – only TCPIP DFT messages.  The receiving PA system (IDX) can only accept the batch of TCPIP messages that have a header (BHS message), followed by the DFTs, and then a footer (BTS) message.  I have no way of telling that the first DFT coming over is the first message of the batch of messages and no way of knowing that the last DFT is the last DFT of the batch of messages.

The current build I have is lengthy:  

Thread 1 – TCPIP for DFTs from sending system

Thread 2 – Writes to file (with xlate)

Thread 3 – Reads file with inbound TPS that creates a different file that has BHS, DFTs, and BTS

Thread 4 – Reads output file from Thread 3 and send to Thread 5

Thread 5 – TCPIP out to receiving system

I’ve read a post that mentioned making the thread to the receiving system with a protocol of upoc, I don’t believe that will work for me because there are four other threads sending to that receiving system.

Any thoughts?