@JK
I know exactly what you mean.
We have a mix of DB2/Windows and DB2/iSeries here and depending on how the wind blows, they move instances around.
(Something to do with licensing).
What we did was design logical rollbacks, which is not the "correct" way to do it, and put the most volatile unit-of-work first!
so if that fails, we don't continue with the others.
Well now, the powers that be have inked a deal with Micro$oft to move everything (except iSeries) to SQL Server!!
Job security I guess, but annoying as hell.
At least I didn't get scared, and just quit like another poster here in a different
thread ;)
I think of it as a challenge, but would really have preferred MySQL on Linux servers.
Oh well, that's what golf course meetings between vendors and clients result in.
WP