Compaq AA-Q88CE-TE - Manual

STOP RTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–177 TRIM FACILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–179 UNREGISTER RESOURCE MANAGER (UNREGISTER RM) . . . . . . . . . 6–182 A Creating ...

Figures 2–1 Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2 2–2 Extend Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6 A–1 Interactively Defined Monitor Picture . . . . . . . . . . . . . . . . . . . . . . . . . A...

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

Preface Purpose of this Manual This manual describes how to configure, manage and monitor the operation ofReliable Transaction Router (RTR) using the RTR Command Line Interface (CLI). Intended Audience The System Manager ’s Manual is intended for persons who perform systemmanagement functions to con...

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 commentsby email to [email protected] . Include the title of the ma...

Table 1 Conventions Used in this Guide Convention Meaning UPPERCASElowercase Some operating systems differentiate between lowercase anduppercase characters. For these systems, examples, syntaxdescriptions, function definitions, and literal strings that appearin text must be typed exactly as shown. C...

1 Introduction For a general introduction to Reliable Transaction Router, Version 3.2 (RTR),you should read the introductory chapter in the Reliable Transaction RouterApplication Design Guide. Additional information about the Reliable TransactionRouter is available in the Reliable Transaction Router...

Introduction1.2 Entering Commands or, when several commands are to be entered at the RTR prompt: % rtrRTR> start rtrRTR> create journal Note For convenience, the user prompt for the operating system is shown hereas the ‘‘%’’ symbol. Your system may have a different prompt. The RTR CLI accepts ...

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

Introduction1.5 Remote Commands This command starts RTR on the three nodes. Note The /CLUSTER and /NOCLUSTER command qualifiers refer to clustersupport. These qualifiers are for operating systems that fully supportclustering. Use of the /CLUSTER qualifier on systems that do not haveclustering causes...

2 Starting and Setting Up RTR This chapter describes how to configure and start an RTR environment. Recoveryjournals, 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...

Starting and Setting Up RTR2.2 Setting Up—An Example Figure 2–1 Configuration Example F E 1 F E 2 F E 3 T R 1 T R 2 B E 1 B E 2 B E 3 SMM_CONFIG_EX 01−99 F r o n t e n d R o u t e r s ( T R ) B a c k e n d s ( B E ) s ( F E ) In this example, the application client processes run on the nodes FE1, FE...

Starting and Setting Up RTR 2.2 Setting Up—An Example Example 2–2 illustrates how to use RTR remote commands to start the sameconfiguration. The set environment command is used to send subsequent commands to a number of RTR nodes. Example 2–2 Remote Setup from one Node % rtrRTR> set environment/n...

Starting and Setting Up RTR2.3 Creating a Recovery Journal • The operator should move any duplicate copies of journal files to alocation other than the rtrjnl/groupname directory so that RTR will see only the one it created. • Track duplicate copies of journal files in the log file to prevent RTRsee...

Starting and Setting Up RTR 2.4 Changing a Facility Example 2–3 Reconfiguration Using Delete and Create Facility % rtrRTR> stop rtr/node=FE3 1 RTR> delete facility funds_transfer/node=TR2 2 RTR> create facility funds_transfer/node=TR2 - 3 _RTR> /frontend=(FE1,FE2) - _RTR> /router=TR2 ...

Starting and Setting Up RTR2.4 Changing a Facility Figure 2–2 Extend Configuration Example SMM_CONFIG_EX_EXT 02−99 F E 1 F E 2 F E 3 F E 4 T R 1 T R 2 T R 3 B E 1 B E 2 B E 3 B A C K E N D S R O U T E R S F R O N T E N D S All backend nodes must be informed when router configurations are changed.Bec...

