Mark,
Thanks for the hint. We installed the 64 bit base release of tsm and then
put the 5.2.2.4 32 bit maintenance release on over the top of that. That
is probably why moving the 32 bit dsmlicense file from the old machine
corrected the problem. I opened a problem with TSM support on this issue
Mark,
Thanks for the info. Yes, I was unable to register licenses after getting
the message. The 32 to 64 bit stuff is interesting because we did go from
the 32 bit TSM on one machine to 64 bit on the other machine. I will be
contacting IBM support to see if we can get this resolved. I'd hate t
Jim,
I just had a customer do an upgrade similar to what you describe and
they had the same problem. It turned out that they installed both the
32 bit and 64 bit code on the machine. This is obviously not a good
thing! BTW, you will probably notice you can't register any licenses
either. When I
Richard,
That doesn't quite explain what happened. I installed TSM on system-new
and tried to move from system-old to system-new. When I tried to start
system-new, I got the ANR9613W message. I then moved dsmlicense from
system-old to system-new and started the server without the error
message.
On Oct 5, 2004, at 3:39 PM, Jim Sporer wrote:
We were running TSM server version 5.2.2.4 on an AIX 5.1
machine. Yesterday we moved the TSM server to a new AIX machine
running
AIX 5.2. We installed TSM server version 5.2.2.4 on the new machine
so the
only difference was we are running AIX 5.2. We
