I spoke with IBM this morning about this problem.  We believe we are hot on
the trail of this problem.

Briefly as I believe someone within IBM will follow this up soon:

In the 4.2 release of the client, the notion of server affinity was
introduced.  This means that when the client connects and establishes a
password this password is stored along with the name of the server.  If a
client communicates with multiple servers there will be multiple
server/password entries.  This is all fine and good.  However, if you change
the name of your server, set server newname, then connect the client again,
it will need to get a new password from you in order to connect
successfully.  You can see this on a Windows client by looking at the
registry entries for this stuff.  What isn't happening is the password from
the original server is not being copied to the new server stanza (the
assumption is that the new server is a completely new server: different TSM
server, so the password is unlikely to be the same.  This is a bad
assumption when all that changed was the name of the server!).

IBM is discussing a fix, but I'm thinking in the meantime refrain from
renaming your server is you are running a 4.2.x client.  Unless you are
willing to go around to all of your clients and enter a new password.  If
you do change the name and have the problem, I would think changing it back
will fix the problem for you temporarily.

Wait for more news from official channels.

Thanks,

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs, CO 80949
lipp AT storsol DOT com or kelly.lipp AT storserver DOT com
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175