Originally Posted by
777boy
I think this falls under the simple answer that there are still MANY out of sync itineraries floating around with the "A modification has been made..." message, which freezes the CPU process.
^
Originally Posted by
777boy
The PMUA system didn't care if an itinerary was out of sync (or didn't have such a thing as out of sync, I'm not sure which), and so was much more reliable in these types of situations.
All airlines have it. It's when the eticket record does not match the PNR (seats held).