In the past support has had a way to correct this problem for clients that
got the wrong OS in them because another system used the field by accident.
I would call support again and see why this workaround is not available for
you.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Edgardo Moso [mailto:edgardo_moso AT KINDREDHEALTHCARE DOT COM]
Sent: Saturday, October 12, 2002 9:27 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Down Level Client Code


Does any body has a work around with the dwon level client code errror?

Here's what happened:  I have an old ADSM client version 3.1 runnning in
Solaris 2.5. We don't want to upgrade it to a higher level, say TSM version
4.2.2, because if we upgrade we need to upgrade first the Solaris to a
higher level.   We dont want to do this beause the client box has nothing
on it except the old patience and nurisng data that we would like to
preserve for a period of time.   Basically this server's data are stagnant,
it would be used for for restore.  Other than this TSM client,  ourTSM
clients had been upgraded to 4.2 and I know Tivoli corrected this bug.
Usually,  when I'd like to verify  query about the  the client nodespecs I
will just use the command in my desktop "dsmc -tcps=server1 -node=node1". I
used this in this node and not knowing with the query command my node data
was changed in the server, it has an error "Down level client code" when I
run any comand in the client box.  For me this is the worst transition
Tivoli had made to a higher TSM client, allowing this command and not
protecting the lower version.  The worst tof all is when I asked Tivoli
support, the Manager himself said, they have no technical solution
to the problem except to upgrade it to the supported level.   I know of
some solution but it's impractical to apply beause for example, I will
resotre the db back, I will sacrifice 99 % of the clients in this TSM
server.  If I used export/import this will take forever because this is
almost 600GB of data.  I consider updating the TSM database but I don't know
how to do it.

Any help will be greatly appreciated.

Thanks.