Re: ANR0481W and COMMTIMEOUT setting

2005-05-12 Thread David McClelland
re Development Reuters 85 Fleet Street London EC4P 4AJ -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Neil Rasmussen Sent: 11 May 2005 21:08 To: ADSM-L@VM.MARIST.EDU Subject: Re: ANR0481W and COMMTIMEOUT setting I noticed that the node in your example i

Re: ANR0481W and COMMTIMEOUT setting

2005-05-11 Thread Neil Rasmussen
Stor Manager" 05/11/2005 12:49 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: ANR0481W and COMMTIMEOUT setting 1800 seconds is a *very* long commtimeout setting. Assuming the clients in question are on relatively fast networks (e.g., n

Re: ANR0481W and COMMTIMEOUT setting

2005-05-11 Thread Andrew Raibeck
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 I could not tell you what that problem is), especially if it continues to occur. Regards, Andy An

Re: ANR0481W and COMMTIMEOUT setting

2005-05-11 Thread robert moulton
Thanks John, appreciate the info. John Naylor wrote, on 05/11/05 01:42: > 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 long the server wa

Re: ANR0481W and COMMTIMEOUT setting

2005-05-11 Thread John Naylor
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 long the server waits for an expected client message during an operation that causes a database update