Inhaltszusammenfassung zur Seite Nr. 1
Reliable Transaction Router
Migration Guide
Order Number: AA–R88LB–TE
June 1999
This guide explains how to migrate from Reliable Transaction Router™
(RTR) Version 2 to RTR Version 3 on OpenVMS™ systems, and provides
information on new and obsolete features.
Revision/Update Information: This guide supersedes the Reliable
Transaction Router Migration Guide
for Version 3.1D.
Operating System: OpenVMS Versions 6.2, 7.1, 7.2
Software Version: Reliable Transaction Router Version
3.2
Compaq Computer Co
Inhaltszusammenfassung zur Seite Nr. 2
First Printing, December 1997 Revised, June 1999 COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDI‘ ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED "AS IS" AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES, EXPRESS, IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, GOOD T
Inhaltszusammenfassung zur Seite Nr. 3
Contents Preface ............................................................ vii 1 Introduction 1.1 Why Migrate?............................................... 1–1 1.2 Goals and Nongoals . . ........................................ 1–2 1.3 Reading Guidelines . . ........................................ 1–2 2 Installation 2.1 Cleaning Up the Old Version 2 Environment....................... 2–1 2.2 Preserving the Old Environment ................................ 2–2 2.3 Can Both RTR Version 2 and
Inhaltszusammenfassung zur Seite Nr. 4
5 System Management 5.1 OpenVMS Quotas............................................ 5–1 5.2 Startup.................................................... 5–1 5.3 Creating Facilities . . . ........................................ 5–1 5.3.1 Naming Nodes . . . ........................................ 5–1 5.3.2 Modifying Facility Configurations ............................ 5–1 5.4 Interoperability ............................................. 5–2 5.5 Monitoring . ........................................
Inhaltszusammenfassung zur Seite Nr. 5
Index Tables 2–1 OpenVMS Limits . ........................................ 2–3 2–2 OpenVMS Disk Requirements ............................... 2–5 3–1 RTR Executables . ........................................ 3–1 5–1 Interoperability Between Nodes.............................. 5–2 5–2 Obsolete RTR Version 2 Monitor Pictures ...................... 5–2 5–3 New RTR Version 3 Monitor Pictures . . ....................... 5–3 5–4 Changed SHOW COMMANDS............................... 5–4 5–5 Obsolete Ope
Inhaltszusammenfassung zur Seite Nr. 6
Inhaltszusammenfassung zur Seite Nr. 7
Preface This guide explains how to migrate a Reliable Transaction Router (RTR) environment and RTR applications from RTR Version 2 to RTR Version 3. It assumes that the application continues to use the RTR Version 2 application programming interface (API) without change. It also provides information on new and obsolete features. Audience This guide is written for RTR system managers. The system manager should be familiar with the following aspects of the OpenVMS operating system: • DIGITAL Comma
Inhaltszusammenfassung zur Seite Nr. 8
Related Documents The following documents provide more information about topics discussed in this guide: Document Title Description Reliable Transaction Router Describes how to install Reliable Transaction Router. Installation Guide Reliable Transaction Router Describes how to configure, manage, and monitor System Manager’s Manual Reliable Transaction Router Reliable Transaction Router Describes how to code RTR applications, and contains Application Programmer’s full descriptions of RTR API calls
Inhaltszusammenfassung zur Seite Nr. 9
Convention Meaning monospace Indicates the actual commands, words, or characters that you type in a dialog box, at a command prompt, or system output. Note: Provides information of special importance. / A forward slash in command descriptions indicates that a command qualifier follows. . . . A horizontal ellipsis following an entry in a command line indicates that the entry or a similar entry can be repeated any number of times. An ellipsis following a file name indicates that additional parameter
Inhaltszusammenfassung zur Seite Nr. 10
Inhaltszusammenfassung zur Seite Nr. 11
1 Introduction This document is intended to assist RTR Version 2 users to migrate to RTR Version 3. 1.1 Why Migrate? Migration to RTR Version 3 takes advantage of the new features and improved capabilities of RTR Version 3. These include: • Improved installation procedure using Polycenter Software Installation Utility (PCSI), not VMSINSTAL • Interoperability with multiple operating systems including: OpenVMS (Alpha and VAX) UNIX (DIGITAL UNIX, SUN Solaris, IBM AIX, HP–UX) Windows NT Windows 95 (
Inhaltszusammenfassung zur Seite Nr. 12
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.
Inhaltszusammenfassung zur Seite Nr. 13
2 Installation The installation for RTR Version 3 has changed significantly from Version 2. In Version 2, the installation tool was VMSINSTAL; for Version 3, the installation tool is PCSI. Follow instructions in the Reliable Transaction Router Installation Guide to perform your RTR Version 3 installation. Note Reading Release Notes in RTR Version 3 is different from in RTR Version 2. See the Reliable Transaction Router Installation Guide for information on installing the product and reading relea
Inhaltszusammenfassung zur Seite Nr. 14
Installation 2.2 Preserving the Old Environment 2.2 Preserving the Old Environment Applications that run in the RTR Version 2 environment on OpenVMS systems will run in the RTR Version 3 environment on OpenVMS systems. However, as part of your testing and verification of the new environment, you should check that an RTR Version 2 application runs as expected after the upgrade. You cannot mix RTR Version 2 and Version 3 routers and back-end systems; all routers and back-end systems in a facility m
Inhaltszusammenfassung zur Seite Nr. 15
Installation 2.5 Process Quotas Table 2–1 OpenVMS Limits Value for Limit Name OpenVMS Name Value for ACP Application AST queue limit ASTlm 2000 or more Byte count limit Bytlm 32K + (32K * appn †) Not less than 100K Buffered I/O count BIOlm Not less than 3 * appn limit Direct I/O count limit DIOlm 2000 or more Paging file limit Pgflquo Not less than 200K Timer Queue Entry TQElm 2000 or more limit †In the table, appn is the number of application processes. For more information on these limits, see t
Inhaltszusammenfassung zur Seite Nr. 16
Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal To verify that the new journal is running correctly, use the DUMP JOURNAL command to verify that transactions are processing as expected, and to be sure that all transactions have completed before bringing down RTR to install RTR Version 3. There is no need to save the old journal file once all transactions have cleared. 2.6.2 Journal Compatibility RTR Version 2 journal files are incompatible with RTR Version 3 journal files. No tools e
Inhaltszusammenfassung zur Seite Nr. 17
Installation 2.8 Memory and Disk Requirements Table 2–2 OpenVMS Disk Requirements Requirement RTR Version 2 RTR Version 3 Disk space 40,000 blocks (20MB) 50,000 blocks (25MB) (installation) Disk space 24,000 blocks (12MB) 36,000 blocks (18MB) (permanent) 2.9 Rollback to RTR Version 2 To restore the RTR Version 2 environment if RTR Version 3 does not work with your applications as expected, use the following procedure: 1. In the RTR Version 3 environment, stop all clients so that no new transacti
Inhaltszusammenfassung zur Seite Nr. 18
Inhaltszusammenfassung zur Seite Nr. 19
3 Architectural Changes RTR Version 3 introduces certain process and other architectural changes. The following sections highlight these changes. 3.1 RTR Daemon Process In RTR Version 3, a new RTR daemon process (called RTRD) is used by the RTRACP process to build TCP/IP connections for internode links. The RTR daemon process is present only on systems with IP networking installed and with IP enabled as an RTR transport (see Chapter 4, Network Issues, for information on setting your network tran
Inhaltszusammenfassung zur Seite Nr. 20
Architectural Changes 3.3 The Shared Library (LIBRTR.EXE) Table 3–1 (Cont.) RTR Executables RTR Version 2 RTR Version 3 RTRRTL No longer apply. 3.4 The ACP Process The RTR Application Control Process (ACP) handles application control, and has the process name RTRACP. This is unchanged from RTR Version 2. 3.5 Interprocess Communication In RTR Version 2, global sections (cache) were used for interprocess communication. In RTR Version 3, interprocess communication is handled with mailboxes. Each RT
