scottklement.com

If the server locks up when it receives a command it doesn't understand, that's a bug in the server, not a bug in FTPAPI.

The best way to use a variable for the library in SQL is to create an alias in QTEMP that points to the correct library, and then run the SQL statement against the alias.

What version of IBM i are you running? Are you up to date on PTFs?

The error you cite doesn't normally have to do with CA certificates being installed... more likely, the site is using a newer version of TLS (aka SSL) than your IBM i version supports.

But that's only one of many possible problems ...

FTPAPI automatically attempts to downgrade from EPSV to PASV if the server doesn't understand EPSV.

Are you running into problems? if so, can you describe them?

HTTPAPI doesn't actually know how to process JSON. (you may be confusing it with YAJL?)

When it reads a response from an HTTP server and saves the result to disk, it only loads 32k into memory at once, then writes it and reads the next ...

The FTP_EXTSTS expects parameters the same as (or at least compatible with) this:


D StatusProc PR
D peBytes 16P 0 value
D peTotBytes 16P 0 value
D peExtra * value


You are passing %paddr(Logger), and logger's parameters aren't compatible, so you will be guaranteed to get pointer errors.

we need to see your code to fully understand what you are describing.

HTTPAPI is compatible with V7R1 and newer, so yes. The current version is 1.52, and I do recommend updating to this when you are able to.

MaxReceivedMessageSize is typically a feature of Microsoft web services.

As such, your question doesn't make a lot of sense.

I don't really understand the question, sorry.