468,106 Members | 1,536 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

DB2 V7.1 DRDA environment TCPIP and DIST address space CPU usage high

Hi,any one know ,in DRDA enviroment DB27.1 running in ZOS/E,I find when
apllication program access DB2 through DB2connect ,in mainframe two address
space TCPIP and DIST CPU usage were very high ,and DBM1 or MSTR address are
low,one sample maybe 15%(tcpip),10%(DIST),1%(DBM1),we are 100% DRDA
envirnoment,I don't know is it normally?
Do anyone has experience on this area?Hope can help me,thanks

--
Message posted via http://www.dbmonster.com
Nov 12 '05 #1
1 2576
Tony,
I don't know if I fully understand your question. So forgive me if
this isn't about what you asked.
When I upgraded from DB2 Connect V7 to V8 our DIST cpu went through the
roof. I opened an ETR with IBM. We found that our passwords were
being encrypted and the de-encryption is very expensive. The reason
our passwords were being encrypted was because of what I consider a bug
in the DB2 client.
I had my DB2 clients cataloged with the setting "Use authentication
value in server's DBM Configuration". On my DB2 Connect Server, I had
Authentication set to SERVER. Thus, my clients should be getting the
equivalent of "Server authentication". However, once your DB2 Connect
Server is becomes V8, you must actually set your clients to "Server
authentication (SERVER)", or else you will actually get SERVER-ENCRYPT.

Hope this helps,

Craig Wahlmeier

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

117 posts views Thread by Steevo | last post: by
3 posts views Thread by TulasiKumar | last post: by
8 posts views Thread by joe.weinstein | last post: by
48 posts views Thread by Ark Khasin | last post: by
9 posts views Thread by =?Utf-8?B?U2hhdW5P?= | last post: by
1 post views Thread by Solo | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.