Re: RDi v7.5, signon info, AS400 instance and JDBC connection

You'll have to forgive me a bit, but due to major ice storms in my location
I cannot get to my actual source code.
Heck, I can bearly leave my town.
However, I'll throw this out with the hope that you can figure out if what
i'm suggesting might work.

Recently, it seems that IBM has implemented some PTF's that deal with JDBC
connections.
Previously one could use parameters for *CURRENT user and password to get
the connection.
With the new PTF's, *CURRENT is no longer valid and one must pass null for
user ID and password.

Is it possible that your system has these PTFs, and you must use null
instead of *CURRENT?

I won't be back to my office for a couple days, so I'll check later this
week to see if this suggestion helps.



On Mon, Dec 15, 2008 at 10:09 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:

Frank Knubben wrote:

I have tried to modify the connection code to first retrieve the AS400
object used by the RSE connection and then re-use that on the JDBC
connection code. That seems to then use the userid from the existing
connection alright, but the password is not propagated, so the second
prompt still appears.

I've had no problems using the AS400 object that is retrieved from an
IBMiConnection. Granted, I don't use it for JDBC ... I use it for a program
call, but you should be able to use the object to create a JDBC connection.

Are you passing a 'true' parameter to the getAS400ToolboxObject method?

david

--
IBM i on Power - For when you can't afford to be out of business
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsc-plugin-dev.