Compaq AAR-88LB-TE Migration Manual
  1. Manuals
  2. Brands
  3. Compaq Manuals
  4. Software
  5. AAR-88LB-TE
  6. Migration manual
Compaq AAR-88LB-TE Migration Manual

Compaq AAR-88LB-TE Migration Manual

Rtr version 2 to rtr version 3
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual

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:
Operating System:
Software Version:
Compaq Computer Corporation
Houston, Texas
This guide supersedes the Reliable
Transaction Router Migration Guide
for Version 3.1D.
OpenVMS Versions 6.2, 7.1, 7.2
Reliable Transaction Router Version
3.2

Advertisement

Table of Contents
loading

Related Manuals for Compaq AAR-88LB-TE

Summary of Contents for Compaq AAR-88LB-TE

  • Page 1: Reliable Transaction Router

    (RTR) Version 2 to RTR Version 3 on OpenVMS™ systems, and provides information on new and obsolete features. Revision/Update Information: Operating System: Software Version: Compaq Computer Corporation Houston, Texas This guide supersedes the Reliable Transaction Router Migration Guide for Version 3.1D.
  • Page 2 The software may be used or copied only in accordance with the terms of the agreement. Compaq and the Compaq logo are registered in the United States Patent and Trademark Office. The following are trademarks of Compaq Computer Corporation: AlphaGeneration, AlphaServer,...

  • Page 3: Table Of Contents

    Preface ............1 Introduction Why Migrate? .
  • Page 4 5 System Management OpenVMS Quotas ..........Startup .
  • Page 5 Index Tables 2–1 OpenVMS Limits ......... 2–2 OpenVMS Disk Requirements .

  • Page 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.

  • Page 8: Related Documents

    Reference Manual for OpenVMS Reader’s Comments Compaq welcomes your comments on this guide. Please send us your comments by email to rtrdoc@compaq.com. Include the title of the manual, date on the title page, section and page numbers with your comments or suggestions. Conventions The following conventions are used in this document.
  • Page 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.

  • Page 11: 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 •...

  • Page 12: Goals And Nongoals

    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 •...

  • Page 13: 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. Reading Release Notes in RTR Version 3 is different from in RTR Version 2.

  • Page 14: Preserving The Old Environment

    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.

  • Page 15: Journal Issues

    Table 2–1 OpenVMS Limits Limit Name AST queue limit Byte count limit Buffered I/O count limit Direct I/O count limit Paging file limit Timer Queue Entry limit †In the table, appn is the number of application processes. For more information on these limits, see the OpenVMS System Manager’s Manual: Essentials.

  • Page 16: Removing The Old Journal

    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.

  • Page 17: Rollback To Rtr Version

    Table 2–2 OpenVMS Disk Requirements Requirement Disk space (installation) Disk space (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.

  • Page 19: 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 transport).

  • Page 20: The Acp Process

    Architectural Changes 3.3 The Shared Library (LIBRTR.EXE) Table 3–1 (Cont.) RTR Executables RTR Version 2 RTRRTL 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.

  • Page 21: 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 used in RTR Version 3; state names and some quorum-related displays have changed. Additionally, the quorum-related condition of a node in a minority network partition is handled more gracefully in RTR Version 3.

  • Page 23: Network Issues

    IP address. RTR does name lookups and name address translations, as appropriate, using a name server. To use multihomed and TCP/IP addresses, Compaq recommends that you have a local name server that provides the names and addresses for all RTR nodes. The local name server should be available and responsive.

  • Page 24: Specifying A Preferred Transport

    Network Issues 4.3 Specifying a Preferred Transport 4.3 Specifying a Preferred Transport During installation, the system manager can specify either transport, using logical names RTR$STARTUP.COM file (found in SYS$STARTUP), the following line specifies DECnet as the default transport: $ DEFINE/SYSTEM RTR_PREF_PROT RTR_DNA_FIRST To set the default transport to TCP/IP, remove (comment out) this definition from RTR$STARTUP.COM and restart RTR.

  • Page 25: System Management

    A number of changes that affect system management have been introduced with RTR Version 3. The following sections describe these changes. 5.1 OpenVMS Quotas RTR Version 2 used OpenVMS quota values specified on the RTR START command or calculated defaults. Because RTR Version 3 uses dynamic allocation (with the exception of the number of partitions that is statically defined), RTR does not calculate the required quotas, but depends on the system manager to configure quotas adequately.

  • Page 26: Interoperability

    System Management 5.4 Interoperability 5.4 Interoperability All supported operating systems can interoperate together in the RTR environment, as described in Table 5–1. Table 5–1 Interoperability Between Nodes RTR Version 3 nodes interoperate with... Other RTR Version 2 nodes Other RTR Version 3 nodes 5.5 Monitoring Several screens that provide dynamic information on transactions and system...

  • Page 27: User Parsing Of Monitor Output

    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 information about RTR user events by process. connect Renamed to netstat.

  • Page 28: History Screens

    System Management 5.5 Monitoring 5.5.5 History Screens New monitor screens that show partition state or network connection history include MONITOR accfail and MONITOR rscbe. 5.6 Remote Command Support With the new support for TCP/IP, you can execute commands on remote systems using the rsh utility.

  • Page 29: Comparing Rtr Version 2 And Version 3 Utility Commands

    Table 5–4 (Cont.) Changed SHOW COMMANDS Command SHOW TRANSACTION SHOW FACILITY/LINK SHOW PARTITION /FULL 5.12 Comparing RTR Version 2 and Version 3 Utility Commands Table 5–5 lists obsolete RTR Version 2 commands; they do not appear in RTR Version 3. In general, they no longer apply. In a mixed RTR Version 2 and Versio n3 environment, you cannot execute commands remotely from a Version 3 to a Version 2 system, or vice versa, with the /NODE qualifier.
  • Page 30 System Management 5.12 Comparing RTR Version 2 and Version 3 Utility Commands Table 5–6 (Cont.) New OpenVMS RTR Utility Commands Command Name QUIT REGISTER RM SET PARTITION SET TRANSACTION SHOW CLIENT SHOW RM UNREGISTER RM UNIX and NT only 5–6 System Management Description Exits RTR.

  • Page 31: Running Version 2 Applications

    Running Version 2 Applications In this chapter the term OpenVMS API refers to the Reliable Transaction Router for OpenVMS Version 2. The term Portable API refers to the API used in Reliable Transaction Router for OpenVMS Version 3. With RTR Version 3, the Portable API provides: •...

  • Page 32: Recompiling And Relinking

    Running Version 2 Applications 6.1 Comparison of OpenVMS API and Portable API Table 6–1 OpenVMS API and Portable API Comparison OpenVMS API (Version 2) $dcl_tx_prc( ) $start_tx( ) $commit_tx( ) $abort_tx( ) $vote_tx( ) $deq_tx( ) $enq_tx( ) $dcl_tx_prc( ) (SHUT) $get_txi( ) $set_txi( ) ASTPRM (on asynch calls)

  • Page 33: Rtr Version 2 Applications Running On Rtr Version

    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 linked against RTRSHR. (RTRSHR has been superseded by LIBRTR.EXE. Existing RTR Version 2 application executables will run without relinking since RTR$STARTUP.COM defines RTRSHR as a logical name that points to LIBRTR.EXE.) However, as RTRSHR.EXE is no longer distributed, change the linker options...

  • Page 34: Running Applications Installed With Privileges

    Running Version 2 Applications 6.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, RTR runs in application process mode, normally user mode. 6.3.1 Running Clients That Share Channels With RTR Version 2, clients that start up and declare channels could use the flag INHNOSRVWT (inhibit-no server-wait) to proceed without waiting.

  • Page 35: Threaded Applications

    6.6 Threaded Applications With RTR Version 3, applications that rely on threading may not work exactly the same way they worked with RTR Version 2 on OpenVMS. Applications that use kernel threads with RTR Version 2 will not work with RTR Version 3.

  • Page 37: 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 mailboxes for processes. Check the RTR Installation Guide for the specific formula to use. 7.2 Journal Sizing With RTR, the larger the journal, the more time it takes to read it.

  • Page 38: Simultaneous Multiprocessing

    Performance Tips 7.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 performance advantages of RTR Version 2. The single control process of RTRACP in RTR Version 3 does not take advantage of an SMP configuration.

  • Page 39: Problem Diagnosis And Reporting

    Problem Diagnosis and Reporting RTR Version 3 provides a new error log and logical names to assist tracing errors including: • the RTR operator log file, capturing events that occur, and useful for diagnosis of problems • the RTR_ERROR.LOG file •...

  • Page 40: Dealing With A Looping Process

    Problem Diagnosis and Reporting 8.4 Producing and Directing a Trace set trace/subsystem=(API, CIF, CRM) set mode/nounsupported set mode/unsupp set trace set mode/nounsupp Running a trace can affect performance, so be sure to turn it off again when done (see step 6). 8.5 Dealing with a Looping Process If your system appears to be hung, this may be caused by an RTR process looping.
  • Page 41 ABORT command, 6–3 ANALYZE/SYSTEM, 8–2 OpenVMS, 6–1 Portable, 6–1 API (defined), vii Back ends, 2–2 Cache, 3–2 Call RTR_<routine>, 5–6 Call stack, 8–1 Channel number, 6–3 CLI, 5–4 Command ABORT, 6–3 CREATE PARTITION, 5–6 DELETE PARTITION, 5–6 DISPLAY STRING, 5–6 DUMP JOURNAL, 2–4, 5–6 EXECUTE, 5–6 QUIT, 5–6...
  • Page 42 MONITOR, 7–1 Monitor pictures, 5–2 MONITOR QUORUM, 3–3 Multihoming, 4–1 Multiple network transports, 4–1 Name server, 4–1 Nested transactions, 1–2 Network partition, 3–3 OpenVMS API, 6–1 Partition network, 3–3 Partition states server-process, 3–3 PCSI (defined), 1–1 Pictures monitor, 5–2 Portable API, 6–1 Process counters, 3–2 Process states, 3–3 Protocol selection, 4–2...

This manual is also suitable for:

Reliable transaction router

Table of Contents