<<I would appreciate contact from anybody using Transact/V or
Transact/iX How difficult was it to migrate from V to iX?>>


For vanilla Transact/V, migration is almost a no-brainer. Appendix B of the
Transact manual discusses migration issues, but they seem to be fairly rare
in practice.

However, if you've been using FASTRAN, and have gotten used to/taken
advantage of some of its variations from the language specification, there
could be more work in store. For example, according to the language spec, a
FIND with MATCH specifications in place puts every record into the list
register, then checks it to see if it satisfies the MATCH criteria. Nick
didn't do that-if a FIND with MATCH doesn't produce any "hits", the
variables identified in the LIST= clause contain the values they had before
the FIND verb started. If a program that takes advantage of this feature is
converted to Transact/iX, it suddenly starts having "garbage" show up in
those variables.

        <<Any Year 2000 tools specific to Transact? (I have the info about
Time Machine etc.) We have a Transact/V user that will migrate to MPE/iX
instead of replacing their in-house application. Many Thanks>>


Don't know of any, but we didn't look very hard. Since we're
Dictionary-based, the Y2K migration was almost completely handled by
changing the definitions of the items in the dictionary and redoing the
forms to match.

Steve