Filter
Top Products
Introduction
1.1 Why Migrate?
• Support for subtransactions or nested transactions
Additionally, other considerations are:
• New features will be implemented in RTR Version 3, not in RTR Version 2
• Some software problems will be addressed only in RTR Version 3 and not in
RTR Version 2
• Some improved capabilities are already available only in RTR Version 3
• More extensive release test coverage than with RTR Version 2
• RTR Version 3 tested for year 2000 compliance (RTR Version 3.1D, Version
3.2)
• Any residual year 2000 problems will be fixed only in RTR Version 3.1D or
later
Other changes introduced with RTR Version 3:
• New format and content of journal to improve security and flexibility of
transactional messaging
• Change of shared library name RTRSHR.EXE to LIBRTR.EXE
Note
There is no upgrade path for Windows 3.1 clients; applications must be
rewritten using the RTR Version 3 API.
1.2 Goals and Nongoals
The goal of this document is to assist the RTR Version 2 system manager in
planning and implementing the migration of an RTR Version 2 environment to
RTR Version 3.
It is not a goal of this document to instruct the system manager about RTR or
teach troubleshooting or analysis of the RTR environment.
1.3 Reading Guidelines
Read this document, the RTR Version 3 documentation and Release Notes before
beginning to implement an RTR migration to RTR Version 3.
1–2 Introduction