470,648 Members | 1,571 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,648 developers. It's quick & easy.

Connecting to DB2 from MS Query

I get the following error message when trying to connect to a host
database (OBCD connection) with "MS Query".

SQL0471N Invocation of routine "SYSIBM .SQLTABLES " failed due to
reason "00E7900C".
SQLSTATE=55023

I've found that this is a error with running the stored procedure
SQLTABLES, but I don't understand why?

This only occurs when trying to connect with MS QUERY.

If I try a db2cmd window, there is no problem connecting.
Using another application "AQT - Advanced Query Tool", there is also no
problem doing the connect.

Does anyone have a clue why this error only occurs when launching the
ms query tool ??

Regards Olaf

Nov 13 '06 #1
3 7902
Olaf:

Are you using MS Query by intself, or via Excel? At any rate, MS Query
is running the SP in order to use its result set to populate a drop
down list of tables for you to then choose from.

It appears that you're using DB2 on OS/390--an environment I'm not
familiar with--but perhaps this explanation of the error might lead you
to a solution:

00E7900C
Explanation:
SQL CALL statement or user-defined function invocation could not be
processed. The WLM application environment name specified for the
user-written routine is not defined or is currently not available for
DB2 use in the active WLM policy.

System action:
The SQL statement is rejected with SQLCODE -471 and this reason code.

Programmer response:
Use the -ALTER PROCEDURE or -ALTER FUNCTION command to update the WLM
ENVIRONMENT to specify an application environment that is defined and
active in the active WLM policy, or update the WLM policy to contain a
valid application environment name.

If the WLM policy definition is updated, use the MVS WLM VARY command
to activate this new definition.

If the WLM application environment is quiesced, use the MVS WLM VARY
APPLENV= applenv, RESUME command to activate the application
environment.

-- Jeff

ol*********@hotmail.com wrote:
I get the following error message when trying to connect to a host
database (OBCD connection) with "MS Query".

SQL0471N Invocation of routine "SYSIBM .SQLTABLES " failed due to
reason "00E7900C".
SQLSTATE=55023

I've found that this is a error with running the stored procedure
SQLTABLES, but I don't understand why?

This only occurs when trying to connect with MS QUERY.

If I try a db2cmd window, there is no problem connecting.
Using another application "AQT - Advanced Query Tool", there is also no
problem doing the connect.

Does anyone have a clue why this error only occurs when launching the
ms query tool ??

Regards Olaf
Nov 13 '06 #2
Thanks Jeff,

I am running MS Query by itself, and I am aware of the SP which is run
to show the list of tables. However I find it strange that MS Query is
not able to call this SP, while other querytools (AQT - Advanced Query
Tool) seem to run it just fine. AQT also displays a list of tables, and
I suspect that the same SP is used.

Sad to say, I'm not 'up and running' with knowledge of what WML
environment is. So I need to do a bit more study on that part.

Thanks!! :)

Nov 14 '06 #3
I agree with you--the SP should certainly run consistently across
tools. I hope you're able to resolve the issue!

ol*********@hotmail.com wrote:
Thanks Jeff,

I am running MS Query by itself, and I am aware of the SP which is run
to show the list of tables. However I find it strange that MS Query is
not able to call this SP, while other querytools (AQT - Advanced Query
Tool) seem to run it just fine. AQT also displays a list of tables, and
I suspect that the same SP is used.

Sad to say, I'm not 'up and running' with knowledge of what WML
environment is. So I need to do a bit more study on that part.

Thanks!! :)
Nov 14 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Steve | last post: by
1 post views Thread by David Sorber via AccessMonster.com | last post: by
9 posts views Thread by noor.rahman | last post: by
3 posts views Thread by BigZero | last post: by
reply views Thread by warner | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.