Résumé du contenu de la page N° 1
Reliable Transaction Router
System Manager’s Manual
Order Number: AA-Q88CE-TE
June, 1999
This manual describes how to configure, manage and monitor Reliable
Transaction Router, Version 3.2 (RTR).
Revision/Update Information: This manual supersedes Version 3.1D
of the System Manager’s Manual
Software Version: Reliable Transaction Router, Version
3.2
Compaq Computer Corporation
Houston, Texas
Résumé du contenu de la page N° 2
June, 1999 COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL 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 TITLE AND AGAINST INFRINGEMENT. Th
Résumé du contenu de la page N° 3
Contents Preface ............................................................ xi 1 Introduction 1.1 Getting Started ............................................. 1–1 1.2 Entering Commands . ........................................ 1–1 1.3 Online Help ................................................ 1–2 1.4 Command Procedures ........................................ 1–3 1.5 Remote Commands . . ........................................ 1–3 2 Starting and Setting Up RTR 2.1 Introduction ............
Résumé du contenu de la page N° 4
3.3 Life Cycle of a Partition . . . .................................... 3–2 3.3.1 Implicit Partition Creation.................................. 3–3 3.3.2 Explicit Partition Creation.................................. 3–3 3.3.3 Persistence of Partition Definitions ........................... 3–3 3.4 Binding Server Channels to Named Partitions . . ................... 3–3 3.5 Entering Partition Commands .................................. 3–4 3.5.1 Command Line Usage . ...............................
Résumé du contenu de la page N° 5
5.2.14 Monitor IPCRATE ........................................ 5–10 5.2.15 Monitor Journal . . ........................................ 5–10 5.2.16 Monitor Link ............................................ 5–11 5.2.17 Monitor Netbytes . ........................................ 5–11 5.2.18 Monitor Netstat . . ........................................ 5–12 5.2.19 Monitor Partit . . . ........................................ 5–12 5.2.20 Monitor Queues . . ........................................ 5–
Résumé du contenu de la page N° 6
DISPLAY BAR . . ............................................ 6–67 DISPLAY NUMERIC ......................................... 6–72 DISPLAY STRING........................................... 6–77 DISPLAY SYMBOLIC ........................................ 6–81 DISPLAY TEXT . ............................................ 6–83 DO ....................................................... 6–86 FLUSH NAME_CACHE . . . .................................... 6–88 EXECUTE ...........................................
Résumé du contenu de la page N° 7
STOP RTR . ................................................ 6–177 TRIM FACILITY ............................................ 6–179 UNREGISTER RESOURCE MANAGER (UNREGISTER RM) . . ....... 6–182 A Creating Monitor Pictures A.1 Interactive Definition of a Monitor Picture . ....................... A–2 A.2 Substitution Symbols . ........................................ A–3 A.3 Arithmetic Expressions and Operators............................ A–3 B Server Shadowing and Recovery B.1 Primary and Secondary
Résumé du contenu de la page N° 8
Figures 2–1 Configuration Example .................................... 2–2 2–2 Extend Configuration Example . . ............................ 2–6 A–1 Interactively Defined Monitor Picture ......................... A–3 B–1 Four Node Shadow/Standby Configuration . . . ................... B–4 B–2 Server States ............................................ B–7 B–3 Client States ............................................ B–8 B–4 Router Partition States .................................... B–9 Tables 1 Co
Résumé du contenu de la page N° 9
A–3 Arithmetic Operators in Display Commands .................... A–4 ix
Résumé du contenu de la page N° 10
Résumé du contenu de la page N° 11
Preface Purpose of this Manual This manual describes how to configure, manage and monitor the operation of Reliable Transaction Router (RTR) using the RTR Command Line Interface (CLI). Intended Audience The System Manager’s Manual is intended for persons who perform system management functions to configure, test, monitor and maintain RTR applications. The reader is assumed to be familiar with their operating system, but not necessarily experienced with RTR operations. New users of RTR are encourag
Résumé du contenu de la page N° 12
Related Documentation • Release Notes • Installation Guide • Application Programmer’s Reference Manual • Application Design Guide • Migration Guide Reader’s Comments Compaq welcomes your comments on this manual. Please send us your comments by email to rtrdoc@compaq.com. Include the title of the manual, section and page numbers with your comments or suggestions. Conventions Table 1 describes the conventions used in this guide. xii
Résumé du contenu de la page N° 13
Table 1 Conventions Used in this Guide Convention Meaning UPPERCASE Some operating systems differentiate between lowercase and lowercase uppercase characters. For these systems, examples, syntax descriptions, function definitions, and literal strings that appear in text must be typed exactly as shown. Commands typed to the RTR CLI are not case sensitive unless enclosed in quote marks # A number sign ( # ) is the default operating system superuser prompt. % A percent sign ( % ) is the default oper
Résumé du contenu de la page N° 14
Résumé du contenu de la page N° 15
1 Introduction For a general introduction to Reliable Transaction Router, Version 3.2 (RTR), you should read the introductory chapter in the Reliable Transaction Router Application Design Guide. Additional information about the Reliable Transaction Router is available in the Reliable Transaction Router Application Programmer’s Reference Manual. In order to use RTR, you must install the RTR software and your application. See the Reliable Transaction Router Installation Guide for instructions for
Résumé du contenu de la page N° 16
Introduction 1.2 Entering Commands or, when several commands are to be entered at the RTR prompt: % rtr RTR> start rtr RTR> create journal Note For convenience, the user prompt for the operating system is shown here as the ‘‘%’’ symbol. Your system may have a different prompt. The RTR CLI accepts commands that you type and can process procedures consisting of RTR commands. Most RTR commands accept qualifiers: these are indicated by the forward slash (/) character. For example, many RTR commands a
Résumé du contenu de la page N° 17
Introduction 1.3 Online Help where error-identification is the identification part of the returned error. The following sequence returns an error message, RTRALRSTA, that can then be explained by the help errors rtralrsta command option: % rtr RTR> start rtr %RTR-F-RTRALRSTA, rtr already started RTR> help errors rtralrsta Errors RTRALRSTA RTR already started Explanation: RTR was already running when the "START RTR" command was executed. This error message is displayed by the RTR utility. RTR> 1.4
Résumé du contenu de la page N° 18
Introduction 1.5 Remote Commands This command starts RTR on the three nodes. Note The /CLUSTER and /NOCLUSTER command qualifiers refer to cluster support. These qualifiers are for operating systems that fully support clustering. Use of the /CLUSTER qualifier on systems that do not have clustering causes the relevant command to be executed on the local node only. For example Windows 95 systems do not support clustering. If several commands need to be executed remotely on the same nodes then the set
Résumé du contenu de la page N° 19
2 Starting and Setting Up RTR This chapter describes how to configure and start an RTR environment. Recovery journals, router load balancing and call-out servers are also discussed. 2.1 Introduction Before RTR applications can run, RTR must be started and the application’s facility must be defined on each node of the application’s environment. This is done by issuing the start rtr and create facility commands on each participating node. There are several ways to accomplish this: • You can log on t
Résumé du contenu de la page N° 20
Starting and Setting Up RTR 2.2 Setting Up—An Example Figure 2–1 Configuration Example F r o n t e n d s ( F E ) R o u t e r s ( T R ) B a c k e n d s ( B E ) F E 1 B E 1 T R 1 F E 2 B E 2 T R 2 F E 3 B E 3 SMM_CONFIG_EX 01−99 In this example, the application client processes run on the nodes FE1, FE2 and FE3. The servers run on BE1, BE2 and BE3. Nodes TR1 and TR2 are routers and have no application processes running on them. This diagram shows all possible connections. The frontend connects to o
