connect db2 7.1 os/2 warp 3 connect to Win2k

[Development at American Savings]

I'm having some trouble being able to connect to my db2 server (it lives on
an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
2003. Any suggestions?

I have a local user account on the server "readonly", i have created a user
in the database of "readonly" and I can connect through the command line,
but from within visual studio .net 2003 I cannot make a connection. Better
stated: I can make a connection but I cannot create data adapters - I can't
get any data from that connection.

I can see it in my server explorer, I can browse the tables and fields, but
as soon as i try to drag some fields onto my form it asks for my username
and password, which I enter, and then I get the following error:
"ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
supplied is incorrect.
SQLSTATE=08004

ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAt tr
failed."

I'm going crazy - what am i doing wrong?

[Mark Yudkin]

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in
message news:10******** ****@corp.super news.com...

I'm having some trouble being able to connect to my db2 server (it lives on an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
2003. Any suggestions?

AFAIK, this is not a supported combination; in any case, I would not expect
it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later;
DB2's ODBC support is frozen at V2.5,. That at a minumum should be
sufficient to cause your second "error" (server doesn't support ODBC API).

You will need to use an API that is supported by DB2 for OS/2 V7.1, such as
native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2 is
frozen, it may be time to consider transitioning away from OS/2 to a
platform with DB2 V8 support, including support for the client API you wish
to use (see http://www.ibm.com/software/os/warp/strategy/).

I have a local user account on the server "readonly", i have created a user in the database of "readonly" and I can connect through the command line,
but from within visual studio .net 2003 I cannot make a connection. Better stated: I can make a connection but I cannot create data adapters - I can't get any data from that connection.

I can see it in my server explorer, I can browse the tables and fields, but as soon as i try to drag some fields onto my form it asks for my username
and password, which I enter, and then I get the following error:
"ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
supplied is incorrect.
SQLSTATE=08004

ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAt tr
failed."

I'm going crazy - what am i doing wrong?

[Development at American Savings]

Isn't there some second opinion - some way to make it work??? Any types of
workarounds or anything?
"Mark Yudkin" <my************ ***********@nos pam.org> wrote in message
news:c8******** **@ngspool-d02.news.aol.co m...

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in
message news:10******** ****@corp.super news.com...

I'm having some trouble being able to connect to my db2 server (it lives on

an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net
2003. Any suggestions?

AFAIK, this is not a supported combination; in any case, I would not

expect it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later;
DB2's ODBC support is frozen at V2.5,. That at a minumum should be
sufficient to cause your second "error" (server doesn't support ODBC API).

You will need to use an API that is supported by DB2 for OS/2 V7.1, such as native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2 is frozen, it may be time to consider transitioning away from OS/2 to a
platform with DB2 V8 support, including support for the client API you wish to use (see http://www.ibm.com/software/os/warp/strategy/).

I have a local user account on the server "readonly", i have created a

user

in the database of "readonly" and I can connect through the command line, but from within visual studio .net 2003 I cannot make a connection.

Better

stated: I can make a connection but I cannot create data adapters - I

can't

get any data from that connection.

I can see it in my server explorer, I can browse the tables and fields,

but

as soon as i try to drag some fields onto my form it asks for my username and password, which I enter, and then I get the following error:
"ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
supplied is incorrect.
SQLSTATE=08004

ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAt tr
failed."

I'm going crazy - what am i doing wrong?

[Mark Yudkin]

Will the the IBM DD2 documentation serve as confirmation?

"The DB2 .NET Data Provider allows your .NET applications to access Version
8 DB2 Universal Database on Windows, UNIX, and Linux-based computers, and
Version 6 and Version 7 of DB2 Universal Database for OS/390 and z/OS via
DB2 Connect. "

You are using none of these servers

Full details are in the Application Development section of Concept, under
APIs - Windows - DB2 .NET.

The only "workaround " is to use a supported API. This means you cannot use
an API not supported by your DB2 for OS/2 V7 server.

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in
message news:10******** *****@corp.supe rnews.com...

Isn't there some second opinion - some way to make it work??? Any types of workarounds or anything?
"Mark Yudkin" <my************ ***********@nos pam.org> wrote in message
news:c8******** **@ngspool-d02.news.aol.co m...

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in
message news:10******** ****@corp.super news.com...

I'm having some trouble being able to connect to my db2 server (it lives

on

an os/2 warp 3 connect box) from my Windows2000 workstation using

vs.net 2003. Any suggestions?

AFAIK, this is not a supported combination; in any case, I would not

expect

it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later; DB2's ODBC support is frozen at V2.5,. That at a minumum should be
sufficient to cause your second "error" (server doesn't support ODBC API).
You will need to use an API that is supported by DB2 for OS/2 V7.1, such

as

native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2 is

frozen, it may be time to consider transitioning away from OS/2 to a
platform with DB2 V8 support, including support for the client API you

wish

to use (see http://www.ibm.com/software/os/warp/strategy/).

I have a local user account on the server "readonly", i have created a

user

in the database of "readonly" and I can connect through the command

line, but from within visual studio .net 2003 I cannot make a connection.

Better

stated: I can make a connection but I cannot create data adapters - I

can't

get any data from that connection.

I can see it in my server explorer, I can browse the tables and fields, but

as soon as i try to drag some fields onto my form it asks for my username and password, which I enter, and then I get the following error:
"ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
supplied is incorrect.
SQLSTATE=08004

ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's

SQLSetConnectAt tr failed."

I'm going crazy - what am i doing wrong?

[Development at American Savings]

Fair enough. I sure appreciate your help.
"Mark Yudkin" <my************ ***********@nos pam.org> wrote in message
news:c8******** **@ngspool-d02.news.aol.co m...

Will the the IBM DD2 documentation serve as confirmation?

"The DB2 .NET Data Provider allows your .NET applications to access Version 8 DB2 Universal Database on Windows, UNIX, and Linux-based computers, and
Version 6 and Version 7 of DB2 Universal Database for OS/390 and z/OS via
DB2 Connect. "

You are using none of these servers

Full details are in the Application Development section of Concept, under
APIs - Windows - DB2 .NET.

The only "workaround " is to use a supported API. This means you cannot use
an API not supported by your DB2 for OS/2 V7 server.

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in
message news:10******** *****@corp.supe rnews.com...

Isn't there some second opinion - some way to make it work??? Any types

of

workarounds or anything?
"Mark Yudkin" <my************ ***********@nos pam.org> wrote in message
news:c8******** **@ngspool-d02.news.aol.co m...

"Developmen t at American Savings" <de*@americansa vingslife.com> wrote in message news:10******** ****@corp.super news.com...
> I'm having some trouble being able to connect to my db2 server (it lives on
> an os/2 warp 3 connect box) from my Windows2000 workstation using vs.net > 2003. Any suggestions?
AFAIK, this is not a supported combination; in any case, I would not

expect

it to work. To start with, DB2 for OS/2 does not support ODBC V3 or later; DB2's ODBC support is frozen at V2.5,. That at a minumum should be
sufficient to cause your second "error" (server doesn't support ODBC API).
You will need to use an API that is supported by DB2 for OS/2 V7.1, such

as

native CLI. That means, ADO.NET is out. Alternatively, since DB2 for OS/2

is

frozen, it may be time to consider transitioning away from OS/2 to a
platform with DB2 V8 support, including support for the client API you

wish

to use (see http://www.ibm.com/software/os/warp/strategy/).

>
> I have a local user account on the server "readonly", i have created

a user
> in the database of "readonly" and I can connect through the command

line,

> but from within visual studio .net 2003 I cannot make a connection.
Better
> stated: I can make a connection but I cannot create data adapters - I can't
> get any data from that connection.
>
> I can see it in my server explorer, I can browse the tables and

fields, but
> as soon as i try to drag some fields onto my form it asks for my

username

> and password, which I enter, and then I get the following error:
> "ERROR [08004][IBM][CLI Driver]SQL1403N The username and/or password
> supplied is incorrect.
> SQLSTATE=08004
>
> ERROR [IM006][Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAt tr > failed."
>
> I'm going crazy - what am i doing wrong?
>
>