DB2 Connect V7.1 stability

Dave Shapiro

DB2 Connect V7.1 stability
Anyone using DB2 Connect v7.1 clients and servers in production, either AIX or NT?

Are you satisfied as to its stability?

Are you using the sysplex option, or connection concentrator?


TIA for the feedback!

Dave



Chad Breiner

DB2 Connect
(in response to Dave Shapiro)
I have a basic question about DB2 connect. My client
is currently using a DB2 connect gateway to get to the
mainframe data. The current direction for my client
is to install DB2 on all PC's. Are there any
advantages of going thru a db2 connect gateway rather
than directly to the database?

Thanks

Chad Breiner
DB2 Database Administrator
CBI Consulting

__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/



Myron Miller

Re: DB2 Connect
(in response to Chad Breiner)
Each has its pros and cons. It really depends. I
won't attempt to give all of the pro's and con's but
some major that I know about:

Gateway:
Advantages
1) Common interface - don't have to install as much on
each user PC;
2) Don't have as many connections directly to DB2 -
can use Gateway connection pooling for some
performance advantages
Disadvantage:
1) must carefully size gateway server to handle loads;
2) another single point of failure that must be
addressed - if gateway down all users down even if DB2
up.
3) Performance needs must be carefully watched - adds
another hop to network - gateway can get over busy.

PC direct;
1)No gateway to worry about;
2) Cheaper solution if limited number of users; more
expensive if number of users gets very large (over
couple thousand)
3) More difficult to roll out new versions and
maintenance, including new connections;
4) Puts users directly onto DB2, must use DB2
connection pooling with V6 or higher to get any thread
reuse/pooling
--- Chad Breiner <[login to unmask email]> wrote:
> I have a basic question about DB2 connect. My
> client
> is currently using a DB2 connect gateway to get to
> the
> mainframe data. The current direction for my client
> is to install DB2 on all PC's. Are there any
> advantages of going thru a db2 connect gateway
> rather
> than directly to the database?
>
> Thanks
>
> Chad Breiner
> DB2 Database Administrator
> CBI Consulting
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15
> Free!
> http://photos.yahoo.com/
>
>
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
> http://www.ryci.com/db2-l. The owners of the list
> can


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/



Gerry McHugh

Re: DB2 Connect
(in response to Myron Miller)
One more advantage of gateway - single point of administration for tuning
purposes. If it's PC directly to DB2, then everyone running the admin
client on their PC would almost need to be a DBA.

-----Original Message-----
From: Myron Miller [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 1:40 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


Each has its pros and cons. It really depends. I
won't attempt to give all of the pro's and con's but
some major that I know about:

Gateway:
Advantages
1) Common interface - don't have to install as much on
each user PC;
2) Don't have as many connections directly to DB2 -
can use Gateway connection pooling for some
performance advantages
Disadvantage:
1) must carefully size gateway server to handle loads;
2) another single point of failure that must be
addressed - if gateway down all users down even if DB2
up.
3) Performance needs must be carefully watched - adds
another hop to network - gateway can get over busy.

PC direct;
1)No gateway to worry about;
2) Cheaper solution if limited number of users; more
expensive if number of users gets very large (over
couple thousand)
3) More difficult to roll out new versions and
maintenance, including new connections;
4) Puts users directly onto DB2, must use DB2
connection pooling with V6 or higher to get any thread
reuse/pooling
--- Chad Breiner <[login to unmask email]> wrote:
> I have a basic question about DB2 connect. My
> client
> is currently using a DB2 connect gateway to get to
> the
> mainframe data. The current direction for my client
> is to install DB2 on all PC's. Are there any
> advantages of going thru a db2 connect gateway
> rather
> than directly to the database?
>
> Thanks
>
> Chad Breiner
> DB2 Database Administrator
> CBI Consulting
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15
> Free!
> http://photos.yahoo.com/
>
>
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
> http://www.ryci.com/db2-l. The owners of the list
> can


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/








Wayne Kline

Re: DB2 Connect
(in response to Gerry McHugh)
Re: then everyone running the admin
client on their PC would almost need to be a DBA.

Isn't that MicroSoft's direction? :-)

-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 12:16 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


One more advantage of gateway - single point of administration for tuning
purposes. If it's PC directly to DB2, then everyone running the admin
client on their PC would almost need to be a DBA.

