It seems that if we rename a user (either new name due to marriage or new OU due to change of departement) Traveler stops to work.
The command traveler reset doesn’t get the intended result.
Only thing that worked was to re-configure the user (he had to insert all his data again like shortname, PW, server etc.)
I this the correct way? I though that the shortname which isn’t changed should secure that the user can still sync without problems. But it seems that Traveler stores the hirachical name somewere (either in the device ot the cloudscape-db) and causes Traveler to stop working after a rename.
Subject: RE: User Rename = Reconfiguration in Traveler?
Traveler has put many fixes in for these rename issues over the releases. If you truly are on 8.5.1, then you really need to update to 8.5.3 to get the fixes that already exist. If you are already on 8.5.3 (which does have some fixes since 8.5.2 as well), you should open a PMR so we can see what is breaking down in the process as we have attempted to make this work.
The web link in another response is old.
Subject: Same here
I have also faced this issue, is there any IBM technote available.
I too think that as the shortname and http password is not getting changed, there should not be any impact on traveler post Rename in CN or OU
Subject: It has been a problem since V1
No answers yet!
Will update if it changes!