CONNECTION ERRORS

While connecting from ASP via ODBC DSN with Named Pipes to DB2 database 7.2 on Win NT 4 workstation,  we got the following error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[IBM][CLI Driver] SQL0902C A system error (reason code = "-20475") occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005

While connecting with TCP/IP, we got this error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[IBM][CLI Driver] SQL1097N The node name was not found in the node directory. SQLSTATE=42720

Can you suggest solutions to the above 2 errors. I used to work with DB2COMM which is a DB2 environment variable. When I give set command at DOS prompt BIN directory, this is not in the list of name value pairs.

But in registry, we have DB2COMM=NETBIOS,TCPIP,NPIPE. In system environment, we have variable DB2COMM=C:\Program Files\sqllib. It should be DB2HOME instead, isn't it & shall I set DB2COMM here as I found in registry. I checked database manager configuration and database configuration parameters and DB2COMM is not there.

How can we set DB2COMM for server, instance, database, connection & transaction and same is my doubt regarding setting instance.
LVL 17
k_murli_krishnaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

k_murli_krishnaAuthor Commented:
What we have to do to work along with 3 instances i.e. DB2, DB2CTLSV and one more user created. Please look at this 3rd error as well:

SQL1097N The node name was not found in the node directory.
sqlcode: -1097
sqlstate: 42720

I will give more points to all deserving.
0
mglxxxCommented:
Just a hunch: did you check the setting of the DB2INSTANCE environment variable?
If you don't want to fiddle around with the environment variable, another option would be to
catalog the other instances as nodes in the default instance (DB2 on a standard installation).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
k_murli_krishnaAuthor Commented:
mglxxx, this is nice & i will work on it. You did not comment on the 2 errors from ASP via ODBC to DB2 & nothing about DB2COMM. Please look at my other very systematic question with 250 points i.e. CONNECTION PROBLEMS.
0
k_murli_krishnaAuthor Commented:
Are the connection problems due to db2, ODBC or ASP.
0
k_murli_krishnaAuthor Commented:
My problem is solved & I deleted the other question. I cataloged the node with all possible details at client end. Thank you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DB2

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.