so when i ask these questions, the spirit in which they are intended are that of simply trying to figure out where the issues are. it's not meant as a "PMCO was better" or "PMUA is better" discussion, but more of a discussion around why all these issues are happening because of some observations i've been making. then again i don't see everything so i very well may be wrong, hence why i'm asking.

so my question is are the majority of issues (ticketing issues, seat changes, GPU clearings, etc) happening predominantly to PMUA MP members and PMUA routes?

and here's why i ask.

as a pre-3/3 onepass member, i habitually fly PMCO routes if anything just out of habit. post 3/3 i booked an EWR-PVG ticket in W. it ticketed in a couple minutes. GPU's were applied, cleared within a week, very drama free.

i also have a short hop EWR-CVG i booked for this month. again, ticket issued in three minutes. both time seat changes and such are all fine. reservations were glitch free.

now i don't have any numbers or anything to speak of to this and it's all just gut feeling i get from perusing the threads, but i'm getting the sense that most of the issues in terms of ticketing, GPU's going missing, etc., when i see them in a thread i notice that a lot of times the OP will mention their itinerary involves SFO, ORD or some other PMUA hub which would lead me to believe (though not guarantee) that it's probably a PMUA flight (and also possibly a PMUA flyer who goes on that route every week for work, for instance).

personally as an IT person who does data migrations for a living, it's just making me wonder. after the decision of sticking with SHARES (not here to debate the merits or opinions of it, just a fact about the environment we operate in now) in my head it would lead me to the possibility of the OP and PMCO information getting ported fine since it's more of a replication task, and the IT team botching the conversion of the PMUA data. it would then make sense to me that the PMUA flights and PMUA members would have more issues since that data involved a mis-handled transformation as opposed to a straight copy.

...unless a ton of ex-OP members are having issues on PMCO flights, in which case my theory is thrown out the window.

i don't know, it's just a thought that occurred to me today. for me i'm not here to incite a flame war, but as an engineer i'm actually curious to find out what happened and where it got messed up. i don't believe my personal examples are the norm, but i think it shows that the system is capable of behaving, if not ideally, at the very least so it's not screwing everything completely up. that makes the engineer in me curious as to the why of everyone else's issues.

just a thought.

There really is no more concept of pmUA or pmCO flight. They are all harmonized as part of the merger, of course. And because of that SHARES doesn't know any better. Flight numbers have all been mixed up, although many have remained the same (e.g. EWR-SEA is still 1481, 1581, 1681 for the most part).

Also with the equipment being more evenly dispersed across UA's network there are now 737's flying SFO-SEA which was a 100% pmUA route and operated by A320s and B757s. Now CO's 737's are on the route so, again, SHARES doesn't know any better.

Ticketing was always tricky through SHARES. Most of my CO tickets would issue within 30 minutes. I'm finding my average to be exactly the same now regardless of which airline originally flew the leg or which city(s) I'm connecting in.

I do think UA attempted to make changes to the CPU system (they had to because they changed elite levels this year and added Platinum) which has hosed a ton of things. Most of the issues of "bad records" being migrated over from UA's old system to SHARES are working their way out of the system but in theory it can't be 100% done until 331 (?) days after 3/3 when no one could have ticketed a flight past that date.

-RM

yeah i get that for a lot of them. i guess a random example i could think of (theoretically to illustrate, i don't have an actual example on hand) would be something like EWR-NRT (UA79) and SFO-NRT (UA837). UA79 i flew a lot and is still operated by the two cabin 772 i fly frequently, and UA837 is flown by the three cabin 744 i've tried once.

all the flight information that was stored in CO's old shares instance about UA79 was always structured in the beginning to work (well... i use the term "work" liberally here). copying it over to the new UA shares should be (relatively) easy.

then all the information about UA937 in apollo has to be translated and moved into whatever format shares wants it. same with the old MP information and pre-3/3 reservations. so if the information about that flight was botched to begin with, it would make sense that all the PMUA stuff would cause more issues.

but to your point, maybe that's what it will take for things to be less painful, where in a year all the screwups from the botched migration are flushed out with purely post-3/3 reservations?