The only thing to be wary of when going to TSM 4.2, is the issue of having a double zero string in the password file. TSM 4.2.0 and 4.2.1 can not read the password file if the file contains this double zero string. We recently upgraded to TSM 4.2.1.25 and had major problems with passwords. After a call to support, we figured out that the password we were using was generating a double zero string. The password we were trying to use was 10 characters in length...they suggested not making the password over 6 characters in length. This reduces the chances of having a double zero string in the password file. Also, you will want to look at updating the password manually for your clients. When password access is set to generate, and a new password is generated, you may run into the above mentioned problem.
According to support, this problem should be fixed in TSM 4.2.2 and TSM 5.1. Regards, Sean Sean M. English Enterprise Storage Management IBM Global Services, SDC Charlotte, NC Internet Mail: [EMAIL PROTECTED] You can't change the wind, but you can adjust the sails.
