On Wed, Aug 28, 2002 at 04:23:15PM +0100, Large, Matthew wrote:

> commands available to everyone. I'm not sure they'd be too happy being
> expected to fix a problem that was actually created by a customers
> mistake(s) with these commands.

It is not a customer mistake. Everybody who can download a client and has
connectivity to the TSM server can cause this problem, since no
authentication is necessary for the problem to occur.

> Just a thought - I was there.

I experienced the same problem. IBM support told me to just delete all
filespaces and everyting else belonging to the client node, and recreate
it. (This was Dutch IBM-support by the way). They didn't mention there was
a fix for this at all. From this list I knew there was supposed to be an
undocumented procedure to fix it, but I didn't bother because this was a
relatively small and not-so-important node. I would *not* be happy if the
node *was* important, and the advice was "just throw away everything from
that node and recreate it".


  <SNIP! Is it *really* necessary to include entire messages here?>

-- 
Jurjen Oskam

PGP Key available at http://www.stupendous.org/

pgpNfbWd48wov.pgp
Description: PGP signature