Originally Posted by
BeatNavy
I can't quote the quote but I'll answer MagPBS in order:
5. That's my point. Process split trips separately.
6. Same as above. Let the straight add/drop/swaps that are full trips on both ends be processed automatically in a separate order than split trips. With as complex and advanced as this software is, there's gotta be a way to program it so that it can do that. For that matter, there should be one software package FLICA and/or Sabre that can do it all, or at least they should be able to talk to each other enough to allow it to happen. The airlines pay these companies enough to have their programmers figure it out.
That wouldn't work. Lets say you put in to swap x5555 for x5575. But 10 requests above you someone put in to swap the last 2 days of x4455 for the last 2 days of x5575. You both want the same pairing. His request requires a human yours doesn't. If it ran two separate process strings his request, which went in before yours wouldn't process before yours.
Sabre refuses to give up the proprietary code to allow 3rd party vendors to modify their software. It's the same reason they have to run 117 checks off a separate program.