scottklement.com

Thanks for the response, Scott!

We have the same function running on three iSeries boxes and I now have it working as expected on two of the three.

Looking at the logs, I now notice that the server that it is not working correctly on is running a way older version:

Bad Box: HTTPAPI Ver 1.23 ...

Talking to myself again! But the resolution might be useful to others!

It seems that our programs were compiled with DFTACTGRP(*NO), but no specific activation group specified. This seems to cause problems for the https_init, and the http_debug functions, as we saw evidence of the wrong certificate ...

New theory:

Certificate is being picked up just fine!

However, we have up to three calls to different endpoints in the same job stream for the same transaction, depending on the set up of the particular customer.

The failing call is on the middle of these calls.

If the first call is made, the ...

We have whittled this down to being an authority problem - the correct certificate is picked up when the job is called interactively under a developer's profile, but fails when being run in the standard batch job which runs under a "runtime" profile.

Can anyone suggest what authority level is ...

Hi Scott

We have been successfully sending data using and http_url_post for several years, but it has recently stopped working - examining the logs, it seems that it is sending our default certificate rather than the one that is assigned to the application id that we are specifying int he https ...