-----Original Message-----
From: Myron Miller [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 1:40 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


Each has its pros and cons. It really depends. I
won't attempt to give all of the pro's and con's but
some major that I know about:

Gateway:
Advantages
1) Common interface - don't have to install as much on
each user PC;
2) Don't have as many connections directly to DB2 -
can use Gateway connection pooling for some
performance advantages
Disadvantage:
1) must carefully size gateway server to handle loads;
2) another single point of failure that must be
addressed - if gateway down all users down even if DB2
up.
3) Performance needs must be carefully watched - adds
another hop to network - gateway can get over busy.

PC direct;
1)No gateway to worry about;
2) Cheaper solution if limited number of users; more
expensive if number of users gets very large (over
couple thousand)
3) More difficult to roll out new versions and
maintenance, including new connections;
4) Puts users directly onto DB2, must use DB2
connection pooling with V6 or higher to get any thread
reuse/pooling
--- Chad Breiner <[login to unmask email]> wrote:
> I have a basic question about DB2 connect. My
> client
> is currently using a DB2 connect gateway to get to
> the
> mainframe data. The current direction for my client
> is to install DB2 on all PC's. Are there any
> advantages of going thru a db2 connect gateway
> rather
> than directly to the database?
>
> Thanks
>
> Chad Breiner
> DB2 Database Administrator
> CBI Consulting
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15
> Free!
> http://photos.yahoo.com/
>
>
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
> http://www.ryci.com/db2-l. The owners of the list
> can


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/













Tim Lowe

Re: DB2 Connect
(in response to Wayne Kline)
At the DB2 Tech conference I heard about another "gateway" option, running
the DB2 Connect V7.1 on Linux/390 for performance and scalability.
I have not tried this, but is sounded like an interesting option for some
cases.



Tam Tran

DB2 connect
(in response to Tim Lowe)
Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2 database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location where
the error was detected: "0.168.180.228". Communication function detecting the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________



Larry Cable

Re: DB2 connect
(in response to Tam Tran)
Speak with your network/systems people on the DB2 side. There is a "TCP/IP
keep alive" parameter that could be causing the problem. This parameter is
suppose to disconnect idle connections after a specified period of time.
Hope this helps.

LarryC

----- Original Message -----
From: "Tam Tran" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Friday, December 15, 2000 2:34 AM
Subject: DB2 connect


> Hello DB2 Experts
>
> About 2 weeks ago, I asked about DB2 Connect without a satisfied reply.
Now I
> try again and hope
> a good reply for Chrismas and new year.
>
> Here is our problem :
>
> A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
> on Server) fails if it is idle for a long time (maybe a day).
>
> We use DB2 with WindowNT on both Client and Server
>
> In a DOS window, type db2cmd to open a DB2 window.
> Then type
>
> db2 connect to ASP user NAME205 using NAME205
> and press Enter (this connects us to the database).
>
> Then type
> db2 select logonid from user where logonid='1050'
> (actually, any valid command will do) and press Enter. These two commands
work
> perfectly.
>
> Now wait for one day. Next day, type
> db2 select logonid from user where logonid='1050'
> and press Enter again.
>
> Now the command fails with the message
>
> SQL30081N A communication error has been detected. Communication
protocol
> being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
> the error was detected: "0.168.180.228". Communication function detecting
the
> error: "send". Protocol specific error code(s): "10054", "*", "0".
> SQLSTATE=08001
> So now we have lost the connection to the database.
>
> We can make the connection again by typing
> db2 connect to ASP user NAME205 using NAME205
> again. But we want the connection to stay forever.
>
> 10054 means WSAECONNRESET (10054) Connection reset by peer.
>
> Please help me or let me who to contact .
> Thank you very much in advances
>
> Merry Chrismas and Happy new year.
>
> TRANCT
>
> ______________________________________________________________________
> This e-mail is confidential and is intended for the use of the addressee
only.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of LASERCOM. If you are not the intended
recipient,
> you are hereby notified that you must not use, copy, disclose or otherwise
> disseminate this e-mail or any information herein. If you receive this
> transmission in error, please notify the sender immediately by reply
e-mail and
> then delete this e-mail. Please note that e-mail may be susceptible to
data
> corruption, interception and unauthorised amendment. LASERCOM does not
accept
> any liability for any such corruption, interception, amendment or the
> consequences thereof.
> ______________________________________________________________________
>
>
>


>



Tam Tran

Re: DB2 connect
(in response to Larry Cable)
Thank you very much Larry, the answer we can find in

