This is why it took soooooo long for them to actually figure out what the
problem was.  As it turns out, if the session did not exceed the coded
server timeout the problem did not show up on any release of the client or
the server.  It is when it went over.  In order to fix the problem, the
client and the server both must be updated if any of your sessions run over
the session timeout.

Paul D. Seay, Jr.
Technical Specialist
Northrop Grumman Information Technology
757-688-8180


-----Original Message-----
From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL AT SAIC DOT COM]
Sent: Monday, February 10, 2003 10:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: summary-table


> It's stuff like this that makes my shake my head in disbelief...
>
> The summary table was working fine will ALL my clients, regardless of
> version, when the server was 4.1.5.  After upgrading ONLY the server
> to 5.1.5. the byte counts in the summary table are Zeroes.

When I called support on this they originally told me I had to upgrade my
clients to fix it. Once I got a SQL statement that would show the TSM
version and amount backed up from Paul, I discovered that they had to be
full of it with their suggestion. What I discovered was that not only were
some versions coming back with data, other nodes with the same version were
coming back with zero's. To throw things off even further even other nodes
with the same version did not even show up on the list.

I too did not have a problem till I upgraded my server, at last count that
was ONE computer. So how is it that I now have to upgrade ALL 160+clients,
+1 server to fix it?


Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154