|
Thanks for your help Scott! SSL wasn’t installed so I reinstalled HTTPAPI and it is working now. I was worried about all the programs that calls HTTPAPI, but I was able to update then and test them with no problem. Thanks, From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]
On Behalf Of Scott Klement
CAUTION: This email originated outside of Terminix-Triad. Matt, Type DSPSRVPGM SRVPGM(your-lib/HTTPAPIR4) Then press F11 to view the character signature. The current export signature will be HTTPAPI001 if it was compiled without SSL, or HTTPAPISSL001 if it was compiled with SSL. If you compiled it without, you will have to recompile HTTPAPI to add SSL support. You can do that by typing CALL INSTALL and answering the prompts such that it will compile support for SSL. You make it sound like this is an arduous process, but really
it only takes 5 minutes. A bigger problem is that it will require any program that currently calls HTTPAPI to be re-bound. Often times this can be done by simply doing UPDPGM (or UPDSRVPGM) on any calling program or service program. Though, recompiling/creating the calling programs
would also work (and would be the first thing to try if the UPDPGM or UPDSRVPGM doesn't work for you.) I wish I could remove the option to compile without SSL. There's ZERO reason to use this option today... 15 years ago, it made sense because special PTFs were needed for V4R5 and older releases to compile with SSL -- but that was FOREVER ago. Problem is,
if I remove the option, anyone who has built it without SSL will have to recreate their programs. Maybe I'll do it anyway -- deal with the pain once, and be done with it. -SK On 5/25/21 8:57 AM, Matt Arnold wrote:
|
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi