scottklement.com

Could you have it set in a QIBM_RPG_JAVA_PROPERTIES environment variable, maybe?

As far as I can tell from your message, the error is "JVMJ9VM007E Command-line option unrecognised: -Djava.compiler=NONE
Unable to create Java Virtual Machine"

JDBCR4 doesn't set that option. You'll need to figure out what is setting it, and change it so that it's not being set.

I'm not familiar with ss_open_object_group or ss_close. Can you explain what they do? Are they similar to ss_begin_object_group and ss_end_object_group? Perhaps you created your own similar tool?

ss_begin_object_group and ss_end_object_group merely tell Java that your program is done with the ...

I'm very familiar with the difference, Cinzia.

Please understand that not every software package in the world works the same way.

IBM's FTP is *NOT* the same thing as FTPAPI. FTPAPI works differently.

Recently, we brought a high-volume HTTPAPI application to production. We're now in the process of monitoring for errors and performance issues.
We're using cookies and a cookie file to store a session cookie. I noticed, that every API call we do results in an update of the cookie file.


Correct ...

There is no need to change FTPAPI to be in NAMEFMT 1, it is always in NAMEFMT 1. (It doesn't understand NAMEFMT 0)

The 'NAMEFMT' command that you type in the IBM FTP client is not sent to the server (which is what you're trying to do.) Instead, it sees the command and changes the client's behavior ...

Please use code tags.

Please don't ever post "I get an error" unless that is followed by what the error actually says.

What are you expecting to happen when you run 'NAMEFMT 1' without SITE in front of it?

Can you explain what you mean by "change this default behavior... at the system-wide level"? It seems to me that it's already changed at the system-wide level. Can you explain what problems it causes you? I'm not seeing why it would cause problems.

Also, why are you asking this in the HTTPAPI forum ...

Yes, it is compatible.