http://support.microsoft.com/support/kb/articles/Q102/9/73.asp?VOTE=2

Again, many thanks, it is a cadeau for Chrismax

Merry Chrismax and Happy new year

TRANCT










Larry Cable <[login to unmask email]> on 12/15/2000 11:34:52 AM

Please respond to Larry Cable <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Tam Tran/Geneva/LaserCom)
Fax to:
Subject: Re: DB2 connect




Speak with your network/systems people on the DB2 side. There is a "TCP/IP
keep alive" parameter that could be causing the problem. This parameter is
suppose to disconnect idle connections after a specified period of time.
Hope this helps.

LarryC

----- Original Message -----
From: "Tam Tran" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Friday, December 15, 2000 2:34 AM
Subject: DB2 connect


> Hello DB2 Experts
>
> About 2 weeks ago, I asked about DB2 Connect without a satisfied reply.
Now I
> try again and hope
> a good reply for Chrismas and new year.
>
> Here is our problem :
>
> A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
> on Server) fails if it is idle for a long time (maybe a day).
>
> We use DB2 with WindowNT on both Client and Server
>
> In a DOS window, type db2cmd to open a DB2 window.
> Then type
>
> db2 connect to ASP user NAME205 using NAME205
> and press Enter (this connects us to the database).
>
> Then type
> db2 select logonid from user where logonid='1050'
> (actually, any valid command will do) and press Enter. These two commands
work
> perfectly.
>
> Now wait for one day. Next day, type
> db2 select logonid from user where logonid='1050'
> and press Enter again.
>
> Now the command fails with the message
>
> SQL30081N A communication error has been detected. Communication
protocol
> being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
> the error was detected: "0.168.180.228". Communication function detecting
the
> error: "send". Protocol specific error code(s): "10054", "*", "0".
> SQLSTATE=08001
> So now we have lost the connection to the database.
>
> We can make the connection again by typing
> db2 connect to ASP user NAME205 using NAME205
> again. But we want the connection to stay forever.
>
> 10054 means WSAECONNRESET (10054) Connection reset by peer.
>
> Please help me or let me who to contact .
> Thank you very much in advances
>
> Merry Chrismas and Happy new year.
>
> TRANCT
>
> ______________________________________________________________________
> This e-mail is confidential and is intended for the use of the addressee
only.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of LASERCOM. If you are not the intended
recipient,
> you are hereby notified that you must not use, copy, disclose or otherwise
> disseminate this e-mail or any information herein. If you receive this
> transmission in error, please notify the sender immediately by reply
e-mail and
> then delete this e-mail. Please note that e-mail may be susceptible to
data
> corruption, interception and unauthorised amendment. LASERCOM does not
accept
> any liability for any such corruption, interception, amendment or the
> consequences thereof.
> ______________________________________________________________________
>
>
>


>








Gerry McHugh

Re: DB2 Connect
(in response to Tam Tran)
good one

-----Original Message-----
From: Kline, Wayne [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 3:21 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


Re: then everyone running the admin
client on their PC would almost need to be a DBA.

Isn't that MicroSoft's direction? :-)

-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 12:16 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


One more advantage of gateway - single point of administration for tuning
purposes. If it's PC directly to DB2, then everyone running the admin
client on their PC would almost need to be a DBA.

-----Original Message-----
From: Myron Miller [mailto:[login to unmask email]
Sent: Thursday, December 14, 2000 1:40 PM
To: [login to unmask email]
Subject: Re: DB2 Connect


Each has its pros and cons. It really depends. I
won't attempt to give all of the pro's and con's but
some major that I know about:

Gateway:
Advantages
1) Common interface - don't have to install as much on
each user PC;
2) Don't have as many connections directly to DB2 -
can use Gateway connection pooling for some
performance advantages
Disadvantage:
1) must carefully size gateway server to handle loads;
2) another single point of failure that must be
addressed - if gateway down all users down even if DB2
up.
3) Performance needs must be carefully watched - adds
another hop to network - gateway can get over busy.

