Re: http_post

Hi Jay,

I'm thinking hard, what the problem might be. But I have a question - do you call the procedure also from STRSQL - or from an iACS SQL session? What kind of stored procedure is it? External? Sourced?

Anyway - I have some ideas:

Maybe it's an implicit data conversion (casting) problem. The result of HTTP_POST is a 2G CLOB with CCSID 1208 (UTF-8) - maybe the stored procedure has a problem with that.

Maybe it's an error in the generated C source of the stored procedure (if its a sourced one) - it might be an idea to look into that source - I think you can find it in QTEMP after the CREATE PROCEDURE statement.

The second one is a long shot - but might be worth a try, as I have found 3 defects around SQL in the last 12 months on 7.4 and 7.5 - so it happens.

Are you able to post the source of the SP? Or a shortened example that replicates your "error"?

HTH
Daniel

Am 16.05.2025 um 16:04 schrieb Jay Vaughn <jeffersonvaughn@xxxxxxxxx>:

why would an http_post work fine in an strsql session, but not in a sql
procedure when called?
Both run under same user, providing the exact same url, bdy, hdr?

the sql proc used to work but no longer does?
In debug everything looks perfectly fine with the values in the http_post
in the sql proc...
Just no response back from the provider - but in strsql I get the response
back.

Nothing in the joblog.

tia

Jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.