Starting and Setting Up RTR 2.4 Changing a Facility Example 2–4 Reconfiguration Using Extend Facility % RTRRTR> start rtr /node=(TR3,FE4)RTR> set environment/node= - 1 _RTR> (FE1,FE2,FE3,TR1,TR2,BE1,BE2,BE3,TR3,FE4) RTR> extend facility funds_transfer - 2 _RTR> /router=TR3/frontend=(F...

Starting and Setting Up RTR2.5 Setting up Callout Servers Example 2–5 Configuration of Callout Servers % rtrRTR> set environment/node= -_RTR> (FE1,FE2,FE3,TR1,TR2,BE1,BE2,BE3) RTR> start rtr RTR> create facility funds_transfer/frontend=(FE1,FE2,FE3) -_RTR> /router=(TR1,TR2) - _RTR>...

Starting and Setting Up RTR 2.6 Router Load Balancing • Use /balance on frontend nodes only. Use of /balance on routers is supported only to enable RTR Version 2 balancing. Use this qualifier only when you areconnecting frontend nodes running RTR Version 2. See CREATE FACILITYand SET FACILITY for mo...

Starting and Setting Up RTR2.7 RTR Privileges The rtrinfo group is currently only used to allow applications to call rtr_request_info( ) For other users, create the groups rtroper and rtrinfo Users who do not fall into the above categories, but are members of the rtrinfo group can only use RTR comma...

Starting and Setting Up RTR 2.8 RTR ACP Virtual Memory Sizing • Add the size of all messages 2. For each transaction router: • Allow one Kbyte for each active transaction 3. For each back end: • Allow one Kbyte per active transaction • Allow fifty bytes for each message of a transaction • Add the si...

Starting and Setting Up RTR2.8 RTR ACP Virtual Memory Sizing Use of /LINK and /PROCESSES do not take into account memory requirementsfor transactions. If an application passes a large amount of data from client toserver or vice-versa this should be included in the sizing calculations. For furtherinf...

Starting and Setting Up RTR 2.8 RTR ACP Virtual Memory Sizing A minimum of 419430 Kbytes for heap data segment sizing A minimum of 33555 Kbytes for core file size A minimum of 8389 Kbytes for stack segment size A minimum of 0 for CPU time • On HPUX: A minimum of 1024 open file descriptors The START ...

Starting and Setting Up RTR2.9 Network Transports 2.9.2 Using RTR with DHCP and Internet Tunnels When using RTR with DHCP or an Internet tunnel, a nodename may not be fullyknown; special naming techniques are provided for these conditions. Anonymous Clients RTR allows the use of wild cards when spec...

Starting and Setting Up RTR 2.9 Network Transports This informs the system administrator that port number 46000/tcp is reservedfor RTR. (Note that the RTR daemon is started by RTRACP and not by inetd ). 2.9.3 Interoperation with RTR Version 2 Using DECnet Reliable Transaction Router is interoperable...

Starting and Setting Up RTR2.10 Network Protocol Selection on OpenVMS 2.10 Network Protocol Selection on OpenVMS • The default network transport protocol on OpenVMS is DECnet. You maychange the default to TCP/IP by removing this line from RTR$STARTUP.COM : $ DEFINE/SYSTEM RTR_PREF_PROT RTR_DNA_FIRST...

Starting and Setting Up RTR 2.11 Running RTR as a Service on Windows NT 2.11.1 Customizing the RTR Windows NT Service While starting RTR, the Service looks for the file UsrStart.RTR in the RTR home directory. On finding the file, the Service executes any RTR commands it maycontain. RTR commands from...

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodes 2.12 How RTR Selects Processing-states (Roles) for Nodes This section discusses how RTR assigns roles to backend node partitions, andhow routers are selected. 2.12.1 Role Assignment for Backend Node Partitions RTR as...

Starting and Setting Up RTR 2.12 How RTR Selects Processing-states (Roles) for Nodes The SHOW PARTITION command on each backend node is as follows: Backend partitions on node BRONZE in group "test" at Mon Mar 22 14:52:32 1999 Partition name: p1 Facility: RTR$DEFAULT_FACILITY State: pri_act L...

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodes 8. The network connection to node Gold is reestablished. The partition on Goldretained its original sequence number of 2 and retains the primary role whilethe partition on Bronze reassumes the secondary role. Alterna...

Starting and Setting Up RTR 2.12 How RTR Selects Processing-states (Roles) for Nodes Router Site A Site B Node-A1 Node-A2 Node-B1 Node-B2 If the relative priority (sequence number) for Node-A2 is changed to four it stillbecomes the primary active server if Node-A1 fails because the failover policyin...

Starting and Setting Up RTR2.12 How RTR Selects Processing-states (Roles) for Nodes relevant to a backend. It is where the backend goes to obtain and verify partitionconfiguration and facility information. Routers are made known to the frontend systems through the list specified inthe /ROUTER=(list)...

3 Partition Management 3.1 Overview This section describes the concepts and operations of RTR’s partitions. 3.1.1 What is a Partition? Partitions are subdivisions of a routing key range of values. They are used witha partitioned data model and RTR data content routing. Partitions exist foreach disti...

Partition Management3.2 Partition Naming 3.2 Partition Naming A prerequisite for partition management is the ability to identify a partition inthe system that is to be the subject of management commands. For this purpose,partitions have been given names, which may be drawn from a number of sourcesde...

Partition Management 3.3 Life Cycle of a Partition 3.3.1 Implicit Partition Creation Partitions are created implicitly when an application program calls rtr_open_channel( ) to create a server channel, specifying the key segments and value ranges for the segments with the pkeyseg argument. Other part...

Partition Management3.5 Entering Partition Commands 3.5 Entering Partition Commands Partitions can be managed by issuing partition commands directed at therequired partition after they are created. Partition commands can be entered inone of two ways: • A command line processed by the RTR command lin...

Partition Management 3.5 Entering Partition Commands The rtr_set_info( ) call completes asynchronously. If the function call is successful, completion will be signaled by the delivery of an RTR messageof type rtr_mt_closed on the channel whose identifier is returned through the pchannel argument. Th...

Partition Management3.6 Managing Partitions 3.6.2 Controlling Transaction Presentation Transaction presentation is the process of passing transactions to idle serverchannels for processing. While transaction presentation is active, newtransactions are started on the first free server channel for the...

Partition Management 3.6 Managing Partitions If a partition enters a wait state or fails but has neither a local or remote journal,an operator can instruct RTR to skip the current step in the recovery processwith the /IGNORE_RECOVERY qualifier. Since this command bypasses parts of the recovery cycle...

Partition Management3.6 Managing Partitions 3.6.4.2 Programming Information To set the partition backend priority list, program the set_qualifier argument of the rtr_set_info( ) call as follows: rtr_qualifier_value_t set_qualifiers[ 2 ]; char *szNodeList = "your,list,of,node,names,here" set_...

Partition Management 3.6 Managing Partitions • rtr_partition_fail_to_shadow • rtr_partition_pre32_compatible 3.6.6 Controlling Transaction Replay RTR has implemented the capability of controlling transaction replay in caseswhere a "killer message" happens during a transaction replay preventi...

Partition Management3.7 Displaying Partition Information 3.7 Displaying Partition Information Information on the definition and state of a partition is displayed with the SHOW PARTITION command. The information of interest in the context of partition management relates to the backend instance of the...

4 Transaction Management 4.1 Overview This section describes the concepts of RTR’s transaction management capability. The RTR transaction is the heart of an RTR application, and transaction stateis the property that characterizes a transaction’s current condition. Whenever atransaction progresses fr...

Transaction Management4.1 Overview this transaction is removed from memory and can no longer be monitored by the command. The RTR DUMP JOURNAL command can be used to trace and review the flow of a transaction. The RTR journal saves all of the information about a transaction,its transaction journal s...

Transaction Management 4.1 Overview 4.1.2 Transaction State Changes There are eight valid state changes allowed for the SET TRANSACTION command. Attempting to change transaction state to a state that is not allowed producesan error message of %RTR-E-INVSTATCHANGE, Invalid to change from current stat...

Transaction Management4.1 Overview This is the case where, for example, a server crashed while performing an SQL commit immediately after receiving a mt_accepted message. The transaction is in COMMIT state as recorded in the RTR journal and thetransaction is also committed in the underlying database...

5 RTR Monitoring This chapter contains a description of the RTR monitor. The RTR monitorgives you a means of viewing the activities of RTR and your applications. Manydifferent aspects of RTR’s behaviour can be viewed, allowing the activities andperformance of RTR to be analyzed. 5.1 Introduction The...

RTR Monitoring5.2 Standard Monitor Pictures Note Obsolete monitor pictures have been removed from the documentation. Table 5–1 Standard Monitor Pictures Picture name Description accfail Shows link transport name for links on which a connection attempt was declined,with a reason for failure. The most...

RTR Monitoring5.2 Standard Monitor Pictures Table 5–1 (Cont.) Standard Monitor Pictures Picture name Description traffic Displays a list of the links to other nodes. Shown for each link are: byte rate, packetrate, message rate and congestion, in both directions. Average packets per second isalso sho...

RTR Monitoring 5.2 Standard Monitor Pictures your domain name, depending on how the name is entered in either your localhosts file or name server. DECnet-Plus systems may yield both a pseudonymand a link name; both are checked for a match with a template. • RTR_STS_FACNOTDEC - "facility name not...

RTR Monitoring5.2 Standard Monitor Pictures 5.2.3 Monitor Active ACTIVE TRANSACTIONS BY PROCESS Fri Mar 12 1999 19:32:41 Starts Completions Active All processes: 5 5 0 Node ID Process Image NodeA 11141 11141 rtr 5 5 0 Displays a list of RTR processes, and for each process the number of transactionst...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.6 Monitor Calls RTR api calls, Node: nodea.zuo.dec.com , PID: 2162 , Process name: -ALL- Image: -ALL- Fri Feb 12 1999 16:38:05 CALLS client server fail MESSAGES client server pend open_channel 1 1 0 mt_opened 1 1 0 close_channel 0 0 0 mt_closed 0 0 0 ...

RTR Monitoring5.2 Standard Monitor Pictures Displays the link protocol for connected links, and the fail reason as a textmessage for any links on which a connection has failed. Unconnected links whereconnection have been attempted are highlighted. Link state and architecture ofthe remote node are al...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.11 Monitor Flow FLOW CONTROL COUNTERS 7-JAN-1999 14:08:06, NODE: -ALL- , FACILITY: -ALL- CREDIT DATA RATE REQUESTS GRANTS ROLE AVAILABLE BYTES/SEC WAITS SENT PENDING SENT PENDING FE=>TR 15000 2065 307 966 0 966 0 TR=>BE 15000 2065 70 998 0 998 0...

RTR Monitoring5.2 Standard Monitor Pictures 5.2.13 Monitor IPC RTR> Monitor IPCNode: LENGTH I P C S u m m a r y Fri Mar 5 1999 11:18:34 +----------------------------------------------------------------------------+ This screen displays usage information on IPC messages, byte counts and IOprimitiv...

RTR Monitoring 5.2 Standard Monitor Pictures Displays information about journal usage, including total number of entries andrecords written, number of records read, and how many bytes were involved. Bargraphs showing current usage of journal blocks (as a percentage of the total) arealso provided. Th...

RTR Monitoring5.2 Standard Monitor Pictures 5.2.18 Monitor Netstat C o n n e c t i o n S t a t u s D e t a i l Node: NODEA Mon March 15 1999 09:50:28 Ini Cnf Acc Abo Rej Loss Gain Ctmo Rstr State Type FailCode Node Link 12 0 2 12 12 1 3 0 0 NODEA ->nodeb 0 0 0 0 0 0 1 0 0 up alpha NODEA ->node...

RTR Monitoring5.2 Standard Monitor Pictures Server recovery state meanings are shown in Table 5–4. Table 5–4 Monitor Recovery States State Meaning wt_tr_ok Server is waiting for routers to accept it wt_quorum Server is waiting for backend to be quorate lcl_rec Local recovery lcl_rec_fail Primary ser...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.24 Monitor Rejhist Rejected Transaction History NODE: NODEA PROCESS: 38009A8B Mon Mar 9 1999 10:26:14 Time Chan Reason Status Text ------------------- ------ ------- -------------------------------------- Mon Mar 15 18:06:06 client 0 Client aborted tx...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.29 Monitor RSCBE RTR> Monitor rscbe Most Recent RSC Dclsrv Calls History on Backend LENGTH Thu Mar 4 1999,15:19:41 Key Range Id: 16777216 Partition Start Time: THU MAR 4 15:18:22 1999 Image Name: RTR.EXE T-delta RSC calls router state seq_nr 0 send...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.32 Monitor System System Status at 10:27:51 Fri Apr 9 1999 node: NODEA Resource OK Warning Facility QUORUM states...... x JOURNAL free space.......... x Note: Additional detail Link CONNECTS............... x about a resource can beobtained by monitori...

RTR Monitoring5.2 Standard Monitor Pictures 5.2.33 Monitor TPS TRANSACTION COMMITS BY PROCESS 14:37:23 7-JAN-1999 Commits Node ID Process Abs. Rate 10 20 30 40 50 60 70 80 90 100 -ALL- 00000000 -REQUESTERS- 123298 31.8 -ALL- 00000000 -SERVERS- 123297 28.9 NODEA 20200BEA RTRACP 0 0.0 NODEA 20200C03 A...

RTR Monitoring 5.2 Standard Monitor Pictures 5.2.36 Monitor V2CALLS RTR> Monitor V2CALLS RTR system service calls, Node: NODEA , PID: 00000000, Process name: -ALL-Image: -ALL- 13:09:18 5-MAR-1999 Accept Reject Success Failure Outstng Calls dcl_tx_prc/server 3 0 4 0 0 4 dcl_tx_prc/req. 1 dcl_tx_pr...

6 RTR Command Line Interface Each RTR API call can be invoked at CLI level using the RTR command utility. This is provided to facilitate testing. For example, clients may be tested beforethe corresponding servers have been written by manually entering the server ’sAPI calls. 6.1 Introduction The com...

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

CALL RTR_ACCEPT_TX CALL RTR_ACCEPT_TX The CALL RTR_ACCEPT_TX command causes a command server to executethe rtr_accept_tx( ) routine and to display the returned status. Format CALL RTR_ACCEPT_TX Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /CLUSTER /NOCLUST...

CALL RTR_ACCEPT_TX Qualifiers /CHANNEL_NAME=channel_name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL Specifies the channel for which the operation is to be performed. The command server uses a combination of the channel_name and the windowfrom which the call was issued to uniquely identify which channel to us...

CALL RTR_ACCEPT_TX Related Commands • CALL RTR_OPEN_CHANNEL • CALL RTR_REJECT_TX Examples Accept the current transaction with a reason of 42. RTR> CALL RTR_ACCEPT_TX /REASON=42%RTR-S-OK, normal successful completion RTR Command Line Interface 6–5

CALL RTR_BROADCAST_EVENT CALL RTR_BROADCAST_EVENT The CALL RTR_BROADCAST_EVENT command causes a command server toexecute the rtr_broadcast_event( ) routine and to display the returned status. Format CALL RTR_BROADCAST_EVENT [message-field1] [,message-field2...] Parameters [message-field1] [,message-...

CALL RTR_BROADCAST_EVENT Table 6–2 Parameters for rtr_broadcast_event C Parameter Name C Parameter Value Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS [none] [D] pmsg, msglen,msgfmt 1 [message definition parameter list with positionalqualifiers. ] evtnum 42 /EVENT_NUMBER=4...

CALL RTR_BROADCAST_EVENT Table 6–3 Generated Format Strings Data Type With /LENGTH= With /NOLENGTH STRING =n, "%nC" "%nC" where n=strlen(string) SIGNED =1, "%SB" "%SL" SIGNED =2, "%SW" "%SL" SIGNED =4, "%SL" "%SL" UNSIGNED =1, "%UB&...

CALL RTR_BROADCAST_EVENT RTR> CALL RTR_BROADCAST_EVENT "Dollar is up"/EVENT_NUMBER=23%RTR-S-OK, Normal successful completion The following command broadcasts user event number 24 to all recipientswhose /RECIPIENT_NAME matches the DEALER% string (that is, DEALER1,DEALER2, DEALERx). Note th...

CALL RTR_CLOSE_CHANNEL CALL RTR_CLOSE_CHANNEL The CALL RTR_CLOSE_CHANNEL command causes a command server toexecute the rtr_close_channel( ) routine and to display the returned status. Format CALL RTR_CLOSE_CHANNEL Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANN...

CALL RTR_CLOSE_CHANNEL /CLUSTER/NOCLUSTER (D) Specifies that the command is executed on all the nodes in the cluster. If neither /NODE nor /CLUSTER is specified then the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered t...

CALL RTR_ERROR_TEXT CALL RTR_ERROR_TEXT The CALL RTR_ERROR_TEXT command causes a command server to executethe rtr_error_text( ) routine and to display the returned error text. Format CALL RTR_ERROR_TEXT Command Qualifiers Defaults /OUTPUT[=file-spec] /OUTPUT=stdout /STATUS=status-code /none Descript...

CALL RTR_GET_TID CALL RTR_GET_TID The CALL RTR_GET_TID command causes a command server to execute the rtr_get_tid( ) routine and to display the returned status. Format CALL RTR_GET_TID Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /CLUSTER /NOCLUSTER /NODE[...

CALL RTR_GET_TID If neither /NODE nor /CLUSTER is specified then the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered then the command is executed only on the node wherethe command was issued. Note: In environments that ...

CALL RTR_OPEN_CHANNEL CALL RTR_OPEN_CHANNEL The CALL RTR_OPEN_CHANNEL command causes a command server toexecute the rtr_open_channel( ) routine and to display the returned status. Format CALL RTR_OPEN_CHANNEL Command Qualifiers Defaults /ACCEPT_EXPLICIT /NOACCEPT_EXPLICIT /ACCESS=access /NOACCESS /B...

CALL RTR_OPEN_CHANNEL rtr_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 *pevtnum, rtr_access_t access, rtr_numseg_t numseg, rtr_keyseg_t *pkeyseg ) ; Table 6–7 shows the correspondence between values you supply on th...

CALL RTR_OPEN_CHANNEL /ACCESS=access/NOACCESS (D) Specifies an access string (that is, a password). All application programs (clientsand servers) must specify the same access string for a given facility. /BE_CALL_OUT/NOBE_CALL_OUT (D) Specifies that the RTR_F_OPE_BE_CALL_OUT flag is set in the flags...

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. An applicationmust specify the facility name when using the RTR CLI. The default facility nameis RTR$DEFAULT_FACILITY. /FOREIGN_TM[=tm_id]/NOFORE...

CALL RTR_OPEN_CHANNEL length_of_key=nnnn Specifies the length of the key field in enqueued messages in bytes. Use this qualifier only if the key field type is string, since the key length isin other cases implied by the key type. The default value for key-length is four bytes. offset_of_key=nnnn Spe...

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, the key is at the start of the messages.Note that only one key segment definition is allowed. /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies tha...

CALL RTR_OPEN_CHANNEL /TYPE_OF_FIELD=key-field-type/TYPE_OF_FIELD=UNSIGNED (D) Specifies the field type of the key. The key-type must be one of UNSIGNED, SIGNED or STRING. The default is UNSIGNED. Related Commands • CALL RTR_CLOSE_CHANNEL Examples This command opens a server channel called RTR$DEFAU...

CALL RTR_PREPARE_TX CALL RTR_PREPARE_TX The CALL RTR_PREPARE_TX command causes a command server to executethe rtr_prepare_tx( ) routine and to display the returned status. Format CALL RTR_PREPARE_TX Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /DATA[=data]...

CALL RTR_PREPARE_TX The CALL RTR_PREPARE_TX can only be used in the context of nestedtransactions (rtr_start_tx was called with the parameter join_txid not equalto NOJOIN_TXID). If this call returns RTR_STS_OK, then the first (prepare)phase of the RTR 2PC protocol has been initiated. The message typ...

CALL RTR_PREPARE_TX /REASON[=reason]/REASON=0 Use /REASON to supply a value for the reason parameter in the call to rtr_prepare_tx( ) . The reason parameter to rtr_prepare_tx( ) is used in place of the reason parameter in the subsequent rtr_accept_tx call( ) (that is, the reason field in the call to...

CALL RTR_RECEIVE_MESSAGE CALL RTR_RECEIVE_MESSAGE The CALL RTR_RECEIVE_MESSAGE command causes a command server toexecute the rtr_receive_message( ) routine and to display the returned status. Format CALL RTR_RECEIVE_MESSAGE Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEF...

CALL RTR_RECEIVE_MESSAGE For all messages received, RTR displays the contents of the message status block(msgsb) as follows: the message type (for example, rtr_mt_opened , rtr_mt_msgn ). the message length in bytesthe transaction ID, user handle, are event number are shown if they arerelevant for th...

CALL RTR_RECEIVE_MESSAGE /TIMEOUT_MS=timoutms/TIMEOUT_MS=0 (D) The timoutms argument defines a timeout for the receive, in milliseconds. Thedefault value is an infinite timeout. /TIMEOUT_MS specifies an immediatetimeout. Examples The following example shows two CALL RTR_RECEIVE_MESSAGE commands on R...

CALL RTR_REJECT_TX CALL RTR_REJECT_TX The CALL RTR_REJECT_TX command causes a command server to executethe rtr_reject_tx( ) routine and to display the returned status. Format CALL RTR_REJECT_TX Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /CLUSTER /NOCLUST...

CALL RTR_REJECT_TX channel_name is not case sensitive. The default channel name is RTR$DEFAULT_CHANNEL. /CLUSTER/NOCLUSTER (D) Specifies that the command is executed on all the nodes in the cluster. If neither /NODE nor /CLUSTER is specified then the command is executed on the nodes specified by the...

CALL RTR_REJECT_TX Examples Reject the current transaction with a reason of 42. RTR> CALL RTR_REJECT_TX /REASON=42%RTR-S-OK, normal successful completion 6–30 RTR Command Line Interface

CALL RTR_REPLY_TO_CLIENT CALL RTR_REPLY_TO_CLIENT The CALL RTR_REPLY_TO_CLIENT command causes a command server toexecute the rtr_reply_to_client( ) routine and to display the returned status. Format CALL RTR_REPLY_TO_CLIENT [message-field1] [,message-field2...] Parameters [message-field1] [,message-...

CALL RTR_REPLY_TO_CLIENT Table 6–11 Parameters for rtr_reply_to_client C Parameter Name C Parameter Value Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS none [D] RTR_F_REP_ACCEPT /ACCEPT pmsg, msglen,msgfmt 1 [message definition parameter list with positionalqualifiers.] 1 ...

CALL RTR_REPLY_TO_CLIENT Table 6–12 Generated Format Strings Data Type With /LENGTH= With /NOLENGTH STRING =n, "%nC" "%nC" where n=strlen(string) SIGNED =1, "%SB" "%SL" SIGNED =2, "%SW" "%SL" SIGNED =4, "%SL" "%SL" UNSIGNED =1, "%UB...

CALL RTR_REPLY_TO_CLIENT Examples The following example replies a message to the client. RTR> CALL RTR_REPLY_TO_CLIENT "Getting that info for you" %RTR-S-OK, Normal successful completion The following example shows a message of type unsigned and entered as ahexadecimal number. RTR> CAL...

CALL RTR_REQUEST_INFO CALL RTR_REQUEST_INFO The CALL RTR_REQUEST_INFO command causes a command server toexecute the rtr_request_info( ) routine and to display the returned status. Format CALL RTR_REQUEST_INFO Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /C...

CALL RTR_REQUEST_INFO Qualifiers /CHANNEL_NAME=channel_name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL Specifies the channel for which the operation is to be performed. The command server uses a combination of the channel_name and the windowfrom which the call was issued to uniquely identify which channel to...

CALL RTR_REQUEST_INFO Examples This command requests the backend transaction IDs for the facility ‘‘CASHFAC’’. RTR> CALL RTR_REQUEST_INFO/CHANNEL=INFOCHAN/INFCLA="btx"/SELITM=fac_id/SELVAL=CASHFAC/GETITMS=tb_txdx.tx_id The information can then be viewed by repeatedly executing the followi...

CALL RTR_SEND_TO_SERVER CALL RTR_SEND_TO_SERVER The CALL RTR_SEND_TO_SERVER command causes a command server toexecute the rtr_send_to_server( ) routine and to display the returned status. Format CALL RTR_SEND_TO_SERVER [message-field1] [,message-field2...] Parameters [message-field] [,message-field2...

CALL RTR_SEND_TO_SERVER Table 6–14 Parameters for rtr_send_to_server C Parameter Name C Parameter Value Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS none [D] RTR_F_SEN_EXPENDABLE /EXPENDABLE RTR_F_SEN_READONLY /READONLY RTR_F_SEN_RETURN_TO_SENDER /RETURN_TO_SENDER pmsg, m...

CALL RTR_SEND_TO_SERVER If /FORMAT is specified without fmt-string , RTR automatically generates a format string. The format string is generated using the parameters given forthe qualifiers /SIGNED, /UNSIGNED, /STRING and /LENGTH. The followingtable shows permitted values for these qualifiers when u...

CALL RTR_SEND_TO_SERVER Examples This command sends a message to a server. The message is type string (the default). RTR> CALL RTR_SEND_TO_SERVER "Get that info for me, please" %RTR-S-OK, Normal successful completion RTR Command Line Interface 6–41

CALL RTR_START_TX CALL RTR_START_TX The CALL RTR_START_TX command causes a command server to execute the rtr_start_tx( ) routine and to display the returned status. Format CALL RTR_START_TX Command Qualifiers Defaults /CHANNEL_NAME=channel-name /CHANNEL_NAME=RTR$DEFAULT_CHANNEL /CLUSTER /NOCLUSTER /...

CALL RTR_START_TX phase cannot be executed on an client FTM channel, may be relaxed in afuture release.) When a nested transaction is started (join_txid not equal to NOJOIN_TXID), then that transaction is given a new RTR TXID (which theoperator can retrieve by calling rtr_get_tid). The foreign TXID ...

CALL RTR_START_TX /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . If /OUTPUT or file-spec is omitted then the standard or default output is used. /TIMEOUT_MS=timoutms/TIMEOUT_MS=0 (D) The timoutms argument defines a timeout for the tr...

CLEAR CLEAR Interactively remove one or more displayed items from a monitor picture. Format CLEAR Command Qualifiers Defaults /ALL /NOALL /X=column/Y=row Description The CLEAR command enables you to interactively remove one or all of the displayed items from a monitor picture. The picture can then b...

CLEAR Examples See Section A.1, Interactive Definition of a Monitor Picture, for an example of how to use the CLEAR command. 6–46 RTR Command Line Interface

CREATE FACILITY CREATE FACILITY Create an RTR facility and ready it for transaction traffic. Format CREATE FACILITY [facility_name] Command Qualifiers Defaults /ALL_ROLES=node-list /NOALL_ROLES /BACKEND=backend-list /NOBACKEND /BALANCE /NOBALANCE /CALL_OUT=role-list /NOCALL_OUT /CLUSTER /NOCLUSTER /...

CREATE FACILITY Qualifiers /ALL_ROLES=node-list /NOALL_ROLES (D) Specifies the names of the nodes that are to act as frontend, router and backend in this facility. Note that the definition order of nodes may be significant. This applies to theorder of router node definitions when frontend load balan...

CREATE FACILITY Note: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on the local node only. /FRONTEND=frontend-list/NOFRONTEND (D) Frontend-list is a list of frontend-nodes separated by commas. If there is more than one fr...

CREATE FACILITY Examples See Chapter 2, Starting and Setting Up RTR, for examples of how to use the CREATE FACILITY command. 6–50 RTR Command Line Interface

CREATE JOURNAL CREATE JOURNAL Create RTR’s recovery journal. Format CREATE JOURNAL [disk-1] ... [,disk-n] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /BLOCKS=nr-blocks /BLOCKS=1000 /MAXIMUM_BLOCKS=nr-blocks /MAXIMUM_BLOCKS=1000 /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=...

CREATE JOURNAL Table 6–17 Platform Specific Information Platform Journal Root Finding Disks Notes UNIX /rtrjnl Use df Enter disk names as thay appear in /dev . Enclose disk names in quotes and separatenames with commas. The journals reside insubdirectories of the /rtrjnl . OpenVMS [RTRJNL] Use SHOWD...

CREATE JOURNAL If /NOSUPERSEDE is specified (default), then a journal is created only if nojournal previously existed. Related commands • DELETE JOURNAL • MODIFY JOURNAL • SHOW JOURNAL Examples RTR> CREATE JOURNAL /SUPERSEDE DISK1$:/BLOCK=1000/MAX_BLOCK=10000, -_RTR> DISK2$:/BLOCK=2000/MAX_BLO...

CREATE PARTITION CREATE PARTITION Creates an RTR partition. Format CREATE PARTITION [partition_name] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /CONCURRENT /NOCONCURRENT /FACILITY=facility-name/NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout /STANDBY /NOSTANDBY /SHAD...

CREATE PARTITION /CONCURRENT (D)/NOCONCURRENT Specifies that concurrent servers are allowed for this partition. /KEYn=keysegdesc Specifies a partition key segment. Up to nine key segments may be defined fora partition (KEY1, KEY2,... up to KEY9). (If more than nine key segements arerequired, a named...

CREATE PARTITION /STANDBY (D)/NOSTANDBY Specifies that standby servers are allowed for this partition. /SHADOW/NOSHADOW (D) Specifies that shadow servers are allowed for this partition. /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . ...

DEFINE /KEY DEFINE /KEY Assign a string to a keyboard function key. Format DEFINE /KEY key-name "equivalence-string" Command Qualifiers Defaults /ECHO /ECHO /IF_STATE /NOIF_STATE /LOCK_STATE /NOLOCK_STATE /LOG /NOLOG /SET_STATE /NOSET_STATE /TERMINATE /NOTERMINATE Description This command le...

DEFINE /KEY Table 6–18 (Cont.) Key names Key-name LK201 VT100-type PF4 PF4 PF4 KP0, KP1 ..KP9 Keypad 0 .. 9 Keypad 0 .. 9 PERIOD Keypad period (.) Keypad period (.) COMMA Keypad comma (,) Keypad comma (,) MINUS Keypad minus (-) Keypad minus (-) ENTER ENTER ENTER E1 Find E2 Insert Here E3 Remove E4 S...

DEFINE /KEY /LOG/NOLOG (D) Controls whether a message is displayed indicating that the key definition hasbeen successfully created. /SET_STATE=state-name/NOSETSTATE (D) Controls whether pressing the key changes the current key state. /SET_STATE changes the current state to state-name when you press ...

DEFINE /KEY The word DEFAULT in the second line of the example refers to the fact that PF1 has been defined in the default state. Note the space before the word CREATE in the second DEFINE /KEY command. If the space is omitted, thesystem fails to recognize CREATE as the keyword for the HELP command....

DELETE FACILITY DELETE FACILITY Delete an RTR facility. Format DELETE FACILITY facility_name Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The DELETE FACILITY command removes the specified facility on the node w...

DELETE FACILITY Related Commands • CREATE FACILITY • SHOW FACILITY Examples See Chapter 2, Starting and Setting Up RTR, for examples of how to use the DELETE FACILITY command. 6–62 RTR Command Line Interface

DELETE JOURNAL DELETE JOURNAL Delete an RTR journal. Format DELETE JOURNAL Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The DELETE JOURNAL command deletes a previously created RTR journal on the node where the ...

DELETE JOURNAL Examples See Chapter 2, Starting and Setting Up RTR, for examples of how to use the DELETE JOURNAL command. 6–64 RTR Command Line Interface

DELETE PARTITION DELETE PARTITION Delete an RTR PARTITION. Format DELETE PARTITION PARTITION_name Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout /FACILITY Description The DELETE PARTITION command removes the specified partit...

DELETE PARTITION Related Commands • CREATE PARTITION • SHOW PARTITION 6–66 RTR Command Line Interface

DISPLAY BAR DISPLAY BAR Display a bar-graph in a monitor picture. Format DISPLAY BAR expression Command Qualifiers Defaults /AVERAGE=(keyword,...) /none /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLANK /BLINK=Boolean-expression /NOBLINK /BOLD=Boolean-expression /BOLD /CHARACTER=ch...

DISPLAY BAR Qualifiers /AVERAGE=(keyword,...) /NOAVERAGE Specifies that the items being monitored relating to keyword are displayed as an average. This allows a number of items to be averaged in one qualifier. The keyword can be one of the following: Keyword Meaning NODE Node data items LINK Link da...

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 the same column as defined by the previousDISPLAY command. /Y[=row]/Y=next-free-row (D) Specifies the screen row where the item is displayed (top r...

DISPLAY NUMERIC DISPLAY NUMERIC Display a number in a monitor picture. Format DISPLAY NUMERIC expression Command Qualifiers Defaults /AVERAGE=(keyword,...) /none /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLANK /BLINK=Boolean-expression /NOBLINK /BOLD=Boolean-expression /NOBOLD /D...

DISPLAY NUMERIC Related Commands • MONITOR • SHOW DISPLAY • CLEAR • DISPLAY BAR • DISPLAY SYMBOLIC • DISPLAY TEXT Examples See Section A.1 for examples of how to use the DISPLAY NUMERIC command. 6–76 RTR Command Line Interface

DISPLAY STRING DISPLAY STRING Display a string in a monitor picture. Format DISPLAY STRING expression Command Qualifiers Defaults /AVERAGE=(keyword,...) /none /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLANK /BLINK=Boolean-expression /NOBLINK /BOLD=Boolean-expression /BOLD /JUSTIF...

DISPLAY STRING The keyword can be one of the following: Keyword Meaning NODE Node data items LINK Link data items FACILITY Facility data items PROCESS Process data items PARTITION Partition data items FE_TRANSACTION Frontend transaction data items TR_TRANSACTION Backend transaction data items BE_TRA...

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 displayed in the same column as defined by the previousDISPLAY command. /Y[=row]/Y=next-free-row (D) Specifies the screen row where the item is di...

DISPLAY SYMBOLIC DISPLAY SYMBOLIC Display a text in a monitor picture depending on the result of an expressionevaluation. Format DISPLAY SYMBOLIC expression "text-string" [,"text-string"]... Command Qualifiers Defaults /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLA...

DISPLAY SYMBOLIC /BOLD[=Boolean-expression]/NOBOLD (D) Specifies that the item is displayed in high intensity if Boolean-expression evaluates to True (non-zero). /REVERSE[=Boolean-expression]/NOREVERSE (D) Specifies that the item is displayed with the foreground and background visualattributes swapp...

DISPLAY TEXT DISPLAY TEXT Display text in a monitor picture. Format DISPLAY TEXT text Command Qualifiers Defaults /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLANK /BLINK=Boolean-expression /NOBLINK /BOLD=Boolean-expression /NOBOLD /FACILITY /NOFACILITY /LINK /NOLINK /NODE /NODE /P...

DISPLAY TEXT /BOLD[=Boolean-expression] /NOBOLD (D) Specifies that the item is displayed in high intensity if Boolean-expression evaluates to True (non-zero). /FACILITY/NOFACILITY (D) Specifies that the symbol substitution in the text is carried out as if a facilitydata item were being displayed. Th...

DISPLAY TEXT /UNDERLINE[=Boolean-expression]/NOUNDERLINE (D) Specifies that the displayed value is underlined if Boolean-expression evaluates to True (non-zero). /X[=column]/X=previous-column (D) Specifies the screen column where the item is displayed (the leftmost column is1). By default, items are...

DO DO Execute an operating system command. Format DO [operating-system-command] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The DO command enables an operating system command to be executed from RTR. By using ...

DO Related Commands • SPAWN Example RTR> DO/CLUSTER SHOW TIME This command shows the time on all nodes in a OpenVMS cluster. RTR> DO/NODE=(TR2,TR1) SHOW LOGICAL MYLOGICAL This command examines the logical name "MYLOGICAL" on nodes TR2 and TR1. RTR> SET ENVIRONMENT/NODE=(TR2,TR1)RTR&...

FLUSH NAME_CACHE FLUSH NAME_CACHE Flushes RTR’s internal network name cache. Format FLUSH NAME_CACHE Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list Description The FLUSH NAME_CACHE removes information for all known nodes from RTR’s internal network name cac...

EXECUTE EXECUTE Executes a file containing RTR commands. Format EXECUTE file-spec Command Qualifiers Defaults /VERIFY /NOVERIFY Description The EXECUTE command reads a file containing RTR commands and executes them. This command also has the form @file-spec . Parameters file-spec Specifies the name ...

EXIT EXIT Exits from the RTR prompt. Format EXIT Description The EXIT command exits from the RTR prompt and returns control to the operating system prompt. The command has no parameters or qualifiers. Sameas QUIT. 6–90 RTR Command Line Interface

EXTEND FACILITY EXTEND FACILITY Adds new nodes or roles or both to an existing facility definition. Format EXTEND FACILITY [facility_name] Command Qualifiers Defaults /BACKEND=backend-list /NOBACKEND /BALANCE /NOBALANCE /CALL_OUT=role-list /NOCALL_OUT /CLUSTER /NOCLUSTER /FRONTEND=frontend-list /NOF...

EXTEND FACILITY $ RTR RTR> SET ENVIRONMENT /NODE=(FE,FETRBE)RTR> CREATE FACILITY facnam /FRONTEND=(FE,FETRBE) - /ROUTER=FETRBE -/BACKEND=FETRBE A new frontend NFE can be added to this facility as follows: $ RTRRTR> SET ENVIRONMENT /NODE=(FETRBE,NFE)RTR> EXTEND FACILITY facnam /FRONTEND=N...

EXTEND FACILITY Backend-list is a list of backend-nodes separated by commas. If there is more than one backend-node , then backend-list must be enclosed in parentheses. Backend-node is either the name of a node or @file-spec , where file-spec specifies a file containing a backend-list on each line. ...

EXTEND FACILITY /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . If /OUTPUT or file-spec is omitted then the standard or default output is used. /ROUTER=router-list/NOROUTER (D) Specifies the names of the added nodes that act as router...

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

LOG LOG Specify RTR to write a log message to a log file. Format LOG Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The LOG command specifies a defined log entry to be written to its log messages. You can write l...

LOG Examples RTR> LOG/OUTPUT=RTRLOG.LOG "Message check here" This command tells RTR to write a log message to the file RTRLOG.LOG. RTR> LOG/CLUSTER="Check for this message to see if logging is working" This command tells RTR to write log messages to all members of a cluster. RT...

MODIFY JOURNAL MODIFY JOURNAL Specifies the desired and maximum allowed sizes of RTR’s recovery journal. Format MODIFY JOURNAL [disk-1] ... [,disk-n] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /BLOCKS=nr-blocks /BLOCKS=1000 /MAXIMUM_BLOCKS=nr-blocks /MAXIMUM_BLOCKS=1000 /NODE=node-list /NODE=de...

MODIFY JOURNAL If neither /NODE nor /CLUSTER is specified then the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered then the command is executed only on the node wherethe command was issued. Note: In environments that do...

MONITOR MONITOR Displays a monitor picture on the screen. Format MONITOR [monitor-file-spec] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /COUNT=nr-updates /COUNT=infinite /FACILITY=facility-name /NOFACILITY /IDENTIFICATION=process-id /NOIDENTIFICATION /INTERVAL=delay-seconds /INTERVAL=2 /LINK=li...

MONITOR Note: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on the local node only. /COUNT=nr-updates/COUNT=infinite (D) Specifies how many times the RTR utility updates the screen before exiting orreturning to the RTR>...

MONITOR qualifier can be used to reset all the averages currently being displayed. It is also useful if monitoring is resumed after issuing one or more RTR commands. /VERIFY/NOVERIFY (D) Specifies that the contents of monitor-file-spec are echoed on stdout . This is useful when developing monitor fi...

QUIT QUIT Quits from the RTR prompt. Format QUIT Description The QUIT command exits from the RTR prompt and returns control to the operating system prompt. The command has no parameters or qualifiers. Sameas EXIT. RTR Command Line Interface 6–103

RECALL RECALL Display a previously entered command for subsequent command editing. Format RECALL [command-specifier] Command Qualifiers Defaults /ALL /NOALL Description When you enter commands to the RTR Utility, they are stored in a recall buffer for later use with the RECALL command. Commands can ...

REGISTER RESOURCE MANAGER (REGISTER RM) REGISTER RESOURCE MANAGER (REGISTER RM) Registers an instance of a resource manager (RM) with RTR. Format REGISTER RESOURCE MANAGER [resource_name] REGISTER RM [resource_name] Command Qualifiers Defaults /open_string /see the Oracle8 Administrator’s Reference ...

REGISTER RESOURCE MANAGER (REGISTER RM) Examples RTR> REGISTER RM rmi_1/open_string="Oracle_XA+Acc=P/user/pw+SesTm=15+db=accounting"/close_string="" /xaswitch_name=xaosw /library_path="library_path" 6–106 RTR Command Line Interface

SCROLL SCROLL Scroll a monitor picture. Format SCROLL direction [amount] Description The SCROLL command causes the the last picture that was displayed using the MONITOR command to be scrolled in the direction specified and then redisplayed. Parameters direction Specifies the direction in which the s...

SET ENVIRONMENT SET ENVIRONMENT Specify the node(s) where subsequent RTR commands are executed. Format SET ENVIRONMENT Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=this_node Description The SET ENVIRONMENT command causes subsequent RTR commands to be executed on the specifie...

SET FACILITY SET FACILITY Sets various facility related options. Format SET FACILITY facility-name Command Qualifiers Defaults /BROADCAST_MINIMUM_RATE=Bps /BROADCAST_MINIMUM_RATE=1000/QUORUM_THRESHOLD=n /QUORUM_THRESHOLD=0 /BALANCE /NOBALANCE /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-li...

SET FACILITY Note A node that combines both backend and router roles is counted twicein determining the threshold. A value of zero implies that the RTRdetermined threshold (half the number of node/role pairs configured plusone) is used. This is the default value; do not alter it unless you are suret...

SET FACILITY Related Commands • SHOW FACILITY Examples RTR> SET FACILITY FINANCE/QUORUM_THRESHOLD=4 quorum threshold set to 4 (from 0) for facility FINANCE The SET FACILITY command tells RTR to set the quorum threshold to four forfacility FINANCE. This command should be used on all the backend an...

SET LINK SET LINK Sets various link related options. Format SET LINK link-name Command Qualifiers Defaults /AUTOISOLATE /NOAUTOISOLATE /ENABLE /DISABLE /CHECKSUM /NOCHECKSUM /CLUSTER /NOCLUSTER /INACTIVITY_TIMEOUT[=secs] /INACTIVITY_TIMEOUT=node-default /NODE=node-list /NODE=default-node-list /OUTPU...

SET LINK Remote node autoisolation may be enabled (at the isolator) where it applies to alllinks using SET NODE/AUTOISOLATE, or for specific links only with the SETLINK/AUTOISOLATE command. An isolated node (isolatee) remains isolateduntil you carry out both of the following actions: • Enable the li...

SET LINK The new value for secs becomes effective only after a time of about one third of the current value of the link inactivity timeout. The minimum useful value for secs is three. If a value is not specified, links inherit the current value of the node inactivity timeout. (See SET NODE/INACTIVIT...

SET LINK Examples RTR> SET LINK JOEY/ENABLE This command re-allows connections from node JOEY. RTR> SET LINK JOEY/AUTOISOLATE This command sets the autoisolate attribute on the link to node JOEY. RTR Command Line Interface 6–115

SET LOG SET LOG Specify where RTR writes its log messages. Format SET LOG Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FILE=file-spec-list /NOFILE /NODE=node-list /NODE=default-node-list /OPERATOR /NOOPERATOR /OUTPUT[=file-spec] /OUTPUT=stdout Description The SET LOG command specifies where RTR ...

SET LOG /OPERATOR/NOOPERATOR (D) Specifies that messages are written to the operator log. /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . If /OUTPUT or file-spec is omitted then the standard or default output is used. Related Commands...

SET MODE SET MODE Specify whether RTR should run in a group mode or the nogroup (system) mode. Format SET MODE Command Qualifiers Defaults /CLUSTER /NOCLUSTER /GROUP[=user-id] /NOGROUP /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SET MODE command specifi...

SET MODE /NODE[=node-list]/NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in node-list . If node-list is omitted then the command is executed only on the node where the command was issued. /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting in...

SET NODE SET NODE Sets various node related options. Format SET node Command Qualifiers Defaults /AUTOISOLATE /NOAUTOISOLATE /CLUSTER /NOCLUSTER /INACTIVITY_TIMEOUT[=secs] /INACTIVITY_TIMEOUT=60 /ISOLATE /NOISOLATE /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Descriptio...

SET NODE /CLUSTER/NOCLUSTER (D) Specifies that the command is executed on all the nodes in the cluster. If neither /NODE nor /CLUSTER is specified then the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered then the comman...

SET PARTITION SET PARTITION Sets various partition related options. Format SET PARTITION partition-name Command Qualifiers Defaults /FACILITY=[facility_name]/FAILOVER_POLICY=[SHADOW | STAND_BY] / /IGNORE_RECOVERY /NOIGNORE_RECOVERY /PRIORITY_LIST=backend-node-list / /RECOVERY_RETRY_COUNT=n / /RESTAR...

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 state or fail because of the unavailability ofeither a local or remote journal, this command can be used to override the defaultRTR behaviour. It ...

SET PARTITION Once shadowing is disabled, the secondary site servers will be unable to startupin shadow mode until shadowing is enabled again. Shadowing for the partition can be turned on by entering the command at thecurrent active member or any of its standbys. If shadowing is already in the desir...

SET TRANSACTION SET TRANSACTION Sets various transaction related options. Format SET TRANSACTION transaction-id Command Qualifiers Defaults /BEFORE[=date] today /STATE=current_state/FACILITY=facility_name /RTR$DEFAULT_FACILITY (D) /NEW_STATE=new_state/NODE[=node_list /default_node_list /OUTPUT[=file...

SET TRANSACTION Usage Notes The command can only be executed on a backend node in which the journal islocated and the RTR log file must be turned on to record the transaction changes.RTR needs to be started before using this command. When a transaction’s state is changed, the new state is written to...

SET TRANSACTION /NEW_STATE Specifies the new transaction state that selected transactions will be changed to.This qualifier is required and new state value must be specified. Value of new_state may be one of the following: ABORTCOMMITDONEEXCEPTION Note that one cannot always change a transaction’s s...

SET TRANSACTION Examples RTR> SET TRANSACTION "50d01f10,0,0,0,0,2166,522b2001" -_RTR> /NEW=ABORT /CURRENT=SENDING /PART=DB_PART Abort this specified transaction running in the DB_PART partition. RTR> SET TRANSACTION /NEW=ABORT /CURRENT=VOTED /PART=DB_PART For all transactions that a...

SHOW CHANNEL SHOW CHANNEL Show the names and state of channels that have been opened using the CLI API. Format SHOW CHANNEL [channel-name] Command Qualifiers Defaults /ALL_WINDOWS /NOALL_WINDOWS /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Descriptio...

SHOW CHANNEL Related Commands • call rtr_open_channel( ) • call rtr_close_channel( ) Examples RTR> SHOW CHANNEL/ALL_WINDOWS 1 Channel type Channel name (Owner pid) server RTR$DEFAULT_CHANNEL (28879) 2 client CLI_CHN (28879) 3 client CLI_CHN2 (26225) 4 1 Display information about all declared chan...

SHOW CLIENT SHOW CLIENT Display information about client channels. Format SHOW CLIENT Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FACILITY /FACILITY="*" /FULL none /IDENTIFICATION=process-id /NOIDENTIFICATION /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout D...

SHOW CLIENT /NODE[=node-list] /NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in node-list . If node-list is omitted then the command is executed only on the node where the command was issued. /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resultin...

SHOW DISPLAY SHOW DISPLAY Show which items were displayed by the most recently issued MONITOR command or DISPLAY commands. Format SHOW DISPLAY Command Qualifiers Defaults /ALL /NOALL /OUTPUT[=file-spec] /OUTPUT=stdout /X=column/Y=row Description The SHOW DISPLAY command shows which items were displa...

SHOW DISPLAY Examples RTR> MON CALLS 1 RTR> SHOW DISPLAY/ALL 2 DISPLAY TEXT "RTR api calls, Node: $node_name ,- 3 PID: $process_id, Process name: -ALL-" - /X=1 /Y=1 - /BOLD="1" ... DISPLAY NUMERIC "rtr_open_channel_succ" - /X=1 /Y=5 - /BLANK -/LABEL=" rtr_open_chann...

SHOW ENVIRONMENT SHOW ENVIRONMENT Shows the default nodes used for remote command execution. Format SHOW ENVIRONMENT Description The SHOW ENVIRONMENT command shows which nodes are used by default for remote command execution. Related Commands • SET ENVIRONMENT Examples RTR> SET ENVIRONMENT/NODE=(...

SHOW FACILITY SHOW FACILITY Show the names, configuration and status of one or more facilities. Format SHOW FACILITY [facility-name] Command Qualifiers Defaults /BALANCE /NOBALANCE /CLUSTER /NOCLUSTER /CONFIGURATION /NOCONFIGURATION /COUNTER[=counter-name] /NOCOUNTER /FULL /NOFULL /LINKS /NOLINKS /S...

SHOW FACILITY /CONFIGURATION/NOCONFIGURATION (D) Specifies that the facility configuration is to be displayed. The configurationinformation indicates the role(s) of the the node where the command is executed,and Whether router call-out servers or backend call-out servers have beenconfigured,Whether ...

SHOW FACILITY On a frontend, this qualifier can be used to find out whether the node is currentlyconnected to a router. Related Commands • CREATE FACILITY • DELETE FACILITY • SHOW LINK Examples RTR> SHOW FACILITY/FULL/NODE=BRONZE 1 Facility: FUNDS_TRANSFER 2 Configuration:- 3 Frontend: no Router:...

SHOW FACILITY 5 The facility’s links. The first link shown (to node ‘‘bronze’’ i.e. itself) showsthat it is a router, connected to the backend, and the router is quorate. Therouter is not current because there is no frontend on this connection. The linkis also a backend, connected to the router, and...

SHOW JOURNAL SHOW JOURNAL Display information about current RTR journal files. Format SHOW JOURNAL Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FILENAMES /NOFILENAMES /FULL /NOFULL /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SHOW JOURNAL command s...

SHOW JOURNAL Related Commands • CREATE JOURNAL • DELETE JOURNAL • INITIALIZE JOURNAL Examples RTR> SHOW JOURNAL/FULL/FILENAMES 1 RTR journal:- 2 3 4 5 6 Disk(1): /dev/rz3a Blocks: 1500 Allocated: 1502 Maximum: 3000 File(1): /dev/rz3a /rtrjnl/SYSTEM/BRONZE.J01 7 Disk(2): /dev/rz2c Blocks: 1500 All...

SHOW KEY SHOW KEY Display the key definitions created by the DEFINE /KEY command. Format SHOW KEY [key-name] Command Qualifiers Defaults /ALL /NOALL /FULL /NOFULL /OUTPUT[=file-spec] /OUTPUT=stdout /IF_STATE /NOIF_STATE Description The SHOW KEY command shows the key definitions created by the DEFINE...

SHOW KEY Related Commands • DEFINE /KEY Examples RTR> SHOW KEY/FULLDEFAULT PF1 defined as ""DEFAULT KP0 defined as "MONITOR/RESUME"DEFAULT KP2 defined as "SCROLL DOWN 1"DEFAULT KP4 defined as "SCROLL LEFT 1"DEFAULT KP5 defined as "SCROLL HOME"DEFAULT KP6 de...

SHOW LINK SHOW LINK Display the configuration and status of the links to other nodes. Format SHOW LINK [node-name] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /COUNTER[=counter-name] /NOCOUNTER /FACILITY /NOFACILITY /FULL /NOFULL /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUT...

SHOW LINK /FULL Equivalent to specifying /FACILITY/STATE . /NODE[=node-list]/NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in node-list . If node-list is omitted then the command is executed only on the node where the command was issued. /OUTPUT[=file-spec]...

SHOW LOG SHOW LOG Display the names of the current log files. Format SHOW LOG Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SHOW LOG command shows the names of the current RTR log files as defined with the...

SHOW LOG Example RTR> SHOW LOG 1 Messages not being sent to operator console 2 Log file[1]: /usr/users/someone/rtr_logfile.log 3 1 Show where RTR log messages are currently written. 2 Currently not being sent to the operator log. 3 Currently being written to file rtr_logfile.log . RTR Command Lin...

SHOW MODE SHOW MODE Displays the current RTR mode. Format SHOW MODE Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SHOW MODE command shows the currently running user group for RTR. For nogroup (system) mode...

SHOW MODE Examples RTR> SHOW MODE Group name is "develop" RTR Command Line Interface 6–149

SHOW NODE SHOW NODE Shows the node network status, the autoisolation state and the node inactivity timer. Format SHOW NODE Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SHOW NODE shows the network status, ...

SHOW NODE Examples RTR> SHOW NODE 1 Node properties: Network state: enabled 2 Auto isolation: disabled 3 Inactivity timer/s: 60 4 1 SHOW NODE command. 2 Network status 3 Auto isolation state (enabled or disabled). 4 Inactivity timer value in seconds. RTR Command Line Interface 6–151

SHOW PARTITION SHOW PARTITION Display server data partition information. Format SHOW PARTITION Command Qualifiers Defaults /BACKEND /BACKEND /BRIEF /NOBRIEF /CLUSTER /NOCLUSTER /FACILITY /FACILITY="*" /FULL /NOFULL /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout ...

SHOW PARTITION Table 6–21 Router Partition States State Meaning BLOCKED Key range is recovering or awaiting journal access ACTIVE Primary server is ready to accept transactions CATCHUP Secondary server is catching up with primary TAKEOVR Standby take-over is in progress LAGGING Secondary is ready, p...

SHOW PARTITION • The state of transaction presentation - one of active, suspended or suspending • The current failover policy - one of fail_to_standby, fail_to_shadow or pre_v32_compatibilty The SHOW PARTITION comand displays callout server data as backend serverdata because a callout server uses se...

SHOW PARTITION Partition name: RTR$DEFAULT_PARTITION_16777217 Facility: RTR$DEFAULT_FACILITY State: active Low Bound: "aaaa" High Bound: "mmmm" Active Servers: 0 Free Servers: 1 Transaction presentation: active Last Rcvy BE: Txns Active: 0 Txns Rcvrd: 0 Failover policy: fail_to_stand...

SHOW PROCESS SHOW PROCESS Display information about processes which are using RTR. Format SHOW PROCESS Command Qualifiers Defaults /CLUSTER /NOCLUSTER /COUNTER[=counter-name] /NOCOUNTER /FULL /NOFULL /IDENTIFICATION=process-id /NOIDENTIFICATION /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file...

SHOW PROCESS /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . If /OUTPUT or file-spec is omitted then the standard or default output is used. Examples RTR> SHOW PROCESSProcesses: Process-id Process Name 326 RTR Command Line Interfac...

SHOW REQUESTER SHOW REQUESTER See SHOW CLIENT. The SHOW REQUESTER command has been replaced bySHOW CLIENT and is retained for compatibility reasons only. 6–158 RTR Command Line Interface

SHOW RESOURCE MANAGER (SHOW RM) SHOW RESOURCE MANAGER (SHOW RM) Displays resource manager instance (RM) information. This command is available only on UNIX and Windows NT systems. Format SHOW RESOURCE MANAGER [resource_name] SHOW RM [resource_name] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FU...

SHOW RESOURCE MANAGER (SHOW RM) /FULL/NOFULL (D) Displays additional information for facilities that reference a particular RM. If normi_name is included, displays information for all RMs. /NODE[=node-list]/NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in n...

SHOW RTR SHOW RTR Display the configuration and status of RTR. Format SHOW RTR Command Qualifiers Defaults /CLUSTER /NOCLUSTER /COUNTER[=counter-name] /NOCOUNTER /FULL /NOFULL /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout /STATUS /NOSTATUS /VERSION /NOVERSION Descripti...

SHOW RTR /STATUS (D) /NOSTATUS Displays the current status of RTR (started, stopped and so on). /VERSION/NOVERSION (D) Displays the RTR version. Related Commands • STOP RTR • START RTR Example RTR> SHOW RTR 1 RTR running on node baby.home.dec.com in group: develpr 2 1 Show the state and configura...

SHOW SEGMENT SHOW SEGMENT Display the type and size of routing key segments. Format SHOW SEGMENT Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FACILITY /FACILITY="*" /FULL /NOFULL /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The SHOW SEGMENT com...

SHOW SEGMENT Examples RTR> SHOW SEGMENT 1 Facility Data Type Length Offset RTR$DEFAULT_FACILITY UNSIGNED 1 0 2 TEST_FAC SIGNED 4 10 1 Show the routing key segments for all facilities. 2 The facility name, the routing key data type, key length and offset are shownfor each facility. 6–164 RTR Comma...

SHOW SERVER SHOW SERVER Display information about server channels. Format SHOW SERVER Command Qualifiers Defaults /CLUSTER /NOCLUSTER /FACILITY /FACILITY="*" /FULL /NOFULL /IDENTIFICATION=process-id /NOIDENTIFICATION /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdou...

SHOW SERVER Table 6–23 Server Flags FLAG Meaning BEC Backend Call-out EXA Explicit Accept EXP Explicit Prepare NCC No Concurrent NSB No Standby SHD Shadow SRV Server TRC Router Call-out Qualifiers /CLUSTER /NOCLUSTER (D) Specifies that the command is executed on all the nodes in the cluster. If neit...

SHOW SERVER Examples RTR> SHOW SERVER Servers: Process-id Facility Channel Flags State 20828 RTR$DEFAULT_FACILITY 589825 SRV active 20828 RTR$DEFAULT_FACILITY 655362 SRV active RTR> SHOW SERVER/FULLServers: Process-id: 20828 Facility: RTR$DEFAULT_FACILITY Channel: 589825 Flags: SRV State: acti...

SHOW TRANSACTION SHOW TRANSACTION Displays information about currently active transactions. Format SHOW TRANSACTION Command Qualifiers Defaults /BACKEND /NOBACKEND (D) /CLUSTER /NOCLUSTER /FACILITY /FACILITY="*" /FRONTEND /NOFRONTEND (D) /FULL /NOFULL /IDENTIFICATION=process-id /NOIDENTIFICA...

SHOW TRANSACTION Note: In environments that do not support clustering, use of the /CLUSTERqualifier will cause the relevant command to be executed on the local node only. /FRONTEND/NOFRONTEND (D) Specifies that information should be listed for transactions in a frontend node. Ifnone of /BACKEND, /FR...

SHOW TRANSACTION Table 6–25 (Cont.) Key-Range States State Meaning active Active non-shadowed sec_act Secondary active pri_act Primary active pri_lone Primary running alone sec_chup Secondary is catching up Examples RTR> SHOW TRANSACTION/BACKEND/FULL Backend transactions: Tid: e100b810,0,0,0,0,a8...

SPAWN SPAWN Allows you to execute operating system commands without leaving the RTRutility. Format SPAWN [operating-system-command] Command Qualifiers Defaults /INPUT=file-spec /NOINPUT /OUTPUT=file-spec /OUTPUT=stdout /WAIT /WAIT Description The SPAWN command allows you to execute operating system ...

START RTR START RTR Start RTR on one or more nodes. Format START RTR Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout The following qualifiers are only relevant when running on OpenVMS. Command Qualifiers Defaults /ASTLM=ast...

START RTR Qualifiers /ASTLM=ast-limit /ASTLM=(max-links + max-processes) 2 2 + 10 = default ast-limit (D) Specifies the AST limit for the RTR ACP. The value for ast-limit must include five for RTR ACP mailbox reads and timer scheduling and a minimum of two per DECNET logical link maintained by RTR. ...

START RTR /DIOLM=io-direct /DIOLM=(max-links + max-processes) 2 2 + 10 = default io-direct (D) Specifies the maximum number of direct I/O operations that the RTR ACP canhave outstanding at any one time. If you do not specify a direct I/O quota, the default value established at systemgeneration time ...

START RTR The default value of page-file is automatically calculated, based on the values of /LINKS and /PROCESSES. /PRCLM=subprocess-limit/PRCLM=10 (D) Specifies the maximum number of subprocesses that the RTR ACP can create. The default for subprocess-limit is 10. /PRIORITY=priority/PRIORITY=6 (D)...

START RTR Related Commands • SHOW RTR • STOP RTR Examples See Chapter 2, Starting and Setting Up RTR, for examples of how to use the START RTR command. 6–176 RTR Command Line Interface

STOP RTR STOP RTR Stop RTR on one or more nodes. Format STOP RTR Command Qualifiers Defaults /ABORT /NOABORT /CLUSTER /NOCLUSTER /NODE[=node-list] /NODE=default-node-list /OUTPUT[=file-spec] /OUTPUT=stdout Description The STOP RTR command stops RTR in an orderly manner. Alternatively, RTR can be sto...

STOP RTR /OUTPUT[=file-spec]/OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec . If /OUTPUT or file-spec is omitted then the standard or default output is used. Related Commands • SHOW RTR • START RTR Examples See Chapter 2, Starting and Setting Up RTR, for ...

TRIM FACILITY TRIM FACILITY Removes nodes or roles or both from an existing facility definition. Format TRIM FACILITY [facility_name] Command Qualifiers Defaults /BACKEND=backend-list /NOBACKEND /CLUSTER /NOCLUSTER /FRONTEND=frontend-list /NOFRONTEND /NODE[=node-list] /NODE=default-node-list /OUTPUT...

TRIM FACILITY RTR MONITOR QUORUM displays a monitor picture which allows the quorum negotiations to be observed. You can use this after using a TRIM FACILITYcommand; once quorum has been re-attained, the participating nodes return tothe quorate state. For example, in a three node facility called fac...

TRIM FACILITY /NOFRONTEND (D) Specifies the names of nodes where the frontend role is removed for this facility. frontend-list is a list of frontend-nodes separated by commas. If there is more than one frontend-node , then frontend-list must be enclosed in parentheses. frontend-node is either the na...

UNREGISTER RESOURCE MANAGER (UNREGISTER RM) UNREGISTER RESOURCE MANAGER (UNREGISTER RM) The UNREGISTER RESOURCE MANAGER command unregisters an instance of a resource manager. Format UNREGISTER RESOURCE MANAGER [resource_name] UNREGISTER RM [resource_name] Command Qualifiers Defaults /CLUSTER /NOCLUS...

A Creating Monitor Pictures The standard monitor pictures provided with RTR (described in Chapter 5) aresufficient for most needs. You may also create your own monitor pictures to suitparticular needs. This appendix tells you how to do this. The RTR monitor utility provides a means to continuously d...

Creating Monitor Pictures The commands used to define and display monitor pictures are: CLEARDISPLAY BARDISPLAY NUMERICDISPLAY STRINGDISPLAY SYMBOLICDISPLAY TEXTMONITORSCROLLSHOW DISPLAY These commands are described in the following sections. A.1 Interactive Definition of a Monitor Picture Example A...

Creating Monitor Pictures A.1 Interactive Definition of a Monitor Picture Figure A–1 Interactively Defined Monitor Picture THE TEST PICTURE AT 11:49:24 SOME DATA ITEM: 0 OTHER DATA ITEM: 0 Caution Because monitor file definitions depend on the internal structure and dataitems of RTR, they may need t...

Creating Monitor PicturesA.3 Arithmetic Expressions and Operators Table A–3 Arithmetic Operators in Display Commands Characters Meaning - Minus + Plus * Multiply / Divide & Logical AND | Logical OR <= Less than or equal >= Greater than or equal != Not equal <> Not equal < Less tha...

Creating Monitor Pictures A.3 Arithmetic Expressions and Operators Aggregation of Data Items DISPLAY commands which select multiple instances of a data item (for example,multiple instances of a process counter) can use the following keywords to controlthe way the items are aggregated. _MIN—select th...

B Server Shadowing and Recovery RTR shadowing gives you the ability to recover from a site disaster without theneed for special coding within your application program. This appendix is anintroduction to RTR shadowing. A server for a database partition is said to be shadowed when two copies of thesam...

Server Shadowing and RecoveryB.2 Automatic Features • RTR_EVTNUM_SRSHADOWGAIN - Server has gained its shadow partner • RTR_EVTNUM_SRRECOVERCMPL - Server has completed recovery The shadow events are delivered with no special status and no data. They aredelivered only to the server(s) whose state has ...

Server Shadowing and Recovery B.3 The RTR Journal System The number of blocks specified by the /BLOCKS qualifier specifies the size of thejournal that RTR attempts to keep to. (The actual number of blocks used mayvary, depending upon the load on RTR.) The command MODIFY JOURNAL also accepts the /BLO...

Server Shadowing and RecoveryB.4 Shadow Site Failure and Journaling B.4.1 Maximum Journal Size The current maxima for the size of a journal are: Number of blocks per disk: 524288 (This is max_segments_per_disk * disk_blocks_per_segment , or 16384 times 32.)Number of disks per journal: 16. B.5 Standb...

Server Shadowing and Recovery B.6 Performance Note that RTR does not have to wait for the secondary shadow server to completeits processing. It only needs to know that the primary has committed thetransaction and that the journal file of the secondary shadow server contains thefinal vote status. The...

Server Shadowing and RecoveryB.8 Application Considerations • Any physical reference to the transaction which is unique to the executingserver, e.g. Channel Id, system time, DB-key, etc., should not be passed backto the client for future references within its subsequent messages, as thiscould lead t...

Server Shadowing and Recovery B.9 Server States Figure B–2 Server States WAIT−TR−OK WAIT−TR−RETRY Retry Router detects definition clash Propose KRto Routers Error Proposal accepted− commit KR ACTIVE REMEMBER CATCHUP WAITCATCHUP SECONDARY WAIT−JNL WAIT RESTART RESTART Router sendslist of recoveryJour...

Server Shadowing and RecoveryB.10 Client States B.10 Client States The current state of a client process can be examined as follows: RTR> show client/fullClients: Process-id: 13340 Facility: RTR$DEFAULT_FACILITY Channel: 458755 Flags: CLI State: declared rcpnam: "CHAN3" User Events: 255 R...

Server Shadowing and Recovery B.11 Partition States B.11 Partition States The current state of a key-range partition can be examined using the SHOW PARTITION/FULL command for the routers and the backends: RTR> show partition/router/full Facility: RTR$DEFAULT_FACILITY State: ACTIVE Low Bound: 0 Hi...

C XA Support This appendix explains how RTR may be used with a X/OPEN DistributedTransaction Processing (DTP) conformant Resource Manager. C.1 Introduction The X/OPEN Distributed Transaction Processing (DTP) architecture definesa standard interface that lets application programs share resources prov...

XA SupportC.1 Introduction facility_name = user-specified facility name /resource_manager = the name ofthose RMs this facility references For example: CREATE FACILITY test /front=N1 /back=N2/router=N3 /resource_manager=(employ_rm,payroll_rm) C.1.3 Modified RTR API An application written to use RTR w...

D RTR Utility Error Messages This appendix describes the various error messages that can be returned by theRTR utility. %RTR-F-ABKEYW, Ambiguous qualifier or keyword - supply more characters Explanation: Too few characters were used to truncate a keyword orqualifier name to make the keyword or quali...

RTR Utility Error Messages %RTR-F-BADDSKWRI, Unable to create/extend a journal file Explanation: An attempt to create or extend a journal file on disk failed.Check that the disk(s) you are using for journals have sufficient free space. %RTR-E-BADOP, Unable to complete operation @[A] line [A] Explana...

RTR Utility Error Messages %RTR-E-CLOSEPEND, Send failed due to close pending on channel - call rtr_ receive_message Explanation: Sending of data to the ACP has been aborted due tothe presence of an undelivered mt_closed message on the channel. Theapplication may retrieve the reason for the channel ...

RTR Utility Error Messages %RTR-S-DISITMCLR, [A] display item(s) cleared Explanation: Indicates how many display items [A] were successfullycleared after issuing a CLEAR DISPLAY command. %RTR-W-DISKALL, Disk is not available to RTR Explanation: An attempt was made to create a journal on a disk which...

RTR Utility Error Messages %RTR-F-DUPJOUFIL, Duplicate RTR journal file found - remove duplicate file or CREATE JOURNAL /SUPERSEDE Explanation: A duplicate RTR journal file has been found. This status maybe returned by the CREATE FACILITY and SHOW JOURNAL commands. Probable cause: System management ...

RTR Utility Error Messages %RTR-F-ERRACCDIR, Directory [A], cannot be accessed or opened Explanation: A directory cannot be accessed or opened. %RTR-E-ERRACCFIL, Error accessing file [A] Explanation: Displays the name [A] of a file that the RTR utility wasunable to access. %RTR-E-ERRACCMBX, Error ac...

RTR Utility Error Messages %RTR-E-ERRSTAACP, Unable to start ACP Explanation: The RTR ACP process could not be started when a "STARTRTR" command was issued. The subsequent message gives more details. %RTR-E-ERRSTARCH, Unable to start remote client handler Explanation: The RTR remote client h...

RTR Utility Error Messages %RTR-E-FACNAMLON, Facility name [A] is longer than 30 characters Explanation: Facility name [A] is too long. %RTR-E-FACNAMSTA, Facility name [A] does not start with a letter Explanation: Facility name [A] does not start with a capital letter ("A" to"Z"). %R...

RTR Utility Error Messages %RTR-E-ILLPARTCHAR, Legal characters are alphanumeric and under-score Explanation: Illegal chars in partition name argument. %RTR-E-ILLREMDEV, Device [A] contains a node specification Explanation: RTR cannot create its journal files on remote systems.Re-issue the "CREA...

RTR Utility Error Messages %RTR-F-INVKSTYPE, Invalid ks_type argument Explanation: Invalid ks_type argument. %RTR-F-INVMSGFMT, Invalid format argument Explanation: Invalid format argument. Possible reasons include the use of an invalid character or expression in theformat string, or a mismatch in th...

RTR Utility Error Messages %RTR-E-ITMALREXI, There is already something displayed at x = [A], y = [A] Explanation: Indicates that invalid coordinates were specified on a"DISPLAY" command within a display file. There already is an item at point[A], [B]. %RTR-F-IVKEYW, Unrecognized keyword - c...

RTR Utility Error Messages %RTR-F-JOUFORCHA, Journal format has been changed - CREATE JOURNAL /SUPERSEDE Explanation: The journal file(s) found have an out-of-date format. Thisstatus may be returned by the CREATE FACILITY and SHOW JOURNALcommands after a new version of RTR has been installed on a sy...

RTR Utility Error Messages %RTR-S-JOURNALINI, Journal has been created on device [A] Explanation: Confirms that the RTR journal has been successfully createdon device [A] after issuing the "CREATE JOURNAL" command. %RTR-S-JOURNALMOD, Journal has been modified on device [A] Explanation: Confi...

RTR Utility Error Messages %RTR-E-LOCKFAIL, Cannot obtain lock for resource [A] Explanation: Failed to obtain lock. Enable logging for more informationabout error. %RTR-S-LOGFILSET, Logging to [A] Explanation: Displays which log files will be used after issuing a "SETLOG" command with the &#...

RTR Utility Error Messages %RTR-E-NDBTABFUL, The NDB table is full Explanation: This message is displayed when an "CREATE FACILITY"command is issued. It indicates that the total number of different nodesspecified with this and all previous "CREATE FACILITY" commands wouldexceed the l...

RTR Utility Error Messages %RTR-E-NODNA, DECnet specified for [A], but transport protocol unavailable or disabled Explanation: DECnet was specified as required through use of a nodename prefix ("dna." or a substitute), but no corresponding entry in the nodedatabase can be found. Add an entry...

RTR Utility Error Messages %RTR-E-NOKEYSEGS, You must specify at least one keysegment - use /KEY1 - /KEY9 Explanation: Except for a callout partition, it is necessary to define the keyrange, so the absence of any key segment descriptors is an error. %RTR-F-NOKEYW, Qualifier name is missing - append ...

RTR Utility Error Messages %RTR-E-NOSUCHITM, Nothing displayed at x = [A], y = [A] Explanation: Indicates that invalid coordinates were specified on a "CLEARDISPLAY" or "SHOW DISPLAY" command. No item is displayed at point [A],[B]. %RTR-E-NOSUCHNOD, No such node, [A] Explanation: The...

RTR Utility Error Messages %RTR-E-NUMCONILL, Numeric constant has illegal syntax, [A] Explanation: The numeric constant [A] is invalid. %RTR-W-OBSQUAL, Qualifier [A] is obsolete - value ignored Explanation: An obsolete qualifier has been specified on a command line.The qualifier no longer has any ef...

RTR Utility Error Messages %RTR-E-PRTBADCMD, Partition command invalid or not implemented in this version of RTR Explanation: Status return indicating that the ACP received a request foran unknown partition command. %RTR-E-PRTBADFPOL, Unrecognised partition failover policy code Explanation: Status i...

RTR Utility Error Messages %RTR-S-PRTNCREATED, Partition created Explanation: The requested partition was successfully created. %RTR-S-PRTNDELETED, Partition deleted Explanation: The requested partition was successfully deleted. %RTR-S-PRTNEWFPOLS, Failover policy set Explanation: Status indicating ...

RTR Utility Error Messages %RTR-E-PRTRUNDOWN, Partition is in rundown prior to deletion - no action taken Explanation: Cannot perform the requested action since the partition isbeing deleted. %RTR-I-PRTSHDOFF, Partition [A]:[A] shadow state set to off by operator [A] Explanation: Written to log file...

RTR Utility Error Messages %RTR-E-RTRALRSTA, RTR already started Explanation: RTR was already running when the "START RTR" commandwas executed. %RTR-S-RTRLOGENT, [A] Explanation: The RTR LOG command was used to make an entry in theRTR LOG %RTR-I-RTRNOTRUN, RTR not running Explanation: Messag...

RTR Utility Error Messages %RTR-F-SPUJOUFIL, Spurious RTR journal file found - remove extra file, or CREATE JOURNAL /SUPERSEDE and submit SPR Explanation: A spurious RTR journal file has been found which does notcorrespond to the other journal files on the system. This status may bereturned by the C...

RTR Utility Error Messages %RTR-E-TOOMANCHN, Too many channels Explanation: Displayed when a "SYS$DCL_TX_PRC" command is issuedand the channel table is full. %RTR-F-TOOMANDIS, Too many disks specified in journal definition Explanation: Explanation: Too many disks were specified in journaldef...

RTR Utility Error Messages %RTR-E-UNEXPEND, Expression ended before [A] encountered Explanation: The expression is invalid because it terminated where whentoken [A] was expected. %RTR-E-UNKNOWQUAL, Invalid qualifier keyword value - check your program Explanation: Status return indicating that an unr...

E RTR log messages This appendix describes the various error messages that can be sent to theoperator console or written to RTR’s operator log file. %RTR-E-ABODEAREQ, Transaction aborted that was started by client that has since exited Explanation: Indicates that a transaction has been aborted that ...

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 of an internal node identifier. The presence of this messageindicates a serious problem in the configuration of the network name/addressdatabases, ...

RTR log messages %RTR-F-BRODISLIN, Broadcast message(s) discarded because of link unavailability Explanation: One or more broadcast messages had to be discarded becausethere is no logical link to the destination node. %RTR-I-CLUENABLED, RTR cluster [A] is enabled using [A] Explanation: Information m...

RTR log messages %RTR-I-CONNALIAS, Link [A] connected as [A] Explanation: Support for internet tunnels allows for the configuration oflinks from which connections appear to originate with an source addressother than that by which the local node is registered locally, for example, theconnection may a...

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 node [B] %RTR-I-FACLOSTTR, Facility [A] lost Router node [A] Explanation: A connection has been lost with router node [B] on facility [A] %RTR-E-FA...

RTR log messages full). RTR has ensured that the TX has been committed, but the operator should nevertheless check the condition on the BE where the TX was abortedto determine why this occurred (possible resource problems on the server, forexample). %RTR-F-INCOMPAT, Incompatible RTR versions Explana...

RTR log messages %RTR-I-JOUSEACOM, Journal search on facility [A] completed. [A] recoverable transactions found Explanation: Journal search has completed. This message appears whenRTR is started The number of transactions needing recovery is indicated by[A]. %RTR-F-JOUSEQERR, RTR journal record sequ...

RTR log messages %RTR-E-NOCURRTR, Current router search failed for facility [A] Explanation: None of the routers specified for facility [A] are currentlyconnectable. The search will continue after a short interval. %RTR-W-NODENOTCNFG, Node is not configured for the facility Explanation: Result of a ...

RTR log messages %RTR-I-PRTCMDFRMBE, Command received for partition [A]:[A] from backend node [A] Explanation: Log file message indicating the origin of a command. %RTR-E-PRTDELCAN, Partition deleted - operation canceled Explanation: Status used to terminate a pending operation when thepartition is ...

RTR log messages %RTR-E-PRTSETFAILTR, Router unable to process command Explanation: A partition set command failed at the router. An entry iswritten to the log file describing the problem. Message arguments are thefacility name and the KR ID. A second message is written detailing thenature of the pr...

RTR log messages %RTR-F-QIROVERFLOW, No more QIRs left Explanation: This status is used to indicate an inadequacy in the staticreservations for the internal query initiation descriptors. Make a note of allQRM counters using SHOW RTR /COUNTER=QRM* Send SPR with thecorresponding RTRACP dump. %RTR-F-RA...

RTR log messages %RTR-W-RSPFAC, Response from Node [A] about Facility [A] Explanation: A negotiation with remote node [A] about facility [B] hasfailed for the reason reported in the following line. This may be a reason forsystem manager intervention. %RTR-W-RSPNODE, Connection to node [A] failed : r...

RTR log messages %RTR-W-TOOMANYNETIDS, Too many net IDs for node ’[A]’ - check for and eliminate any unnecessary adapter/protocol combinations Explanation: On a system configured to run multiple network protocolsover multiple adpaters, RTR can run out of space to store and communicatethe resultant n...

Index A Active Monitor, 5–2 Aggregation of Data Items, A–5 B Backend, 2–1BAR DISPLAY, 6–67 Broadcast Monitor, 5–2 C Call Rtr_accept_tx, 6–3rtr_prepare_tx, 6–22 CALL RTR_BROADCAST_EVENT, 6–6RTR_CLOSE_CHANNEL, 6–10RTR_ERROR_TEXT, 6–12RTR_GET_TID, 6–13RTR_OPEN_CHANNEL, 6–15RTR_RECEIVE_MESSAGE, 6–25RTR_...

DTC Support, C–2 E ENVIRONMENT SET, 1–4, 6–108SHOW, 6–135 Errors, 1–2Event Monitor, 5–2 EXECUTE, 6–89EXIT, 6–90EXTEND FACILITY, 6–91 F Facility, 1–1 Create, 2–1Monitor, 5–2 FACILITY CREATE, 6–47DELETE, 2–4, 6–61EXTEND, 6–91SET, 6–109SHOW, 6–136TRIM, 6–179 @file, 1–3Flow Monitor, 5–2 FLUSH NAME_CACHE...

Monitor (cont’d) Routing, 5–3Rtr, 5–3Stalls, 5–3System, 5–3Tps, 5–3Tpslo, 5–3Traffic, 5–3V2calls, 5–4XA, 5–4 MONITOR, 5–1, 6–100Monitor file, 5–1Monitor picture, 5–1, A–1 N NAME_CACHE FLUSH, 6–88 Netbytes Monitor, 5–3 Netstat Monitor, 5–3 Network transports, 2–13NODE SET, 6–120SHOW, 6–150 NUMERIC DI...

SET (cont’d) MODE, 6–118NODE, 6–120PARTITION, 6–122TRANSACTION, 6–125 SHOW CHANNEL, 6–129CLIENT, 6–131DISPLAY, 6–133, A–2ENVIRONMENT, 6–135FACILITY, 6–136JOURNAL, 6–140KEY, 6–142LINK, 6–144LOG, 6–146MODE, 6–148NODE, 6–150PARTITION, 6–152PROCESS, 6–156REQUESTER, 6–158RESOURCE MANAGER, 6–159RM, 6–159R...