Hi All,

I am just - finally - being allowed to upgrade my TSM server from 4.2 to 5.2.  So I'm 
reading the README and come to the recommendation to run CLEANUP BACKUPGROUPS.  Now 
fortunately I was far enough backlevel that I missed all of that issue at the time, 
but it got me thinking about code quality.

Long time subscribers to this list will recall that TSM code quality was somewhat 
average for the whole of the 4.2 series - well it may not have been in general, but 
there were a lot of complaints about many aspects of 4.2 and the bugs that bit us all. 
 Compare that with the number of complaints about 5.1 and 5.2 - the traffic has 
dropped off significantly and we are back to talking about ptfs that have already been 
raised and configuration and how-to issues.

That is a dramatic improvement on the behalf of the TSM code cutters/testers and QA 
folks.  And it deserves some recognition.

Well done gang.


Steve Harris
AIX and TSM Admin
Queensland Health
Brisbane, Australia

ps just one teensy little gripe - you've got to make the library client backward 
compatible with the library server - its really hard to test and implement properly 
when the compatibility is the other way around. 







***********************************************************************************
This email, including any attachments sent with it, is confidential and for the sole 
use of the intended recipients(s).  This confidentiality is not waived or lost, if you 
receive it and you are not the intended recipient(s), or if it is transmitted/received 
in error.

Any unauthorised use, alteration, disclosure, distribution or review of this email is 
prohibited.  It may be subject to a statutory duty of confidentiality if it relates to 
health service matters.

If you are not the intended recipients(s), or if you have received this e-mail in 
error, you are asked to immediately notify the sender by telephone or by return 
e-mail.  You should also delete this e-mail message and destroy any hard copies 
produced.
***********************************************************************************

Reply via email to