Problems with Unisys Dorado support?

[comp.sys.unisys]

Is it just me or has Unisys Dorado (2200, for us old-timers) support degraded lately? Six months ago I opened a trouble report against the SLIB product for a simple, re-producible, compile-time problem. I supplied a half-dozen line C program that demonstrates the problem.

Since then all Unisys has managed to do is open a UCF (00061620), but has not yet created a fix. The UCF is marked: "Engineering Location: UNISYS GLOBAL SERVICES - INDIA" which surprised me.

A Unisys employee tells me ("off the record") that Unisys laid off its old support staff and moved the work to India.

Have other customers noticed similar problems? (I'm now hesitant to upgrade our system software from 19.0 to 20.0 because I'm losing confidence in Unisys.)

- Steve J. Martin
(speaking only for myself, not for my employer)

[Don Vito Martinelli]

Hi Steve,

I retired a couple of weeks under five years ago and noticed back then
that some of the support work was being carried out in India (probably a
year earlier). I know we had an argument over something but we resolved
it eventually.
Actually I had more problems with Teamquest, specifically the Cobol
procs associated with the Log-Read part of SAUtilities - they had a
maintainer who did not understand COBOL data allocation. At one stage I
gave them a list of all the allocation errors in their procs, a couple
of months later they released a new level but refused to give me a copy
so I could "proofread" it. Yes, when we moved to the new level they had
my changes in there but had introduced new errors.

Cheers
Andrew