LO89772: MULTIPLE REPLIES TO CHAIR FOR NON-REPEATING MEETING
Direct links to fixes
Closed as program error.
For a non-repeating meeting if the user takes a action from the ios natvie calendar for which Traveler does not find any outstanding notices (change status from tentative to accepted for example) then Traveler may return a failed status to the device. The action was actually done but incorrect status is returned. Now each time the user leave the calendar app and then reopens the calendar app the ios native client will resend the action again. This results in another notice flowing to the chair. Traveler should return the successful status in this scenario which would avoid the issue. As a workaround the invitee user can turn off calendar sync on their iOS native client and then turn it back on.
Workaround is to turn off calendar sync of the iOS native client of the invitee user and then turn it back on. This will delete the calendar data from the device and sync it again. The device will forgot about the previous attempted action in this case.
The Apple Native Calendar application will continue to send event notice until it recieves a positive acknowledgment. In this scenario the IBM Traveler server incorrectly sent a failed response to the mobile device.
The IBM Traveler server has been updated to correctly handle this scenario.
This fix will be included in IBM Traveler server 184.108.40.206 and all later releases. See this technote for the latest available maintenance release: 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