English dropdown-ico

Compaq AAR-88LB-TE manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Compaq AAR-88LB-TE, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Compaq AAR-88LB-TE one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Compaq AAR-88LB-TE. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Compaq AAR-88LB-TE should contain:
- informations concerning technical data of Compaq AAR-88LB-TE
- name of the manufacturer and a year of construction of the Compaq AAR-88LB-TE item
- rules of operation, control and maintenance of the Compaq AAR-88LB-TE item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Compaq AAR-88LB-TE alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Compaq AAR-88LB-TE, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Compaq service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Compaq AAR-88LB-TE.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Compaq AAR-88LB-TE item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    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. Revision/Update Information: This guide supersedes the Reliable T ransaction Rou[...]

  • Page 2

    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. THIS INFORMA TION IS PROVIDED "AS IS" AND COMP AQ COMPUTER COR[...]

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

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

  • Page 5

    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 .............................. 5–2 5–2 Obsolete RTR V ersion 2 Monitor Pictures ....[...]

  • Page 6

    [...]

  • Page 7

    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. It also provides information on new and obsolete features. Audience This g[...]

  • Page 8

    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 . Reliable T ransaction Router System Manager ’ s Manual Describes how to configure, manage, and monitor Reliable[...]

  • 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. . . . A horizontal ellipsis following an entry in a command li[...]

  • Page 10

    [...]

  • Page 11

    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. These include: • Improved installation procedure using Polycenter Software Installation Utility (PCSI), not VMSINST AL ?[...]

  • Page 12

    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 ersion 2 • Some software problems will be addressed only in RTR V ersion 3 and not in RTR V ersion 2 • Some improved capabilities are already available[...]

  • Page 13

    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. Note Reading Release Notes in RTR V[...]

  • Page 14

    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. However , as part of your testing and verification of the new environment, you should check that an RTR V ersion 2 application r[...]

  • Page 15

    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 †) Not less than 100K Buffered I/O count limit BIOlm Not less than 3 * appn Direct I/O count limit DIOlm 2000 or more Paging file limit Pgflquo Not [...]

  • Page 16

    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. There is no need to save the old journal ?[...]

  • Page 17

    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.9 Rollback to RTR V ersion 2 T o restore the RTR V ersion 2 environment if RTR V ersion [...]

  • Page 18

    [...]

  • Page 19

    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. The RTR daemon process is present only on s[...]

  • Page 20

    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 . This is unchanged from RTR V ersion 2. 3.5 Interprocess Communication In RT[...]

  • Page 21

    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. Additionally , the quorum-related condition of a node [...]

  • Page 22

    [...]

  • Page 23

    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. For example, for[...]

  • Page 24

    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 . For example, in the RTR$ST ARTUP .COM file (found in SYS$ST ARTUP), the following line specifies DECnet as the default transport: $ DE[...]

  • Page 25

    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. Because RTR V ersion 3 uses dynamic allocation (with the exception of [...]

  • Page 26

    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... Description Other RTR V ersion 2 nodes In RTR V ersion 3, RTR uses data marshalling (examina[...]

  • Page 27

    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. broadcast Shows information about RTR user events by process. connec[...]

  • Page 28

    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 . T o use this feature, check your operating syst[...]

  • Page 29

    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. SHOW P ARTITION /F[...]

  • Page 30

    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 . SET P ARTITION Sets partition properties. SET TRANSACTION Changes the state of a transaction. [...]

  • Page 31

    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. W ith RTR V ersion 3, the Portable API provides: • Portability over a wide range of language and machine envi[...]

  • Page 32

    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( ) rtr_open_channel( ) $start_tx( ) rtr_start_tx( ) [optional] $commit_tx( ) rtr_accept_tx( ) $abort_tx( ) rtr_reject_tx( ) $vote_tx( ) rtr_accept_tx( ) rt[...]

  • Page 33

    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.EXE. Existing RTR V ersion 2 application executables will run witho[...]

  • Page 34

    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. 6.3.1 Running Clients That Share Channels W ith RTR V ersion 2, clients that star[...]

  • Page 35

    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. RTR V ersion 2 was thread-reentrant, b[...]

  • Page 36

    [...]

  • Page 37

    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. Check the RTR Installation Guide for the specific formula to use. 7.2 Journal Sizing W i[...]

  • Page 38

    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. The single control process of RTRACP in RTR V ersion 3 does not take advantage of[...]

  • Page 39

    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 (.DMP), a binary crash dump that, if needed, must be sent to your support se[...]

  • Page 40

    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. 6. set trace Stops the trace. 7. set mode/nounsupp Sets mo[...]

  • Page 41

    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 number, 6–3 CLI, 5–4 Command ABORT, 6–3 CREA TE P ARTITION, 5–6 DELETE P ARTITION, 5–6 DISPLA Y STRING, 5–6 DUMP JOURNAL, 2–4, 5–6 EXEC[...]

  • Page 42

    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 API, 6–1 P Partition network, 3–3 Partition states server-process, 3–3 PCSI (defined), 1–1 Pictures monitor, 5–2 Portable API, 6–1 Proces[...]