PC direct;
1)No gateway to worry about;
2) Cheaper solution if limited number of users; more
expensive if number of users gets very large (over
couple thousand)
3) More difficult to roll out new versions and
maintenance, including new connections;
4) Puts users directly onto DB2, must use DB2
connection pooling with V6 or higher to get any thread
reuse/pooling
--- Chad Breiner <[login to unmask email]> wrote:
> I have a basic question about DB2 connect. My
> client
> is currently using a DB2 connect gateway to get to
> the
> mainframe data. The current direction for my client
> is to install DB2 on all PC's. Are there any
> advantages of going thru a db2 connect gateway
> rather
> than directly to the database?
>
> Thanks
>
> Chad Breiner
> DB2 Database Administrator
> CBI Consulting
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15
> Free!
> http://photos.yahoo.com/
>
>
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
> http://www.ryci.com/db2-l. The owners of the list
> can


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/


















Gerry McHugh

Re: DB2 connect
(in response to Gerry McHugh)
If a connection is broken (i.e. TCP/IP) then you're gonna lose the session.
Period. End of story. Check the "idle active thread timeout" ZPARM. If
you don't want idle threads to timeout, make sure this doesn't have a
non-zero value.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 3:35 AM
To: [login to unmask email]
Subject: DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee
only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended
recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail
and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not
accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________








Piontkowski Michael ML

Re: DB2 connect
(in response to Gerry McHugh)
Tran is not connecting to DB2 for OS/390.
He's connecting to DB2 for NT database server
from a NT client.

Mike Piontkowski
TP&S Technical Maintenance
Voice: +1 302.886.4612
Fax: +1 302.886.4749


-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 12:30
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 connect


If a connection is broken (i.e. TCP/IP) then you're gonna lose the session.
Period. End of story. Check the "idle active thread timeout" ZPARM. If
you don't want idle threads to timeout, make sure this doesn't have a
non-zero value.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 3:35 AM
To: [login to unmask email]
Subject: DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee
only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended
recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail
and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not
accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________













Wayne Driscoll

Re: DB2 connect
(in response to Piontkowski Michael ML)


Tam,
Would you really want a 24 hour delay in processing from sign-on until a
transaction is entered? This would seem to be contrary to Auditing
concerns, after 24 hours of inactivity, how can you safely assume that the
statement is being submitted by the same user that originally logged on?
Wayne Driscoll
Product Developer
Quest Software Inc.
[login to unmask email]
Note: All opinions are strictly my own.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 2:35 AM
To: [login to unmask email]
Subject: [DB2-L] DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

Tam Tran

Re: DB2 connect
(in response to Wayne Driscoll)
Michael,

Thank you very much. Harry cABLE gave me a solution, you can find it in :

http://support.microsoft.com/support/kb/articles/Q102/9/73.asp?VOTE=2

It was very nice cadeau for Chrismax and New Year
Thanks again Harry.

TRANCT











"Piontkowski, Michael L" <[login to unmask email]> on 12/15/2000
07:55:24 PM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Tam Tran/Geneva/LaserCom)
Fax to:
Subject: Re: DB2 connect




Tran is not connecting to DB2 for OS/390.
He's connecting to DB2 for NT database server
from a NT client.

Mike Piontkowski
TP&S Technical Maintenance
Voice: +1 302.886.4612
Fax: +1 302.886.4749


-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 12:30
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 connect


If a connection is broken (i.e. TCP/IP) then you're gonna lose the session.
Period. End of story. Check the "idle active thread timeout" ZPARM. If
you don't want idle threads to timeout, make sure this doesn't have a
non-zero value.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 3:35 AM
To: [login to unmask email]
Subject: DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee
only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended
recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail
and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not
accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________


















Marcus Davage

Re: DB2 connect
(in response to Tam Tran)
"make sure this doesn't have a non-zero value."

Sounds like a JCL COND statement!

-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: 15 December 2000 17:30
To: [login to unmask email]
Subject: Re: DB2 connect


If a connection is broken (i.e. TCP/IP) then you're gonna lose the session.
Period. End of story. Check the "idle active thread timeout" ZPARM. If
you don't want idle threads to timeout, make sure this doesn't have a
non-zero value.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 3:35 AM
To: [login to unmask email]
Subject: DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee
only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended
recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail
and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not
accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________












-----------------------------------------------------------------------------------------------------------------------
This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.

evolvebank.com is a division of Lloyds TSB Bank plc.
Lloyds TSB Bank plc, 71 Lombard Street, London EC3P 3BS. Registered in
England, number 2065. Telephone No: 020 7626 1500
Lloyds TSB Scotland plc, Henry Duncan House, 120 George Street,
Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone
No: 0131 225 4555

