Re: [ EXTERNAL ] HTTPAPI and truncation issues with move to TR9

Looking through Scott's FTPAPI Forum I think I may have found the problem. We are backlevel on our HttpAPI version, surprise surprise, and he noted some changes coming out of V7R4 that were then pushed back to V7R3. Going to get up to latest level of his software and see if that addresses the problem.

ken

----- Original Message -----
From: "Ken Meade" <kmeade@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Friday, April 9, 2021 4:52:06 AM
Subject: Re: [ EXTERNAL ] HTTPAPI and truncation issues with move to TR9

Seems that we had thought that our truncation issues were limited to those with record lengths of 1317 bytes, but we've found that we have records greater than that length that are also suffering from the truncation problem. So nothing magical about the 1317 number, just happened to be a common size.

Ken

----- Original Message -----
From: "Ken Meade" <kmeade@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 8, 2021 11:27:54 AM
Subject: [ EXTERNAL ] HTTPAPI and truncation issues with move to TR9

All,

Running on V7R3 and had been at TR3. Over the weekend we finally got permission to take down our system and brought it up to TR9.

We've had a few 'opportunities' coming out of this, but the most perplexing, and causing us the most pain is a call to our cloud base sales tax system. We are using Scott Klement's HttpAPI tool for these calls. But since the upgrade to TR9 we've been having intermittent issues with the calls returning blanks, which we attribute to a failed call, or truncating the XML (the common theme appears to be a 1317 byte length on the truncation).

We've been down any number of paths with this from working with our cloud provider, as we first thought the issue was related to their end. Found out that traceroute is not always our friend. To working with our network providers and of course trying to find anything in the different TRs that may lead us down the correct path to address this. And even looking at rewriting our code and not using HttpAPI, but that lead to other problems.

We also found that we had issues with our ZEND server and configurations being overwritten, totally separate issue, but just another piece of info.

Thanks for any input.
Ken Meade