Instruction/ maintenance manual of the product AA-Q88CE-TE Compaq
Go to page of 320
Reliable T ransaction Router System Manager ’ s Manual Order Number: AA-Q88CE-TE June, 1999 This manual describes how to configure, manage and monitor Reliable T ransaction Router , V ersion 3.2 (RTR). Revision/Update Information: This manual supersedes V ersion 3.
June, 1999 COMP AQ COMPUTER CORPORA TION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONT AINED HEREIN, NOR FOR INCIDENT AL OR CONSEQUENTIAL DAMAGES RESUL TING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MA TERIAL.
Contents Preface ............................................................ xi 1 Introduction 1.1 Getting Started ............................................. 1–1 1.2 Entering Commands . ........................................ 1–1 1.3 Online Help .
3.3 Life Cycle of a Partition . . . .................................... 3–2 3.3.1 Implicit Partition Creation .................................. 3–3 3.3.2 Explicit Partition Creation .................................. 3–3 3.3.3 Persistence of Partition Definitions .
5.2.14 Monitor IPCRA TE ........................................ 5–10 5.2.15 Monitor Journal . . ........................................ 5–10 5.2.16 Monitor Link ............................................ 5–1 1 5.2.17 Monitor Netbytes . .....
DISPLA Y BAR . . ............................................ 6–67 DISPLA Y NUMERIC ......................................... 6–72 DISPLA Y STRIN G........................................... 6–77 DISPLA Y SYMBOLIC ...............................
STOP RTR . ................................................ 6–177 TRIM F ACILITY ............................................ 6–179 UNREGISTER RESOURCE MANAGER (UNREGISTER RM) . . ....... 6–182 A Creating Monitor Pictures A.1 Interactive Definition of a Monitor Picture .
Figures 2–1 Configuration Example .................................... 2–2 2–2 Extend Configuration Example . . ............................ 2–6 A–1 Interactively Defined Monitor Picture ......................... A–3 B–1 Four Node Shadow/Standby Configuration .
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 of Reliable T ransaction Router (RTR) using the RTR Command Line Interface (CLI).
Related Documentation • Release Notes • Installation Guide • Application Programmer ’ s Reference Manual • Application Design Guide • Migration Guide Reader ’ s Comments Compaq welcomes your comments on this manual. Please send us your comments by email to rtrdoc@compaq.
T able 1 Conventions Used in this Guide Convention Meaning UPPERCASE lowercase Some operating systems differentiate between lowercase and uppercase characters. For these systems, examples, syntax descriptions, function definitions, and literal strings that appear in text must be typed exactly as shown.
.
1 Introduction For a general introduction to Reliable T ransaction Router , V ersion 3.2 (RTR), you should read the introductory chapter in the Reliable T ransaction Router Application Design Guide .
Introduction 1.2 Entering Commands or , when several commands are to be entered at the RTR prompt: % rtr RTR> start rtr RTR> create journal Note For convenience, the user prompt for the operating system is shown here as the ‘‘%’ ’ symbol.
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 t.
Introduction 1.5 Remote Commands This command starts RTR on the three nodes. Note The /CLUSTER and /NOCLUSTER command qualifiers refer to cluster support.
2 Starting and Setting Up RTR This chapter describes how to configure and start an RTR environment. Recovery journals, router load balancing and call-out servers are also discussed.
Starting and Setting Up RTR 2.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, FE2 and FE3.
Starting and Setting Up RTR 2.2 Setting Up—An Example Example 2–2 illustrates how to use RTR remote commands to start the same configuration. The set environment command is used to send subsequent commands to a number of RTR nodes.
Starting and Setting Up RTR 2.3 Creating a Recovery Journal • The operator should move any duplicate copies of journal files to a location other than the rtrjnl/groupname directory so that RTR will see only the one it created.
Starting and Setting Up RTR 2.4 Changing a Facility Example 2–3 Reconfiguration Using Delete and Create Facility % rtr RTR> stop rtr/node=FE3 1 RTR> delete facility funds_transfer/node=TR2 2 .
Starting and Setting Up RTR 2.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.
Starting and Setting Up RTR 2.4 Changing a Facility Example 2–4 Reconfiguration Using Extend Facility % RTR RTR> start rtr /node=(TR3,FE4) RTR> set environment/node= - 1 _RTR> (FE1,FE2,FE3.
Starting and Setting Up RTR 2.5 Setting up Callout Servers Example 2–5 Configuration of Callout Servers % rtr RTR> set environment/node= - _RTR> (FE1,FE2,FE3,TR1,TR2,BE1,BE2,BE3) RTR> star.
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 V ersion 2 balancing. Use this qualifier only when you are connecting frontend nodes running RTR V ersion 2.
Starting and Setting Up RTR 2.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 w.
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.
Starting and Setting Up RTR 2.8 RTR ACP V irtual Memory Sizing Use of /LINK and /PROCESSES do not take into account memory requirements for transactions. If an application passes a large amount of data from client to server or vice-versa this should be included in the sizing calculations.
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 s.
Starting and Setting Up RTR 2.9 Network T ransports 2.9.2 Using RTR with DHCP and Internet T unnels When using RTR with DHCP or an Internet tunnel, a nodename may not be fully known; special naming techniques are provided for these conditions.
Starting and Setting Up RTR 2.9 Network T ransports This informs the system administrator that port number 46000/tcp is reserved for RTR. (Note that the RTR daemon is started by RTRACP and not by inetd ). 2.9.3 Interoperation with RTR V ersion 2 Using DECnet Reliable T ransaction Router is interoperable with RTR V ersion 2.
Starting and Setting Up RTR 2.10 Network Protocol Selection on OpenVMS 2.10 Network Protocol Selection on OpenVMS • The default network transport protocol on OpenVMS is DECnet. Y ou may change the default to TCP/IP by removing this line from RTR$STARTUP.
Starting and Setting Up RTR 2.1 1 Running RTR as a Service on W indows NT 2.1 1.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 may contain.
Starting and Setting Up RTR 2.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, and how routers are selected.
Starting and Setting Up RTR 2.12 How RTR Selects Processing-states (Roles) for Nodes The SHOW P ARTITION command on each backend node is as follows: Backend partitions on node BRONZE in group "te.
Starting and Setting Up RTR 2.12 How RTR Selects Processing-states (Roles) for Nodes 8. The network connection to node Gold is reestablished. The partition on Gold retained its original sequence number of 2 and retains the primary role while the partition on Bronze reassumes the secondary role.
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 chan.
Starting and Setting Up RTR 2.12 How RTR Selects Processing-states (Roles) for Nodes relevant to a backend. It is where the backend goes to obtain and verify partition configuration and facility information. Routers are made known to the frontend systems through the list specified in the /ROUTER=(list) qualifier to the CREA TE F ACILITY command.
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 with a partitioned data model and RTR data content routing.
Partition Management 3.2 Partition Naming 3.2 Partition Naming A prerequisite for partition management is the ability to identify a partition in the 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 sources described below .
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.
Partition Management 3.5 Entering Partition Commands 3.5 Entering Partition Commands Partitions can be managed by issuing partition commands directed at the required partition after they are created.
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 message of type rtr_mt_closed on the channel whose identifier is returned through the pchannel argument.
Partition Management 3.6 Managing Partitions 3.6.2 Controlling T ransaction Presentation T ransaction presentation is the process of passing transactions to idle server channels for processing. While transaction presentation is active, new transactions are started on the first free server channel for the appropriate partition.
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 process with the /IGNORE_RECOVERY qualifier .
Partition Management 3.6 Managing Partitions 3.6.4.2 Programming Information T o 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_qualifiers[ 0 ].
Partition Management 3.6 Managing Partitions • rtr_partition_fail_to_shadow • rtr_partition_pre32_compatible 3.6.6 Controlling T ransaction Replay RTR has implemented the capability of controlling transaction replay in cases where a "killer message" happens during a transaction replay preventing recovery from continuing normally .
Partition Management 3.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 partition.
4 T ransaction 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 state is the property that characterizes a transaction’ s current condition.
T ransaction Management 4.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.
T ransaction Management 4.1 Overview 4.1.2 T ransaction 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 produces an error message of %RTR-E-INVSTATCHANGE, Invalid to change from current state to the specified state .
T ransaction Management 4.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 the transaction is also committed in the underlying database.
5 RTR Monitoring This chapter contains a description of the RTR monitor . The RTR monitor gives you a means of viewing the activities of RTR and your applications. Many different aspects of RTR’ s behaviour can be viewed, allowing the activities and performance of RTR to be analyzed.
RTR Monitoring 5.2 Standard Monitor Pictures Note Obsolete monitor pictures have been removed from the documentation. T able 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.
RTR Monitoring 5.2 Standard Monitor Pictures T able 5–1 (Cont.) Standard Monitor Pictures Picture name Description jcalls Displays counts of successful (success), failed (fail) and total journal calls for local and remote journals. journal Displays the current journal usage on a node.
RTR Monitoring 5.2 Standard Monitor Pictures T able 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, packet rate, message rate and congestion, in both directions.
RTR Monitoring 5.2 Standard Monitor Pictures your domain name, depending on how the name is entered in either your local hosts file or name server . DECnet-Plus systems may yield both a pseudonym and a link name; both are checked for a match with a template.
RTR Monitoring 5.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 111.
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.
RTR Monitoring 5.2 Standard Monitor Pictures Displays the link protocol for connected links, and the fail reason as a text message for any links on which a connection has failed. Unconnected links where connection have been attempted are highlighted. Link state and architecture of the remote node are also displayed.
RTR Monitoring 5.2 Standard Monitor Pictures 5.2.1 1 Monitor Flow FLOW CONTROL COUNTERS 7-JAN-1999 14:08:06, NODE: -ALL- , FACILITY: -ALL- CREDIT DATA RATE REQUESTS GRANTS ROLE AVAILABLE BYTES/SEC WAI.
RTR Monitoring 5.2 Standard Monitor Pictures 5.2.13 Monitor IPC RTR> Monitor IPC Node: LENGTH I P C S u mmary F r iM a r 5 1999 11:18:34 +----------------------------------------------------------------------------+ This screen displays usage information on IPC messages, byte counts and IO primitives.
RTR Monitoring 5.2 Standard Monitor Pictures Displays information about journal usage, including total number of entries and records written, number of records read, and how many bytes were involved. Bar graphs showing current usage of journal blocks (as a percentage of the total) are also provided.
RTR Monitoring 5.2 Standard Monitor Pictures 5.2.18 Monitor Netstat Connection Status Detail Node: NODEA Mon March 15 1999 09:50:28 Ini Cnf Acc Abo Rej Loss Gain Ctmo Rstr State Type FailCode Node Lin.
RTR Monitoring 5.2 Standard Monitor Pictures T able 5–3 (Cont.) Monitor Partition States State Meaning active Server is active pri_act Server is active as primary shadow sec_act Server is active as secondary shadow remember Primary is running without shadow secondary 5.
RTR Monitoring 5.2 Standard Monitor Pictures Server recovery state meanings are shown in T able 5–4. T able 5–4 Monitor Recovery States State Meaning wt_tr_ok Server is waiting for routers to acce.
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 ------------------- .
RTR Monitoring 5.2 Standard Monitor Pictures 5.2.26 Monitor Rolequorum QUORUM COUNTS BY FACILITY 7-JAN-1999 14:32:48, NODE: -ALL- Router View of Backend View of backends routers backend routers CNF RCH QRT CNF RCH QRT CNF RCH QRT CNF RCH QRT V I P 111 111 111 111 5.
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.
RTR Monitoring 5.2 Standard Monitor Pictures 5.2.31 Monitor Stalls NETWORK STALLS AT 29-JAN-1999 15:35:03, ON NODE: TR1 QIOs Bytes Link Stalls Issued Rate Sent Drops Secs <3s <10s <30s >30s Tot Total 5467 0.0 327148 2 33 23 1 0 0 24 TR1 -> TR1 29 0.
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............
RTR Monitoring 5.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.
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.
.
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 before the corresponding servers have been written by manually entering the server ’ s API calls.
ADD F ACILITY ADD F ACILITY See CREA TE F ACILITY ; ADD F ACILITY is retained for compatibility reasons only . 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 execute the rtr_accept_tx( ) routine and to display the returned status.
CALL RTR_ACCEPT_TX Qualifiers /CHANNEL_NAME=channel_name /CHANNEL_NAME=RTR$DEF AUL T_CHANNEL Specifies the channel for which the operation is to be performed. The command server uses a combination of the channel_name and the window from which the call was issued to uniquely identify which channel to use.
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, norma.
CALL RTR_BROADCAST_EVENT CALL RTR_BROADCAST_EVENT The CALL RTR_BROADCAST_EVENT command causes a command server to execute the rtr_broadcast_event( ) routine and to display the returned status. Format CALL RTR_BROADCAST_EVENT [message-field1] [,message-field2.
CALL RTR_BROADCAST_EVENT T able 6–2 Parameters for rtr_broadcast_event C Parameter Name C Parameter V alue Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS [none] [D] pmsg, msglen, msgfmt 1 [message definition parameter list with positional qualifiers.
CALL RTR_BROADCAST_EVENT T able 6–3 Generated Format Strings Data T ype With /LENGTH= With /NOLENGTH STRING =n, "%nC" "%nC" where n=strlen(string) SIGNED =1, "%SB" &quo.
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 recipients whose /RECIPIENT_NAME matches the DEALER% string (that is, DEALER1, DEALER2, DEALERx).
CALL RTR_CLOSE_CHANNEL CALL RTR_CLOSE_CHANNEL The CALL RTR_CLOSE_CHANNEL command causes a command server to execute the rtr_close_channel( ) routine and to display the returned status.
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.
CALL RTR_ERROR_TEXT CALL RTR_ERROR_TEXT The CALL RTR_ERROR_TEXT command causes a command server to execute the rtr_error_text( ) routine and to display the returned error text.
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.
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 where the command was issued.
CALL RTR_OPEN_CHANNEL CALL RTR_OPEN_CHANNEL The CALL RTR_OPEN_CHANNEL command causes a command server to execute the rtr_open_channel( ) routine and to display the returned status.
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 .
CALL RTR_OPEN_CHANNEL /ACCESS=access /NOACCESS (D) Specifies an access string (that is, a password). All application programs (clients and servers) must specify the same access string for a given facility .
CALL RTR_OPEN_CHANNEL /F ACILITY_NAME=facility-name /F ACILITY=RTR$DEF AUL T_F ACILITY (D) Specifies the name of the facility for which the channel is declared. An application must specify the facility name when using the RTR CLI. The default facility name is RTR$DEF AUL T_F ACILITY .
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 is in other cases implied by the key type. The default value for key-length is four bytes.
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.
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.
CALL RTR_PREP ARE_TX CALL RTR_PREP ARE_TX The CALL RTR_PREP ARE_TX command causes a command server to execute the rtr_prepare_tx( ) routine and to display the returned status.
CALL RTR_PREP ARE_TX The CALL RTR_PREP ARE_TX can only be used in the context of nested transactions (rtr_start_tx was called with the parameter join_txid not equal to NOJOIN_TXID). If this call returns RTR_STS_OK, then the first (prepare) phase of the RTR 2PC protocol has been initiated.
CALL RTR_PREP ARE_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 .
CALL RTR_RECEIVE_MESSAGE CALL RTR_RECEIVE_MESSAGE The CALL RTR_RECEIVE_MESSAGE command causes a command server to execute the rtr_receive_message( ) routine and to display the returned status.
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 bytes the transaction ID, user handle, are event number are shown if they are relevant for the message type.
CALL RTR_RECEIVE_MESSAGE /TIMEOUT_MS=timoutms /TIMEOUT_MS=0 (D) The timoutms argument defines a timeout for the receive, in milliseconds. The default value is an infinite timeout. /TIMEOUT_MS specifies an immediate timeout. Examples The following example shows two CALL RTR_RECEIVE_MESSAGE commands on RTR$DEF AUL T_CHANNEL.
CALL RTR_REJECT_TX CALL RTR_REJECT_TX The CALL RTR_REJECT_TX command causes a command server to execute the rtr_reject_tx( ) routine and to display the returned status.
CALL RTR_REJECT_TX channel_name is not case sensitive. The default channel name is RTR$DEF AUL T_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.
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_REPL Y_TO_CLIENT CALL RTR_REPL Y_T O_CLIENT The CALL RTR_REPL Y_TO_CLIENT command causes a command server to execute the rtr_reply_to_client( ) routine and to display the returned status. Format CALL RTR_REPL Y_TO_CLIENT [message-field1] [,message-field2.
CALL RTR_REPL Y_TO_CLIENT T able 6–1 1 Parameters for rtr_reply_to_client C Parameter Name C Parameter V alue 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 positional qualifiers.
CALL RTR_REPL Y_TO_CLIENT T able 6–12 Generated Format Strings Data T ype With /LENGTH= With /NOLENGTH STRING =n, "%nC" "%nC" where n=strlen(string) SIGNED =1, "%SB" &q.
CALL RTR_REPL Y_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 a hexadecimal number .
CALL RTR_REQUEST_INFO CALL RTR_REQUEST_INFO The CALL RTR_REQUEST_INFO command causes a command server to execute the rtr_request_info( ) routine and to display the returned status.
CALL RTR_REQUEST_INFO Qualifiers /CHANNEL_NAME=channel_name /CHANNEL_NAME=RTR$DEF AUL T_CHANNEL Specifies the channel for which the operation is to be performed. The command server uses a combination of the channel_name and the window from which the call was issued to uniquely identify which channel to use.
CALL RTR_REQUEST_INFO Examples This command requests the backend transaction IDs for the facility ‘‘CASHF AC’’. RTR> CALL RTR_REQUEST_INFO/CHANNEL=INFOCHAN /INFCLA="btx"/SELITM=fac_id/SELVAL=CASHFAC /GETITMS=tb_txdx.
CALL RTR_SEND_TO_SER VER CALL RTR_SEND_TO_SER VER The CALL RTR_SEND_TO_SER VER command causes a command server to execute the rtr_send_to_server( ) routine and to display the returned status. Format CALL RTR_SEND_T O_SERVER [message-field1] [,message-field2.
CALL RTR_SEND_TO_SER VER T able 6–14 Parameters for rtr_send_to_server C Parameter Name C Parameter V alue Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS none [D] RTR_F_S.
CALL RTR_SEND_TO_SER VER If /FORMA T is specified without fmt-string , RTR automatically generates a format string. The format string is generated using the parameters given for the qualifiers /SIGNED, /UNSIGNED, /STRING and /LENGTH. The following table shows permitted values for these qualifiers when using /FORMA T without fmt-string .
CALL RTR_SEND_TO_SER VER 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-O.
CALL RTR_ST ART_TX CALL RTR_ST ART_TX The CALL RTR_ST ART_TX command causes a command server to execute the rtr_start_tx( ) routine and to display the returned status.
CALL RTR_ST ART_TX phase cannot be executed on an client FTM channel, may be relaxed in a future release.) When a nested transaction is started (join_txid not equal to NOJOIN_ TXID), then that transaction is given a new RTR TXID (which the operator can retrieve by calling rtr_get_tid).
CALL RTR_ST ART_TX /OUTPUT[=file-spec] /OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec .I f /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 transaction, in milliseconds.
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.
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.
CREA TE F ACILITY CREA TE F ACILITY Create an RTR facility and ready it for transaction traffic. Format CREA TE F ACILITY [facility_name] Command Qualifiers Defaults /ALL_ROLES=node-list /NOALL_ROLE.
CREA TE F ACILITY 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 the order of router node definitions when frontend load balancing is not enabled.
CREA TE F ACILITY Note: In environments that do not support clustering, use of the /CLUSTER qualifier 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.
CREA TE F ACILITY 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.
CREA TE JOURNAL CREA TE JOURNAL Create RTR’ s recovery journal. Format CREA TE JOURNAL [disk-1] ... [,disk-n] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /BLOCKS=nr-blocks /BLOCKS=1000 /MAXIMUM.
CREA TE JOURNAL T able 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 separate names with commas. The journals reside in subdirectories of the /rtrjnl .
CREA TE JOURNAL If /NOSUPERSEDE is specified (default), then a journal is created only if no journal previously existed. Related commands • DELETE JOURNAL • MODIFY JOURNAL • SHOW JOURNAL Exampl.
CREA TE P ARTITION CREA TE P ARTITION Creates an RTR partition. Format CREA TE P ARTITION [partition_name] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /CONCURRENT /NOCONCURRENT /F ACILITY=facilit.
CREA TE P ARTITION /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 for a partition (KEY1, KEY2,... up to KEY9).
CREA TE P ARTITION /ST ANDBY (D) /NOST ANDBY 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_ST A TE /NOIF_ST A TE /LOCK.
DEFINE /KEY T able 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 (.
DEFINE /KEY /LOG /NOLOG (D) Controls whether a message is displayed indicating that the key definition has been successfully created. /SET_ST A TE=state-name /NOSETST A TE (D) Controls whether pressing the key changes the current key state. /SET_STATE changes the current state to state-name when you press the key .
DEFINE /KEY The word DEF AUL T 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 CREA TE in the second DEFINE /KEY command. If the space is omitted, the system fails to recognize CREA TE as the keyword for the HELP command.
DELETE F ACILITY DELETE F ACILITY Delete an RTR facility . Format DELETE F ACILITY 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 where the command is issued.
DELETE F ACILITY 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.
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 command is issued.
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 P ARTITION DELETE P ARTITION Delete an RTR P ARTITION. Format DELETE P ARTITION P ARTITION_name Command Qualifiers Defaults /CLUSTER /NOCLUSTER /NODE=node-list /NODE=default-node-list /OUTPUT[.
DELETE P ARTITION Related Commands • CREATE PARTITION • SHOW PARTITION 6–66 RTR Command Line Interface.
DISPLA Y BAR DISPLA Y BAR Display a bar-graph in a monitor picture. Format DISPLA Y BAR expression Command Qualifiers Defaults /A VERAGE=(keyword,...) /none /BELL=Boolean-expression /NOBELL /BLANK=Bo.
DISPLA Y BAR Qualifiers /A VERAGE=(keyword,...) /NOA VERAGE Specifies that the items being monitored relating to keyword are displayed as an average.
DISPLA Y BAR /LABEL=text /NOLABEL (D) Specifies the text used to label the value being displayed. Symbols are substituted at display time. (See Section A.2, Substitution Symbols). /LENGTH[=nr-chars] /LENGTH=50 (D) Specifies the number of characters in a bar chart representing the maximum value.
DISPLA Y BAR Keyword Meaning PROCESS Process data items P ARTITION Partition data items FE_TRANSACTION Frontend transaction data items TR_TRANSACTION Backend transaction data items BE_TRANSACTION Router transaction data items /TOT ALIZE=(keyword,.
DISPLA Y BAR /X=previous-column (D) Specifies the screen column where the item is displayed (the leftmost column is 1). By default, items are displayed in the same column as defined by the previous DISPLA Y command. /Y[=row] /Y=next-free-row (D) Specifies the screen row where the item is displayed (top row is 1).
DISPLA Y NUMERIC DISPLA Y NUMERIC Display a number in a monitor picture. Format DISPLA Y NUMERIC expression Command Qualifiers Defaults /A VERAGE=(keyword,.
DISPLA Y NUMERIC The keyword can be one of the following: Keyword Meaning NODE Node data items LINK Link data items F ACILITY Facility data items PROCESS Process data items P ARTITION Partition data i.
DISPLA Y NUMERIC /RA TE[=interval] /NORA TE (D) Specifies that the rate of change of the expression is to be displayed rather than the absolute value. When /RATE is used, interval specifies the time interval in seconds used to calculate the rate of change.
DISPLA Y NUMERIC Keyword Meaning LINK Link data items F ACILITY Facility data items PROCESS Process data items P ARTITION Partition data items FE_TRANSACTION Frontend transaction data items TR_TRANSAC.
DISPLA Y 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.
DISPLA Y STRING DISPLA Y STRING Display a string in a monitor picture. Format DISPLA Y STRING expression Command Qualifiers Defaults /A VERAGE=(keyword,.
DISPLA Y STRING The keyword can be one of the following: Keyword Meaning NODE Node data items LINK Link data items F ACILITY Facility data items PROCESS Process data items P ARTITION Partition data it.
DISPLA Y STRING /SEP ARA TE=(keyword,...) /NOSEP ARA TE Specifies that the items being monitored relating to keyword are separated from each other and displayed as a list.
DISPLA Y STRING /X[=column] /X=previous-column (D) Specifies the screen column where the item is displayed (the leftmost column is 1). By default, items are displayed in the same column as defined by the previous DISPLA Y command. /Y[=row] /Y=next-free-row (D) Specifies the screen row where the item is displayed (top row is 1).
DISPLA Y SYMBOLIC DISPLA Y SYMBOLIC Display a text in a monitor picture depending on the result of an expression evaluation. Format DISPLA Y SYMBOLIC expression "text-string" [,"text-string"].
DISPLA Y SYMBOLIC /BOLD[=Boolean-expression] /NOBOLD (D) Specifies that the item is displayed in high intensity if Boolean-expression evaluates to T rue (non-zero).
DISPLA Y TEXT DISPLA Y TEXT Display text in a monitor picture. Format DISPLA Y TEXT text Command Qualifiers Defaults /BELL=Boolean-expression /NOBELL /BLANK=Boolean-expression /NOBLANK /BLINK=Boolean.
DISPLA Y TEXT /BOLD[=Boolean-expression] /NOBOLD (D) Specifies that the item is displayed in high intensity if Boolean-expression evaluates to T rue (non-zero). /F ACILITY /NOF ACILITY (D) Specifies that the symbol substitution in the text is carried out as if a facility data item were being displayed.
DISPLA Y TEXT /UNDERLINE[=Boolean-expression] /NOUNDERLINE (D) Specifies that the displayed value is underlined if Boolean-expression evaluates to T rue (non-zero). /X[=column] /X=previous-column (D) Specifies the screen column where the item is displayed (the leftmost column is 1).
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.
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.
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 cache.
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 .
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.
EXTEND F ACILITY EXTEND F ACILITY Adds new nodes or roles or both to an existing facility definition. Format EXTEND F ACILITY [facility_name] Command Qualifiers Defaults /BACKEND=backend-list /NOBAC.
EXTEND F ACILITY $ 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 facilit.
EXTEND F ACILITY 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 F ACILITY /OUTPUT[=file-spec] /OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec .I f /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 routers for this facility .
INITIALIZE JOURNAL INITIALIZE JOURNAL See CREA TE 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.
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 .
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 /NOCLUST.
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 where the command was issued.
MONITOR MONIT OR Displays a monitor picture on the screen. Format MONITOR [monitor-file-spec] Command Qualifiers Defaults /CLUSTER /NOCLUSTER /COUNT=nr-updates /COUNT=infinite /F ACILITY=facility-n.
MONITOR Note: In environments that do not support clustering, use of the /CLUSTER qualifier 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 or returning to the RTR> prompt.
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 .
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.
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.
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 .
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 /libra.
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 screen is to be scrolled.
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 specified nodes.
SET F ACILITY SET F ACILITY Sets various facility related options. Format SET F ACILITY facility-name Command Qualifiers Defaults /BROADCAST_MINIMUM_RA TE=Bps /BROADCAST_MINIMUM_RA TE=1000 /QUORUM_TH.
SET F ACILITY Note A node that combines both backend and router roles is counted twice in determining the threshold. A value of zero implies that the RTR determined threshold (half the number of node/role pairs configured plus one) is used. This is the default value; do not alter it unless you are sure that the unreachable nodes are really down.
SET F ACILITY Related Commands • SHOW FACILITY Examples RTR> SET FACILITY FINANCE/QUORUM_THRESHOLD=4 quorum threshold set to 4 (from 0) for facility FINANCE The SET F ACILITY command tells RTR to set the quorum threshold to four for facility FINANCE.
SET LINK SET LINK Sets various link related options. Format SET LINK link-name Command Qualifiers Defaults /AUTOISOLA TE /NOAUTOISOLA TE /ENABLE /DISABLE /CHECKSUM /NOCHECKSUM /CLUSTER /NOCLUSTER /IN.
SET LINK Remote node autoisolation may be enabled (at the isolator) where it applies to all links using SET NODE/AUTOISOLA TE, or for specific links only with the SET LINK/AUTOISOLA TE command.
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.
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 .
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 /OPERA TOR /NOOPERA T OR /OUTPUT[=file-spec] /OUTPUT=stdout Description The SET LOG command specifies where RTR writes its log messages.
SET LOG /OPERA TOR /NOOPERA TOR (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 .I f /OUTPUT or file-spec is omitted then the standard or default output is used.
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-lis.
SET MODE /NODE[=node-list] /NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in node-list .I f node-list is omitted then the command is executed only on the node where the command was issued.
SET NODE SET NODE Sets various node related options. Format SET node Command Qualifiers Defaults /AUTOISOLA TE /NOAUTOISOLA TE /CLUSTER /NOCLUSTER /INACTIVITY_TIMEOUT[=secs] /INACTIVITY_TIMEOUT=60 /I.
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.
SET P ARTITION SET P ARTITION Sets various partition related options. Format SET P ARTITION partition-name Command Qualifiers Defaults /F ACILITY=[facility_name] /F AILOVER_POLICY=[SHADOW | ST AND_BY.
SET P ARTITION /IGNORE_RECOVER Y /NOIGNORE_RECOVER Y (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 of either a local or remote journal, this command can be used to override the default RTR behaviour .
SET P ARTITION Once shadowing is disabled, the secondary site servers will be unable to startup in shadow mode until shadowing is enabled again. Shadowing for the partition can be turned on by entering the command at the current active member or any of its standbys.
SET TRANSACTION SET TRANSACTION Sets various transaction related options. Format SET TRANSACTION transaction-id Command Qualifiers Defaults /BEFORE[=date] today /ST A TE=current_state /F ACILITY=faci.
SET TRANSACTION Usage Notes The command can only be executed on a backend node in which the journal is located 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 the RTR journal synchronously .
SET TRANSACTION /NEW_ST A TE Specifies the new transaction state that selected transactions will be changed to. This qualifier is required and new state value must be specified.
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_P ART partition.
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 /CLU.
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 channels.
SHOW CLIENT SHOW CLIENT Display information about client channels. Format SHOW CLIENT Command Qualifiers Defaults /CLUSTER /NOCLUSTER /F ACILITY /F ACILITY="*" /FULL none /IDENTIFICA TION=p.
SHOW CLIENT /NODE[=node-list] /NODE=default-node-list (D) Specifies that the command is executed on all nodes specified in node-list .I f node-list is omitted then the command is executed only on the node where the command was issued.
SHOW DISPLA Y SHOW DISPLA Y Show which items were displayed by the most recently issued MONITOR command or DISPLAY commands. Format SHOW DISPLA Y Command Qualifiers Defaults /ALL /NOALL /OUTPUT[=fil.
SHOW DISPLA Y 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_channel " - /WIDTH=9 .
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.
SHOW F ACILITY SHOW F ACILITY Show the names, configuration and status of one or more facilities. Format SHOW F ACILITY [facility-name] Command Qualifiers Defaults /BALANCE /NOBALANCE /CLUSTER /NOCL.
SHOW F ACILITY /CONFIGURA TION /NOCONFIGURA TION (D) Specifies that the facility configuration is to be displayed. The configuration information indicates the role(s) of the the node where the comm.
SHOW F ACILITY On a frontend, this qualifier can be used to find out whether the node is currently connected to a router . Related Commands • CREATE FACILITY • DELETE FACILITY • SHOW LINK Exam.
SHOW F ACILITY 5 The facility’ s links. The first link shown (to node ‘‘bronze’ ’ i.e. itself) shows that it is a router , connected to the backend, and the router is quorate. The router is not current because there is no frontend on this connection.
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-l.
SHOW JOURNAL Related Commands • CREATE JOURNAL • DELETE JOURNAL • INITIALIZE JOURNAL Examples RTR> SHOW JOURNAL/FULL/FILENAMES 1 RTR journal:- 23 4 56 Disk(1): /dev/rz3a Blocks: 1500 Allocated: 1502 Maximum: 3000 File(1): /dev/rz3a /rtrjnl/SYSTEM/BRONZE.
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_ST A TE /NOIF_ST A TE Description The SHOW KEY command shows the key definitions created by the DEFINE /KEY command.
SHOW KEY Related Commands • DEFINE /KEY Examples RTR> SHOW KEY/FULL DEFAULT PF1 defined as "" DEFAULT KP0 defined as "MONITOR/RESUME" DEFAULT KP2 defined as "SCROLL DOWN .
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 .
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 .I f node-list is omitted then the command is executed only on the node where the command was issued.
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 SET LOG command.
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.
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.
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=def.
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.
SHOW P ARTITION SHOW P ARTITION Display server data partition information. Format SHOW P ARTITION Command Qualifiers Defaults /BACKEND /BACKEND /BRIEF /NOBRIEF /CLUSTER /NOCLUSTER /F ACILITY /F ACILI.
SHOW P ARTITION T able 6–21 Router Partition States State Meaning BLOCKED Key range is recovering or awaiting journal access ACTIVE Primary server is ready to accept transactions CA TCHUP Secondary .
SHOW P ARTITION • 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 P ARTITION comand displays callout server data as backend server data because a callout server uses server , not router , data structures.
SHOW P ARTITION Partition name: RTR$DEFAULT_PARTITION_16777217 Facility: RTR$DEFAULT_FACILITY State: active Low Bound: "aaaa" High Bound: "mmmm" Active Servers: 0 Free Servers: 1 T.
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.
SHOW PROCESS /OUTPUT[=file-spec] /OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec .I f /OUTPUT or file-spec is omitted then the standard or default output is used.
SHOW REQUESTER SHOW REQUESTER See SHOW CLIENT . The SHOW REQUESTER command has been replaced by SHOW CLIENT and is retained for compatibility reasons only .
SHOW RESOURCE MANAGER (SHOW RM) SHOW RESOURCE MANAGER (SHOW RM) Displays resource manager instance (RM) information. This command is available only on UNIX and W indows NT systems.
SHOW RESOURCE MANAGER (SHOW RM) /FULL /NOFULL (D) Displays additional information for facilities that reference a particular RM. If no rmi_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 node-list .
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] /NOD.
SHOW RTR /ST A TUS (D) /NOST A TUS 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.
SHOW SEGMENT SHOW SEGMENT Display the type and size of routing key segments. Format SHOW SEGMENT Command Qualifiers Defaults /CLUSTER /NOCLUSTER /F ACILITY /F ACILITY="*" /FULL /NOFULL /NOD.
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 shown for each facility .
SHOW SERVER SHOW SER VER Display information about server channels. Format SHOW SERVER Command Qualifiers Defaults /CLUSTER /NOCLUSTER /F ACILITY /F ACILITY="*" /FULL /NOFULL /IDENTIFICA TI.
SHOW SERVER T able 6–23 Server Flags FLAG Meaning BEC Backend Call-out EXA Explicit Accept EXP Explicit Prepare NCC No Concurrent NSB No Standby SHD Shadow SR V Server TRC Router Call-out Qualifiers /CLUSTER /NOCLUSTER (D) Specifies that the command is executed on all the nodes in the cluster .
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/.
SHOW TRANSACTION SHOW TRANSACTION Displays information about currently active transactions. Format SHOW TRANSACTION Command Qualifiers Defaults /BACKEND /NOBACKEND (D) /CLUSTER /NOCLUSTER /F ACILITY .
SHOW TRANSACTION Note: In environments that do not support clustering, use of the /CLUSTER qualifier 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.
SHOW TRANSACTION T able 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 ca.
SP A WN SP A WN Allows you to execute operating system commands without leaving the RTR utility . Format SP AWN [operating-system-command] Command Qualifiers Defaults /INPUT=file-spec /NOINPUT /OUTP.
ST ART RTR ST ART RTR Start RTR on one or more nodes. Format ST ART R TR 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.
ST ART RTR Qualifiers /ASTLM=ast-limit /ASTLM=(max-links + max-processes) 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.
ST ART 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 the RTR ACP can have outstanding at any one time. If you do not specify a direct I/O quota, the default value established at system generation time is used.
ST ART 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.
ST ART 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.
STOP RTR ST OP RTR Stop RTR on one or more nodes. Format STOP R TR Command Qualifiers Defaults /ABORT /NOABOR T /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 .
STOP RTR /OUTPUT[=file-spec] /OUTPUT=stdout (D) Specifies that the resulting information is written to the file file-spec .I f /OUTPUT or file-spec is omitted then the standard or default output is used.
TRIM F ACILITY TRIM F ACILITY Removes nodes or roles or both from an existing facility definition. Format TRIM F ACILITY [facility_name] Command Qualifiers Defaults /BACKEND=backend-list /NOBACKEND .
TRIM F ACILITY RTR MONITOR QUORUM displays a monitor picture which allows the quorum negotiations to be observed. Y ou can use this after using a TRIM F ACILITY command; once quorum has been re-attained, the participating nodes return to the quorate state.
TRIM F ACILITY /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.
UNREGISTER RESOURCE MANAGER (UNREGISTER RM) UNREGISTER RESOURCE MANAGER (UNREGISTER RM) The UNREGISTER RESOURCE MANAGER command unregisters an instance of a resource manager .
A Creating Monitor Pictures The standard monitor pictures provided with RTR (described in Chapter 5) are sufficient for most needs. Y ou may also create your own monitor pictures to suit particular needs.
Creating Monitor Pictures The commands used to define and display monitor pictures are: CLEAR DISPLA Y BAR DISPLA Y NUMERIC DISPLA Y STRING DISPLA Y SYMBOLIC DISPLA Y TEXT MONITOR SCROLL SHOW DISPLA Y These commands are described in the following sections.
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 data items of RTR, they may need to be changed for future versions of RTR.
Creating Monitor Pictures A.3 Arithmetic Expressions and Operators T able A–3 Arithmetic Operators in Display Commands Characters Meaning - Minus + Plus * Multiply / Divide & Logical AND | Logic.
Creating Monitor Pictures A.3 Arithmetic Expressions and Operators Aggregation of Data Items DISPLA Y commands which select multiple instances of a data item (for example, multiple instances of a process counter) can use the following keywords to control the way the items are aggregated.
.
B Server Shadowing and Recovery RTR shadowing gives you the ability to recover from a site disaster without the need for special coding within your application program.
Server Shadowing and Recovery B.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 are delivered only to the server(s) whose state has changed.
Server Shadowing and Recovery B.3 The RTR Journal System The number of blocks specified by the /BLOCKS qualifier specifies the size of the journal that RTR attempts to keep to. (The actual number of blocks used may vary , depending upon the load on RTR.
Server Shadowing and Recovery B.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.
Server Shadowing and Recovery B.6 Performance Note that RTR does not have to wait for the secondary shadow server to complete its processing. It only needs to know that the primary has committed the transaction and that the journal file of the secondary shadow server contains the final vote status.
Server Shadowing and Recovery B.8 Application Considerations • Any physical reference to the transaction which is unique to the executing server , e.
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 KR to Routers Error Proposal accepted − comm.
Server Shadowing and Recovery B.10 Client States B.10 Client States The current state of a client process can be examined as follows: RTR> show client/full Clients: Process-id: 13340 Facility: RTR$.
Server Shadowing and Recovery B.1 1 Partition States B.1 1 Partition States The current state of a key-range partition can be examined using the SHOW PARTITION/FULL command for the routers and the bac.
.
C XA Support This appendix explains how RTR may be used with a X/OPEN Distributed T ransaction Processing (DTP) conformant Resource Manager . C.1 Introduction The X/OPEN Distributed T ransaction Processing (DTP) architecture defines a standard interface that lets application programs share resources provided by resource managers.
XA Support C.1 Introduction facility_name = user-specified facility name /resource_manager = the name of those RMs this facility references For example: CREATE FACILITY test /front=N1 /back=N2/router=N3 /resource_manager=(employ_rm,payroll_rm) C.
D RTR Utility Error Messages This appendix describes the various error messages that can be returned by the RTR utility . %RTR-F-ABKEYW , Ambiguous qualifier or keyword - supply more characters Explanation: T oo few characters were used to truncate a keyword or qualifier name to make the keyword or qualifier name unique.
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.
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 to the presence of an undelivered mt_closed message on the channel.
RTR Utility Error Messages %RTR-S-DISITMCLR, [A] display item(s) cleared Explanation: Indicates how many display items [A] were successfully cleared after issuing a CLEAR DISPLA Y command. %RTR-W -DISKALL, Disk is not available to RTR Explanation: An attempt was made to create a journal on a disk which is allocated to a different process.
RTR Utility Error Messages %RTR-F-DUPJOUFIL, Duplicate RTR journal file found - remove duplicate file or CREA TE JOURNAL /SUPERSEDE Explanation: A duplicate RTR journal file has been found. This status may be returned by the CREA TE F ACILITY and SHOW JOURNAL commands.
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 was unable to access.
RTR Utility Error Messages %RTR-E-ERRST AACP , Unable to start ACP Explanation: The RTR ACP process could not be started when a "ST ART RTR" command was issued.
RTR Utility Error Messages %RTR-E-F ACNAMLON, Facility name [A] is longer than 30 characters Explanation: Facility name [A] is too long. %RTR-E-F ACNAMST A, Facility name [A] does not start with a letter Explanation: Facility name [A] does not start with a capital letter ("A" to "Z").
RTR Utility Error Messages %RTR-E-ILLP ARTCHAR, 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.
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.
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 "DISPLA Y" command within a display file. There already is an item at point [A], [B].
RTR Utility Error Messages %RTR-F-JOUFORCHA, Journal format has been changed - CREA TE JOURNAL /SUPERSEDE Explanation: The journal file(s) found have an out-of-date format. This status may be returned by the CREA TE F ACILITY and SHOW JOURNAL commands after a new version of RTR has been installed on a system.
RTR Utility Error Messages %RTR-S-JOURNALINI, Journal has been created on device [A] Explanation: Confirms that the RTR journal has been successfully created on device [A] after issuing the "CREA TE JOURNAL" command.
RTR Utility Error Messages %RTR-E-LOCKF AIL, Cannot obtain lock for resource [A] Explanation: Failed to obtain lock. Enable logging for more information about error .
RTR Utility Error Messages %RTR-E-NDBT ABFUL, The NDB table is full Explanation: This message is displayed when an "CREA TE F ACILITY" command is issued.
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 node name prefix ("dna." or a substitute), but no corresponding entry in the node database can be found.
RTR Utility Error Messages %RTR-E-NOKEYSEGS, Y ou must specify at least one keysegment - use /KEY1 - /KEY9 Explanation: Except for a callout partition, it is necessary to define the key range, so the absence of any key segment descriptors is an error .
RTR Utility Error Messages %RTR-E-NOSUCHITM, Nothing displayed at x = [A] ,y=[ A ] Explanation: Indicates that invalid coordinates were specified on a "CLEAR DISPLA Y" or "SHOW DISPLA Y" command. No item is displayed at point [A], [B].
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.
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 for an unknown partition command.
RTR Utility Error Messages %RTR-S-PRTNCREA TED, Partition created Explanation: The requested partition was successfully created. %RTR-S-PRTNDELETED, Partition deleted Explanation: The requested partition was successfully deleted.
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 is being deleted.
RTR Utility Error Messages %RTR-E-RTRALRST A, RTR already started Explanation: RTR was already running when the "ST ART RTR" command was executed.
RTR Utility Error Messages %RTR-F-SPUJOUFIL, Spurious RTR journal file found - remove extra file, or CREA TE JOURNAL /SUPERSEDE and submit SPR Explanation: A spurious RTR journal file has been found which does not correspond to the other journal files on the system.
RTR Utility Error Messages %RTR-E-TOOMANCHN, T oo many channels Explanation: Displayed when a "SYS$DCL_TX_PRC" command is issued and the channel table is full. %RTR-F-TOOMANDIS, T oo many disks specified in journal definition Explanation: Explanation: T oo many disks were specified in journal definition.
RTR Utility Error Messages %RTR-E-UNEXPEND, Expression ended before [A] encountered Explanation: The expression is invalid because it terminated where when token [A] was expected. %RTR-E-UNKNOWQUAL, Invalid qualifier keyword value - check your program Explanation: Status return indicating that an unrecognised qualifier keyword value was supplied.
E RTR log messages This appendix describes the various error messages that can be sent to the operator console or written to RTR’ s operator log file.
RTR log messages %RTR-E-BADIDSIZ, Bad node ID size [A] detected at 0x[A] Explanation: This message indicates that errors have been detected in processing of an internal node identifier .
RTR log messages %RTR-F-BRODISLIN, Broadcast message(s) discarded because of link unavailability Explanation: One or more broadcast messages had to be discarded because there is no logical link to the destination node.
RTR log messages %RTR-I-CONNALIAS, Link [A] connected as [A] Explanation: Support for internet tunnels allows for the configuration of links from which connections appear to originate with an source .
RTR log messages %RTR-I-F ACLOSTFE, Facility [A] lost Frontend node [A] Explanation: This node is no longer a current router on facility [A], for frontend node [B] %RTR-I-F ACLOSTTR, Facility [A] lost.
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 aborted to determine why this occurred (possible resource problems on the server , for example).
RTR log messages %RTR-I-JOUSEACOM, Journal search on facility [A] completed. [A] recoverable transactions found Explanation: Journal search has completed. This message appears when RTR is started The number of transactions needing recovery is indicated by [A].
RTR log messages %RTR-E-NOCURRTR, Current router search failed for facility [A] Explanation: None of the routers specified for facility [A] are currently connectable.
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 the partition is deleted prior to completion of the operation.
RTR log messages %RTR-E-PRTSETF AIL TR, Router unable to process command Explanation: A partition set command failed at the router . An entry is written to the log file describing the problem. Message arguments are the facility name and the KR ID. A second message is written detailing the nature of the problem.
RTR log messages %RTR-F-QIROVERFLOW , No more QIRs left Explanation: This status is used to indicate an inadequacy in the static reservations for the internal query initiation descriptors. Make a note of all QRM counters using SHOW RTR /COUNTER=QRM* Send SPR with the corresponding RTRACP dump.
RTR log messages %RTR-W -RSPF AC, Response from Node [A] about Facility [A] Explanation: A negotiation with remote node [A] about facility [B] has failed for the reason reported in the following line. This may be a reason for system manager intervention.
RTR log messages %RTR-W -TOOMANYNETIDS, T oo many net IDs for node ’[A]’ - check for and eliminate any unnecessary adapter/protocol combinations Explanation: On a system configured to run multiple network protocols over multiple adpaters, RTR can run out of space to store and communicate the resultant node IDs.
.
Index A Active Monitor, 5–2 Aggregation of Data Items, A–5 B Backend, 2–1 BAR DISPLA Y, 6–67 Broadcast Monitor, 5–2 C Call Rtr_accept_tx, 6–3 rtr_prepare_tx, 6–22 CALL RTR_BROADCAST_EVEN.
DTC Support, C–2 E ENVIRONMENT SET, 1–4, 6–108 SHOW, 6–135 Errors, 1–2 Event Monitor, 5–2 EXECUTE, 6–89 EXIT, 6–90 EXTEND F ACILITY, 6–91 F Facility, 1–1 Create, 2–1 Monitor, 5.
Monitor (cont’d) Routing, 5–3 Rtr, 5–3 Stalls, 5–3 System, 5–3 Tps, 5–3 Tpslo, 5–3 T raffic, 5–3 V2calls, 5–4 XA, 5–4 MONITOR, 5–1, 6–100 Monitor file, 5–1 Monitor picture,.
SET (cont’d) MODE, 6–1 18 NODE, 6–120 P ARTITION, 6–122 TRANSACTION, 6–125 SHOW CHANNEL, 6–129 CLIENT, 6–131 DISPLA Y, 6–133, A–2 ENVIRONMENT, 6–135 F ACILITY, 6–136 JOURNAL, 6.
An important point after buying a device Compaq AA-Q88CE-TE (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Compaq AA-Q88CE-TE yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Compaq AA-Q88CE-TE - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Compaq AA-Q88CE-TE you will learn all the available features of the product, as well as information on its operation. The information that you get Compaq AA-Q88CE-TE will certainly help you make a decision on the purchase.
If you already are a holder of Compaq AA-Q88CE-TE, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Compaq AA-Q88CE-TE.
However, one of the most important roles played by the user manual is to help in solving problems with Compaq AA-Q88CE-TE. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Compaq AA-Q88CE-TE along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
