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

Corrupted connections using DB2 Gateway

P: n/a
Hi all...

We are running UDB 6.1 and DB2 Gateway on Windows, to attach to a z/OS
mainframe DB2 database.

Normally everything is fine. However, on recent mornings we get
reports of slowness from our users. When we open UDB control center
on Windows, instead of the normal 3-7 connections open, we'll have 20+
connections open. Where it says client platform and client protocol,
instead of the normal NT and Windows, it'll have a whole bunch of
garbage and gibberish, little squares and shit, like you would see as
output from a bad C program :-) When we kill/force just the
'corrupted' connections, all the other connections clear up on their
own, and the users are happy once again (for now, hahaha)

We have our mainframe systems people looking on the z/OS side, but I'm
wondering if anyone has seen this before. Very strange.

Thanks in advance for any advice. Thanks.
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Jeff wrote:
Hi all...

We are running UDB 6.1 and DB2 Gateway on Windows, to attach to a z/OS
mainframe DB2 database.
Support for V6.1 ended in December 2001.
Support for follow up version - V7.1 ended in December 2002
Support for V7.2 (which is V7.1 with FP3 applied at least - although current
fixpack is FP12) will end on September 30, 2004.
Thanks in advance for any advice. Thanks.


Please migrate to supported version and try again. It is much easier to get
questions answered when using supported version.

Jan M. Nelken
Nov 12 '05 #2

P: n/a
Unfortunately that's not my decision. We can't upgrade UDB until we
get off webSphere 3.5 hahahahaah We are a small shop with no money,
just trying to get by. It's all junk, just give me COBOL and VSAM
files and I'll be happy. Well at least it's not microsoft I guess.

"Jan M. Nelken" <Un**********@Invalid.Domain> wrote in message news:<41********@news1.prserv.net>...
Jeff wrote:
Hi all...

We are running UDB 6.1 and DB2 Gateway on Windows, to attach to a z/OS
mainframe DB2 database.


Support for V6.1 ended in December 2001.
Support for follow up version - V7.1 ended in December 2002
Support for V7.2 (which is V7.1 with FP3 applied at least - although current
fixpack is FP12) will end on September 30, 2004.
Thanks in advance for any advice. Thanks.


Please migrate to supported version and try again. It is much easier to get
questions answered when using supported version.

Jan M. Nelken

Nov 12 '05 #3

P: n/a
Jeff wrote:
Unfortunately that's not my decision. We can't upgrade UDB until we
get off webSphere 3.5 hahahahaah We are a small shop with no money,
just trying to get by. It's all junk, just give me COBOL and VSAM
files and I'll be happy. Well at least it's not microsoft I guess.


If the database resides on z/OS - you would neet DB2 Connect only. I have no
clue about product pricing but DB2 Connect Personal Edition would not be that
expensive, right?

Anyway db2level output and any interesting entries in db2diag.log could be
agood opening point in any social conversation (Remember that this product is
not supported :-). Also - what make you think it is not Websphere hickup?

Jan M. Nelken
Nov 12 '05 #4

P: n/a
Interesting. It appears that the control center is what is messing
up. When I start and stop monitor, the garbage characters come and
go. That's good news.
I changed some settings in webSphere and it seems to help. I
decreased the amount of time an orphaned connection will be held, as
well as reducing the max connections. DB2 seems to be much happier
now. Nothing at all of interest in db2diag.log, wish there was.
OK, the moral of the story is need to stay current on this or any
software to get good support. Thanks for the insight.

"Jan M. Nelken" <Un**********@Invalid.Domain> wrote in message news:<Rc*********************@twister01.bloor.is.n et.cable.rogers.com>...
Jeff wrote:
Unfortunately that's not my decision. We can't upgrade UDB until we
get off webSphere 3.5 hahahahaah We are a small shop with no money,
just trying to get by. It's all junk, just give me COBOL and VSAM
files and I'll be happy. Well at least it's not microsoft I guess.


If the database resides on z/OS - you would neet DB2 Connect only. I have no
clue about product pricing but DB2 Connect Personal Edition would not be that
expensive, right?

Anyway db2level output and any interesting entries in db2diag.log could be
agood opening point in any social conversation (Remember that this product is
not supported :-). Also - what make you think it is not Websphere hickup?

Jan M. Nelken

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.