scottklement.com

Is the entire document there if you look at the IFS file that you're putting it (before sending it)?

http_stmf() has a limit of, I believe, 2 gb. For sure its nothing close to as small as 177,000 -- that's a very small document, actually.

I've not heard of a certificate causing an error like this... It could be a cipher error -- like, a bug in the cryptography is causing things to go awry, so it disconnects. ...but I can't see how it'd be a certificate? The certificate exchange happened at the start, and it was accepted... At any rat...

The "broken pipe" error means that you were disconnected while it was sending or receiving data.

Based on the code you posted, here's an example of using http_stmf(). As you can see, its actually a little simpler than http_post, and I really think it'll work a lot better for you. http_xproc(HTTP_POINT_ADDL_HEADER: %paddr(add_headers)); monitor; http_stmf( 'POST' : claimurl : resultpath : jsonpa...

Instead of sending JSON data to the server, you're sending a path name. You need to send them the data that's in the file rather than just the name of the file! http_post won't do this for you (and I wouldn't recommend using http_post in 2021, anyway... http_post is an old, outdated, way to do thing...

I plan to eventually put it on GitHub. Before doing so, I'd like to change the way its built so that the code is stored in the IFS and you build it with a Makefile... I just haven't had time to do so, I've been very busy... but that's the direction I plan to go.

It sounds like a good idea to me.

Hi Eric, You have 'trackNumber' but the JSON says 'trackingNumber' You have listed 150 'batchClaimResponse' elements (via DIM(150)) however, the JSON only has one. You have listed 300 'claimProcessMsgInfo' elements, but the JSON only has two. Your 'claimProcessMsgInfo' structure is directly inside '...

There's nothing built-in that will parse that timestamp... you'll have to write something of your own.