Lloyds TSB Bank plc and Lloyds TSB Scotland plc are regulated by the
Personal Investment Authority and represent only the Scottish Widows
and Lloyds TSB Marketing Group for life assurance, pensions and
investment business.

Members of the UK Banking Ombudsman Scheme and signatories to the UK
Banking Code.
-----------------------------------------------------------------------------------------------------------------------



Tam Tran

Re: DB2 connect
(in response to Tam Tran)

Hi Wayne,

Thank you very much for reply. I got a solution for that. You can find solution
on :

http://support.microsoft.com/support/kb/articles/Q102/9/73.asp?VOTE=2

Solution is given by Harry Cable

Regards

TAM








Wayne Driscoll <[login to unmask email]> on 12/16/2000 12:00:44 AM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Tam Tran/Geneva/LaserCom)
Fax to:
Subject: Re: DB2 connect






Tam,
Would you really want a 24 hour delay in processing from sign-on until a
transaction is entered? This would seem to be contrary to Auditing
concerns, after 24 hours of inactivity, how can you safely assume that the
statement is being submitted by the same user that originally logged on?
Wayne Driscoll
Product Developer
Quest Software Inc.
[login to unmask email]
Note: All opinions are strictly my own.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 2:35 AM
To: [login to unmask email]
Subject: [DB2-L] DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT


Tam Tran

Re: DB2 connect
(in response to Marcus Davage)
Thanks to all who reply my question about DB2 connect.

Harry CABLE gave me a solution, you can find it in :

http://support.microsoft.com/support/kb/articles/Q102/9/73.asp?VOTE=2


TRANCT











"Piontkowski, Michael L" <[login to unmask email]> on 12/15/2000
07:55:24 PM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Tam Tran/Geneva/LaserCom)
Fax to:
Subject: Re: DB2 connect




Tran is not connecting to DB2 for OS/390.
He's connecting to DB2 for NT database server
from a NT client.

Mike Piontkowski
TP&S Technical Maintenance
Voice: +1 302.886.4612
Fax: +1 302.886.4749


-----Original Message-----
From: McHugh, Gerry [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 12:30
To: [login to unmask email]
Subject: Re: [DB2-L] DB2 connect


If a connection is broken (i.e. TCP/IP) then you're gonna lose the session.
Period. End of story. Check the "idle active thread timeout" ZPARM. If
you don't want idle threads to timeout, make sure this doesn't have a
non-zero value.

-----Original Message-----
From: Tam Tran [mailto:[login to unmask email]
Sent: Friday, December 15, 2000 3:35 AM
To: [login to unmask email]
Subject: DB2 connect


Hello DB2 Experts

About 2 weeks ago, I asked about DB2 Connect without a satisfied reply. Now
I
try again and hope
a good reply for Chrismas and new year.

Here is our problem :

A DB2 session (i.e. DB2 client software on Client talking to the DB2
database
on Server) fails if it is idle for a long time (maybe a day).

We use DB2 with WindowNT on both Client and Server

In a DOS window, type db2cmd to open a DB2 window.
Then type

db2 connect to ASP user NAME205 using NAME205
and press Enter (this connects us to the database).

Then type
db2 select logonid from user where logonid='1050'
(actually, any valid command will do) and press Enter. These two commands
work
perfectly.

Now wait for one day. Next day, type
db2 select logonid from user where logonid='1050'
and press Enter again.

Now the command fails with the message

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where
the error was detected: "0.168.180.228". Communication function detecting
the
error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001
So now we have lost the connection to the database.

We can make the connection again by typing
db2 connect to ASP user NAME205 using NAME205
again. But we want the connection to stay forever.

10054 means WSAECONNRESET (10054) Connection reset by peer.

Please help me or let me who to contact .
Thank you very much in advances

Merry Chrismas and Happy new year.

TRANCT

______________________________________________________________________
This e-mail is confidential and is intended for the use of the addressee
only.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of LASERCOM. If you are not the intended
recipient,
you are hereby notified that you must not use, copy, disclose or otherwise
disseminate this e-mail or any information herein. If you receive this
transmission in error, please notify the sender immediately by reply e-mail
and
then delete this e-mail. Please note that e-mail may be susceptible to data
corruption, interception and unauthorised amendment. LASERCOM does not
accept
any liability for any such corruption, interception, amendment or the
consequences thereof.
______________________________________________________________________