Page 3 - Contents; Preface; vii; Introduction
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 1 Introduction 1.1 Why Migrate? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 1.2 Goals and Nongoals . . . ...
Page 7 - Audience
Preface This guide explains how to migrate a Reliable Transaction Router (RTR)environment and RTR applications from RTR Version 2 to RTR Version 3. Itassumes that the application continues to use the RTR Version 2 applicationprogramming interface (API) without change. It also provides information on...
Page 8 - Related Documents; Reader’s Comments; The following conventions are used in this document.
Related Documents The following documents provide more information about topics discussed in thisguide: Document Title Description Reliable Transaction RouterInstallation Guide Describes how to install Reliable Transaction Router. Reliable Transaction RouterSystem Manager ’s Manual Describes how to ...
Page 9 - monospace
Convention Meaning monospace Indicates the actual commands, words, or characters that you typein 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 commandqualifier follows. . . . A horizon...
Page 11 - Introduction
1 Introduction This document is intended to assist RTR Version 2 users to migrate to RTRVersion 3. 1.1 Why Migrate? Migration to RTR Version 3 takes advantage of the new features and improvedcapabilities of RTR Version 3. These include: • Improved installation procedure using Polycenter Software Ins...
Page 12 - Note; Goals and Nongoals
Introduction1.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 inRTR Version 2 • Some improved...
Page 13 - Installation; Cleaning Up the Old Version 2 Environment
2 Installation The installation for RTR Version 3 has changed significantly from Version 2. InVersion 2, the installation tool was VMSINSTAL; for Version 3, the installationtool is PCSI. Follow instructions in the Reliable Transaction Router InstallationGuide to perform your RTR Version 3 installati...
Page 15 - Table 2–1 OpenVMS Limits
Installation 2.5 Process Quotas Table 2–1 OpenVMS Limits Limit Name OpenVMS Name Value for ACP Value forApplication AST queue limit ASTlm 2000 or more Byte count limit Bytlm 32K + (32K * appn †) Not less than100K Buffered I/O countlimit BIOlm Not less than 3 * appn Direct I/O count limit DIOlm 2000 ...
Page 16 - Rights and Privileges
Installation2.6 Journal Issues 2.6.1 Removing the Old Journal To verify that the new journal is running correctly, use the DUMP JOURNALcommand to verify that transactions are processing as expected, and to be surethat all transactions have completed before bringing down RTR to install RTRVersion 3. ...
Page 17 - Table 2–2 OpenVMS Disk Requirements; Rollback to RTR Version 2
Installation 2.8 Memory and Disk Requirements Table 2–2 OpenVMS Disk Requirements Requirement RTR Version 2 RTR Version 3 Disk space(installation) 40,000 blocks (20MB) 50,000 blocks (25MB) Disk space(permanent) 24,000 blocks (12MB) 36,000 blocks (18MB) 2.9 Rollback to RTR Version 2 To restore the RT...
Page 19 - Architectural Changes; RTR Daemon Process; Command server timeouts are the same in RTR V3 as in RTR V2.; Table 3–1 RTR Executables
3 Architectural Changes RTR Version 3 introduces certain process and other architectural changes. Thefollowing sections highlight these changes. 3.1 RTR Daemon Process In RTR Version 3, a new RTR daemon process (called RTRD) is used by theRTRACP process to build TCP/IP connections for internode link...
Page 20 - Interprocess Communication
Architectural Changes3.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 hasthe process name RTRACP. This is unchanged from RTR Version...
Page 21 - Primary
Architectural Changes 3.8 Quorum Issues 3.8 Quorum Issues Network partitioning in RTR Version 3 is based on a router and backend count,whereas in RTR Version 2 it was based on quorum. However, quorum is still usedin RTR Version 3; state names and some quorum-related displays have changed. Additional...
Page 23 - Network Issues; With RTR Version 3, two network transports are available:
4 Network Issues With RTR Version 3, two network transports are available: • DECnet (default on OpenVMS) • TCP/IP At least one transport is required. If a destination supports both transports, RTRVersion 3 can use either. Any node can run either protocol, but the appropriate transport software must ...
Page 24 - Specifying a Preferred Transport; or
Network Issues4.3 Specifying a Preferred Transport 4.3 Specifying a Preferred Transport During installation, the system manager can specify either transport,using logical names RTR_DNA_FIRST or RTR_TCP_FIRST . For example, in the RTR$STARTUP.COM file (found in SYS$STARTUP), the following line specif...
Page 25 - System Management; Creating Facilities
5 System Management A number of changes that affect system management have been introduced withRTR Version 3. The following sections describe these changes. 5.1 OpenVMS Quotas RTR Version 2 used OpenVMS quota values specified on the RTR STARTcommand or calculated defaults. Because RTR Version 3 uses...
Page 26 - Table 5–1 Interoperability Between Nodes; Table 5–2 Obsolete RTR Version 2 Monitor Pictures; Table 5–3 lists the monitor screens that are new to RTR Version 3.
System Management5.4 Interoperability 5.4 Interoperability All supported operating systems can interoperate together in the RTRenvironment, as described in Table 5–1. Table 5–1 Interoperability Between Nodes RTR Version 3 nodesinteroperate with... Description Other RTR Version 2nodes In RTR Version ...
Page 27 - Table 5–3 New RTR Version 3 Monitor Pictures
System Management 5.5 Monitoring Table 5–3 New RTR Version 3 Monitor Pictures Picture Description accfail Shows most recent links on which a connection attempt was declined. acp2app Shows RTRACP-to-application message counts. app2acp Shows application-to-RTRACP message counts. broadcast Shows inform...
Page 28 - Table 5–4 Changed SHOW COMMANDS
System Management5.5 Monitoring 5.5.5 History Screens New monitor screens that show partition state or network connection historyinclude MONITOR accfail and MONITOR rscbe. 5.6 Remote Command Support With the new support for TCP/IP, you can execute commands on remote systemsusing the rsh utility. To ...
Page 29 - Comparing RTR Version 2 and Version 3 Utility Commands; Table 5–6 lists commands that are new to RTR Version 3.; Table 5–6 New OpenVMS RTR Utility Commands
System Management 5.11 Interpreting Output from SHOW Commands Table 5–4 (Cont.) Changed SHOW COMMANDS Command Description SHOW TRANSACTION With the SHOW TRANSACTION command, you can now specify display for a frontend, backend, or router. SHOW FACILITY/LINK The SHOW FACILITY/LINK command provides new...
Page 31 - Running Version 2 Applications; With RTR Version 3, the Portable API provides:; Comparison of OpenVMS API and Portable API; Table 6–1 lists the OpenVMS API and comparable Portable API calls.
6 Running Version 2 Applications In this chapter the term OpenVMS API refers to the Reliable Transaction Routerfor OpenVMS Version 2. The term Portable API refers to the API used in ReliableTransaction Router for OpenVMS Version 3. With RTR Version 3, the Portable API provides: • Portability over a ...
Page 32 - Table 6–1 OpenVMS API and Portable API Comparison; Recompiling and Relinking; An existing RTR Version 2 application will run on RTR Version 3.
Running Version 2 Applications6.1 Comparison of OpenVMS API and Portable API Table 6–1 OpenVMS API and Portable API Comparison OpenVMS API (Version 2) Portable API (Version 3) $dcl_tx_prc( ) rtr_open_channel( ) $start_tx( ) rtr_start_tx( ) [optional] $commit_tx( ) rtr_accept_tx( ) $abort_tx( ) rtr_r...
Page 33 - Linking Version 2 applications; Channel number
Running Version 2 Applications 6.2 Recompiling and Relinking 6.2.1 RTR Version 2 Applications Running on RTR Version 3 • Linking Version 2 applications Existing RTR Version 2 applications will run if they have been linkedagainst RTRSHR. (RTRSHR has been superseded by LIBRTR.EXE. ExistingRTR Version ...
Page 34 - Running Applications Installed with Privileges; Running Clients That Share Channels; Application Level Interoperability; Table 6–2 Application Interoperability
Running Version 2 Applications6.3 Running Applications Installed with Privileges 6.3 Running Applications Installed with Privileges With RTR Version 2, RTR calls execute in kernel mode; with RTR Version 3, RTRruns in application process mode, normally user mode. 6.3.1 Running Clients That Share Chan...
Page 35 - Threaded Applications
Running Version 2 Applications 6.6 Threaded Applications 6.6 Threaded Applications With RTR Version 3, applications that rely on threading may not work exactlythe same way they worked with RTR Version 2 on OpenVMS. Applications that use kernel threads with RTR Version 2 will not work with RTRVersion...
Page 37 - Performance Tips; RTR Startup Qualifiers
7 Performance Tips With RTR Version 3, there are several considerations for improving performance.These are described in the following sections. 7.1 Process Quotas OpenVMS process quotas should be increased to accomodate the use of mailboxesfor processes. Check the RTR Installation Guide for the spe...
Page 38 - Simultaneous Multiprocessing
Performance Tips7.6 Simultaneous Multiprocessing 7.6 Simultaneous Multiprocessing With RTR Version 2, threaded applications could use Symmetric Multiprocessing(SMP) effectively. In RTR Version 3, SMP will not provide the performanceadvantages of RTR Version 2. The single control process of RTRACP in...
Page 39 - Problem Diagnosis and Reporting; Producing and Directing a Trace
8 Problem Diagnosis and Reporting RTR Version 3 provides a new error log and logical names to assist tracing errorsincluding: • the RTR operator log file, capturing events that occur, and useful for diagnosisof problems • the RTR_ERROR.LOG file • the dump file (.DMP), a binary crash dump that, if ne...
Page 40 - set mode/nounsupported; set trace; Dealing with a Looping Process; SHOW PROCESS RTRACP/CONTINUOUS; Lower the priority of the ACP process.; ANALYZE/SYSTEM SET PROCESS RTRACP; Enter the; Contents of the RTR Journal File; DUMP JOURNAL
Problem Diagnosis and Reporting8.4 Producing and Directing a Trace or set trace/subsystem=(API, CIF, CRM) Starts the trace on subsystems API, CIF andCRM. 4. set mode/nounsupported Sets mode to supported. . Trace continues. . Trace continues. 5. set mode/unsupp Sets mode to unsupported. 6. set trace ...
Page 41 - Index
Index A ABORT command, 6–3ANALYZE/SYSTEM, 8–2API OpenVMS, 6–1Portable, 6–1 API (defined), vii B Back ends, 2–2 C Cache, 3–2Call RTR_<routine>, 5–6Call stack, 8–1Channel number, 6–3CLI, 5–4Command ABORT, 6–3CREATE PARTITION, 5–6DELETE PARTITION, 5–6DISPLAY STRING, 5–6DUMP JOURNAL, 2–4, 5–6EXECU...
