467,199 Members | 981 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

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

connect UDB V8 client to 390 V6 instance

i was able to run client configuration successfully, but
got 805s on real connection. couldn't complete the binds
due to permissions on my userid (they don't like me).

monday should produce someone high enough in the food chain
to run them.

but it occurs to me: can V8 drop down to V6?? so, even
if/when the binds get run, am i still hosed??

thanks,
robert
Nov 12 '05 #1
  • viewed: 1124
Share:
1 Reply
Think that DB2 Connect V8 supports DB2/390 V5 or better, so you should
be ok. But that doesn't mean that there couldn't be maintenance that may
be required, especially on the 390 side. BTW, you'll require either
SYSADMIN or BINDADD authorization.

Larry Edelstein

robert wrote:
i was able to run client configuration successfully, but
got 805s on real connection. couldn't complete the binds
due to permissions on my userid (they don't like me).

monday should produce someone high enough in the food chain
to run them.

but it occurs to me: can V8 drop down to V6?? so, even
if/when the binds get run, am i still hosed??

thanks,
robert


Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Kevin Sage | last post: by
3 posts views Thread by Fabian Knopf | last post: by
4 posts views Thread by traceable1 | last post: by
11 posts views Thread by Mikael Arhelger | last post: by
3 posts views Thread by roxrox_1959@yahoo.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.