scottklement.com

both properties and failedValidations should be arrays of character strings, not arrays of data structures.

I think the example provided by the OP violates the HTTP specs -- but assuming that's truly what the server requires, you can do it with a user-defined auth.

Also verify that 'atoken' is large enough for the entirety of the token. If it is larger than the 15000 characters allowed by http_setAuth, then consider using the xproc technique.

Changing HTTPAPI's timeout won't prevent the server from timing out, it'll only prevent HTTPAPI from timing out. You are using the old http_url_post_xml() routine, which has a parameter for the timeout.. you can just pass that parameter if you want to change HTTPAPI's timeout.) Also, not sure if it'...

I'm not aware of any such limitations. Is it possible that your JSON data is loaded into a 100000 variable before you call DATA-INTO, and that the 100000 isn't large enough?

how can i reproduce the problem?

I could see using an additional header callback to set the 'accept' header. I don't see why you'd use it for the Authorization, though... why wouldn't you just use http_setAuth for that?

You have written an "additional header" callback. Is it possible that you wrote that incorrectly? This is a common reason for a timeout.

the code you provided (http_setoption) is how you change the timeout.

This doesn't affect HTTP_TIMEOUT, which is just a constant.

Please explain why you are asking this. Are you having a problem? What problem are you having?

You cleared QSQPTABL? As you said, it should only have one row and one column, containing the number 1. It shouldn't ever be updated or changed -- that's always what that table contains. Moti's message makes no sense. QSQPTABL *is* a physical file. And I don't see why you'd ever have a copy of it an...