By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,017 Members | 951 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,017 IT Pros & Developers. It's quick & easy.

connect UDB V8 client to 390 V6 instance

P: n/a
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
Share this Question
Share on Google+
1 Reply


P: n/a
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.