Direct links to fixes
Closed as program error.
iOS native client may get in loop retrying calendar action for repeating event. It appears these cases occur when there are no outstanding notices and Traveler just responds successful for the action request. The device will still send a sendmail (reply notice to chair). Traveler has some code to try and avoid processing these replies if the event is already in the requested state. In some cases where there are child documents in cancelled or removed states Traveler thinks the event reply still needs to be processed. Fix is to better detect states where no reply to chair is needed. This does not stop the device action loop but prevents a flood of replies to the chair. </Update>
Native calendar application on iOS devices may get stuck in retry loop for sending a notice to the event chair when replying to a single instance of a repeating event.
The IBM Traveler server has been updated to detect and work around this device bug by not sending the notice more than once.
This fix is included in IBM Traveler server 18.104.22.168 and will be included in all future releases. For the latest available maintenance release please 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
01 September 2016