All, a warning.
As of this writing, I have been unable to get FC4W1 to work. Ultimately, I reverted to FC3, where everything works fine.The good news here is that this is apparently part of an effort by IBM to phase out the kludgy GSKit and switch to using OpenSSL like the rest of modern civilization. However, they shouldn't have broken stuff that already worked in the process, and some heads up would have been nice. Even the tech support agent hadn't heard about any of these changes until he went digging.As of right now, it looks to me as if FC4W1 has been pulled from Passport Advantage, although that could just be IBM's usual MO of making things extremely difficult to find on Passport Advantage. ;)Two final notes:
1. A 14.10.FC4W1 engine seems to recognize client.kdb/client.sth without issue, so whatever the problem is here, it seems to be unique to the SDK (and possibly even the Windows SDK)2. I've done a bunch of testing with JDBC 4.50.FC4W1 and that seems to work just fine in my limited testing.
That resolves the dll problem, which I was already able to work around on my own; it does NOT resolve the SSL keystore/stash problem, which is the much larger issue.
Shesh:But the old GSKit way should still work, and does not. IBM/HCL don't really want to force clients to do a massive redeploy of SSL as part of a minor CSDK revision, do they?
I fully support a transition to OpenSSL support, but that transition should break existing configurations.