Hi Richard,

We are running one 4.x client and all the others at 5.x.

Sorry I sent the "4" output.  Here is the 5.1.6 client output

04/27/06   23:49:39 ANS1810E TSM session has been reestablished.
04/28/06   02:37:24 sessSendVerb: Error sending Verb, rc: -50
04/28/06   02:37:24 ANS1809W Session is lost; initializing session
reopen procedure.
04/28/06   02:37:24 ANS1809W Session is lost; initializing session
reopen procedure.
04/28/06   02:37:39 ANS1810E TSM session has been reestablished.
04/28/06   02:38:31 ANS1005E TCP/IP read error on socket = 6, errno =
73, reason
 : 'A connection with a remote socket was reset by that socket.'.
04/28/06   02:38:31 ANS1809W Session is lost; initializing session
reopen procedure. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Tuesday, May 02, 2006 8:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: archive hangs

On May 2, 2006, at 8:30 AM, Levi, Ralph wrote:

> ANS1809E Session is lost; initializing session reopen procedure.

Ralph - That message form makes the situation even more "interesting"...

The last time we saw that form of the ANS1809* message was in TSM 4.2.
(It is ANS1809W these days.)  Is this an antiquated client?  And, if so,
is this the only old, such client you have, and is it the only one
exhibiting this issue?  (Problem reduction exercise.)
A client upgrade may be due there; and old age of a TSM client is often
accompanied by a geriatric operating system level.

Just pursuing evidentiary data,    Richard Sims