LO90368: ALLOW CORPORATE NAME LOOKUP DUPLICATE RESOLUTION TO BE CASE INSENSITIVE
Direct links to fixes
Closed as program error.
Allow Corporate Name Lookup duplicate resolution to be case insensitive. For example if Traveler Corporate lookup has with two directories. One is Domino Directory and one is Active Directory. and with the default NTS_NAME_LOOKUP_UNIQUEITEMS (InternetAddress and $$NoteID) fields are used for duplicate resolution. Today the code duplicate resolution is case sensitive. so that , if the Domino directory has entry with email: email@example.com and Active Directory has entry with email: Test.Testing@abc.com the duplicate resolution feature does not detect that this is a duplicate entry.
To prevent duplicate contacts from syncing to the mobile device IBM Traveler server uses the fields in NTS_NAME_LOOKUP_UNIQUEITEMS to identify if two contacts are for the same person. By default this check is case sensitive.
IBM Traveler server added ability to specify this check to be case insensitive. To change this behavior set this notes.ini parameter: NTS_NAME_LOOKUP_UNIQUE_KEY_CASE_SENSITIVE=false
This fix will be included in IBM Traveler 18.104.22.168 and later releases. For the lastest available Traveler Server release see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels
Translate this page: