Compaq AA-Q88CE-TE Bedienungsanleitung

Stöbern Sie online oder laden Sie Bedienungsanleitung nach Vernetzung Compaq AA-Q88CE-TE herunter. Compaq AA-Q88CE-TE User's Manual Benutzerhandbuch

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 320
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen

Inhaltsverzeichnis

Seite 1 - SystemManager’sManual

ReliableTransactionRouterSystemManager’sManualOrder Number: AA-Q88CE-TEJune, 1999This manual describes how to configure, manage and monitor ReliableTra

Seite 3 - Contents

CALL RTR_PREPARE_TX/REASON[=reason]/REASON=0Use /REASON to supply a value for thereasonparameter in the call tortr_prepare_tx( ).The reason parameter

Seite 4 - 4 Transaction Management

CALL RTR_RECEIVE_MESSAGECALL RTR_RECEIVE_MESSAGEThe CALL RTR_RECEIVE_MESSAGE command causes a command server toexecute thertr_receive_message( )routin

Seite 5 - 6 RTR Command Line Interface

CALL RTR_RECEIVE_MESSAGEFor all messages received, RTR displays the contents of the message status block(msgsb) as follows:the message type (for examp

Seite 6

CALL RTR_RECEIVE_MESSAGE/TIMEOUT_MS=timoutms/TIMEOUT_MS=0 (D)The timoutms argument defines a timeout for the receive, in milliseconds. Thedefault value

Seite 7

CALL RTR_REJECT_TXCALL RTR_REJECT_TXThe CALL RTR_REJECT_TX command causes a command server to executethertr_reject_tx( )routine and to display the ret

Seite 8

CALL RTR_REJECT_TXchannel_nameis not case sensitive.The default channel name is RTR$DEFAULT_CHANNEL./CLUSTER/NOCLUSTER (D)Specifies that the command is

Seite 9

CALL RTR_REJECT_TXExamplesReject the current transaction with a reason of 42.RTR> CALL RTR_REJECT_TX /REASON=42%RTR-S-OK, normal successful complet

Seite 10

CALL RTR_REPLY_TO_CLIENTCALL RTR_REPLY_TO_CLIENTThe CALL RTR_REPLY_TO_CLIENT command causes a command server toexecute thertr_reply_to_client( )routin

Seite 11 - Structure of Document

CALL RTR_REPLY_TO_CLIENTTable 6–11 Parameters for rtr_reply_to_clientC Parameter Name C Parameter Value Command Line Specificationchannel /CHANNEL_NAME

Seite 12 - Conventions

CALL RTR_REPLY_TO_CLIENTTable 6–12 Generated Format StringsData Type With /LENGTH= With /NOLENGTHSTRING =n, "%nC" "%nC" where n=st

Seite 13

PrefacePurpose of this ManualThis manual describes how to configure, manage and monitor the operation ofReliable Transaction Router (RTR) using the RTR

Seite 14

CALL RTR_REPLY_TO_CLIENTExamplesThe following example replies a message to the client.RTR> CALL RTR_REPLY_TO_CLIENT "Getting that info for you

Seite 15 - Introduction

CALL RTR_REQUEST_INFOCALL RTR_REQUEST_INFOThe CALL RTR_REQUEST_INFO command causes a command server toexecute thertr_request_info( )routine and to dis

Seite 16 - 1.3 Online Help

CALL RTR_REQUEST_INFOQualifiers/CHANNEL_NAME=channel_name/CHANNEL_NAME=RTR$DEFAULT_CHANNELSpecifies the channel for which the operation is to be perform

Seite 17 - 1.5 Remote Commands

CALL RTR_REQUEST_INFOExamplesThis command requests the backend transaction IDs for the facility ‘‘CASHFAC’’.RTR> CALL RTR_REQUEST_INFO/CHANNEL=INFO

Seite 18

CALL RTR_SEND_TO_SERVERCALL RTR_SEND_TO_SERVERThe CALL RTR_SEND_TO_SERVER command causes a command server toexecute thertr_send_to_server( )routine an

Seite 19 - Starting and Setting Up RTR

CALL RTR_SEND_TO_SERVERTable 6–14 Parameters for rtr_send_to_serverC Parameter Name C Parameter Value Command Line Specificationchannel /CHANNEL_NAME=n

Seite 20 - 2.2 Setting Up—An Example

CALL RTR_SEND_TO_SERVERIf /FORMAT is specified withoutfmt-string, RTR automatically generates aformat string. The format string is generated using the

Seite 21

CALL RTR_SEND_TO_SERVERExamplesThis command sends a message to a server. The message is type string (thedefault).RTR> CALL RTR_SEND_TO_SERVER "

Seite 22 - 2.4 Changing a Facility

CALL RTR_START_TXCALL RTR_START_TXThe CALL RTR_START_TX command causes a command server to execute thertr_start_tx( )routine and to display the return

Seite 23

CALL RTR_START_TXphase cannot be executed on an client FTM channel, may be relaxed in afuture release.)When a nested transaction is started (join_txid

Seite 24

Related Documentation• Release Notes• Installation Guide• Application Programmer’s Reference Manual• Application Design Guide• Migration GuideReader’s

Seite 25

CALL RTR_START_TX/OUTPUT[=file-spec]/OUTPUT=stdout (D)Specifies that the resulting information is written to the filefile-spec.If/OUTPUTorfile-specis omi

Seite 26 - 2.6 Router Load Balancing

CLEARCLEARInteractively remove one or more displayed items from a monitor picture.FormatCLEARCommand Qualifiers Defaults/ALL /NOALL/X=column/Y=rowDescr

Seite 27 - 2.7 RTR Privileges

CLEARExamplesSee Section A.1, Interactive Definition of a Monitor Picture, for an example ofhow to use theCLEARcommand.6–46 RTR Command Line Interface

Seite 28

CREATE FACILITYCREATE FACILITYCreate an RTR facility and ready it for transaction traffic.FormatCREATE FACILITY [facility_name]Command Qualifiers Defaul

Seite 29

CREATE FACILITYQualifiers/ALL_ROLES=node-list/NOALL_ROLES (D)Specifies the names of the nodes that are to act as frontend, routerandbackendin this facil

Seite 30

CREATE FACILITYNote: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on the

Seite 31 - 2.9 Network Transports

CREATE FACILITYExamplesSee Chapter 2, Starting and Setting Up RTR, for examples of how to use theCREATE FACILITYcommand.6–50 RTR Command Line Interfac

Seite 32

CREATE JOURNALCREATE JOURNALCreate RTR’s recovery journal.FormatCREATE JOURNAL [disk-1] ... [,disk-n]Command Qualifiers Defaults/CLUSTER /NOCLUSTER/BLO

Seite 33

CREATE JOURNALTable 6–17 Platform Specific InformationPlatform Journal Root Finding Disks NotesUNIX /rtrjnl UsedfEnter disk names as thay appear in/dev

Seite 34

CREATE JOURNALIf /NOSUPERSEDE is specified (default), then a journal is created only if nojournal previously existed.Related commands•DELETE JOURNAL•MO

Seite 35

Table 1 Conventions Used in this GuideConvention MeaningUPPERCASElowercaseSome operating systems differentiate between lowercase anduppercase characte

Seite 36

CREATE PARTITIONCREATE PARTITIONCreates an RTR partition.FormatCREATE PARTITION [partition_name]Command Qualifiers Defaults/CLUSTER /NOCLUSTER/CONCURRE

Seite 37

CREATE PARTITION/CONCURRENT (D)/NOCONCURRENTSpecifies that concurrent servers are allowed for this partition./KEYn=keysegdescSpecifies a partition key s

Seite 38

CREATE PARTITION/STANDBY (D)/NOSTANDBYSpecifies that standby servers are allowed for this partition./SHADOW/NOSHADOW (D)Specifies that shadow servers ar

Seite 39 - 2.12.2 Router Selection

DEFINE /KEYDEFINE /KEYAssign a string to a keyboard function key.FormatDEFINE /KEY key-name "equivalence-string"Command Qualifiers Defaults/E

Seite 40

DEFINE /KEYTable 6–18 (Cont.) Key namesKey-name LK201 VT100-typePF4 PF4 PF4KP0, KP1 ..KP9 Keypad 0 .. 9 Keypad 0 .. 9PERIOD Keypad period (.) Keypad p

Seite 41 - Partition Management

DEFINE /KEY/LOG/NOLOG (D)Controls whether a message is displayed indicating that the key definition hasbeen successfully created./SET_STATE=state-name/

Seite 42 - 3.3 Life Cycle of a Partition

DEFINE /KEYThe word DEFAULT in the second line of the example refers to the fact thatPF1has been defined in the default state. Note the space before th

Seite 43

DELETE FACILITYDELETE FACILITYDelete an RTR facility.FormatDELETE FACILITY facility_nameCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE=node-list /

Seite 44 - 3.5.1 Command Line Usage

DELETE FACILITYRelated Commands•CREATE FACILITY•SHOW FACILITYExamplesSee Chapter 2, Starting and Setting Up RTR, for examples of how to use theDELETE

Seite 45 - 3.6 Managing Partitions

DELETE JOURNALDELETE JOURNALDelete an RTR journal.FormatDELETE JOURNALCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE=node-list /NODE=default-node-

Seite 47

DELETE JOURNALExamplesSee Chapter 2, Starting and Setting Up RTR, for examples of how to use theDELETE JOURNALcommand.6–64 RTR Command Line Interface

Seite 48 - 3.6.5 Controlling Failover

DELETE PARTITIONDELETE PARTITIONDelete an RTR PARTITION.FormatDELETE PARTITION PARTITION_nameCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE=node-l

Seite 49

DELETE PARTITIONRelated Commands•CREATE PARTITION•SHOW PARTITION6–66 RTR Command Line Interface

Seite 50

DISPLAY BARDISPLAY BARDisplay a bar-graph in a monitor picture.FormatDISPLAY BAR expressionCommand Qualifiers Defaults/AVERAGE=(keyword,...) /none/BELL

Seite 51 - Transaction Management

DISPLAY BARQualifiers/AVERAGE=(keyword,...)/NOAVERAGESpecifies that the items being monitored relating tokeywordare displayed as anaverage. This allows

Seite 52 - 4.1.1 Exception Transactions

DISPLAY BAR/LABEL=text/NOLABEL (D)Specifies the text used to label the value being displayed. Symbols are substitutedat display time. (See Section A.2,

Seite 53

DISPLAY BARKeyword MeaningPROCESS Process data itemsPARTITION Partition data itemsFE_TRANSACTION Frontend transaction data itemsTR_TRANSACTION Backend

Seite 54

DISPLAY BAR/X=previous-column (D)Specifies the screen column where the item is displayed (the leftmost column is1). By default, items are displayed in

Seite 55 - RTR Monitoring

DISPLAY NUMERICDISPLAY NUMERICDisplay a number in a monitor picture.FormatDISPLAY NUMERIC expressionCommand Qualifiers Defaults/AVERAGE=(keyword,...) /

Seite 56 - 5.2 Standard Monitor Pictures

DISPLAY NUMERICThekeywordcan be one of the following:Keyword MeaningNODE Node data itemsLINK Link data itemsFACILITY Facility data itemsPROCESS Proces

Seite 57

1IntroductionFor a general introduction to Reliable Transaction Router, Version 3.2 (RTR),you should read the introductory chapter in the Reliable Tra

Seite 58

DISPLAY NUMERIC/RATE[=interval]/NORATE (D)Specifies that the rate of change of theexpressionis to be displayed rather thanthe absolute value. When/RATE

Seite 59 - 5.2.2 Monitor ACP2APP

DISPLAY NUMERICKeyword MeaningLINK Link data itemsFACILITY Facility data itemsPROCESS Process data itemsPARTITION Partition data itemsFE_TRANSACTION F

Seite 60 - 5.2.5 Monitor Broadcast

DISPLAY NUMERICRelated Commands•MONITOR•SHOW DISPLAY•CLEAR•DISPLAY BAR•DISPLAY SYMBOLIC•DISPLAY TEXTExamplesSee Section A.1 for examples of how to use

Seite 61 - 5.2.8 Monitor Connects

DISPLAY STRINGDISPLAY STRINGDisplay a string in a monitor picture.FormatDISPLAY STRING expressionCommand Qualifiers Defaults/AVERAGE=(keyword,...) /non

Seite 62 - 5.2.10 Monitor Facility

DISPLAY STRINGThekeywordcan be one of the following:Keyword MeaningNODE Node data itemsLINK Link data itemsFACILITY Facility data itemsPROCESS Process

Seite 63 - 5.2.12 Monitor Group

DISPLAY STRING/SEPARATE=(keyword,...)/NOSEPARATESpecifies that the items being monitored relating tokeywordare separated fromeach other and displayed a

Seite 64 - 5.2.15 Monitor Journal

DISPLAY STRING/X[=column]/X=previous-column (D)Specifies the screen column where the item is displayed (the leftmost column is1). By default, items are

Seite 65 - 5.2.17 Monitor Netbytes

DISPLAY SYMBOLICDISPLAY SYMBOLICDisplay a text in a monitor picture depending on the result of an expressionevaluation.FormatDISPLAY SYMBOLIC expressi

Seite 66 - 5.2.19 Monitor Partit

DISPLAY SYMBOLIC/BOLD[=Boolean-expression]/NOBOLD (D)Specifies that the item is displayed in high intensity ifBoolean-expressionevaluates to True (non-

Seite 67 - 5.2.22 Monitor Recovery

DISPLAY TEXTDISPLAY TEXTDisplay text in a monitor picture.FormatDISPLAY TEXT textCommand Qualifiers Defaults/BELL=Boolean-expression /NOBELL/BLANK=Bool

Seite 68 - 5.2.23 Monitor Rejects

Introduction1.2 Entering Commandsor, when several commands are to be entered at the RTR prompt:% rtrRTR> start rtrRTR> create journalNoteFor con

Seite 69 - 5.2.25 Monitor Response

DISPLAY TEXT/BOLD[=Boolean-expression]/NOBOLD (D)Specifies that the item is displayed in high intensity ifBoolean-expressionevaluates to True (non-zero

Seite 70 - 5.2.28 Monitor Routing

DISPLAY TEXT/UNDERLINE[=Boolean-expression]/NOUNDERLINE (D)Specifies that the displayed value is underlined ifBoolean-expressionevaluatesto True (non-z

Seite 71 - 5.2.30 Monitor RTR

DODOExecute an operating system command.FormatDO [operating-system-command]Command Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE=node-list /NODE=default-

Seite 72 - 5.2.31 Monitor Stalls

DORelated Commands•SPAWNExampleRTR> DO/CLUSTER SHOW TIMEThis command shows the time on all nodes in a OpenVMS cluster.RTR> DO/NODE=(TR2,TR1) SHO

Seite 73 - 5.2.32 Monitor System

FLUSH NAME_CACHEFLUSH NAME_CACHEFlushes RTR’s internal network name cache.FormatFLUSH NAME_CACHECommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE[=no

Seite 74 - 5.2.35 Monitor Trans

EXECUTEEXECUTEExecutes a file containing RTR commands.FormatEXECUTE file-specCommand Qualifiers Defaults/VERIFY /NOVERIFYDescriptionThe EXECUTE command r

Seite 75 - 5.2.37 Monitor XA

EXITEXITExits from the RTR prompt.FormatEXITDescriptionThe EXIT command exits from the RTR prompt and returns control to theoperating system prompt. T

Seite 76

EXTEND FACILITYEXTEND FACILITYAdds new nodes or roles or both to an existing facility definition.FormatEXTEND FACILITY [facility_name]Command Qualifiers

Seite 77 - RTR Command Line Interface

EXTEND FACILITY$ RTRRTR> SET ENVIRONMENT /NODE=(FE,FETRBE)RTR> CREATE FACILITY facnam /FRONTEND=(FE,FETRBE) -/ROUTER=FETRBE -/BACKEND=FETRBEA ne

Seite 78 - ADD FACILITY

EXTEND FACILITYBackend-listis a list ofbackend-nodesseparated by commas. If there is morethan onebackend-node, thenbackend-listmust be enclosed in par

Seite 79 - CALL RTR_ACCEPT_TX

Introduction1.3 Online Helpwhereerror-identificationis the identification part of the returned error.The following sequence returns an error message,RT

Seite 80

EXTEND FACILITY/OUTPUT[=file-spec]/OUTPUT=stdout (D)Specifies that the resulting information is written to the filefile-spec.If/OUTPUTorfile-specis omitt

Seite 81

INITIALIZE JOURNALINITIALIZE JOURNALSee CREATE JOURNAL; INITIALIZE is only retained for compatibility reasons.RTR Command Line Interface 6–95

Seite 82 - CALL RTR_BROADCAST_EVENT

LOGLOGSpecify RTR to write a log message to a log file.FormatLOGCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE=node-list /NODE=default-node-list/OU

Seite 83

LOGExamplesRTR> LOG/OUTPUT=RTRLOG.LOG "Message check here"This command tells RTR to write a log message to the file RTRLOG.LOG.RTR> LOG

Seite 84

MODIFY JOURNALMODIFY JOURNALSpecifies the desired and maximum allowed sizes of RTR’s recovery journal.FormatMODIFY JOURNAL [disk-1] ... [,disk-n]Comman

Seite 85

MODIFY JOURNALIf neither/NODEnor/CLUSTERis specified then the command is executed on thenodes specified by the latestSET ENVIRONMENTcommand. If noSET EN

Seite 86 - CALL RTR_CLOSE_CHANNEL

MONITORMONITORDisplays a monitor picture on the screen.FormatMONITOR [monitor-file-spec]Command Qualifiers Defaults/CLUSTER /NOCLUSTER/COUNT=nr-updates

Seite 87

MONITORNote: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on the local n

Seite 88 - CALL RTR_ERROR_TEXT

MONITORqualifier can be used to reset all the averages currently being displayed. It is alsouseful if monitoring is resumed after issuing one or more R

Seite 89 - CALL RTR_GET_TID

QUITQUITQuits from the RTR prompt.FormatQUITDescriptionThe QUIT command exits from the RTR prompt and returns control to theoperating system prompt. T

Seite 90

Introduction1.5 Remote CommandsThis command starts RTR on the three nodes.NoteThe /CLUSTER and /NOCLUSTER command qualifiers refer to clustersupport. T

Seite 91 - CALL RTR_OPEN_CHANNEL

RECALLRECALLDisplay a previously entered command for subsequent command editing.FormatRECALL [command-specifier]Command Qualifiers Defaults/ALL /NOALLDe

Seite 92

REGISTER RESOURCE MANAGER (REGISTER RM)REGISTER RESOURCE MANAGER (REGISTER RM)Registers an instance of a resource manager (RM) with RTR.FormatREGISTER

Seite 93

REGISTER RESOURCE MANAGER (REGISTER RM)ExamplesRTR> REGISTER RM rmi_1/open_string="Oracle_XA+Acc=P/user/pw+SesTm=15+db=accounting"/close_

Seite 94

SCROLLSCROLLScroll a monitor picture.FormatSCROLL direction [amount]DescriptionTheSCROLLcommand causes the the last picture that was displayed using t

Seite 95

SET ENVIRONMENTSET ENVIRONMENTSpecify the node(s) where subsequent RTR commands are executed.FormatSET ENVIRONMENTCommand Qualifiers Defaults/CLUSTER /

Seite 96

SET FACILITYSET FACILITYSets various facility related options.FormatSET FACILITY facility-nameCommand Qualifiers Defaults/BROADCAST_MINIMUM_RATE=Bps /B

Seite 97

SET FACILITYNoteA node that combines both backend and router roles is counted twicein determining the threshold. A value of zero implies that the RTRd

Seite 98

SET FACILITYRelated Commands•SHOW FACILITYExamplesRTR> SET FACILITY FINANCE/QUORUM_THRESHOLD=4quorum threshold set to 4 (from 0) for facility FINAN

Seite 99

SET LINKSET LINKSets various link related options.FormatSET LINK link-nameCommand Qualifiers Defaults/AUTOISOLATE /NOAUTOISOLATE/ENABLE /DISABLE/CHECKS

Seite 100 - Examples

SET LINKRemote node autoisolation may be enabled (at the isolator) where it applies to alllinks using SET NODE/AUTOISOLATE, or for specific links only

Seite 101 - CALL RTR_RECEIVE_MESSAGE

2Starting and Setting Up RTRThis chapter describes how to configure and start an RTR environment. Recoveryjournals, router load balancing and call-out

Seite 102 - Qualifiers

SET LINKThe new value forsecsbecomes effective only after a time of about one third ofthe current value of the link inactivity timeout.The minimum use

Seite 103

SET LINKExamplesRTR> SET LINK JOEY/ENABLEThis command re-allows connections from node JOEY.RTR> SET LINK JOEY/AUTOISOLATEThis command sets the a

Seite 104 - CALL RTR_REJECT_TX

SET LOGSET LOGSpecify where RTR writes its log messages.FormatSET LOGCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/FILE=file-spec-list /NOFILE/NODE=nod

Seite 105 - Related Commands

SET LOG/OPERATOR/NOOPERATOR (D)Specifies that messages are written to the operator log./OUTPUT[=file-spec]/OUTPUT=stdout (D)Specifies that the resulting

Seite 106

SET MODESET MODESpecify whether RTR should run in a group mode or the nogroup (system) mode.FormatSET MODECommand Qualifiers Defaults/CLUSTER /NOCLUSTE

Seite 107 - CALL RTR_REPLY_TO_CLIENT

SET MODE/NODE[=node-list]/NODE=default-node-list (D)Specifies that the command is executed on all nodes specified innode-list.Ifnode-listis omitted then

Seite 108

SET NODESET NODESets various node related options.FormatSET nodeCommand Qualifiers Defaults/AUTOISOLATE /NOAUTOISOLATE/CLUSTER /NOCLUSTER/INACTIVITY_TI

Seite 109

SET NODE/CLUSTER/NOCLUSTER (D)Specifies that the command is executed on all the nodes in the cluster.If neither/NODEnor/CLUSTERis specified then the com

Seite 110

SET PARTITIONSET PARTITIONSets various partition related options.FormatSET PARTITION partition-nameCommand Qualifiers Defaults/FACILITY=[facility_name]

Seite 111 - CALL RTR_REQUEST_INFO

SET PARTITION/IGNORE_RECOVERY/NOIGNORE_RECOVERY (D)Forces the partition to exit any current wait state it may be in.If a partition should enter a wait

Seite 112

June, 1999COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OREDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL ORCONSEQU

Seite 113

Starting and Setting Up RTR2.2 Setting Up—An ExampleFigure 2–1 Configuration ExampleF E 1F E 2F E 3T R 1T R 2B E 1B E 2B E 3SMM_CONFIG_EX 01−99F r o n

Seite 114 - CALL RTR_SEND_TO_SERVER

SET PARTITIONOnce shadowing is disabled, the secondary site servers will be unable to startupin shadow mode until shadowing is enabled again.Shadowing

Seite 115

SET TRANSACTIONSET TRANSACTIONSets various transaction related options.FormatSET TRANSACTION transaction-idCommand Qualifiers Defaults/BEFORE[=date] to

Seite 116

SET TRANSACTIONUsage NotesThe command can only be executed on a backend node in which the journal islocated and the RTR log file must be turned on to r

Seite 117

SET TRANSACTION/NEW_STATESpecifies the new transaction state that selected transactions will be changed to.This qualifier is required and new state valu

Seite 118 - CALL RTR_START_TX

SET TRANSACTIONExamplesRTR> SET TRANSACTION "50d01f10,0,0,0,0,2166,522b2001" -_RTR> /NEW=ABORT /CURRENT=SENDING /PART=DB_PARTAbort thi

Seite 119

SHOW CHANNELSHOW CHANNELShow the names and state of channels that have been opened using the CLI API.FormatSHOW CHANNEL [channel-name]Command Qualifier

Seite 120

SHOW CHANNELRelated Commands•call rtr_open_channel( )•call rtr_close_channel( )ExamplesRTR> SHOW CHANNEL/ALL_WINDOWS1Channel type Channel name (Own

Seite 121 - Description

SHOW CLIENTSHOW CLIENTDisplay information about client channels.FormatSHOW CLIENTCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/FACILITY /FACILITY=&quo

Seite 122

SHOW CLIENT/NODE[=node-list]/NODE=default-node-list (D)Specifies that the command is executed on all nodes specified innode-list.Ifnode-listis omitted t

Seite 123 - CREATE FACILITY

SHOW DISPLAYSHOW DISPLAYShow which items were displayed by the most recently issuedMONITORcommandorDISPLAYcommands.FormatSHOW DISPLAYCommand Qualifiers

Seite 124

Starting and Setting Up RTR2.2 Setting Up—An ExampleExample 2–2 illustrates how to use RTR remote commands to start the sameconfiguration. Theset envir

Seite 125

SHOW DISPLAYExamplesRTR> MON CALLS1RTR> SHOW DISPLAY/ALL2DISPLAY TEXT "RTR api calls, Node: $node_name ,-3PID: $process_id, Process name: -

Seite 126

SHOW ENVIRONMENTSHOW ENVIRONMENTShows the default nodes used for remote command execution.FormatSHOW ENVIRONMENTDescriptionTheSHOW ENVIRONMENTcommand

Seite 127 - CREATE JOURNAL

SHOW FACILITYSHOW FACILITYShow the names, configuration and status of one or more facilities.FormatSHOW FACILITY [facility-name]Command Qualifiers Defau

Seite 128

SHOW FACILITY/CONFIGURATION/NOCONFIGURATION (D)Specifies that the facility configuration is to be displayed. The configurationinformation indicates the r

Seite 129

SHOW FACILITYOn a frontend, this qualifier can be used to find out whether the node is currentlyconnected to a router.Related Commands•CREATE FACILITY•D

Seite 130 - CREATE PARTITION

SHOW FACILITY5The facility’s links. The first link shown (to node ‘‘bronze’’ i.e. itself) showsthat it is a router, connected to the backend, and the r

Seite 131

SHOW JOURNALSHOW JOURNALDisplay information about current RTR journal files.FormatSHOW JOURNALCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/FILENAMES /

Seite 132

SHOW JOURNALRelated Commands•CREATE JOURNAL•DELETE JOURNAL•INITIALIZE JOURNALExamplesRTR> SHOW JOURNAL/FULL/FILENAMES1RTR journal:-23 456Disk(1): /

Seite 133 - DEFINE /KEY

SHOW KEYSHOW KEYDisplay the key definitions created by theDEFINE /KEYcommand.FormatSHOW KEY [key-name]Command Qualifiers Defaults/ALL /NOALL/FULL /NOFUL

Seite 134

SHOW KEYRelated Commands•DEFINE /KEYExamplesRTR> SHOW KEY/FULLDEFAULT PF1 defined as ""DEFAULT KP0 defined as "MONITOR/RESUME"D

Seite 135

Starting and Setting Up RTR2.3 Creating a Recovery Journal• The operator should move any duplicate copies of journal files to alocation other than ther

Seite 136

SHOW LINKSHOW LINKDisplay the configuration and status of the links to other nodes.FormatSHOW LINK [node-name]Command Qualifiers Defaults/CLUSTER /NOCLU

Seite 137 - DELETE FACILITY

SHOW LINK/FULLEquivalent to specifying/FACILITY/STATE./NODE[=node-list]/NODE=default-node-list (D)Specifies that the command is executed on all nodes s

Seite 138

SHOW LOGSHOW LOGDisplay the names of the current log files.FormatSHOW LOGCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE[=node-list] /NODE=default-n

Seite 139 - DELETE JOURNAL

SHOW LOGExampleRTR> SHOW LOG1Messages not being sent to operator console2Log file[1]: /usr/users/someone/rtr_logfile.log31Show where RTR log messag

Seite 140

SHOW MODESHOW MODEDisplays the current RTR mode.FormatSHOW MODECommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE[=node-list] /NODE=default-node-list/

Seite 141 - DELETE PARTITION

SHOW MODEExamplesRTR> SHOW MODEGroup name is "develop"RTR Command Line Interface 6–149

Seite 142

SHOW NODESHOW NODEShows the node network status, the autoisolation state and the node inactivitytimer.FormatSHOW NODECommand Qualifiers Defaults/CLUSTE

Seite 143 - DISPLAY BAR

SHOW NODEExamplesRTR> SHOW NODE1Node properties:Network state: enabled2Auto isolation: disabled3Inactivity timer/s: 6041SHOW NODE command.2Network

Seite 144

SHOW PARTITIONSHOW PARTITIONDisplay server data partition information.FormatSHOW PARTITIONCommand Qualifiers Defaults/BACKEND /BACKEND/BRIEF /NOBRIEF/C

Seite 145

SHOW PARTITIONTable 6–21 Router Partition StatesState MeaningBLOCKED Key range is recovering or awaiting journal accessACTIVE Primary server is ready

Seite 146

Starting and Setting Up RTR2.4 Changing a FacilityExample 2–3 Reconfiguration Using Delete and Create Facility% rtrRTR> stop rtr/node=FE31RTR> de

Seite 147

SHOW PARTITION• The state of transaction presentation - one of active, suspended or suspending• The current failover policy - one of fail_to_standby,

Seite 148 - DISPLAY NUMERIC

SHOW PARTITIONPartition name: RTR$DEFAULT_PARTITION_16777217Facility: RTR$DEFAULT_FACILITY State: activeLow Bound: "aaaa" High Bound: "

Seite 149

SHOW PROCESSSHOW PROCESSDisplay information about processes which are using RTR.FormatSHOW PROCESSCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/COUNTE

Seite 150

SHOW PROCESS/OUTPUT[=file-spec]/OUTPUT=stdout (D)Specifies that the resulting information is written to the filefile-spec.If/OUTPUTorfile-specis omitted

Seite 151

SHOW REQUESTERSHOW REQUESTERSee SHOW CLIENT. The SHOW REQUESTER command has been replaced bySHOW CLIENT and is retained for compatibility reasons only

Seite 152

SHOW RESOURCE MANAGER (SHOW RM)SHOW RESOURCE MANAGER (SHOW RM)Displays resource manager instance (RM) information.This command is available only on UN

Seite 153 - DISPLAY STRING

SHOW RESOURCE MANAGER (SHOW RM)/FULL/NOFULL (D)Displays additional information for facilities that reference a particular RM. If normi_name is include

Seite 154

SHOW RTRSHOW RTRDisplay the configuration and status of RTR.FormatSHOW RTRCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/COUNTER[=counter-name] /NOCOUNT

Seite 155

SHOW RTR/STATUS (D)/NOSTATUSDisplays the current status of RTR (started, stopped and so on)./VERSION/NOVERSION (D)Displays the RTR version.Related Com

Seite 156

SHOW SEGMENTSHOW SEGMENTDisplay the type and size of routing key segments.FormatSHOW SEGMENTCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/FACILITY /FA

Seite 157 - DISPLAY SYMBOLIC

Starting and Setting Up RTR2.4 Changing a FacilityFigure 2–2 Extend Configuration ExampleSMM_CONFIG_EX_EXT 02−99F E 1F E 2F E 3F E 4T R 1T R 2T R 3B E

Seite 158

SHOW SEGMENTExamplesRTR> SHOW SEGMENT1Facility Data Type Length OffsetRTR$DEFAULT_FACILITY UNSIGNED 1 02TEST_FAC SIGNED 4 101Show the routing key s

Seite 159 - DISPLAY TEXT

SHOW SERVERSHOW SERVERDisplay information about server channels.FormatSHOW SERVERCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/FACILITY /FACILITY=&quo

Seite 160

SHOW SERVERTable 6–23 Server FlagsFLAG MeaningBEC Backend Call-outEXA Explicit AcceptEXP Explicit PrepareNCC No ConcurrentNSB No StandbySHD ShadowSRV

Seite 161

SHOW SERVERExamplesRTR> SHOW SERVERServers:Process-id Facility Channel Flags State20828 RTR$DEFAULT_FACILITY 589825 SRV active20828 RTR$DEFAULT_FAC

Seite 162 - Parameters

SHOW TRANSACTIONSHOW TRANSACTIONDisplays information about currently active transactions.FormatSHOW TRANSACTIONCommand Qualifiers Defaults/BACKEND /NOB

Seite 163

SHOW TRANSACTIONNote: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on th

Seite 164 - FLUSH NAME_CACHE

SHOW TRANSACTIONTable 6–25 (Cont.) Key-Range StatesState Meaningactive Active non-shadowedsec_act Secondary activepri_act Primary activepri_lone Prima

Seite 165 - @file-spec

SPAWNSPAWNAllows you to execute operating system commands without leaving the RTRutility.FormatSPAWN [operating-system-command]Command Qualifiers Defau

Seite 166

START RTRSTART RTRStart RTR on one or more nodes.FormatSTART RTRCommand Qualifiers Defaults/CLUSTER /NOCLUSTER/NODE[=node-list] /NODE=default-node-list

Seite 167 - EXTEND FACILITY

START RTRQualifiers/ASTLM=ast-limit/ASTLM=(max-links + max-processes) 2 + 10 = default ast-limit (D)Specifies the AST limit for the RTR ACP.The value fo

Seite 168

Starting and Setting Up RTR2.4 Changing a FacilityExample 2–4 Reconfiguration Using Extend Facility% RTRRTR> start rtr /node=(TR3,FE4)RTR> set en

Seite 169

START RTR/DIOLM=io-direct/DIOLM=(max-links + max-processes) 2 + 10 = default io-direct (D)Specifies the maximum number of direct I/O operations that th

Seite 170

START RTRThe default value ofpage-fileis automatically calculated, based on the values of/LINKS and /PROCESSES./PRCLM=subprocess-limit/PRCLM=10 (D)Spe

Seite 171 - INITIALIZE JOURNAL

START RTRRelated Commands•SHOW RTR•STOP RTRExamplesSee Chapter 2, Starting and Setting Up RTR, for examples of how to use theSTART RTRcommand.6–176 RT

Seite 172

STOP RTRSTOP RTRStop RTR on one or more nodes.FormatSTOP RTRCommand Qualifiers Defaults/ABORT /NOABORT/CLUSTER /NOCLUSTER/NODE[=node-list] /NODE=defaul

Seite 173

STOP RTR/OUTPUT[=file-spec]/OUTPUT=stdout (D)Specifies that the resulting information is written to the filefile-spec.If/OUTPUTorfile-specis omitted then

Seite 174 - MODIFY JOURNAL

TRIM FACILITYTRIM FACILITYRemoves nodes or roles or both from an existing facility definition.FormatTRIM FACILITY [facility_name]Command Qualifiers Defa

Seite 175 - OpenVMS Example

TRIM FACILITYRTR MONITOR QUORUM displays a monitor picture which allows the quorumnegotiations to be observed. You can use this after using a TRIM FAC

Seite 176

TRIM FACILITY/NOFRONTEND (D)Specifies the names of nodes where the frontend role is removed for this facility.frontend-listis a list offrontend-nodesse

Seite 177

UNREGISTER RESOURCE MANAGER (UNREGISTER RM)UNREGISTER RESOURCE MANAGER (UNREGISTER RM)TheUNREGISTER RESOURCE MANAGERcommand unregisters an instance of

Seite 178

ACreating Monitor PicturesThe standard monitor pictures provided with RTR (described in Chapter 5) aresufficient for most needs. You may also create yo

Seite 179

Starting and Setting Up RTR2.5 Setting up Callout ServersExample 2–5 Configuration of Callout Servers% rtrRTR> set environment/node= -_RTR> (FE1,

Seite 180 - /ALL /NOALL

Creating Monitor PicturesThe commands used to define and display monitor pictures are:CLEARDISPLAY BARDISPLAY NUMERICDISPLAY STRINGDISPLAY SYMBOLICDISP

Seite 181

Creating Monitor PicturesA.1 Interactive Definition of a Monitor PictureFigure A–1 Interactively Defined Monitor PictureTHE TEST PICTURE AT 11:49:24SOME

Seite 182

Creating Monitor PicturesA.3 Arithmetic Expressions and OperatorsTable A–3 Arithmetic Operators in Display CommandsCharacters Meaning- Minus+ Plus* Mu

Seite 183

Creating Monitor PicturesA.3 Arithmetic Expressions and OperatorsAggregation of Data ItemsDISPLAY commands which select multiple instances of a data i

Seite 185 - SET FACILITY

BServer Shadowing and RecoveryRTR shadowing gives you the ability to recover from a site disaster without theneed for special coding within your appli

Seite 186

Server Shadowing and RecoveryB.2 Automatic Features• RTR_EVTNUM_SRSHADOWGAIN - Server has gained its shadow partner• RTR_EVTNUM_SRRECOVERCMPL - Server

Seite 187

Server Shadowing and RecoveryB.3 The RTR Journal SystemThe number of blocks specified by the /BLOCKS qualifier specifies the size of thejournal that RTR

Seite 188 - SET LINK

Server Shadowing and RecoveryB.4 Shadow Site Failure and JournalingB.4.1 Maximum Journal SizeThe current maxima for the size of a journal are:Number o

Seite 189

Server Shadowing and RecoveryB.6 PerformanceNote that RTR does not have to wait for the secondary shadow server to completeits processing. It only nee

Seite 190

Starting and Setting Up RTR2.6 Router Load Balancing• Use/balanceon frontend nodes only. Use of/balanceon routers is supportedonly to enable RTR Versi

Seite 191

Server Shadowing and RecoveryB.8 Application Considerations• Any physical reference to the transaction which is unique to the executingserver, e.g. Ch

Seite 192

Server Shadowing and RecoveryB.9 Server StatesFigure B–2 Server StatesWAIT−TR−OKWAIT−TR−RETRYRetryRouter detectsdefinition clashPropose KRto RoutersEr

Seite 193

Server Shadowing and RecoveryB.10 Client StatesB.10 Client StatesThe current state of a client process can be examined as follows:RTR> show client/

Seite 194 - SET MODE

Server Shadowing and RecoveryB.11 Partition StatesB.11 Partition StatesThe current state of a key-range partition can be examined using theSHOWPARTITI

Seite 196 - SET NODE

CXA SupportThis appendix explains how RTR may be used with a X/OPEN DistributedTransaction Processing (DTP) conformant Resource Manager.C.1 Introducti

Seite 197

XA SupportC.1 Introductionfacility_name = user-specified facility name /resource_manager = the name ofthose RMs this facility referencesFor example:CRE

Seite 198 - SET PARTITION

DRTR Utility Error MessagesThis appendix describes the various error messages that can be returned by theRTR utility.%RTR-F-ABKEYW, Ambiguous qualifier

Seite 199

RTR Utility Error Messages%RTR-F-BADDSKWRI, Unable to create/extend a journal fileExplanation: An attempt to create or extend a journal file on disk fai

Seite 200

RTR Utility Error Messages%RTR-E-CLOSEPEND, Send failed due to close pending on channel - call rtr_receive_messageExplanation: Sending of data to the

Seite 201 - SET TRANSACTION

Starting and Setting Up RTR2.7 RTR PrivilegesThertrinfogroup is currently only used to allow applications to callrtr_request_info( )For other users, c

Seite 202

RTR Utility Error Messages%RTR-S-DISITMCLR, [A] display item(s) clearedExplanation: Indicates how many display items [A] were successfullycleared afte

Seite 203

RTR Utility Error Messages%RTR-F-DUPJOUFIL, Duplicate RTR journal file found - remove duplicate fileor CREATE JOURNAL /SUPERSEDEExplanation: A duplicate

Seite 204

RTR Utility Error Messages%RTR-F-ERRACCDIR, Directory [A], cannot be accessed or openedExplanation: A directory cannot be accessed or opened.%RTR-E-ER

Seite 205 - SHOW CHANNEL

RTR Utility Error Messages%RTR-E-ERRSTAACP, Unable to start ACPExplanation: The RTR ACP process could not be started when a "STARTRTR" comma

Seite 206

RTR Utility Error Messages%RTR-E-FACNAMLON, Facility name [A] is longer than 30 charactersExplanation: Facility name [A] is too long.%RTR-E-FACNAMSTA,

Seite 207 - SHOW CLIENT

RTR Utility Error Messages%RTR-E-ILLPARTCHAR, Legal characters are alphanumeric and under-scoreExplanation: Illegal chars in partition name argument.%

Seite 208

RTR Utility Error Messages%RTR-F-INVKSTYPE, Invalid ks_type argumentExplanation: Invalid ks_type argument.%RTR-F-INVMSGFMT, Invalid format argumentExp

Seite 209 - SHOW DISPLAY

RTR Utility Error Messages%RTR-E-ITMALREXI, There is already something displayed at x = [A], y = [A]Explanation: Indicates that invalid coordinates we

Seite 210

RTR Utility Error Messages%RTR-F-JOUFORCHA, Journal format has been changed - CREATE JOURNAL/SUPERSEDEExplanation: The journal file(s) found have an ou

Seite 211 - SHOW ENVIRONMENT

RTR Utility Error Messages%RTR-S-JOURNALINI, Journal has been created on device [A]Explanation: Confirms that the RTR journal has been successfully cre

Seite 212 - SHOW FACILITY

Starting and Setting Up RTR2.8 RTR ACP Virtual Memory Sizing• Add the size of all messages2. For each transaction router:• Allow one Kbyte for each ac

Seite 213

RTR Utility Error Messages%RTR-E-LOCKFAIL, Cannot obtain lock for resource [A]Explanation: Failed to obtain lock. Enable logging for more informationa

Seite 214

RTR Utility Error Messages%RTR-E-NDBTABFUL, The NDB table is fullExplanation: This message is displayed when an "CREATE FACILITY"command is

Seite 215

RTR Utility Error Messages%RTR-E-NODNA, DECnet specified for [A], but transport protocol unavailableor disabledExplanation: DECnet was specified as requ

Seite 216 - SHOW JOURNAL

RTR Utility Error Messages%RTR-E-NOKEYSEGS, You must specify at least one keysegment - use /KEY1 -/KEY9Explanation: Except for a callout partition, it

Seite 217

RTR Utility Error Messages%RTR-E-NOSUCHITM, Nothing displayed at x = [A],y=[A]Explanation: Indicates that invalid coordinates were specified on a "

Seite 218 - SHOW KEY

RTR Utility Error Messages%RTR-E-NUMCONILL, Numeric constant has illegal syntax, [A]Explanation: The numeric constant [A] is invalid.%RTR-W-OBSQUAL, Q

Seite 219

RTR Utility Error Messages%RTR-E-PRTBADCMD, Partition command invalid or not implemented in thisversion of RTRExplanation: Status return indicating th

Seite 220 - SHOW LINK

RTR Utility Error Messages%RTR-S-PRTNCREATED, Partition createdExplanation: The requested partition was successfully created.%RTR-S-PRTNDELETED, Parti

Seite 221

RTR Utility Error Messages%RTR-E-PRTRUNDOWN, Partition is in rundown prior to deletion - no actiontakenExplanation: Cannot perform the requested actio

Seite 222 - SHOW LOG

RTR Utility Error Messages%RTR-E-RTRALRSTA, RTR already startedExplanation: RTR was already running when the "START RTR" commandwas executed

Seite 223

ContentsPreface ... xi1 Introduction1.1 Getting Started ...

Seite 224 - SHOW MODE

Starting and Setting Up RTR2.8 RTR ACP Virtual Memory SizingUse of /LINK and /PROCESSES do not take into account memory requirementsfor transactions.

Seite 225

RTR Utility Error Messages%RTR-F-SPUJOUFIL, Spurious RTR journal file found - remove extra file, orCREATE JOURNAL /SUPERSEDE and submit SPRExplanation:

Seite 226 - SHOW NODE

RTR Utility Error Messages%RTR-E-TOOMANCHN, Too many channelsExplanation: Displayed when a "SYS$DCL_TX_PRC" command is issuedand the channel

Seite 227

RTR Utility Error Messages%RTR-E-UNEXPEND, Expression ended before [A] encounteredExplanation: The expression is invalid because it terminated where w

Seite 228 - SHOW PARTITION

ERTR log messagesThis appendix describes the various error messages that can be sent to theoperator console or written to RTR’s operator log file.%RTR-

Seite 229

RTR log messages%RTR-E-BADIDSIZ, Bad node ID size [A] detected at 0x[A]Explanation: This message indicates that errors have been detected inprocessing

Seite 230

RTR log messages%RTR-F-BRODISLIN, Broadcast message(s) discarded because of linkunavailabilityExplanation: One or more broadcast messages had to be di

Seite 231

RTR log messages%RTR-I-CONNALIAS, Link [A] connected as [A]Explanation: Support for internet tunnels allows for the configuration oflinks from which co

Seite 232 - SHOW PROCESS

RTR log messages%RTR-I-FACLOSTFE, Facility [A] lost Frontend node [A]Explanation: This node is no longer a current router on facility [A], forfrontend

Seite 233

RTR log messagesfull). RTR has ensured that the TX has been committed, but the operatorshould nevertheless check the condition on the BE where the TX

Seite 234 - SHOW REQUESTER

RTR log messages%RTR-I-JOUSEACOM, Journal search on facility [A] completed. [A] recoverabletransactions foundExplanation: Journal search has completed

Seite 235

Starting and Setting Up RTR2.8 RTR ACP Virtual Memory SizingA minimum of 419430 Kbytes for heap data segment sizingA minimum of 33555 Kbytes for core

Seite 236

RTR log messages%RTR-E-NOCURRTR, Current router search failed for facility [A]Explanation: None of the routers specified for facility [A] are currently

Seite 237 - SHOW RTR

RTR log messages%RTR-I-PRTCMDFRMBE, Command received for partition [A]:[A] from backendnode [A]Explanation: Log file message indicating the origin of a

Seite 238

RTR log messages%RTR-E-PRTSETFAILTR, Router unable to process commandExplanation: A partition set command failed at the router. An entry iswritten to

Seite 239 - SHOW SEGMENT

RTR log messages%RTR-F-QIROVERFLOW, No more QIRs leftExplanation: This status is used to indicate an inadequacy in the staticreservations for the inte

Seite 240

RTR log messages%RTR-W-RSPFAC, Response from Node [A] about Facility [A]Explanation: A negotiation with remote node [A] about facility [B] hasfailed f

Seite 241 - SHOW SERVER

RTR log messages%RTR-W-TOOMANYNETIDS, Too many net IDs for node ’[A]’ - check for andeliminate any unnecessary adapter/protocol combinationsExplanatio

Seite 243

IndexAActiveMonitor, 5–2Aggregation of Data Items, A–5BBackend, 2–1BARDISPLAY, 6–67BroadcastMonitor, 5–2CCallRtr_accept_tx, 6–3rtr_prepare_tx, 6–22CAL

Seite 244 - SHOW TRANSACTION

DTC Support, C–2EENVIRONMENTSET, 1–4, 6–108SHOW, 6–135Errors, 1–2EventMonitor, 5–2EXECUTE, 6–89EXIT, 6–90EXTENDFACILITY, 6–91FFacility, 1–1Create, 2–1

Seite 245

Monitor (cont’d)Routing, 5–3Rtr, 5–3Stalls, 5–3System, 5–3Tps, 5–3Tpslo, 5–3Traffic, 5–3V2calls, 5–4XA, 5–4MONITOR, 5–1, 6–100Monitor file, 5–1Monitor p

Seite 246

Starting and Setting Up RTR2.9 Network Transports2.9.2 Using RTR with DHCP and Internet TunnelsWhen using RTR with DHCP or an Internet tunnel, a noden

Seite 247

SET (cont’d)MODE, 6–118NODE, 6–120PARTITION, 6–122TRANSACTION, 6–125SHOWCHANNEL, 6–129CLIENT, 6–131DISPLAY, 6–133, A–2ENVIRONMENT, 6–135FACILITY, 6–13

Seite 248 - START RTR

Starting and Setting Up RTR2.9 Network TransportsThis informs the system administrator that port number 46000/tcp is reservedfor RTR. (Note that the R

Seite 249

Starting and Setting Up RTR2.10 Network Protocol Selection on OpenVMS2.10 Network Protocol Selection on OpenVMS• The default network transport protoco

Seite 250

Starting and Setting Up RTR2.11 Running RTR as a Service on Windows NT2.11.1 Customizing the RTR Windows NT ServiceWhile starting RTR, the Service loo

Seite 251

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodes2.12 How RTR Selects Processing-states (Roles) for NodesThis sectio

Seite 252

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for NodesThe SHOW PARTITION command on each backend node is as follows:Backe

Seite 253 - STOP RTR

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodes8. The network connection to node Gold is reestablished. The partit

Seite 254

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for NodesRouterSite ASite BNode-A1 Node-A2Node-B1 Node-B2If the relative pri

Seite 255 - TRIM FACILITY

3.3 Life Cycle of a Partition . . . ... 3–23.3.1 Implicit Partition Creation ... 3–33.

Seite 256

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodesrelevant to a backend. It is where the backend goes to obtain and v

Seite 257

3Partition Management3.1 OverviewThis section describes the concepts and operations of RTR’s partitions.3.1.1 What is a Partition?Partitions are subdi

Seite 258 - SHOW RESOURCE MANAGER

Partition Management3.2 Partition Naming3.2 Partition NamingA prerequisite for partition management is the ability to identify a partition inthe syste

Seite 259 - Creating Monitor Pictures

Partition Management3.3 Life Cycle of a Partition3.3.1 Implicit Partition CreationPartitions are created implicitly when an application program callsr

Seite 260

Partition Management3.5 Entering Partition Commands3.5 Entering Partition CommandsPartitions can be managed by issuing partition commands directed at

Seite 261 - A.2 Substitution Symbols

Partition Management3.5 Entering Partition CommandsThertr_set_info( )call completes asynchronously. If the function call issuccessful, completion will

Seite 262

Partition Management3.6 Managing Partitions3.6.2 Controlling Transaction PresentationTransaction presentation is the process of passing transactions t

Seite 263

Partition Management3.6 Managing PartitionsIf a partition enters a wait state or fails but has neither a local or remote journal,an operator can instr

Seite 264

Partition Management3.6 Managing Partitions3.6.4.2 Programming InformationTo set the partition backend priority list, program theset_qualifierargument

Seite 265 - Server Shadowing and Recovery

Partition Management3.6 Managing Partitions•rtr_partition_fail_to_shadow•rtr_partition_pre32_compatible3.6.6 Controlling Transaction ReplayRTR has imp

Seite 266 - B.3 The RTR Journal System

5.2.14 Monitor IPCRATE ... 5–105.2.15 Monitor Journal . . ... 5–105.2.16 Mon

Seite 267

Partition Management3.7 Displaying Partition Information3.7 Displaying Partition InformationInformation on the definition and state of a partition is d

Seite 268 - B.6 Performance

4Transaction Management4.1 OverviewThis section describes the concepts of RTR’s transaction management capability.The RTR transaction is the heart of

Seite 269 - B.7 Shadows in Action

Transaction Management4.1 Overviewthis transaction is removed from memory and can no longer be monitored by thecommand.The RTRDUMP JOURNALcommand can

Seite 270 - B.9 Server States

Transaction Management4.1 Overview4.1.2 Transaction State ChangesThere are eight valid state changes allowed for theSET TRANSACTIONcommand.Attempting

Seite 271

Transaction Management4.1 OverviewThis is the case where, for example, a server crashed while performingan SQL commit immediately after receiving amt_

Seite 272 - B.10 Client States

5RTR MonitoringThis chapter contains a description of the RTR monitor. The RTR monitorgives you a means of viewing the activities of RTR and your appl

Seite 273 - B.11 Partition States

RTR Monitoring5.2 Standard Monitor PicturesNoteObsolete monitor pictures have been removed from the documentation.Table 5–1 Standard Monitor PicturesP

Seite 274

RTR Monitoring5.2 Standard Monitor PicturesTable 5–1 (Cont.) Standard Monitor PicturesPicture name Descriptionjcalls Displays counts of successful (su

Seite 275 - XA Support

RTR Monitoring5.2 Standard Monitor PicturesTable 5–1 (Cont.) Standard Monitor PicturesPicture name Descriptiontraffic Displays a list of the links to o

Seite 276 - C.2 Microsoft DTC Support

RTR Monitoring5.2 Standard Monitor Picturesyour domain name, depending on how the name is entered in either your localhosts file or name server. DECnet

Seite 277 - RTR Utility Error Messages

DISPLAY BAR . . ... 6–67DISPLAY NUMERIC ... 6–72DISPLAY STRING...

Seite 278

RTR Monitoring5.2 Standard Monitor Pictures5.2.3 Monitor ActiveACTIVE TRANSACTIONS BY PROCESS Fri Mar 12 1999 19:32:41Starts Completions ActiveAll pro

Seite 279

RTR Monitoring5.2 Standard Monitor Pictures5.2.6 Monitor CallsRTR api calls, Node: nodea.zuo.dec.com , PID: 2162 , Process name: -ALL-Image: -ALL- Fri

Seite 280

RTR Monitoring5.2 Standard Monitor PicturesDisplays the link protocol for connected links, and the fail reason as a textmessage for any links on which

Seite 281

RTR Monitoring5.2 Standard Monitor Pictures5.2.11 Monitor FlowFLOW CONTROL COUNTERS 7-JAN-1999 14:08:06, NODE: -ALL- , FACILITY: -ALL-CREDIT DATA RATE

Seite 282

RTR Monitoring5.2 Standard Monitor Pictures5.2.13 Monitor IPCRTR> Monitor IPCNode: LENGTH I P C S u mmary FriMar 51999 11:18:34+-------------------

Seite 283

RTR Monitoring5.2 Standard Monitor PicturesDisplays information about journal usage, including total number of entries andrecords written, number of r

Seite 284

RTR Monitoring5.2 Standard Monitor Pictures5.2.18 Monitor NetstatConnection Status DetailNode: NODEA Mon March 15 1999 09:50:28Ini Cnf Acc Abo Rej Los

Seite 285

RTR Monitoring5.2 Standard Monitor PicturesTable 5–3 (Cont.) Monitor Partition StatesState Meaningactive Server is activepri_act Server is active as p

Seite 286

RTR Monitoring5.2 Standard Monitor PicturesServer recovery state meanings are shown in Table 5–4.Table 5–4 Monitor Recovery StatesState Meaningwt_tr_o

Seite 287

RTR Monitoring5.2 Standard Monitor Pictures5.2.24 Monitor RejhistRejected Transaction HistoryNODE: NODEA PROCESS: 38009A8B Mon Mar 9 1999 10:26:14Time

Seite 288

STOP RTR . ... 6–177TRIM FACILITY ... 6–179UNREGISTER RESOURCE M

Seite 289

RTR Monitoring5.2 Standard Monitor Pictures5.2.26 Monitor RolequorumQUORUM COUNTS BY FACILITY 7-JAN-1999 14:32:48, NODE: -ALL-Router View of Backend V

Seite 290

RTR Monitoring5.2 Standard Monitor Pictures5.2.29 Monitor RSCBERTR> Monitor rscbeMost Recent RSC Dclsrv Calls History on Backend LENGTH Thu Mar 4 1

Seite 291

RTR Monitoring5.2 Standard Monitor Pictures5.2.31 Monitor StallsNETWORK STALLS AT 29-JAN-1999 15:35:03, ON NODE: TR1QIOs Bytes Link StallsIssued Rate

Seite 292

RTR Monitoring5.2 Standard Monitor Pictures5.2.32 Monitor SystemSystem Status at 10:27:51 Fri Apr 9 1999node: NODEAResource OK WarningFacility QUORUM

Seite 293

RTR Monitoring5.2 Standard Monitor Pictures5.2.33 Monitor TPSTRANSACTION COMMITS BY PROCESS 14:37:23 7-JAN-1999CommitsNode ID Process Abs. Rate 10 20

Seite 294

RTR Monitoring5.2 Standard Monitor Pictures5.2.36 Monitor V2CALLSRTR> Monitor V2CALLSRTR system service calls, Node: NODEA , PID: 00000000, Process

Seite 296

6RTR Command Line InterfaceEach RTR API call can be invokedat CLI levelusing the RTR command utility.This is provided to facilitate testing. For examp

Seite 297

ADD FACILITYADD FACILITYSee CREATE FACILITY; ADD FACILITY is retained for compatibility reasonsonly.6–2 RTR Command Line Interface

Seite 298

CALL RTR_ACCEPT_TXCALL RTR_ACCEPT_TXThe CALL RTR_ACCEPT_TX command causes a command server to executethertr_accept_tx( )routine and to display the ret

Seite 299

Figures2–1 Configuration Example ... 2–22–2 Extend Configuration Example . . ... 2–6A–1 Intera

Seite 300

CALL RTR_ACCEPT_TXQualifiers/CHANNEL_NAME=channel_name/CHANNEL_NAME=RTR$DEFAULT_CHANNELSpecifies the channel for which the operation is to be performed.

Seite 301

CALL RTR_ACCEPT_TXRelated Commands•CALL RTR_OPEN_CHANNEL•CALL RTR_REJECT_TXExamplesAccept the current transaction with a reason of 42.RTR> CALL RTR

Seite 302

CALL RTR_BROADCAST_EVENTCALL RTR_BROADCAST_EVENTThe CALL RTR_BROADCAST_EVENT command causes a command server toexecute thertr_broadcast_event( )routin

Seite 303 - RTR log messages

CALL RTR_BROADCAST_EVENTTable 6–2 Parameters for rtr_broadcast_eventC Parameter Name C Parameter Value Command Line Specificationchannel /CHANNEL_NAME=

Seite 304

CALL RTR_BROADCAST_EVENTTable 6–3 Generated Format StringsData Type With /LENGTH= With /NOLENGTHSTRING =n, "%nC" "%nC" where n=str

Seite 305

CALL RTR_BROADCAST_EVENTRTR> CALL RTR_BROADCAST_EVENT "Dollar is up"/EVENT_NUMBER=23%RTR-S-OK, Normal successful completionThe following

Seite 306

CALL RTR_CLOSE_CHANNELCALL RTR_CLOSE_CHANNELThe CALL RTR_CLOSE_CHANNEL command causes a command server toexecute thertr_close_channel( )routine and to

Seite 307

CALL RTR_CLOSE_CHANNEL/CLUSTER/NOCLUSTER (D)Specifies that the command is executed on all the nodes in the cluster.If neither/NODEnor/CLUSTERis specifie

Seite 308

CALL RTR_ERROR_TEXTCALL RTR_ERROR_TEXTThe CALL RTR_ERROR_TEXT command causes a command server to executethertr_error_text( )routine and to display the

Seite 309

CALL RTR_GET_TIDCALL RTR_GET_TIDThe CALL RTR_GET_TID command causes a command server to execute thertr_get_tid( )routine and to display the returned s

Seite 310

A–3 Arithmetic Operators in Display Commands ... A–4ix

Seite 311

CALL RTR_GET_TIDIf neither/NODEnor/CLUSTERis specified then the command is executed on thenodes specified by the latestSET ENVIRONMENTcommand. If noSET

Seite 312

CALL RTR_OPEN_CHANNELCALL RTR_OPEN_CHANNELThe CALL RTR_OPEN_CHANNEL command causes a command server toexecute thertr_open_channel( )routine and to dis

Seite 313

CALL RTR_OPEN_CHANNELrtr_status_t rtr_open_channel (rtr_channel_t *pchannel,rtr_ope_flag_t flags,rtr_facnam_t facnam,rtr_rcpnam_t rcpnam,rtr_evtnum_t

Seite 314

CALL RTR_OPEN_CHANNEL/ACCESS=access/NOACCESS (D)Specifies an access string (that is, a password). All application programs (clientsand servers) must sp

Seite 315

CALL RTR_OPEN_CHANNEL/FACILITY_NAME=facility-name/FACILITY=RTR$DEFAULT_FACILITY (D)Specifies the name of the facility for which the channel is declared

Seite 316

CALL RTR_OPEN_CHANNELlength_of_key=nnnnSpecifies the length of the key field in enqueued messages inbytes. Use this qualifier only if the key field type i

Seite 317

CALL RTR_OPEN_CHANNEL/OFFSET_OF_KEY=offset/OFFSET_OF_KEY=0 (D)Specifies the offset of the key within the messages in bytes. The default is zero,that is

Seite 318

CALL RTR_OPEN_CHANNEL/TYPE_OF_FIELD=key-field-type/TYPE_OF_FIELD=UNSIGNED (D)Specifies the field type of the key. Thekey-typemust be one of UNSIGNED,SIGN

Seite 319

CALL RTR_PREPARE_TXCALL RTR_PREPARE_TXThe CALL RTR_PREPARE_TX command causes a command server to executethertr_prepare_tx( )routine and to display the

Seite 320

CALL RTR_PREPARE_TXThe CALL RTR_PREPARE_TX can only be used in the context of nestedtransactions (rtr_start_tx was called with the parameter join_txid

Kommentare zu diesen Handbüchern

Keine Kommentare