Author: robert moulton <rmoulton AT U.WASHINGTON DOT EDU>
Date: Tue, 10 May 2005 12:07:03 -0700
Greetings ADSM List - Seeking your advice and/or a nudge toward applicable documentation ... TSM Version 5, Release 2, Level 4.0 AIX 5.2 We're seeing an increasing number of these ANR0481W messages i
Author: John Naylor <John.Naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
Date: Wed, 11 May 2005 09:42:43 +0100
Robert, My commtimeout is set 3600 with no problems Where you are seeing hits where you had none before you may want to consider/alleviate the cause per the description in Admin Ref Specifies how lon
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 11 May 2005 12:49:31 -0700
1800 seconds is a *very* long commtimeout setting. Assuming the clients in question are on relatively fast networks (e.g., not dial-up), I would tend to suspect that a problem in the network (though
Author: Neil Rasmussen <rasmussn AT US.IBM DOT COM>
Date: Wed, 11 May 2005 13:07:56 -0700
I noticed that the node in your example is a TDP SQL node (if I am reading correctly). It is not uncommon for nodes that are TDPs to require longer timeouts. What happens is that databases will start
Author: David McClelland <David.McClelland AT REUTERS DOT COM>
Date: Thu, 12 May 2005 09:00:46 +0100
Neil, Rob et al, Similarly with MSSQL, particularly during restores of large databases where SQL Server (completely aside from TDPS) goes away and formats its database files leaving the TDPS session