@giri-zano Thanks. Great suggestion. So, basically by-pass the “open and read.” The problem with that approach in my specific context is that the system I am talking to is quirky (to put it nicely). I’m trying to work around the http API on the other server and use the existing ftp process on the receiving side. They have two very separate processes and I do not think I can do what you suggested. Or, at least, I cannot wrap my head around how to make it work in this specific context, though I totally get the idea. If I had any control over the environment (or even viable documentation) on the receiving server, I might have a prayer of making that work. Sadly, I don’t have either of those things.
Fortunately, I did just discover one solution to one of the server quirks, so I may be back to being able to post individual records using http post, meaning I may not need to try to replicate the ftp process I have been using.