Manuale d’uso / di manutenzione del prodotto AAR-88LB-TE del fabbricante Compaq
Vai alla pagina of 42
Reliable T ransaction Router Migration Guide Order Number: AA–R88LB–TE June 1999 This guide explains how to migrate from Reliable T ransaction Router™ (RTR) V ersion 2 to RTR V ersion 3 on OpenVMS™ systems, and provides information on new and obsolete features.
First Printing, December 1997 Revised, June 1999 COMP AQ COMPUTER CORPORA TION SHALL NOT BE LIABLE FOR TECHNICAL OR EDI‘ ERRORS OR OMISSIONS CONT AINED HEREIN, NOR FOR INCIDENT AL OR CONSEQUENTIAL DAMAGES RESUL TING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MA TERIAL.
Contents Preface ............................................................ vii 1 Introduction 1.1 Why Migrate? ............................................... 1–1 1.2 Goals and Nongoals . . ........................................ 1–2 1.3 Reading Guidelines .
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 .
Index T ables 2–1 OpenVMS Limits . ........................................ 2–3 2–2 OpenVMS Disk Requirements ............................... 2–5 3–1 RTR Executables . ........................................ 3–1 5–1 Interoperability Between Nodes .
.
Preface This guide explains how to migrate a Reliable T ransaction Router (RTR) environment and RTR applications from RTR V ersion 2 to RTR V ersion 3. It assumes that the application continues to use the RTR V ersion 2 application programming interface (API) without change.
Related Documents The following documents provide more information about topics discussed in this guide: Document Title Description Reliable T ransaction Router Installation Guide Describes how to install Reliable T ransaction Router .
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.
.
1 Introduction This document is intended to assist RTR V ersion 2 users to migrate to RTR V ersion 3. 1.1 Why Migrate? Migration to RTR V ersion 3 takes advantage of the new features and improved capabilities of RTR V ersion 3.
Introduction 1.1 Why Migrate? • Support for subtransactions or nested transactions Additionally , other considerations are: • New features will be implemented in RTR V ersion 3, not in RTR V ersio.
2 Installation The installation for RTR V ersion 3 has changed significantly from V ersion 2. In V ersion 2, the installation tool was VMSINST AL; for V ersion 3, the installation tool is PCSI. Follow instructions in the Reliable T ransaction Router Installation Guide to perform your RTR V ersion 3 installation.
Installation 2.2 Preserving the Old Environment 2.2 Preserving the Old Environment Applications that run in the RTR V ersion 2 environment on OpenVMS systems will run in the RTR V ersion 3 environment on OpenVMS systems.
Installation 2.5 Process Quotas T able 2–1 OpenVMS Limits Limit Name OpenVMS Name V alue for ACP V alue for Application AST queue limit ASTlm 2000 or more Byte count limit Bytlm 32K + (32K * appn .
Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal T o 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 V ersion 3.
Installation 2.8 Memory and Disk Requirements T able 2–2 OpenVMS Disk Requirements Requirement RTR V ersion 2 RTR V ersion 3 Disk space (installation) 40,000 blocks (20MB) 50,000 blocks (25MB) Disk space (permanent) 24,000 blocks (12MB) 36,000 blocks (18MB) 2.
.
3 Architectural Changes RTR V ersion 3 introduces certain process and other architectural changes. The following sections highlight these changes. 3.1 RTR Daemon Process In RTR V ersion 3, a new RTR daemon process (called RTRD) is used by the RTRACP process to build TCP/IP connections for internode links.
Architectural Changes 3.3 The Shared Library (LIBRTR.EXE) T able 3–1 (Cont.) RTR Executables RTR V ersion 2 RTR V ersion 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 .
Architectural Changes 3.8 Quorum Issues 3.8 Quorum Issues Network partitioning in RTR V ersion 3 is based on a router and backend count, whereas in RTR V ersion 2 it was based on quorum. However , quorum is still used in RTR V ersion 3; state names and some quorum-related displays have changed.
.
4 Network Issues W ith RTR V ersion 3, two network transports are available: • DECnet (default on OpenVMS) • TCP/IP At least one transport is required. If a destination supports both transports, RTR V ersion 3 can use either . Any node can run either protocol, but the appropriate transport software must be running on that node.
Network Issues 4.3 Specifying a Preferred T ransport 4.3 Specifying a Preferred T ransport During installation, the system manager can specify either transport, using logical names RTR_DNA_FIRST or RTR_TCP_FIRST .
5 System Management A number of changes that affect system management have been introduced with RTR V ersion 3. The following sections describe these changes. 5.1 OpenVMS Quotas RTR V ersion 2 used OpenVMS quota values specified on the RTR ST ART command or calculated defaults.
System Management 5.4 Interoperability 5.4 Interoperability All supported operating systems can interoperate together in the RTR environment, as described in T able 5–1. T able 5–1 Interoperability Between Nodes RTR V ersion 3 nodes interoperate with.
System Management 5.5 Monitoring T able 5–3 New RTR V ersion 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.
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 W ith the new support for TCP/IP , you can execute commands on remote systems using the rsh utility .
System Management 5.1 1 Interpreting Output from SHOW Commands T able 5–4 (Cont.) Changed SHOW COMMANDS Command Description SHOW TRANSACTION W ith the SHOW TRANSACTION command, you can now specify display for a frontend, backend, or router . SHOW F ACILITY/LINK The SHOW F ACILITY/LINK command provides new information on states.
System Management 5.12 Comparing RTR V ersion 2 and V ersion 3 Utility Commands T able 5–6 (Cont.) New OpenVMS RTR Utility Commands Command Name Description QUIT Exits RTR. REGISTER RM 1 Registers resource managers with the current transaction manager .
6 Running V ersion 2 Applications In this chapter the term OpenVMS API refers to the Reliable T ransaction Router for OpenVMS V ersion 2. The term Portable API refers to the API used in Reliable T ransaction Router for OpenVMS V ersion 3.
Running V ersion 2 Applications 6.1 Comparison of OpenVMS API and Portable API T able 6–1 OpenVMS API and Portable API Comparison OpenVMS API (V ersion 2) Portable API (V ersion 3) $dcl_tx_prc( ) rt.
Running V ersion 2 Applications 6.2 Recompiling and Relinking 6.2.1 RTR V ersion 2 Applications Running on RTR V ersion 3 • Linking V ersion 2 applications Existing RTR V ersion 2 applications will run if they have been linked against RTRSHR. (RTRSHR has been superseded by LIBRTR.
Running V ersion 2 Applications 6.3 Running Applications Installed with Privileges 6.3 Running Applications Installed with Privileges W ith RTR V ersion 2, RTR calls execute in kernel mode; with RTR V ersion 3, RTR runs in application process mode, normally user mode.
Running V ersion 2 Applications 6.6 Threaded Applications 6.6 Threaded Applications W ith RTR V ersion 3, applications that rely on threading may not work exactly the same way they worked with RTR V ersion 2 on OpenVMS. Applications that use kernel threads with RTR V ersion 2 will not work with RTR V ersion 3.
.
7 Performance T ips W ith RTR V ersion 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.
Performance Tips 7.6 Simultaneous Multiprocessing 7.6 Simultaneous Multiprocessing W ith RTR V ersion 2, threaded applications could use Symmetric Multiprocessing (SMP) effectively . In RTR V ersion 3, SMP will not provide the performance advantages of RTR V ersion 2.
8 Problem Diagnosis and Reporting RTR V ersion 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 • the dump file (.
Problem Diagnosis and Reporting 8.4 Producing and Directing a T race or set trace/subsystem=(API, CIF, CRM) Starts the trace on subsystems API, CIF and CRM. 4. set mode/nounsupported Sets mode to supported. . T race continues. . T race continues. 5. set mode/unsupp Sets mode to unsupported.
Index A ABORT command, 6–3 ANAL YZE/SYSTEM, 8–2 API OpenVMS, 6–1 Portable, 6–1 API (defined), vii B Back ends, 2–2 C Cache, 3–2 Call RTR_<routine>, 5–6 Call stack, 8–1 Channel n.
M MONITOR, 7–1 Monitor pictures, 5–2 MONITOR QUORUM, 3–3 Multihoming, 4–1 Multiple network transports, 4–1 N Name server, 4–1 Nested transactions, 1–2 Network partition, 3–3 O OpenVMS .
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Compaq AAR-88LB-TE è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Compaq AAR-88LB-TE - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Compaq AAR-88LB-TE imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Compaq AAR-88LB-TE ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Compaq AAR-88LB-TE, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Compaq AAR-88LB-TE.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Compaq AAR-88LB-TE. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Compaq AAR-88LB-TE insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
