I should also add, this has been fixed to some extent in server 4.2.2.0,
per APAR IC32075. Note that this will not fix any clients where the
problem already exists, but it should prevent the problem from occurring
once the PTF is installed.
============================================================
ABSTRACT:
ANS1357S WHEN CONNECTING WITH NON-UNICODE CLIENT
ERROR DESCRIPTION:
Once a unicode TSM client (V4.2.0 or higher Windows NT/2000
or V4.2.1.15 or higher Windows XP client)
has been used to connect to a TSM V4.2 server
with a given node name, that node name can no longer be
used by a non-unicode TSM client. If you attempt to connect
with that node name using a non-unicode TSM client, you will
receive the following error:
.
You may see the following error:
ANR0428W Session 432 for node ENCRYP (WinNT)
refused - client is down-level with this server version.
..
ANS1357S Session rejected: Downlevel client code version
.
Any operation attempted by a non-unicode TSM client with this
node name, will fail with the above error message. For example,
if the V4.2 Windows 2000 client has done queries or restores
for non-unicode filesystems for NODE1 to a V4.2 TSM server,
a V4.1 Windows 2000 client can no longer connect to
that V4.2 server as NODE1.
Initial Impact: High
LOCAL FIX:
None.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: Non-unicode clients connecting to a V4.2 *
* server once a unicode client (V4.2.0 or *
* higher Windows NT/2000 or V4.2.1.15 or *
* higher Windows XP ) has been used to *
* access that server using the non-unicode *
* client's nodename. *
****************************************************************
* PROBLEM DESCRIPTION: ANS1357S Session rejected: Downlevel *
* client code version received after *
* connecting to server. *
****************************************************************
* RECOMMENDATION: Install the PTF *
****************************************************************
Once a TSM unicode client (V4.2.0 or higher Windows NT/2000 or
V4.2.1.15 or higher Windows XP ) node has connected to a
TSM 4.2.0 or greater server (any platform) using a non-unicode
client's node, the non-unicode client node may no longer
connect to that server. A down level client message is
received.
PROBLEM CONCLUSION:
The TSM unicode client (V4.2.0 or higher Windows NT/2000 or
V4.2.1.15 or higher Windows XP ) can now be used for queries
and restores, and a lower level or non-unicode 4.2 client can
still connect to the server. As long as no unicode filespaces
exist, the 4.2 and above TSM server will allow a lower level
or non--unicode V4.2 client to connect to the server. If any
unicode filespaces exist for a node, a unicode client will be
required to connect to the server. If any unicode filespaces
exist for a node, and lower level or non-unicode clients
attempt to connect, the connection will be refused, and the
down level client message will be displayed.
============================================================
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Andrew Raibeck/Tucson/IBM@IBMUS
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/28/2002 07:43
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: tsm client is down-level with this server version
Matt,
If you are experiencing this problem, then you need to contact IBM
support. The procedures for resolving this are potentially dangerous, and
are therefore undocumented. They are not intended to be shared publicly.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Adams, Matt (US - Hermitage)" <maadams AT DELOITTE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/28/2002 07:11
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: tsm client is down-level with this server
version
I would be interested in hearing what Tivoli support had to say on
"patching" or correcting this.
Thanks,
Matt
-----Original Message-----
From: Loon, E.J. van - SPLXM [mailto:Eric-van.Loon AT KLM DOT COM]
Sent: Wednesday, August 28, 2002 8:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: tsm client is down-level with this server version
Hi Oscar!
I've read on this list some time ago that there is a way to fix this. If I
remember correctly it has something to do with "patching" the client
status
in the TSM database.
I would recommend contacting Tivoli Support and opening a PMR.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Oscar Kolsteren [mailto:Oscar.Kolsteren AT POSTBANKMAIL DOT NL]
Sent: Wednesday, August 28, 2002 10:17
To: ADSM-L AT VM.MARIST DOT EDU
Subject: tsm client is down-level with this server version
Hi All,
Situation :
NT and OS/2 environment with TSM client 3.7.* and we have a AIX server
running
with 4.2.1.7.
Recently we installed some new servers with clientsversion 4.2. At the
same
time
some administrators upgraded there local TSM version to 4.2.
If they want some info from a server running 3.7 and contact this server
from
their local installation the server won't backup anymore because we get
the
message " tsm client is down-level with this server version".
When we upgrade the TSM client on this server everything is solved.
This is a known problem and has to do with unicode and non-unicode.
But now my problem :
There is no upgrade available for OS/2 and I can't backup this machine
anymore.
Does someone has a solution for this problem ???
(Remove the client and start all over is no option...)
Thanx,
Oscar Kolsteren
Postbank NV
Netherlands
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not
the
addressee, you are notified that no part of the e-mail or any attachment
may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender
immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**********************************************************************
- This message (including any attachments) contains confidential
information
intended for a specific individual and purpose, and is protected by law. -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
|
