LO87975: AUTO DETECT AND FIX REPEAT PARENT DOCUMENT THAT WILL NOT SYNC TO DEVICE DUE TO CONFLICT ON UPDATE
Direct links to fixes
Closed as program error.
When a conflict occurs when accepting a repeating meeting the parent document may be left in invitation meeting notice state (actual changes stored in conflict document) but the child document(s) does get created. Traveler will not sync the event when in this state. Traveler has support tell command to fix the parent. This APAR is to automate this such the Traveler detects this case and fixes it without any user or support action.
Traveler tell command can be issued by SCN support to fix once support has determine this situation exists for an event. In many cases opening the event in Notes may fix parent document also.
The auto detection has been completed and will be in IBM Traveler 188.8.131.52 and later releases. Delivery to the cloud will be disabled until sufficient testing is completed and the feature enabled.
The IBM Traveler server has been update to handle this scenario.
This fix will be included in IBM Traveler 184.108.40.206 and all future releases. For the latest available maintenance 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