REMINDER: On December 1, 2018, this forum will be closed to new posts and responses. After that date, you will still be able to view and search the forum. New discussions should take place in the IBM Developer Answers forum.
"...if there are no devices that exist for the name as entered, it will do the lookup, find the new name, and use the new name"
What you describe is exactly what happens, you try to delete the old name from the database but it finds the new name deletes that one and leaves the old in the database. According to the APAR's this should be fixed in that way that now the old name will be deleted from the database. But unfortunately it isn't.
In regards of the ecryption issue. Yes we are sure about the PWs. It worked until people upgraded the Companion App to 2.05. Nobody of them changed the PW and it was broken.
It was told that upgrading to 188.8.131.52 will fix that problem and the 2.05 Companion version will work with 184.108.40.206 again.
So having done an emergency upgrade and realizing that the major problem wasn't fixed and in addition finding out that other things (at least the ones we could reproduce easily, like the delete thing) aren't fixed too doesn't really make us happy.
The information that an app that is created by IBM and is an essential part of Traveler isn't part of the PMR suppport doesn't really help too!
Feedback response number WEBB8S5BYQ created by Harald Gaerttner on 03/06/2012