"GlenB" wrote:
Quote:
Yikes! You know, if you don't have a huge amount of PROCs in it you
should consider downloading OpenQM and giving it a whirl. Even if you
do have PROCs, don't lose hope. There is a group on Google Groups
where you can ask questions. Responses are normally quick, but this
week is the Spectrum conference.
I have not personally attemped a migration from our D3 box yet... |
Since D3 is my primary platform I tend to look at everything these
days from a D3 perspective. While QM is excellent, feature-rich, and
very stable software (at least for my personal single-user testing) I
find it is quite different from D3. I have a list of aliases
(alternative verbs) which I invoke to get QM to do things like D3.
I've had to write my own Pick-style QSelect command. I have to be
vigilant about using the numerous flags which enable or disable QM
functionality in order to make it seem more Pick-like. And there are
many aspects of the software which are simply different. I would work
with someone to migrate D3 to QM (with some reluctance of course but
that wouldn't affect the end result) but one must be prepared for
quite a number of code changes to get an AP/D3 app to conform to QM.
Of all the good things one can say about QM, "easy migration" is not
yet one of them.
Art - your best successor to AP/SCO is D3/Linux. This would include
any commands you may have which !execute into the host OS. D3/NT is
good software (depending on who you ask) but if you're looking for a
smooth migration, NT is further from SCO than Linux. As an indication
of how close the platforms are, for a long time the Ix86 monitor code
for Linux was exactly the same as for SCO. D3/SCO and D3/Linux was
essentially the same software except for the installation and text in
the dataset.
Please feel free to contact me if you'd like assistance with
migration, adding a new GUI, or anything else related to updating your
software.
Good luck.
Tony Gravagno
Nebula Research and Development
TG@ removethisNebula-RnD.com