Home

Compaq AA-Q88CE-TE User's Manual

1. 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 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 6 88 RTR Command Line Interface EXECUTE EXECUTE Format Description Parameters Qualifiers Examples Executes a file containing RTR commands EXECUTE file spec Command Qualifiers Defaults VERIFY NOVERIFY The EXECUTE command reads a file containing RTR commands and executes them This command also has the form file spec file spec Specifies the name of the file containing commands to be executed VERIFY NOVERIFY D Specifies that the commands being executed and the resulting information is displayed on the terminal RTR gt execute facility_startup This command executes the file facility_startup This file might contain commands such as start rtr create journal create facility funding fontend nodel node2 router node3 RTR Command Line Interface 6 89 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 Same as QUIT 6 90 RTR Command
2. 2 18 2 12 1 Role Assignment for Backend Node Partitions 2 18 2 12 2 Router Select esos a cin kod gor Gales a ar nea ele Me ee E are eg 2 21 3 Partition Management 3 1 OVENVIEW 24g cn eee eee a EE Cee Eee EE ES 3 1 3 1 1 What Is a Partition 22 005e seceded bese deeb eee eee eas 3 1 3 1 2 What is Partition Management 000000 eee 3 1 3 2 Partition NAMINO a aca cise ache a Oe nee ae ee ER e eee ke 3 2 3 2 1 Default Partition Names scs e sacs ei aaie cece tes 3 2 3 2 2 Programmer Supplied Names 0000 cece ees 3 2 3 2 3 System Manager Supplied Partition Names 0005 3 2 3 2 4 Name Format and Scope oss aiwnis amea immi amna gwi tees 3 2 3 3 Life Cyde of a Partition icccseenaweee nace Senge eee eee eine EEEE 3 2 3 3 1 Implicit Partition Creation 0 0 0 ee 3 3 3 3 2 Explicit Partition Creati0N oooccccccconcoooo 3 3 3 3 3 Persistence of Partition Definitions 0000 eevee 3 3 3 4 Binding Server Channels to Named Partitions 3 3 3 5 Entering Partition Commands ea ae E aa eee 3 4 3 5 1 Command Line Usage sessa si menaa aa eann a ee 3 4 3 5 2 Programmed Partition Management 000 cee eee 3 4 3 6 Managing Partitions ess sisia amwe dami anna ga ia tee 3 5 3 6 1 Controlling Shadowing seassa ferimerias i iera ee 3 5 3 6 1 1 Command Line Example 0 000000 ee 3 5 3 6 1 2 Programming Information
3. 5 4 5 2 2 Monitor ACPZAPP sessi saae ease sabes ot ee eee de weds ek 5 5 5 2 3 Monitor Active 0 ee 5 6 5 2 4 Monitor APPZACP e uensc eda ine e eGo a eS 5 6 5 2 5 Monitor Broadcast oocccccccococc a o 5 6 5 2 6 Monitor Calls saipe seh genrde eb eb ead edb ee added Reeds E 5 7 5 2 7 Monitor Channel oc coccion aud db a we packed and aha 5 7 5 2 8 Monitor CONNECES occcccccccoc eee 5 7 5 2 9 Monitor EVERT weee aten e a ao e ed aia 5 8 5 2 10 Monitor Facility seo aria ed eden e A 5 8 5 2 11 Monitor FION 3 0 4 okt tea ath Mad ote i coe ah a ee a ated a 2 5 9 5 2 12 Monitor Group 2 0 ees 5 9 5 2 13 Monitor PC osc sade en adage e 5 10 5 2 14 5 2 15 5 2 16 5 2 17 5 2 18 5 2 19 5 2 20 5 2 21 5 2 22 5 2 23 5 2 24 5 2 25 5 2 26 5 2 27 5 2 28 5 2 29 5 2 30 5 2 31 5 2 32 5 2 33 5 2 34 5 2 35 5 2 36 5 2 37 Monitor IRCRAT E gt ica ra se Gti ae ae ae wed Soe nag a ee ee Monitor Journal c0 5 sac 8 os wees ee tweens Bie ad a dw eas Monitor LINK raider ai eae Oo Monitor Netbytes 0 0 0 cece Monitor Netstat iii al a da al eatin bela aia ola a Monitor Partit cia ata wie e a ti wae le Monitor QUEUES iii aora a aa aii Monitor QUORUM si ad ada ac Monitor RECOVETY AA Aided eiaa a iei haved aie nd et Seid lees Monitor RejectS cc ad eed ieee eed Se Sede de eee ss Monitor Rejhist 0 0 es Monitor Response 0 000 ees Monitor Rolequorum a eeaeee a es Monitor ROQUES its
4. ENABLE DISABLE ENABLE specifies that connect attempts are honoured from the node specified by link name This command is used to enable a link which is in a disabled state A link can be disabled either as a result of operator action or automatically if it has been suspected of causing severe congestion If a link is automatically disabled an entry is madein the RTR error log DISABLE specifies that connect attempts are no longer honoured from the node link name Note that disabling the link does not have any immediate effect on an established link It only takes effect when new connection attempts are made 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 command is executed only on the node where the command was issued 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 INACTIVITY_TIMEOUT secs JINACTIVITY_TIMEOUT node default INACTIVITY_TIMEOUT secs specifies the maximum elapsed time in seconds before RTR discards a link that is neither receiving traffic nor responding to explicit link state queries Link failover occurs between
5. low_bound Specifies the lower bound of the key range that servers in the partition will service The interpretation of low bound depends on the key type if the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for low bound is the smallest possible value that can fit in the specified key type If the key bound value length is less than the key length given in length_of_key the key bound will automatically be null padded to the required length high_bound Specifies the upper bound of the key range that servers in the partition will service The interpretation of high bound depends on the key type If the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for high bound is the largest possible value that can fit in the specified key type If the key bound value length is less than the key length given in length_of_key the key bound will automatically be null padded to the required length If the specified key range overlaps that of an existing partition in the facility or if the key segment description conflicts with an existing definition the command fails FACILITY Specifies the name of the facility in which the partition is being created 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 comma
6. 0 00 c eee es 3 5 3 6 2 Controlling Transaction Presentation s sasaaa eee eee 3 6 3 6 2 1 Command Line Example o 3 6 3 6 2 2 Programming Information 0000 cece eee es 3 6 3 6 3 Controlling Recovery 0 0 ee 3 6 3 6 3 1 Command Line Example s soie saia maiaa a dea ai Eoi agai ia a 3 7 3 6 3 2 Programming Information a sesia sisia da aai i maa a i ees 3 7 3 6 4 Controlling the Active Site 6 ee 3 7 3 6 4 1 Command Line Example o 3 7 3 6 4 2 Programming Information 0 000 cece eee ee 3 8 3 6 5 Controlling Failover o o o o oooooooooo ee 3 8 3 6 5 1 Command Line Example o 3 8 3 6 5 2 Programming Information 0 000 aaa 3 8 3 6 6 Controlling Transaction Replay 0 000000 eee oo 3 9 3 6 6 1 Command Line Example s aeieea a aaa ea aaa eee 3 9 3 6 6 2 Programming Information sssaaa aaaea 3 9 3 7 Displaying Partition Information 00 00 a E a a eee 3 10 3 7 0 1 Command Line Example 0 00000 ee 3 10 4 Transaction Management 4 1 OVOIVIOW oe fae cet ii ee ee ee ee eee eee eels 4 1 4 1 0 1 Command Line Examples 0 000000 ee 4 2 4 1 1 Exception TransactionS 0 00 c cee ee 4 2 4 1 2 Transaction State Changes 0 0 asitie tes 4 3 5 RTR Monitoring 5 1 IAEROGUCHION 2 iii ra dace Gawd wel RR ae hehe aed ee wR oes basa 5 1 5 2 Standard Monitor PiCtUrEs sioiias aii ei a a aia eee 5 1 5 2 1 Monitor ACCFAIL Link Acceptance Failures
7. NOREVERSE D Specifies that the item is displayed with the foreground and background visual attributes swapped if Boolean expression evaluates to True non zero ROWS nr rows ROWS 1 D Specifies how many rows are used to display the item This is only meaningful if SEPARATE is also Specified The default number of rows is one SELECT Boolean expression NOSELECT D Displays the item if Boolean expression evaluates to True non zero SEPARATE keyword NOSEPARATE Specifies that the items being monitored relating to keyword are separated from each other and displayed as a list This allows a number of items to be separated in one qualifier 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_TRANSACTION Router transaction data items TOTALIZE keyword NOTOTALIZE Specifies that the items being monitored relating to keyword are added together and displayed as a total The keyword can be one of the following Keyword Meaning NODE Node data items 6 74 RTR Command Line Interface DISPLAY NUMERIC Keyword Meaning LINK Link data items FACILITY Facility data items PROCESS Process data items PARTITION Partition data items FE_TRAN
8. OpenVMS 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 RTRJ NL Use SHOW If the SYSTEM account has insufficient disk DEVICE quota for journal file creation you must have the EXQUOTA privilege in order for the command to complete successfully Qualifiers BLOCKSj nr blocks BLOCKS 1000 D Specifies the target size of the journal file in 512 byte blocks This qualifier can be applied locally to each disk or globally for all disks 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 command is executed only on the node where the command was issued 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 MAXIMUM_BLOCKS nr blocks MAXIMUM_BLOCKS 1000 D Specifies the maximum size that the journal file can use This qualifier can be applied locally to each disk or globally for all disks 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 omitt
9. The RTR CLI is accessed by entering RTR at the operating system prompt Commands can either be entered on the same line as the RTR verb for example o rtr command Introduction 1 1 Introduction 1 2 Entering Commands or when several commands are to be entered at the RTR prompt Q 9 rtr RTR gt start rtr RTR gt create journal Note For convenience the user prompt for the operating system is shown here as the symbol Your system may have a different prompt The RTR CLI accepts commands that you type and can process procedures consisting of RTR commands Most RTR commands accept qualifiers these are indicated by the forward slash character For example many RTR commands accept the OUTPUT qualifier it directs the output from the command to a file The forward slash character may also appear in the filenames of some operating systems such filenames must be enclosed in quotation marks to ensure that RTR does not interpret the filename as a command qualifier When RTR commands are entered on a single line you may need to use extra quotation characters depending on the operating system in use For example when running on most UNIX platforms additional single quotation marks are required when entering quoted items such as filenames Compare the following commands Q rtr RIR gt show facility output usr users test fac_output lis rtr show facility output usr users tes
10. _RTR gt router TR1 TR2 _RTR gt pbackend BE1 BE2 BE3 _RTR gt call_out router 2 6 Router Load Balancing Router load balancing or intelligent re connection of frontends to a router is possible allowing a frontend to select the router that has least loading The create facility and set facility commands have the balance qualifier to control this RTR now allows frontends to determine their router connection The RTR version 2 implementation of load balancing treated all routers as equal and this could cause reconnection timeouts in geographically distant routers When used with create facility balance specifies that load balancing is enabled for frontend router connections across the facility Use the set facility no balance to switch load balancing off and on The default behavior nobalance is for a frontend to connect to the preferred router Preferred routers are selected in the order specified in the create facility router tr1 tr2 tr3 qualifier Automatic failback ensures that the frontend will reconnect to the first router in the order when it becomes available Manual balancing can be attained by specifying different router orders across the frontends Non load balanced frontend connections will fail back to the preferred router when it becomes available Automatic load balancing institutes a router list with a random value for the frontend assigned at the time the create facility with the balance command
11. Related Commands e CREAT E PAR e SHOW PARTIT ITION 6 66 RTR Command Line Interface DISPLAY BAR DISPLAY BAR Format Description Parameters Display a bar graph in a monitor picture DISPLAY BAR expression Command Qualifiers AVERAGE keyword BELL Boolean expression BLANK Boolean expression BLINK Boolean expression BOLD Boolean expression CHARACTER char DAMPING damping factor LABEL text LENGTH nr chars MAXIMUM max value MINIMUM min value RATE interval REVERSE Boolean expression ROWS nr rows SELECT Boolean expression SEPARATE keyword TOTALIZE keyword UNDERLINE Boolean expression VALUE value type X column Y row Defaults none NOBELL NOBLANK NOBLINK BOLD CHARACTER a NODAMPING NOLABEL LENGTH 50 MAXIMUM 10 MINIMUM 0 NORATE NOREVERSE ROWS 1 NOSELECT none none NOUNDERLINE VALUE CURRENT Column of previous item Next free row The DISPLAY BAR command displays the expression as a bar graph in a monitor picture It can be used within a monitor file or issued at the RTR prompt when interactively defining a monitor picture for use in a subsequent MONITOR command Note that the introduction of the SEPARATE TOTALIZE and AVERAGE qualifiers has superseded the qualifiers FACILITY LINK PARTITION NODE and PROCESS These superseded qualifiers are no longer described here however they are still supported
12. The CALL RTR_START_TX command causes a command server to call the rtr_start_tx routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_start_tx routine itself is described in Application Programmer s Reference Manual The prototype of rtr_start_tx is rtr_status_t rtr_start_tx rtr_channel_t channel rtr_sta_flag_t flags rtr_timout_t timoutms rtr_channel_t joinchan y Table 6 16 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 16 Parameters for rtr_start_tx C Parameter Name C Parameter Value Command Line Specification channel CHANNEL_NAME name flags RTR_NO_FLAGS none D timoutms TIMEOUT_MS timoutms joinchan OIN_CHANNEL channel name Nested Transaction Usage If the FOREIGN_TM qualifier is specified for channel then the global coordinating TM for this transaction is a foreign TM In this case rtr_start_tx must be called to start a transaction cannot be started implicitly on first call to rtr_send_to_server and the join_txid parameter must be specified The txid_type parameter defaults to RTR if not specified This restriction that classic transactions without a prepare 6 42 RTR Command Line Interface Qualifiers CALL RTR_START_TX phase cannot be executed on an client
13. The rtrinfo group is currently only used to allow applications to call rtr_request_info Depending on your UNIX system see the addgroup groupadd or mkgroup commands or the System Administration documentation for details on how to add new groups to your system Starting and Setting Up RTR 2 9 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 who do not fall into the above categories but are members of the rtrinfo group can only use RTR commands that display information SHOW MONITOR call rtr_request_info etc If the groups rtroper and rtrinfo are not defined then all users automatically belongs to them This means that there is no system management required for systems that do not need privilege checking Setting RTR Privileges on OpenVMS Systems Create the Rights Identifiers RTRSOPERATOR and RTR INFO if they do not already exist on your system and assign them to users as appropriate The RTR System Manager must have the RTR OPERATOR identifier or the OPER privilege Setting RTR Privileges on Windows NT Systems Administrator privileges are needed for RtrOperator rights by the RTR System Manager 2 8 RTR ACP Virtual Memory Sizing In addition to basic memory requirements of an unconfigured RTR ACP of approximately 5 8 Mbytes additional memory requirements may be require
14. XA 5 4 MONITOR 5 1 6 100 Monitor file 5 1 Monitor picture 5 1 A 1 N R NAME_CACHE FLUSH 6 88 Netbytes Monitor 5 3 Netstat Monitor 5 3 Network transports 2 13 NODE SET 6 120 SHOW 6 150 NUMERIC DISPLAY 6 72 O Operating system command SPAWN 6 86 6 171 P Partit Monitor 5 3 PARTITION CREATE 6 54 DELETE 6 65 SET 6 122 SHOW 6 152 PROCESS SHOW 6 156 Q Queues Monitor 5 3 QUIT 6 103 Quorum Monitor 5 3 RECALL 6 104 Recovery Monitor 5 3 REGISTER RESOURCE MANAGER 6 105 RM 6 105 Rejects Monitor 5 3 Rejhist Monitor 5 3 Remote commands 1 3 2 3 REQUESTER SHOW 6 158 RESOURCE MANAGER REGISTER 6 105 SHOW 6 159 UNREGISTER 6 182 Response Monitor 5 3 RM REGISTER 6 105 SHOW 6 159 UNREGISTER 6 182 Role assignment for backend node partitions 2 18 Rolequorum Monitor 5 3 Router 2 1 Router load balancing 2 8 Routers Monitor 5 3 Router Selection 2 21 Routing Monitor 5 3 Rtr Monitor 5 3 Start 2 1 RTR SHOW 6 161 START 6 172 STOP 6 177 S SCROLL 6 107 SEGMENT SHOW 6 163 Server 2 2 SERVER SHOW 6 165 SET ENVIRONMENT 1 4 6 108 FACILITY 6 109 LINK 6 112 LOG 6 116 Index 3 SET cont d MODE 6 118 NODE 6 120 PARTITION 6 122 TRANSACTION 6 125 SHOW CHANNEL 6 129 CLIENT 6 131 DISPLAY 6 133 A 2 ENVIRONMENT 6 135 FACILITY 6 136 JOURNAL 6 140 KEY 6 142 LINK 6 144 LOG 6 146 MO
15. and the dollar sign Partition names must be unique within a facility name and should be referenced on the command line with the facility name when using partition commands Partition names exist only on the backend where the partition resides You won t see the partition names at the RTR routers 3 3 Life Cycle of a Partition 3 2 Partition Management 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 partition attributes are established with the flags argument Before RTR V3 2 this was the only way in which partitions could be created Partitions created in this way are automatically deleted when the last server channel to the partition is closed 3 3 2 Explicit Partition Creation Partitions can also be created by the system operator before server application program start up using system management commands This gives the operator more control over partition characteristics Partitions created in this way remain in the system until either explicitly deleted by the operator or RTR is stopped 3 3 3 Persistence of Partition Definitions RTR stores partition definitions in the journal and records for each transaction the partition in which it was processed This is convenient when viewin
16. 3 Number of links down 0 atus Sum mary Tue Feb 16 1999 13 02 18 nodea gt nodea nodea gt nodeb nodea gt nodec up alpha 1386 up TC TC P P RTR Monitoring 5 7 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 Summarizes link status and is less detailed than the monitor netstat display 5 2 9 Monitor Event EVENT ROUTING STATISTICS BY FACILITY 6 APR 1999 15 21 47 Destination Transit Node Facility In Out Lost In Out Lost Total 180 175 5 180 180 0 NODEA FACCMS 25 25 0 25 25 0 NODEA TESTFAC 155 150 5 155 138 0 Displays event routing data by facility Information includes events in transit from RTR to a destination facility and destination information showing number of events enqueued for the application In column number of events processed by the application Out column and the number of events discarded by RTR Lost column 5 2 10 Monitor Facility FACILITY COUNTERS 7 JAN 1999 14 04 27 NODE ALL FACILITY ALL ASM_MSGS_TO_APPS 290005 TMBE_TX_RQ_COMMITS 0 CF_TR_FE_LOSS 0 ASM_MSGS_FROM_APPS290404 TMBE_TX_RQ_ABORTS 0 CF_TR_BE_LOSS 0 BM_NCF_EVENTS_DELV 6 TMBE_TX_ACCEPTS 72501 CF_TR_F
17. Anonymous Clients RTR allows the use of wild cards when specifying the frontends that a router is permitted to accept connections from that is in the facility definition on the router Valid wild card characters are and The result of using a wild card character at facility configuration time is the creation of a template link When operating RTR in conjunction with the Compaq Internet Personal Tunnel a client system outside of the corporate firewall uses tunnel software to obtain a secure channel from the Internet to inside the corporate domain The tunnel client is assigned an address by the tunnel server from a pool when the tunnel software starts up When an RTR router receives a connection request from RTR running on this client the source of the address is the address assigned by the tunnel server There is no longer a fixed relationship between the client and its address The method of configuring the router to accept such a connection is to define the frontends nodes with all the possible addresses that the tunnel server can assign to tunnel clients you can do this with wildcards For example RTR gt create facility frontend pool places dec com This command enables all nodes connecting through the tunnel to connect as frontends The anonymous client feature may also be used with frontends that are using DHCP for TCP IP address assignment Using the Tunnel Prefix By using the node name prefix
18. Both the RM instance name and the database name RM name contained in open string must be the same as that registered earlier using the REGISTER RM command This information is now stored in the RTR key segment structure A new RTR_F_OPE_XA_MANAGED flag is created to associate the channel with the XA interface For example typedef struct rtr_keyseg_type_t ks_type RM_NAME_TYPE rtr_keylen_t ks_length N A rtr_keylen_t ks_offset N A rtr_pointer_t ks_lo_bound RM_NAME rtr_pointer_t ks_hi_bound OPEN_STRING rtr_keyseg_t C 2 Microsoft DTC Support RTR for Windows NT is interoperable with Microsoft s Distributed Transaction Controller DTC DTC is supported via the RTR XA software architecture That is with the X Open XA protocol RTR users can develop application programs to update MS SQL Server databases MSMQ or other Microsoft resource managers under the control of a true distributed transaction This is possible because RTR as a distributed transaction manager is able to directly communicate with MS DTC to manage a transaction or perform a recovery via the XA protocol For each standard XA call received from RTR MS DTC will translate it into a corresponding OLE transaction call that SQL Server or MSMQ can use to update databases C 2 XA Support D RTR Utility Error Messages This appendix describes the various error messages that can be returned by the RTR utility RTR F ABKEYW A
19. Explanation Invalid pkeyseg argument RTR F INVRCPNAM Invalid rconam argument Explanation Invalid rconam argument RTR F INVREASON Invalid reason argument Explanation Invalid reason argument RTR E INVRMNAME Invalid resource manager name Explanation Invalid resource manager name RTR E INVSTATCHANGE Invalid to change from current state to the specified state Explanation RTR SET TRAN command cannot change RTR F INVWAKEUP Invalid wakeup argument Explanation Invalid wakeup argument D 10 RTR Utility Error Messages RTR Utility Error Messages RTR E ITMALREXI There is already something displayed at x A y A Explanation ndicates 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 check validity and spelling n A Explanation A keyword specified in a command is not valid for the command The rejected portion of the command is displayed between backslashes RTR F IVQUAL Unrecognized qualifier check validity spelling and placement n A Explanation An invalid qualifier is specified RTR F IVVERB Unrecognized command verb check validity and spelling n A Explanation The first word in the command is not a valid CLI command or a name equated with a command The rejected portion of the command is displayed between backslashes RTR W OUALREXI Journal already created Expl
20. FACILITY_NAME facility name FOREIGN_TM tm_id HIGH_BOUND shigh bound KEY1 keysegdesc KEYn keysegdesc Defaults NOACCEPT_EXPLICIT NOACCESS NOBE_CALL_OUT CHANNEL_NAME RTR DEFAULT_CHANNEL NOCLIENT NOCLUSTER CONCURRENT NOEVENTS FACILITY_NAME RTR DEFAULT_FACILITY NOFOREIGN_TM HIGH_BOUND max value for key type LENGTH_OF_FIELD key field length LENGTH_OF_FIELD 4 LOW_BOUND low bound NODE node list OFFSET_OF_KEY offset OUTPUT file spec PARTITION_NAME partition name PREPARE_EXPLICIT RECIPIENT_NAME rcpnam SERVER SHADOW STANDBY TR_CALL_OUT TYPE_OF_FIELD key field type LOW_BOUND lowest value for key type NODE default node list OFFSET_OF_KEY 0 OUTPUT stdout NOPREPARE_EXPLICIT RECIPIENT_NAME null NOSERVER NOSHADOW STANDBY NOTR_CALL_OUT TYPE_OF_FIELD UNSIGNED The CALL RTR_OPEN_CHANNEL command causes a command server to call the rtr_open_channel routine using values supplied on the command line The numeric status returned from the call is then converted to ts textual representation and displayed The rtr_open_channel routine itself is described in Application Programmer s Reference Manual The prototype of rtr_open_channel is RTR Command Line Interface 6 15 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
21. RTR may in fact remain started Pressing whichever action button is functioning should repair the problem By default RTR will not restart automatically at system reboot time You can change this by setting the Control Panel Services entry for RTR Occasionally an RTR process may continue to run after STOP has been pressed and subsequent START and STOP actions may have no effect or produce an error Under these circumstances it will be necessary to intervene directly as a privileged SYSTEM user to stop RTR This can be done either using RTR commands or with the Task Manager or by rebooting 2 16 Starting and Setting Up RTR Starting and Setting Up RTR 2 11 Running RTR as a Service on Windows NT 2 11 1 Customizing the RTR Windows NT Service 2 11 2 Files 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 RTR commands from UsrStart RTR execute after RTR has been started From the point of view of the Service the RTR home directory is found in the system level environment variable RTR_DIRECTORY or if that is not defined then the directory from which the Service was executed For the RTR Service to use it RTR_DIRECTORY must be defined in the system level environment variables list not the user level environment variables list Also the system must be rebooted after the definition of RTR_DIRECTORY is eith
22. RTR_NO_FLAGS none D RTR_NO_REASON NOREASON D reason_value REASON Teason_value DATA data The CALL RTR_PREPARE_TX command causes a command server to execute the rtr_prepare tx routine using the values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed 6 22 RTR Command Line Interface Qualifiers CALL RTR_PREPARE_TX The CALL RTR_PREPARE_TX can only be used in the context of nested transactions rtr_start_tx was called with the parameter join_txid not equal to NOJ OIN_TXID If this call returns RTR_STS OK then the first prepare phase of the RTR 2PC protocol has been initiated The message type associated with this command is rtr_mt_prepared Similar to the message types rtr_mt_accepted and rtr_mt_rejected the rtr_mt_prepared message type returns data of type rtr_status_data_t in the user buffer In this case the status field of rtr_status data t is always RTR_STS OK and the reason field contains the same reason mask that would be returned in the rtr_ mt_accepted message type for the same TX were the TX to be accepted Only when the rtr_mt_prepared message is delivered can the operator be sure that all participants of the nested TX are ready to commit Alternatively calling rtr_prepare tx can result in the message rtr_mt_rejected being delivered if one of the participating servers votes to reject the nested TX The rtr_mt_prepared
23. 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 e SET ENVIRONMENT Examples RTR gt SET ENVIRONMENT NODE FE2 FE3 1 RTR gt SHOW ENVIRONMENT 2 SRTR S COMARESEN commands sent by default to node FE2 3 SRTR S COMARESEN commands sent by default to node FE3 1 Set the command environment so that subsequent commands will be executed on nodes FE2 and FE3 2 Show which nodes are selected 3 The RTR S COMARESEN message is displayed for each selected node RTR Command Line Interface 6 135 SHOW FACILITY SHOW FACILITY Format Description Parameters Qualifiers Show the names configuration and status of one or more facilities SHOW FACILITY _ facility name Command Qualifiers Defaults BALANCE NOBALANCE CLUSTER NOCLUSTER CONFIGURATION NOCONFIGURATION COUNTER counter name NOCOUNTER FULL NOFULL LINKS NOLINKS STATE NOSTATE OUTPUT file spec OUTPUT stdout NODE node list NODE default node list The SHOW FACILITY command shows the names configuration and status of facilities on the node where the command is executed If no qualifiers are used only the facility name or names and the roles in the facility on the node are displayed facility name Specifies the
24. Specifies the selval parameter in the rtr_request_info call 6 36 RTR Command Line Interface CALL RTR_REQUEST_INFO Examples This command requests the backend transaction Ds for the facility CASHFAC RTR gt 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 following command until the channel is closed RTR gt CALL RTR_RECEIVE_MESSAGE CHANNEL INFOCHAN TIMEOUT RTR Command Line Interface 6 37 CALL RTR_SEND_TO_SERVER CALL RTR_SEND_TO_SERVER Format Parameters Description The CALL RTR_SEND_TO_SERVER command causes a command server to execute the rtr_send_to_server routine and to display the returned status CALL RTR_SEND_TO_SERVER message field1 message field2 message field message field2 Specify the message to be sent as one or more comma separated parameter values You can use the TYPE_OF_DATA and LENGTH_OF_DATA positional qualifiers on each parameter value to specify the data type and length of each field Command Qualifiers Defaults ACCEPT NOACCEPT CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER EXPENDABLE NOEXPENDABLE FORMAT fmt string NOFORMAT LENGTH_OF_FIELD message lengthDepends on data type see description NODE node list NODE default node list OUTPUT file spec OUTPUT stdout READONLY NOREADONLY RETU
25. System management error A user has copied a journal file or a disk containing a journal file RTR can now see extra journal files or copies that do not belong in the set Corrective action either a Check the log for the relevant filenames and delete or move the spurious journal file or files or b Reissue the CREATE JOURNAL SUPERSEDE command in this case any recovery information in the old journal is lost RTR I STACOMSRV Starting command server on node A A Explanation Indicates that a command server is being started on node A RTR E SUPCHAEND Superfluous characters at end of expression A Explanation The expression is invalid because the characters A at the end of the expression could not be interpreted RTR SYSSRVCOM A completed on channel A Explanation Displays the name A of the operation that completed on a channel after issuing a SYS SYNCH command RTR I SYSSRVNOW A posted with no wait on channel A Explanation Displays the name A of the operation that was issued with the NOWAIT qualifier on channel B RTR E TEMPLATE_NOT_FE Template link A valid for front ends only Explanation Template link names are valid for front end roles only It is an error to attempt to associate a template link name with the router or back end roles A template link is link whose name contains one or more wild characters chosen from the set indicates a sequence of wild character
26. Transaction states are maintained in memory and some types of transaction states are also stored in the RTR J ournal for recovery purposes Three different types of states are used internally by RTR to keep track of transaction status e Transaction Runtime State e Transaction J ournal State e Transaction Server State These three state types are very closely related The Transaction Runtime State also known as Transaction State describes how a transaction progresses from a RTR role FE TR BE point of view For example a transaction can enter a stage in which its transaction state from an RTR frontend viewpoint is different than the transaction state of an RTR router The Transaction J ournal State describes how a transaction running on an RTR backend progresses from the RTR journal perspective When a transaction transitions its Transaction J ournal State gets updated and the new state along with other information pertaining to this transaction is stored in the RTR journal The Transaction J ournal State is primarily used by RTR to perform the recovery replay of a transaction after a failure if necessary An RTR frontend and router will not see this state The Transaction Server State describes transaction state transition seen by the server RTR uses this state to determine if a server is available to process a new transaction or if a server has voted on a particular transaction As with the Transaction J ournal State the Transact
27. aborting Displays transaction state for transactions in a facility 5 20 RTR Monitoring FE User RTRCSV_TETRAUL FE User FE User RTRCSV_TETRAUL 5 2 36 Monitor V2CALLS RTR gt Monitor V2CALLS RTR Monitoring 5 2 Standard Monitor Pictures RTR system service calls Node NODEA PID 00000000 Process name ALL Image ALL Accept dcl_tx_prc server 3 dcl_tx_prc req L dcl_tx_prc shut 0 start_tx l start_tx timeout 0 enq_tx L enq_tx broadcast 25187 eng_tx reply 25207 deq_tx 5038 deq_tx reply 12 commit_tx abort_tx 0 vote_tx commit 25187 vote_tx abort 0 vote_tx forget 2 Reject 0 13 09 18 5 MAR 1999 Success Failure Outstng Calls 4 0 0 4 1 0 0 1 50395 0 0 50395 50391 0 2 50393 1 0 0 1 0 0 0 0 25189 0 0 25189 Displays RTR Version 2 calls when running RTR Version 2 or mixture of RTR Version 3 and 2 environment 5 2 37 Monitor XA RTR gt Monitor XA MONITOR XA RTR XA Calls Image ALL open close start end prepare commit rollback recovery Txn starts Node nodea zko Calls Success 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Rate 0 2 4 0 0 PID ALL Process name ALL 11 42 06 Tue 6 Apr 1999 Readonly Failure 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 12 16 18 20 Active 0 Displays XA calls when using XA with RTR RTR Monitoring 5 21 6 RTR Command Line Interface Each RTR API call can be invoked at CLI level using the RTR command utility This is pr
28. 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 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 Specifies the names of the added nodes that act as frontends in 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 name of a node or file spec where file spec specifies a text file containing a frontend list on each line 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 RTR Command Line Interface 6 93 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 routers for this facility Router list is a list of router nodes separated by commas If there is more than one router node
29. then router list must be enclosed in parentheses If NOBALANCE is specified with the EXTEND FACILITY command then the order in which router nodes are specified with the ROUTER qualifier defines the preferred routing order Router node is either the name of a node or file spec File spec specifies a text file containing a router list on each line Related Commands e CREATE FACILITY e DELETE FACILITY e SHOW FACILITY e TRIM FACILITY Examples See Chapter 2 Starting and Setting Up RTR for examples of how to use the EXTEND FACILITY command 6 94 RTR Command Line Interface INITIALIZE JOURNAL INITIALIZE JOURNAL See CREATE J OURNAL INITIALIZE is only retained for compatibility reasons RTR Command Line Interface 6 95 LOG LOG Format Description Qualifiers Specify RTR to write a log message to a log file LOG Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The LOG command specifies a defined log entry to be written to its log messages You can write log messages to the operator console and to a maximum of four log files Log files must be periodically purged to avoid difficulties with full disks Do this by using SET LOG to specify a new file and deleting the old one If neither the OPERATOR nor the FILE qualifier is specified then logging is suppressed C
30. tunnel it is possible to configure RTR to accept a network connection from a particular remote node even if it is connecting via a Internet tunnel using an unknown pseudoadapter address This method allows stricter access control than the anonymous client feature where wild cards may be used when specifying a remote node name For example on the router node behind a firewall the facility definition could include RTR gt create facility router router rtr dec com frontend tunnel client rtr dec com The definition on the frontend could be RTR gt create facility router router rtr dec com frontend client rtr dec com Troubleshooting Tunnel and Wildcard Connections To assist in diagnosing connect acceptance problems use the monitor picture ACCFAIL This picture displays the recent history of those links from which the local node has refused to accept connections It displays the failed link name as provided by the network transport and can assist in rapidly identifying any problems TCP Services File e RTR uses the TCP IP port number 46000 for the network communication daemon rtr rtrd On UNIX platforms you should edit the file etc services to add the line rtracp 46000 tcp 2 14 Starting and Setting Up RTR Starting and Setting Up RTR 2 9 Network Transports 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
31. 00 cece eee eee Parameters for rtr_prepare tX 0 0 00 Parameters for rtr_receive MeSSage 2 2 ee Parameters for rtr roe EK 6 ees Parameters for rtr_reply to client 0 0 ce eee ee Generated Format StringS 000000 ee Parameters for rtr_request_infOo 0 000 cece es Parameters for rtr_send_to_server 0 0 eee eee eee Generated Format StringS 000000 ee Parameters for rtr_start_tx ooooooocconnonrnnranomoos Platform Specific Information 0 00 cee ees Key NAMES ek fits S e e ace ha eh ele HG ae ae tele Wad a alee cla ale A Valid Transaction State Changes 0 000 K y RAMGe States ss a ina a iene i n ed BG toe e Gee ate Need ww ca enc Router Partition States lt s scime aia ade im apa adi es Key range States s s s i aiiai ai es Server Fla vaso via das bee ee ates a Ba ed E i Transaction Invocation Typ S 1 0 0 0 eee Key Range States seos es Information Classes 0 0 Substitution symbols o ooooooooo rm aner ir EpR ERAEN 2 2 2 6 A 3 B 4 B 7 B 8 B 9 6 10 6 12 6 13 6 16 6 22 6 25 6 28 6 32 6 33 6 35 6 39 6 40 6 42 6 52 6 57 6 127 6 152 6 153 6 165 6 166 6 168 6 169 A 3 A 3 Arithmetic Operators in Display Commands Preface Purpose of this Manual This manual describes how to configure manage and monitor the operation of Reliable Transaction Router RTR using the RTR Command Line Interface CLI Intended Audie
32. 2 0 2 0 LINK DATA RATE WAITS PENDING REQS SENT CACHE IN USE NODEA gt NODEA 0 0 0 1 NODEA 0 NODEA gt NODEB 0 0 0 0 NODEB 51456 NODEB gt NODEB 2065 307 0 968 NODEB gt NODEA 2065 70 0 999 Displays the flow control internals 5 2 12 Monitor Group rtr monitor group Concurrency Measures Tue Apr 6 1999 10 04 26 NODE NODEA averages txn server transactions srv txn txn krid state ent cnt act vreq vote ack csn act sec csn 16777216 shd_rec_fail 0 1 0 0 0 0 0 0 0 0 0 0 0 16777217 shd_rec_fail 0 1 0 0 0 0 0 0 0 0 0 0 0 Table 5 2 MONITOR GROUP Fields Field Meaning krid Key range partition identifier state Partition state txn cnt Number of transactions executed for this partition srv cnt Number of servers active for this partition srv act Number servers that are currently busy processing txns for this sample The following fields track the progress of a transaction through the states vote requested voted acknowledged vreq Number of transactions that are waiting for the server to vote vote Number of transactions that have been voted on by the server but not committed by RTR ack Number of transactions that have been committed but have not been acknowledged by the server Acknowledgment occurs on a subsequent rtr_receive_message call by the server processing this transaction to get a message for a new transaction csn Number of transactions which have been grouped under the same co
33. 20417274 server 0 No server available to handle 0 Client aborted tx Displays the last rtr_mt_rejected message received by each running process Table 5 5 MONITOR REJECTS Fields Field Meaning Time Time of day that the rtr_mt_rejected message was received Pid The process id that received the message Chan The type of channel client or server that received the message Reason The reason field returned in the rtr_status_data_t buffer Status Text The textual status that describes the reject reason 5 14 RTR Monitoring 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 Mon Mar 15 18 06 41 server 0 Normal successful completion Mon Mar 15 18 06 41 client 0 Server aborted tx number of reject msgs 3 number of accept msgs 0 rejected total txns 100 Displays the last ten rtr_mt_re jected messages received by the selected process This picture should always be invoked with the ID qualifier The transaction identifier associated with the rejected transaction can be displayed with the SHOW PROCESS lt id gt COUNTER api_reject command Table 5 6 MONITOR REJHIST Fields Field Meaning Time Time of day that the rtr_mt_rejected message was generated Chan The type of channel client or server that received the message Reason T
34. 23643 0 0 0 0 0 BE1 gt BEL 355 0 0 28121 0 0 0 0 0 BE1 gt FE2 284 0 0 13014 1 0 0 0 0 BE1 gt TR2 515 0 0 27502 0 2 2 0 0 BE1 gt TR1 328 0 0 25698 0 1 1 0 0 BE1 gt FEL 335 0 0 17022 0 2 2 0 0 Displays in real time any network links that are currently stalling that is T O 8S SS ESOO SS ASEO Ss SS Ss SS ES 24 pe NPRDNDOOOOPOODNOLDO O gt Stall waiting to transmit outbound traffic and provides a history of the stalls that the various links have encountered during their lifetime The display shows The total number of network QIOs issued Rate of network QIOs per second Total number of bytes sent Number of DE Cnet link losses Total waited seconds for QIO completions Number of 1 to 2 second stalls Number of 3 to 9 second stalls Number of 10 to 29 second stalls Number of stalls longer than 30 seconds Total number of stalled QI Os Current number of incomplete network writes 5 18 RTR Monitoring 5 2 32 Monitor System RTR Monitoring 5 2 Standard Monitor Pictures System Status at 10 27 51 Fri Apr 9 1999 node NODEA Resource OK Warning Facility QUORUM states x JOURNAL free space Xx Link CONNECTS Note Additional detail NN x about a resource can be obtained by monitoring Link traffic STALLS X the subsystem specified in capital letters FLOW control credits x PARTITION sta CALL Msg outs Transaction Q Transaction
35. 5 2 4 Monitor APP2ACP RTR Application to ACP Messages Node NodeA PID ALL Process name ALL Image ALL 14 21 19 Mon Jan 25 1999 messages client server other Bytes Bytes Bytes open_channel 0 0 0 0 0 0 close_channel 0 0 0 0 0 0 accept_tx 0 0 0 0 reject_tx 0 0 0 0 broadcast_event 0 0 start_tx 0 0 send_to_server 0 0 reply_to_client 0 0 request_info 0 0 set_info 0 0 Displays counts of messages and number of bytes from the application to RTRACP as viewed from a specific node Includes open_channel close channel accept_tx accept transaction reject tx reject transaction broadcast_event start_tx send_to server reply to client request_info and set_info The default is to display counts for all PIDs and processes for client server and other roles 5 2 5 Monitor Broadcast BROADCAST RECEPTION BY PROCESS 15 20 27 6 APR 1999 Node ID Process Received Queued Lost Rate of delivery Total 2750 5 17 850 0 NODEA 20400249 RTRACP 0 0 0 NODEA 2040024D BATCH_2993 2750 5 17 850 0 NODEA 2040024B BATCH_2991 0 0 0 NODEA 2040024C BATCH_2992 0 0 0 Displays information about the RTR user events process Fields displayed included number of user events enqueued for the application number of user events received by the application and number of user events discarded by RTR 5 6 RTR Monitoring 5 2 6 Monitor Calls RTR api calls Node nodea zuo dec com Image ALL CALLS open_channel close_channel start_tx send_t
36. A Explanation The process with PID A does not exist or is not using RTR Like NOSUCHPRC but used where the PID is only available as a string RTR E NOSUCHPRT No partition matched A Explanation The requested partition A does not exist RTR E NOTCP TCP specified for A but transport protocol unavailable or disabled Explanation TCP was specified as required through use of a hostname tcp or a substitute but no hostname entry can be found Add an entry for the indicated node to your etc hosts file or to you name server RTR E NOTHLIST Nothing to LIST Explanation Nothing to list RTR E NOTHTODIS There is nothing to display Explanation Indicates that no items had been defined with the DISPLAY command when a MONITOR or SCROLL command was issued RTR W NOTNEG Qualifier or keyword not negatable remove NO or omit n A Explanation The word NO preceded a qualifier or keyword but the qualifier or keyword cannot be specified as a negative RTR E NOTNESTEDTX TX in progress is not nested Explanation A call to rtr_prepare tx was called on a channel with an active TX that is not a nested TX To start a nested TX you must start the TX by calling rtr_start_tx with a valid jointxid parameter RTR E NOTSAMTYP All counters must have same type A Explanation Counter A is not the same type as the other counters in the expression All counters in an expression must be either process count
37. FTM channel may be relaxed in a future release When a nested transaction is started join_txid not equal to NOJ OIN_ TXID then that transaction is given a new RTR TXID which the operator can retrieve by calling rtr_get_tid The foreign TXID passed in join_txid is used only to identify the transaction for the foreign TM for example when the foreign TM goes through recovery and requests RTR to return all transactions in prepared state The channel on which a nested transaction is started must be opened as a client channel which implies the node is defined with the FE role However a journal is required on that node If there are no other facilities on that node with the BE role defined then RTR will behave as an honorary BE causing the journal to be opened locally CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use 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 latest SET ENVIRONMENT command If no SET ENVIRONMENT command has been entered then the command is execut
38. Four typical situations are listed below where transaction state changes by the system administrator are allowed 1 State SENDING changed to state ABORT The application server after receiving a rtr_mt_msg_1 message and before calling rtr_accept_tx for a particular transaction experiences a hung situation and cannot proceed Aborting this transaction with the SET TRANSACTION command is the only way to correct it Internally RTRACP will send the ABORT message to the router as well as the all participating servers to abort this transaction in a consistent matter 2 State VOTED changed to state COMMIT This is the case where a application server running on the backend may have been separated from the rest of participating servers after casting the VOTE for the transaction The other servers may have already committed the transaction but not forgotten it As far as the application is concerned this global transaction is committed and all changes have been committed to the underlying database on the different sites However the local transaction record is still in VOTED state in the RTR journal You can use the command to manually commit the local transaction branch Note that this command is only applicable if there is no coordinating router running e servers are separated from the rest of the RTR network If this is not the case RTR rejects the command 3 State VOTED changed to state ABORT In a simila
39. Image ALL 14 15 46 Mon Jan 25 1999 messages client server other pend Bytes Bytes Bytes opened 0 0 0 0 0 0 0 closed 0 0 0 0 0 0 0 msgl 0 0 0 msgl_uncertain 0 0 0 msgn 0 0 0 repl_2_client 0 0 0 rettosend 0 0 0 accepted 0 0 0 0 0 rejected 0 0 0 0 0 user_event 0 0 0 0 0 rtr_event 0 0 0 0 0 mt_prepare 0 0 0 other request_info 0 0 0 set_info 0 0 0 calls active fail timeout receive_message 0 0 0 0 user_wakeup 0 0 Displays counts of messages and number of bytes from RTRACP to the application as viewed from a specific node Includes openend closed msgl msg1_uncertain msgn repl_2 client reply to client rettosend return to sender accepted rejected user_event rtr_event mt_prepare request_info and set_info messages as appropriate For receive_message and user_wakeup displays calls active fail and timeout counts The default is to display information on all PIDs process names and images To display information on one process only user the qualifer ADENTIFICATION process id RTR Monitoring 5 5 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 11141 11141 rtr 5 5 0 Displays a list of RTR processes and for each process the number of transactions they have started the number of transactions they have completed and the number of transactions still active
40. KEY2 up to KEY 8 The syntax of the KEYn qualifier is KEYn type_of_key signed unsigned string length_of_key nnnn offset_of_key nnnn low_bound low bound string high_bound high_bound_string type_of_key Specifies the field type of the key The key type must be one of unsigned signed or string The default is unsigned 6 18 RTR Command Line Interface 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 offset_of_key nnnn 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 low_bound Specifies the lower bound of the key range that servers in the partition will service The interpretation of low bound depends on the key type if the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for low bound is the smallest possible value that can fit in the specified key type If the key bound value length is less than the key length given in length_of_key the key bound will automatically be null padded to the required length high_bound Specifies the upper bound of the key range that servers in the partition will service The interpretation of high boun
41. LL command can be used to view a different portion of the list of Scroll the picture up 10 lines Note that SCROLL automatically redisplays the current picture Restore the original picture position RTR Command Line Interface 6 107 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 NODEs this_node Description The SET ENVIRONMENT command causes subsequent RTR commands to be executed on the specified nodes Entering SET ENVIRONMENT without any qualifiers causes subsequent RTR commands to be executed on the local node only Qualifiers CLUSTER Currently only fully supported in an OpenVMS environment in which case it specifies that subsequent RTR commands are executed on all nodes in the VMScluster For other implementations using CLUSTER is interpreted as NODE this_ node NODE node list Specifies that subsequent RTR commands are executed on all nodes specified in node list If node list is omitted or both the NODE and CLUSTER qualifiers are omitted then subsequent commands are executed on only the local node Related Commands e SHOW ENVIRONMENT Examples See Section 1 5 Remote Commands for examples of how to use the SET ENVIRONMENT command 6 108 RTR Command Line Interface SET FACILITY SET FACILITY Format Desc
42. R Broadcast EVE For example to get more oir rra x information on links type MONITOR CONNECTS GANG ia x To modify threshold values UBUES cir x edit the file SYSTEM MON BUBGT dada x TUS Sins x Displays the state of critical resources within the RTR environment If a resource has exceeded a predefined threshold a warning indicator is displayed The default thresholds are as follows Quorum J ournal Links Stalls Flow Partition Calls Queues Rejects Events Warn if any roles are inquorate Warn if journal free space is less than 30 of total Warn if any link is disconnected Warn if 10 second stalls are greater than 1 of all messages sent Warn if the wait is more than one second for 10 of the total credit requests Warn if any of the partitions are not in one of the following states Standby Active Pri_act or Sec_act Warn if any messages have been pending for more than 30 seconds Warn if the transaction queue cannot be emptied within 10 seconds Warn if the number of rejects non user is greater than 5 of the total transactions processed or a reject non user has occurred within the last 30 minutes Warn if the number of discards is greater than 5 of the total events sent Threshold values can be customized by editing the file SYSTEM MON RTR Monitoring 5 19 RTR Monitoring 5 2 Standard Monitor Pictures 5 2 33 Monitor TPS TRANSACTION COMMITS BY PROCESS 14 37 23 7 JAN 1999
43. RTR Command Line Interface 6 121 SET PARTITION SET PARTITION Format Description Parameters Qualifiers Sets various partition related options 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 RESTART_RECOVERY RESUME SHADOW NOSHADOW SUSPEND TIMEOUT nn The SET PARTITION command sets the characteristics of a named partition Only backend partitions may be manipulated with this command the command must be entered on the backend where the partition is located Use SET PARTITION any time after the partition has been created either explicitly by CREATE PARTITION or implicitly by starting a server Note that the command only takes effect after the first server joins a partition Any errors encountered at that time will appear as RTR log file entries Using SET PARTITION to change the state of the system results in a log file entry partition name The name of the partition being manipulated This may be specified as partition_name if the partition name is unique on the node or as facility_name partition_name FACILITY facility_name D Determines the facility that the partition command will act on This is required FAILOVER_POLICY SHADOW FAILOVER_POLICY STAND_BY D Determines the action to take when the primary partiti
44. RTR Command Line Interface 6 53 CREATE PARTITION CREATE PARTITION Format Description Parameters Qualifiers Creates an RTR partition 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 SHADOW NOSHADOW KEY1 keysegdesc KEYn keysegdesc The CREATE PARTITION command defines an RTR partition The partition characteristics that may be defined include key range or ranges and whether attached server processes can be shadows or standbys The command must be issued before any server application programs using the partition are started partition_name Specifies the name of the partition to be created Partition names must be unique within a facility Any application program which uses this partition must specify the same name when it calls rtr_open_channel Partition names can contain up to sixty three 63 characters Letters numbers and underline characters are all valid but the first character of a partition name must be a letter If a partition name already exists in the facility the command fails There is no default value for partition_name 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 ex
45. SHOW LINK COUNTER ndb Iw _trips command Dividing the latter by the former yields the average round trip time in milliseconds Note The inactivity timeout is used for all RTR links but the effect of a timeout and failover depends on what connections the link is supporting In brief a link between a router and a backend timing out causes a router or backend failover and quorum re negotiations A frontend will search for another router 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used SUSPECT NOSUSPECT Obsolete Available for compatibility reasons only use AUTOISOLATE instead Related Commands e SET NODE AUTOISOLATE e SHOW LINK STATUS 6 114 RTR Command Line Interface SET LINK Examples RTR gt SET LINK JOEY ENABLE This command re allows connections from node J OEY RTR gt SET LINK JOEY AUTOISOLATE This command sets the autoisolate attribute on the link to node J OEY RTR Command Line Interface 6 115 SET LOG SET LOG Format Description Qualifiers Specify where RTR writes its log messages SET L
46. Specifies the screen row where the item is displayed top row is 1 By default items are displayed on the next free row after the item defined by the previous DISPLAY command RTR Command Line Interface 6 75 DISPLAY NUMERIC Related Commands e MONITOR e SHOW DISPLAY e CLEAR e DISPLAY BAR e DISPLAY SYMBOLIC e 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 Format Description Parameters Qualifiers Display a string in a monitor picture DISPLAY STRING expression Command Qualifiers AVERAGE keyword BELL Boolean expression BLANK Boolean expression BLINK Boolean expression BOLD Boolean expression JUSTIFY keyword LABEL text REVERSE Boolean expression ROWS nr rows SELECT Boolean expression SEPARATE keyword TOTALIZE keyword UNDERLINE Boolean expression WIDTH field width X column Y row Defaults none NOBELL NOBLANK NOBLINK BOLD JUSTIFY LEFT NOLABEL NOREVERSE ROWS 1 NOSELECT none none NOUNDERLINE WIDTH 0 Column of previous item Next free row The DISPLAY STRING command displays the specified expression as an alphanumeric in a monitor picture It can be used within a monitor file or issued at the RTR prompt when interactively defining a monitor picture for use in a subsequent MONITOR command Note that the int
47. The SET MODE command specifies whether RTR runs in group mode or nogroup mode Nogroup mode is the same as system mode Production systems use RTR in the default mode i e nogroup or system mode whereby all users running in this mode use one common invocation of RTR Developers typically wish to have their own invocation of RTR to avoid their RTR actions affecting other developers or the production system This mode is termed group mode Group mode allows development or testing of applications by several groups of people on the same system without interference 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 command is executed only on the node where the command was issued 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 GROUP user id NOGROUP GROUP specifies that RTR be set to GROUP mode for the user who issues the command The groupname defaults to the first eight characters of your current user id You may also change to another group by entering a user or group ID Note that group names are used for naming RTR journal files do not use a group name con
48. and underlined if its greater than 1952 4 The value of RTR_SOME_DATA_ITEM is displayed in text form if it is less than six otherwise it is displayed as a numeric A 4 Creating Monitor Pictures 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 control the way the items are aggregated _MIN select the data item instance with the lowest value _MAX select the data item instance with the higheest value By default data items are totaled unless the AVERAGE qualifier is specified The following example from SYSTEM MON shows the use of the_MIN keyword Warn if any messages have been pending for more than 30 seconds DISPLAY TEXT X 32 Y 17 wy BOLD SELECT rtrirtr_current_time _MIN prc rtr_mt_received_time lt 30 DISPLAY TEXT X 40 Y 17 ny BOLD BLINK SELECT rtr rtr current_time _MIN prc rtr_mt_received_time gt 30 Some output has been omitted for clarity Creating Monitor Pictures A 5 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 This appendix is an introduction to RTR shadowing A server for a database partition is said to be
49. argument of rtr_set_info as follows rtr_qualifier_value_t set_qualifiers 2 rtr_uns_32_t newLimit set_qualifiers set_qualifiers set_qualifiers set_qualifiers qv_qualifier rtr_partition_rcvy_retry_count qv_value amp newLimit qv_qualifier rtr_qualifiers_end 0 0 iL 1 qv_value NULL Partition Management 3 9 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 For more information see the SHOW PARTITION command in Chapter 6 3 7 0 1 Command Line Example RTR gt show partition backend Backend partitions on node BE1 in group Facilityl at Wed Feb 24 15 07 50 1999 Partition name Facility State RTRSDEFAULT_PARTITION_16777217 RTRSDEFAULT_FACILITY active RTRSDEFAULT_PARTITION_16777218 RTRSDEFAULT_FACILITY active 3 10 Partition Management 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 state is the property that characterizes a transaction s current condition Whenever a transaction progresses from one stage to another the transaction state is updated to reflect a transaction transition
50. automatic network link reconnection and recovery Node autoisolation allows a node the isolator to disconnect a congested or unresponsive remote node the isolatee in such a way that when the congested node attempts to reconnect it receives an instruction to close all its network links and cease connection attempts A node in this state is termed isolated Some applications require that a node which is suspected of causing congestion that is not processing network data sufficiently quickly is isolated from the rest of the network so as to cause minimum disruption The node autoisolation feature meets this requirement Remote node autoisolation may be enabled at the isolator where it applies to all links using SET NODE AUTOISOLATE or for specific links only with the SET LINK AUTOISOLATE command An isolated node isolatee remains isolated until you carry out both of the following actions e Enable the link to the isolated node on all nodes that have isolated it that is set link isolated node enabl e Exit the isolated state on the isolated node that is set node noisolate Autoisolation is disabled at the isolator using the NOAUTOISOLATE qualifier 6 120 RTR Command Line Interface 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 comm
51. be executed on the local node only 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used 6 26 RTR Command Line Interface Examples 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 The following example shows two CALL RTR_RECEIVE_MESSAGE commands on RTR DEFAULT CHANNEL RTR gt CALL RTR_RECEIVE_MESSAGE TIMEOUT_MS SRTR S OK normal successful completion channel name RTRSDEFAULT_CHANNEL msgsb msgtype rtr_mt_rtr_event msglen 0 evtnum Lis RTR_EVTNUM_SRRECOVERCMPL RTR gt CALL RTR_RECEIVE_MESSAGE TIMEOUT_MS SRTR S OK normal successful completion channel name RTRSDEFAULT_CHANNEL msgsb msgtype rtr_mt_msgl msglen 55 usrhdl 0 tid lfe5c 495a4 0 0 1bf80 84 36 message offset bytes text 000000 54 68 69 73 20 69 73 20 74 68 65 20 6D 65 73 73 This is the mess 000010 61 67 65 20 74 65 78 74 2E 20 53 6F 6D 65 20 64 age text Some d 000020 69 67 69 74 73 20 68 65 72 65 3A 20 31 32 3
52. catching up RTR gt SHOW TRANSACTION BACKEND FULL Backend transactions Tid Facility RTIRSDEFAULT_FACILITY Frontend RARA State RECEIVING Router bronze Active Key Ranges 1 Total Tx Engs il Server Pid 20828 Journal Node iron zuo dec com First Enq 1 Nr Replies 0 6 170 RTR Command Line Interface e100b810 0 0 0 0 a85 83290001 FE User anders 7780 Start Time Tue Feb 21 15 53 53 1995 Invocation ORIGINAL Recovering Key Ranges 0 Key Range Id 16973824 Server State RECEIVING Journal State SENDING Nr Engs SPAWN SPAWN Format Description Parameters Qualifiers Allows you to execute operating system commands without leaving the RTR utility SPAWN operating system command Command Qualifiers Defaults INPUT file spec NOINPUT OUTPUT file spec OUTPUT stdout WAIT WAIT The SPAWN command allows you to execute operating system commands without leaving the RTR session If you specify an operating system command as the parameter to SPAWN the command is executed in the context of a spawned subprocess For example the command SPAWN mail invokes the mail utility when you exit from mail you return to your RTR session If you do not specify a parameter the SPAWN command enters the operating system command level in the spawned subprocess You can then enter commands you can return to your RTR session by exiting the subprocess operating system command Can be any operating system comm
53. containing the message data for the pmsg parameter the message length for the msglen parameter and a record type description for the msgfmt parameter ACCEPT NOACCEPT The ACCEPT qualifier sets the flag RTR_F_REP_ACCEPT in the call to send_to_server It means the transaction is accepted by this client CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use 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 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 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 EXPENDABLE NOEXPENDABLE The EXPENDABLE qualifier sets the flag RTR_F_SEN EXPENDABLE in the call rtr_send_to_server FORMAT fmt string NOFORMAT D Specifies that a format string should be sent with this message RTR C
54. detailed information on these commands see Chapter 6 4 1 1 Exception Transactions Transactions can cause servers to fail after the VOTE phase and impact availability of a server in a recovery These EXCEPTION transactions can now be flagged by RTR as fail transactions after the user sets the attempts at recovery from a failure with the SET PARTITION RECOVERY_RETRY_COUNT nn command They then can be identified and removed from the RTR journal and from the system to allow recovery to continue with the SET TRANSACTION command In the case of a flagged EXCEPTION transaction the system administrator can take action by changing the state of the EXCEPTION transaction to that of DONE with the SET TRANSACTION STATE EXCEPTION NEW_STATE DONE to allow the recovery to continue 4 2 Transaction Management 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 produces an error message of SRTR E INVSTATCHANGE Invalid to change from current state to the specified state The Table 6 19 table identifies the valid state changes Table 4 19 Valid Transaction State Transitions NEW STATE Current State COMMIT ABORT EXCEPTION DONE SENDING YES VOTED YES YES COMMIT YES YES EXCEPTION YES YES PRI_DONE YES
55. do not support clustering use of the CLUSTER qualifier will cause the relevant command to be executed on the local node only 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 RTR Command Line Interface 6 177 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 e START RTR Examples See Chapter 2 Starting and Setting Up RTR for examples of how to use the STOP RTR command 6 178 RTR Command Line Interface TRIM FACILITY TRIM FACILITY Format Description Removes nodes or roles or both from an existing facility definition 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 file spec OUTPUT stdout ROUTER router list NOROUTER The TRIM FACILITY command removes nodes or roles or both from an RTR facility definition A node can be removed from a facility or a role can be removed from a node For example a node having both router and frontend roles can be trimmed to have only a router role A TRIM FACILITY c
56. event name and partition ID can be displayed The State field of the SHOW SERVER command can display the following values Table 6 22 Key range States State Meaning wt_tr_ok Server is waiting for routers to accept it wt_quorum Server is waiting for backend to be quorate Icl_rec Local recovery Icl_rec fail Primary server waiting for access to a restart journal Icl_rec_icpl Getting next journal to recover from Icl_rec_cpl Processed all journals for local recovery shd_rec Shadow recovery shd_rec fail Shadow server waiting for access to a restart journal shd_rec_icpl Shadow getting next journal to recover from shd_rec_cpl Processed all journals for shadow recovery catchup Secondary is catching up with primary standby Server is declared as standby 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 The Flags field of the SHOW SERVER command can display the following values RTR Command Line Interface 6 165 SHOW SERVER Qualifiers 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 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 com
57. expression Specifies the quantity to be displayed Expression can either be the name of a single data item or an expression combining several items using simple arithmetic operations and constants In the latter case EXPRESSION must be in quotes RTR Command Line Interface 6 67 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 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_TRANSACTION Router transaction data items BELL Boolean expression NOBELL D Sends a bell character to the terminal if Boolean expression evaluates to True non zero BLINK Boolean expression NOBLINK D Specifies that the displayed value blinks if Boolean expression evaluates to True non zero BLANK Boolean expression NOBLANK D Specifies that the displayed value is replaced by blanks if Boolean expression evaluates to True non zero BOLD Boolean expression NOBOLD D Specifies that the item is displayed in high intensity if Boolean expression evaluates to True non zero CHARACTER char NOC
58. facility name for which information should be displayed By default information is displayed for all Facilities FULL NOFULL D Produces a detailed listing of transaction information 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used ROUTER NOROUTER D Specifies that information should be listed for transactions in a router node If none of BACKEND FRONTEND or ROUTER are specified then information for all of them are displayed If either BACKEND or FRONTEND are specified then the default NOROUTER inhibits display of router transaction information The Key Range State field for SHOW TRANSACTION ROUTER FULL shows the following states Table 6 25 Key Range States State Meaning locl_rec Local recovery in progress shad_rec Shadow recovery in progress continued on next page RTR Command Line Interface 6 169 SHOW TRANSACTION Examples 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
59. 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used TYPE_OF_DATA STRING SIGNED UNSIGNED TYPE_OF_DATA STRING D Enter the data type of the message field that you want to define The default is the string type This is a positional qualifier it must immediately follow the message field that it refers to Related commands CALL ve R_SEND_TO_SERVER e CALL mw R_RECEIVE_MESSAGE RTR Command Line Interface 6 33 CALL RTR_REPLY_TO_CLIENT Examples The following example replies a message to the client RTR gt CALL RTR_REPLY_TO_CLIENT Getting that info for you SRTR S OK Normal successful completion The following example shows a message of type unsigned and entered as a hexadecimal number RTR gt CALL RTR_REPLY_TO_CLIENT 0xFA9BCO TYPE_OF_DATA UNSIGNED SRTR S OK Normal successful completion 6 34 RTR Command Line Interface 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 Format CALL RTR REQUEST_INFO Command Qualifiers CHANNEL_NAME channel name CLUSTER GETITM
60. 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 BALANCE NOBALANCE D Specifies that load balancing is enabled for frontend router connections across the facility In order for load balancing to function correctly BALANCE must be defined on all routers as well as on those frontends requiring load balancing It has no significance on a backend node and will be ignored if specified The default behavior NOBALANCE is for a frontend to connect to the preferred Router Preferred routers are defined by the order specified in the ROUTER qualifier of the EXTEND FACILITY command Note that this preference is subject to the router being available and quorate For more details on frontend load balancing see Section 2 6 Router Load Balancing CALL_OUT role list NOCALL_OUT D Specifies which node types are to have call out servers running on them Role list is a comma separated list of roles If role list contains more than one role then it must be enclosed in parentheses Role is one of the keywords ROUTER or BACKEND The default for role list is ROUTER BACKEND 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
61. 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 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 EVENT_NUMBER user event number The user event number associated with this broadcast in the range of RTR_EVTNUM_USERBASE to RTR_EVTNUM_USERMAX i e 0 to 250 FORMAT fmt string NOFORMAT D Specifies that a format string should be sent with this message If FORMAT 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 FORMAT without fmt string RTR Command Line Interface 6 7 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 UB SL UNSIGNED 2 AUW SL UNSIGNED 4 UL SL Refer to Application Programmer s Reference Manual section Defining a Message Format Description for information on constructi
62. item name INFCLA infoclass NODE node list OUTPUT file spec SELITM item name SELVAL item value Description Defaults CHANNEL_NAME RTR DEFAULT_CHANNEL NOCLUSTER none none NODE default node list OUTPUT stdout none none The CALL RTR_REQUEST_INFO command causes a command server to call to the rtr_request_info routine using values supplied on the command line The rtr_request_info routine itself is described in Application Programmer s Reference M anual The prototype of rtr_request_info is rtr_status_t rtr_request_info rtr_channel_t pchannel rtr_req_flag_t flags rtr_infoclass_t infcla rtr_itemcode_t selitm rtr_selval_t selval rtr_itemcode_t getitms i Table 6 13 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 13 Parameters for rtr_request_info C Parameter Name Parameter Value Command Line Specification pchannel CHANNEL_NAME name flags RTR_NO_FLAGS none D infcla RTR_INFCLA_BACKEND_TX ANFCLA BTX selitm fdb_f name SELITM fdb_f_ name selval CASHFACIL SELVAL CASHFACIL getitms fe_node id GETITMS fe_node_id RTR Command Line Interface 6 35 CALL RTR_REQUEST_INFO Qualifiers CHANNEL_NAMEschannel_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 wi
63. links from which connections appear to originate with an source address other than that by which the local node is registered locally for example the connection may appear to originate from an pseudo adapter address assigned by the tunnel server The CONNALIAS message registers the acceptance of such a connection and lists the names of the local and connecting IP addresses RTR S CURRTR Node A now a router for facility A Explanation A new current router A has been found for facility B RTR E CURRTRLOSS Current router lost for facility A Explanation The router handling facility A for this frontend node has failed or A has been deleted on the router No user intervention is expected an attempt is being made to reconnect to an alternate router if one is available RTR DTXRECOV Commencing DTX journal search for transactions needing recovery log_id 08X 04X 04X 02X 02X 02X Y 02X 02X 02X 02X 02X Explanation DTX J ournal search is starting This message appears when RTR is started RTR 1 DTXRECOVDONE DTX journal search completed A transactions found Explanation DTX J ournal search has completed This message appears when RTR is started RTR 1 DUMPOBJ ECT A n A Explanation Object dumped to log RTR E ENQDEAREQ Server rtr_reply_to client to a client that has since exited Explanation Indicates that a call to rtr_reply_to client was made for a client that has since exited RTR 1 FACE
64. mode The command will fail if it is entered on either an active primary or secondary If entered on a standby of either the primary or secondary the command is accepted but fails in the RTR router this is recorded with a log file entry at the router RTR Command Line Interface 6 123 SET PARTITION 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 If shadowing is already in the desired mode the command has no effect SUSPEND Stops presenting new transactions on the specified partition until a RESUME is issued Use SUSPEND to temporarily halt the presentation of new transactions to servers on the backend where the command is entered The command completes when the processing of all currently active transactions is complete The optional TIMEOUT qualifier may be used to limit the time that the command waits for completion If the command times out presentation of new transactions is suspended but there still exist transactions for which servers have yet to complete processing The operator must decide to either reenter the command and wait a further period of time or resume the partition Note that use of this command does not affect any transaction timeout value specified by RTR clients so such transactions may encounter a timeo
65. name of the facility you want to display Facility name may contain wild cards and in which case all matching facilities will be displayed If facility name is omitted all configured facilities are displayed BALANCE NOBALANCE D Specifies that the load balancing status of the facility is also displayed See Section 2 6 Router Load Balancing for details of load balancing 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 command is executed only on the node where the command was issued 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 6 136 RTR Command Line Interface SHOW FACILITY CONFIGURATION NOCONFIGURATION D Specifies that the facility configuration is to be displayed The configuration information 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 been configured Whether load balancing has been configured Whether quorum check is being handled on this node Whether reply consistency check for replayed messages is enabled COUNTER counter na
66. nodes specified in node list If node list is omitted then the command is executed only on the node where the command was issued 6 116 RTR Command Line Interface 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 Examples e SHOW LOG RTR gt SET LOG FILE RTRLOG LOG OPERATOR This command tells RTR to write log messages to the file RTRLOG LOG and to the operator log RTR gt SET LOG NOFILE NOOPERATOR This command suppresses all RTR log messages RTR gt SET LOG FILE usr users rtruser daily_logfile This command tells RTR to write log messages to the file usr users rtruser daily_logfile log RTR gt SET LOG FILE logfilel log logfile2 log This command tells RTR to write log messages to logfilel log and logfile2 log RTR gt SET LOG OPERATOR This command tells RTR to write log messages to the system log RTR Command Line Interface 6 117 SET MODE SET MODE Format Description Qualifiers Specify whether RTR should run in a group mode or the nogroup system mode SET MODE Command Qualifiers Defaults CLUSTER NOCLUSTER GROUP user id NOGROUP NODE node list NODE default node list OUTPUT file spec OUTPUT stdout
67. only on the OpenVMS operating system The qualifier has no effect on the executing platform and the specified value will be ignored RTR OPTSUPSED The RTR V2 x option A is obsolete in V3 x Explanation The option is obsolete in this version of RTR RTR E OWNNODMIS Executing node A not specified as frontend backend or router Explanation The node A wherea CREATE FACILITY or EXTEND FACILITY command was executed was not specified as being a frontend router or backend RTR F PARMDEL Invalid parameter delimiter check use of special characters n A Explanation A command contains an invalid character following the specification of a parameter or an invalid character is present in a file specification RTR F PARREQ Missing parameter supply required parameter n A Explanation Missing parameter RTR E PARTNAMELONG Partition name too long Explanation Long partition name argument RTR E PROCIDILL Illegal process ID A Explanation The specified process ID A has an invalid format Process ID s are hexadecimal numbers with up to eight digits RTR Utility Error Messages D 19 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 E PRTBADFPOL Unrecognised partition failover policy code Explanation Status indicating that an in
68. recovery A from A journal A Explanation RTR transaction manager requested recovery from a remote journal but the request could not be delivered to the node hosting the journal In a non clustered standby configuration this indicates that local recovery after a server failure could not be completed No user action required since the transaction manager will attempt to send the recovery query again once it has detected that the remote journal has become available RTR F OUOVERFL RTR journal file overflow transaction recovery information lost Explanation The journal file is so full that some transaction recovery information has had to be discarded One or more of the currently active transactions may be incorrectly recovered if a system failure occurs in the near future E 6 RTR log messages RTR log messages RTR I J OUSEACOM Journal search on facility A completed A recoverable transactions found Explanation J ournal search has completed This message appears when RTR is started The number of transactions needing recovery is indicated by A RTR F OUSEQERR RTR journal record sequence error CREATE J OURNAL SUPERSEDE and submit SPR Explanation An inconsistency has been found in the record sequence within the RTR journal Corrective action 1 Reissue the RTR CREATE J OURNAL SUPERSEDE command 2 Restart RTR 3 Submit an SPR RTR E LINKSHUT No longer accepting connect requests from thi
69. rejects group Shows server and transaction concurrency on a partition basis ipc Shows counts of inter process communication IPC activity in the RTR ACP and active RTR applications ipcrate Displays rate information on IPC messages byte counts and 10 primitive usage continued on next page 5 2 RTR Monitoring RTR Monitoring 5 2 Standard Monitor Pictures Table 5 1 Cont Standard Monitor Pictures Picture name Description jcalls journal link netbytes netstat partit queues quorum rdm recovery rejects rejhist response rfb rolequor routers routing rscbe rtr stalls system tps tpslo Displays counts of successful success failed fail and total journal calls for local and remote journals Displays the current journal usage on a node Local node journal statistics are provided and data for non local journals accessed from the local node Include statistics covering total number of entries and records written the 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 Displays a number of per link data items The LINK 1ink name qualifier can be used if the values for one specific link are to be displayed otherwise the total values for all links are displayed Displays a list of the links to other nodes For each link the total number of bytes received and sent on that li
70. router and backend roles are quorate Quorate means that this node s view of the availability of the other nodes in the configuration matches that of the other backends and routers A facility that is not in the quorate state is effectively unusable The quorum threshold is at the default zero and no minimum broadcast rate has been set 6 138 RTR Command Line Interface SHOW FACILITY 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 The link is also a backend connected to the router and this backend is quorate This backend would also be the backend coordinator if load balancing was enabled 6 The second link shown to node airola shows that it is a frontend and is a frontend to router connection RTR gt SHOW FACILITY BALANCE Facilities Facility RTRSDEFAULT_FACILITY Load Frontends connected 1 Frontends allowed dl Load coordinator yes Quorate routers 1 Total Frontends 1 Current Credit 1 FE gt TR This display shows the load balancing status This node is the current load coordinator RTR Command Line Interface 6 139 SHOW JOURNAL SHOW JOURNAL Format Description Qualifiers Display information about current RTR journal files SHOW JOURNAL Command Qualifiers Defaults CLUSTER NOCLUSTER FILENAMES
71. shadowed when two copies of the same server perform identical actions on identical database copies on separate nodes It is possible to declare servers to be members of a pair of shadow sites for any particular RTR key range Shadowed sites can either be two nodes within a single cluster or can be two separate clusters Note that concurrent servers handle similar transactions that is in the same key range but not the same transactions Standby servers do not handle transactions at all for the given key range and shadow servers handle the same transactions B 1 Primary and Secondary Roles There is a concept of primary and secondary role for the shadow server pair although in most cases this is transparent to the user when the processing is the same on both sites Initial role assignment is arbitrary in that the first server of a shadow pair to start is given the primary role and the second the secondary The assigned roles may change as servers come and go Roles are required since RTR needs to determine the voting order on the primary site before the transaction is presented to the secondary site B 2 Automatic Features Shadow sites each have an identical copy of the customer s database Transactions are sent by RTR to both sites and RTR ensures that they are processed by the servers in equivalent order on each of these sites so that both copies of the customer database remain up to date A transaction is sent to the secondary
72. site only after the primary has accepted it or if the primary fails before being asked to vote RTR suppresses replies and broadcasts issued by the secondary shadow server B 2 1 Shadow Events RTR provides the following shadowing events e RTR_EVTNUM_SRPRIMARY Server is in primary mode e RTR_EVTNUM_SRSTANDBY Server is in standby mode e RTR_EVTNUM_SRSECONDARY Server is in secondary mode e RTR_EVTNUM_SRSHADOWLOST Server has lost its shadow partner Server Shadowing and Recovery B 1 Server Shadowing and Recovery B 2 Automatic Features e RTR_EVTNUM_SRSHADOWGAIN Server has gained its shadow partner e 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 A server receives RTR_EVTNUM_SRPRIMARY under the following circumstances e On initial startup if servers for the key range are not already running on other nodes e f the server had previously been standby and the previous primary has failed e If the server had previously been shadow secondary and the previous primary has failed A server receives RTR_EVTNUM_SRSTANDBY when it starts up and servers already exist for the same key range on another node in the same cluster A server receives RTR_EVTNUM_SRSECONDARY when it starts up and a shadow primary set of servers exist elsewhere A server receives RTR_EVTNUM_SRSHADOWLOST if it
73. size The MAXIMUM_BLOCKS qualifier specifies the maximum size that the journal file can extend to the RTR journaling system will not extend the journal file beyond this size BLOCKS and MAXIMUM_BLOCKS are positional qualifiers so the journal files need not have the same size on each disk The CREATE J OURNAL command checks that a journal does not already exist for the node An error occurs if a journal does exist unless the SUPERSEDE qualifier is specified When the SUPERSEDE qualifier is specified any previously existing journal files are deleted For this reason the CREATE J OURNAL SUPERSEDE command should not be issued on a node being started up after a failure if the transactions interrupted by the failure need to be recovered The CREATE JOURNAL command is normally entered interactively not automatically from a startup command procedure RTR only uses journal files on nodes that are configured to run servers that is on backends and on routers with call out servers disk 1 disk n Specifies a list of disk names where the new journal is to reside If no disks are specified then the issuer s current default disk will be used Spreading the journal over more than one physical disk can improve performance if I O to the journal file becomes a bottleneck RTR Command Line Interface 6 51 CREATE JOURNAL Table 6 17 Platform Specific Information Platform Journal Root Finding Disks Notes UNIX
74. that have a current sequence number of zero or if the backend partition is joining an existing facility and has a sequence number that conflicts with another backend partition on another node Sequence number information can be obtained from the SHOW PARTITION command In the output of this command the sequence number is indicated by the relative priority The following example shows a sample of the SHOW PARTITION command from a router partition This example shows that the backend partition called Bronze has a sequence number of 1 and backend partition called Gold has a sequence number of 2 Router partitions on node SILVER in group test at Mon Mar 22 14 51 16 1999 State ACTIVE Low bound 0 High bound 4294967295 Failover policy fail_to_standby Backends bronze gold States pri_act sec_act Relative priorities Le Primary main bronze Shadow main gold 2 18 Starting and Setting Up RTR 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 pl Facility RTRSDEFAULT_FACILITY State pri_act Low bound 0 High bound 4294967295 Active servers 0 Free servers 1 Transaction presentation active Last Revy BE gold Active transaction count 0 Transactions recovered 0 Failover policy fail_to_standby Key range ID 16777217 Master router silver Relat
75. 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 command is executed only on the node where the command was issued 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 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 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 e SET NODE ISOLATE e SET LINK 6 150 RTR Command Line Interface SHOW NODE Examples RTR gt 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 Autoisolation state enabled or disabled 4 Inactivity timer value in seconds RTR Command Line Interface 6 151 SHOW PARTITION SHOW PARTITION Format Description 6 152 RTR Command Line Interface Display server dat
76. the adjustable environmental timer parameters RTR_TIMEOUT_CONNECT default of 60 seconds and RTR_TIMEOUT_CONNECT_RELAX default of 90 seconds on a network link or remote node When there is a failure RTR detects it within the timer parameters stipulated and disconnects and retries the link according to the router preferences for a frontend If a router fails to respond to the reconnect tries there will bea time lapse of RTR_TIMEOUT_CONNECT plus RTR_TIMEOUT_CONNECT_RELAX for the link failover to occur RTR Command Line Interface 6 113 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 ANACTIVITY_TIMEOUT You can check the current value of the link inactivity timeout with the command SHOW LINK linkname COUNTER ndb_lw_inact You should not specify a value of less than five times the time required for a round trip over the link If you don t know this value RTR can measure it for you Make sure that there is no transactional traffic over the link and monitor the link with the MONITOR LINK command between the two nodes whose round trip time you want to measure After a few minutes look at the link counters ndb_lw_trips and ndb_lw_trips_ms using the
77. the file file spec If OUTPUT or file spec is omitted then the standard or default output is used Related Commands e CREATE JOURNAL e INITIALIZE JOURNAL e SHOW JOURNAL OpenVMS Example Example RTR gt MODIFY JOURNAL DISK1 BLOCKS 3000 MAXIMUM_BLOCKS 20000 This command specifies that the desired size of the journal file is 3000 blocks and the maximum journal file size is 20 000 blocks RTR gt MODIFY JOURNAL dev rz3a BLOCK 2000 MAXIMUM_BLOCKS 20000 This command specifies that the desired size of the journal file is 2000 blocks and the maximum journal file size is 20 000 blocks RTR Command Line Interface 6 99 MONITOR MONITOR Displays a monitor picture on the screen Format MONITOR monitor file spec Command Qualifiers CLUSTER COUNT nr updates FACILITY facility name IDENTIFICATION process id INTERVAL delay seconds LINK link name NODE node list OUTPUT file spec PARTITION partition name RESUME VERIFY Description Defaults NOCLUSTER COUNT infinite NOFACILITY NOIDENTIFICATION INTERVAL 2 NOLINK NODE default node list OUTPUT stdout NOPARTITION NORESUME NOVERIFY The MONITOR command allows certain RTR status variables to be continuously displayed on your terminal The individual items displayed in the monitor picture may be defined interactively using DISPLAY commands and then executed using a MONITOR RESUME command You
78. the journal In addition the SET TRANSACTION command also helps users to better control the RTR runtime environment in difficult operational situations For example a transaction while still in SENDING state on the backend may appear to be hung and cannot proceed Using the SET TRANSACTION command an RTR administrator can abort this transaction on the fly and free runtime resources While the SET TRANSACTION command enables RTR users to have full control of RTR transactions it introduces the risk that a transaction could be lost or corrupted The command must be used with discretion and should only be used by expeerienced RTR system administrators After using the SET TRANSACTION command complete you may use the DUMP J OURNAL command to verify the results RTR Command Line Interface 6 125 SET TRANSACTION Parameters Qualifiers 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 RTR will try to determine whether the change also affects other portion of RTR environment For example in a runtime situation where RTR routers and RTR backend servers are active the RTRACP will send the new status to applicaiton servers as well as RTR routers to make
79. the last backend accessed to recover transactions If the server state is Icl_rec_fail or shd_ rec_fail this entry is the name of the background which could not be accessed J ournal scans is the number of journal files searched Transactions recovered is the number of transactions found for this partition RTR Monitoring 5 13 RTR Monitoring 5 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 Icl_rec Local recovery Icl_rec_fail Primary server waiting for access to a restart journal Icl_rec_icpl Getting next journal to recover from Icl_rec_cpl Processed all journals for local recovery shd_rec Shadow recovery shd_rec_fail Shadow server waiting for access to a restart journal shd_rec_icpl Shadow getting next journal to recover from shd_rec_cpl Processed all journals for shadow recovery catchup Secondary is catching up with primary standby Server is declared as standby 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 2 23 Monitor Rejects NODE NODEA Rejected Transaction Summary PROCESS 20413894 Fri Apr 9 1999 10 26 14 Time Pid Chan Reason Status Text Fri Apr 9 10 18 43 20417266 client Fri Apr 9 10 17 47
80. these nodes may be in this state RTR determines the processing state of a given partition through the use of a globally managed sequence number for that partition By default the RTR master router will automatically assign sequence numbers to partitions during startup When a server is started up on a backend node and declares a new partition for that node the partition initially has a sequence number of zero When the partition on that backend makes an initial connection to the master router the router increases its sequence number count for that partition by one and assigns the new sequence number to the new backend partition The active node with the lowest backend partition sequence number gets the primary processing state in both shadow and standby configurations That node is also referred to as the primary node though the same node could have a standby processing state for a different partition Under certain failover conditions backend partitions may either retain their original sequence number or be assigned a new sequence number by the router If a failure is caused by a network disruption for example a backend partition will retain its sequence number when it reconnects with the router However if the backend node is rebooted or RTR is restarted on the backend node a new sequence number will be assigned by the router to any partitions that start up on that node Routers will only assign new sequence numbers to backend partitions
81. this command the facility being extended may lose quorum until the affected nodes agree upon the new facility definition During this time server applications will not be presented with any new transactions RTR Command Line Interface 6 179 TRIM FACILITY Parameters Qualifiers RTR MONITOR QUORUM displays a monitor picture which allows the quorum negotiations to be observed You can use this after using a TRIM FACILITY command once quorum has been re attained the participating nodes return to the quorate state For example in a three node facility called facnam the nodes FE and NFE have only frontend roles and node FETRBE has frontend router and backend roles This facility could have been created as follows RTR RTR gt SET ENVIRONMENT NODE FE FETRBE NFE RTR gt CREATE FACILITY facnam FRONTEND NFE FE FETRBE ROUTER FETRBE BACKEND FETRBE The frontend node NFE can be removed from the facility as follows RIR RTR gt SET ENVIRONMENT NODE FETRBE NFE RTR gt TRIM FACILITY facnam FRONTEND NFE facility_name Specifies the name of the facility to be trimmed The default value for facility_name is RTRSDEFAULT_FACILITY BACKEND backend list NOBACKEND D Specifies the names of the nodes where backend roles for this facility are removed backend list is a list of backend nodes separated by commas If there is more than one backend node then backend 1ist must be enc
82. to be executed on the local node only FACILITY FACILITY D Specifies the facility name for which information should be displayed By default information is displayed for all Facilities 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 163 SHOW SEGMENT Examples RTR gt SHOW SEGMENT 1 Facility Data Type Length Offset RTRSDEFAULT_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 6 164 RTR Command Line Interface SHOW SERVER SHOW SERVER Format Description Display information about server channels SHOW SERVER Command Qualifiers Defaults CLUSTER NOCLUSTER FACILITY FACILITY FULL NOFULL IDENTIFICATION process id NOIDENTIFICATION NODE node list OUTPUT file spec NODE default node list OUTPUT stdout The SHOW SERVER command displays information about server channels Information such as PID key range state event mask
83. 0 RTR Command Line Interface SHOW JOURNAL Related Commands Examples A N Oo oF CREATE JOURNAL DELETE JOURNAL Hi ITIALIZE JOURNAL RTR gt 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 J017 Disk 2 dev rz2c Blocks 1500 Allocated 1502 Maximum 3000 File 2 dev rz2c usr users rtrjnl SYSTEM BRONZE J11 Show the disks used for RTR recovery journal and the filenames Two disks are currently in use Device name File size in blocks Allocated file size in blocks Maximum file size in blocks Filename RTR Command Line Interface 6 141 SHOW KEY SHOW KEY Format Description Parameters Qualifiers Display the key definitions created by the DEFINE KEY command SHOW KEY key name Command Qualifiers Defaults ALL NOALL FULL NOFULL OUTPUT file spec OUTPUT stdout IF_STATE NOIF_STATE The SHOW KEY command shows the key definitions created by the DEFINE KEY command key name Specifies the name of the key whose definition you want displayed See the description of the DEFINE KEY command for a list of the valid key names ALL NOALL D Requests that all key definitions in the current state be displayed You can use the IF_STATE qualifier to request key definitions in other states Do not specif
84. 1 Table A 1 Information Classes Information Class String per node rtr per facility fac per link to a node Ink per client process eli per server process srv per application process pre per partition on a router rpt per partition on a backend bpt per key segment ksg per transaction on a frontend fox per transaction on a router pex per transaction on a backend btx The monitor is invoked with the RTR MONITOR command RTR monitor displays a monitor picture that is periodically updated See Section 6 2 for the full syntax of the MONITOR command A monitor picture contains elements that are either text such as labels and titles or variables derived from data items Monitor pictures can be defined either interactively at the RTR gt prompt or defined in a file called a monitor file Creating Monitor Pictures A 1 Creating Monitor Pictures The commands used to define and display monitor pictures are CLEAR DI DI DI DI DI SPLAY BAR SPLAY NUMERIC SPLAY STRING SPLAY SYMBOLIC SPLAY TEXT MONITOR SCROLL SHOW DISPLAY These A 1 Interactive commands are described in the following sections Definition of a Monitor Picture Example A 1 shows a monitor picture being defined in an interactive RTR session Example A 1 Interactive Picture Definition RTR RTR gt CLEAR ALL 1 RTR gt RTR gt _RTR gt RTR gt RTR gt RTR gt DISPLAY TEXT X 25 Y 1 THE TEST PICTURE AT
85. 3 34 igits here 1234 000030 35 36 37 38 39 30 00 567890 RTR Command Line Interface 6 27 CALL RTR_REJECT_TX CALL RTR_REJECT_TX Format Description The CALL RTR_REJ ECT_TX command causes a command server to execute the rtr_reject_tx routine and to display the returned status CALL RTR_REJECT_TX Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout REASON rsnsts REASON 0 RETRY NORETRY D The CALL RTR_REJ ECT_TX command causes a command server to call the rtr_reject_tx routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_reject_tx routine itself is described in Application Programmer s Reference Manual The prototype of rtr_reject_tx is rtr_status_t rtr_reject_tx rtr_channel_t channel rtr_rej_flag_t flags rtr_reason_t reason Y Table 6 10 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 10 Parameters for rtr_reject_tx C Parameter Name C Parameter Value Command Line Specification channel CHANNEL_NAME name flags RTR_NO_FLAGS none D RTR_F_REJ_RETRY RETRY reason RTR_NO_REASON NOREASON D reason_value REASON Teason_value Qu
86. 4 The channel called CLI_CHN2 is open as a client channel and has been opened by another process in another window 6 130 RTR Command Line Interface SHOW CLIENT SHOW CLIENT Format Description Qualifiers Display information about client channels 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 The SHOW CLIENT command displays information about client channels Information such as PID key range state event mask and event name are displayed 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 command is executed only on the node where the command was issued 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 IDENTIFICATION process id NOIDENTIFICATION D Specifies the PID of the process for which information is displayed The default NOIDENTIFICATION displays information for all clients FACILITY FACILITY D Specifies the facility name for which informat
87. 66 6776 0 nodea gt nodea 3072248 336 0 nodea gt nodeb 42569496 4974 0 nodea gt nodec 13559722 1466 0 336 0 4974 0 1466 0 Bytes Sent Abs Rate Max 1002579480 113857 0 z 3072248 336 0 336 0 717457678 84438 0 84438 0 282049554 29083 0 29083 0 Displays a list of the links to other nodes For each link the total number of bytes received and sent on that link and the number of bytes received and sent per second are displayed Derived from the NIO_BYTES RCVD and NIO_ BYTES SENT counters The Max field represents the maximum rate since the link started RTR Monitoring 5 11 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 Link 12 0 2 12 12 1 3 0 0 NODEA gt nodeb 0 0 0 0 0 0 1 0 0 up alpha NODEA gt nodec 6 0 0 6 6 0 0 0 0 down 76490676 NODEA gt noded 6 0 0 6 6 0 0 0 0 down 76490676 NODEA gt nodee 0 0 2 0 0 1 2 0 0 up alpha Displays the link status for connected links in detail and the fail code for any links on which a connection has failed Unconnected links where connection have been lost are highlighted Link aborts rejects loss gain restarts state and architecture of the remote node are also displayed More detail included than in in the monitor connects display 5 2 19 Monitor Partit PARTITION DEFINITIONS Tue Apr 6 1999 10 40 31 NODE NODEA Partit
88. 72 SHOW 6 133 A 2 STRING 6 77 SYMBOLIC 6 81 TEXT 6 83 DO DCL command 6 86 Index 1 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 FACILITY 6 91 F Facility 1 1 Create 2 1 Monitor 5 2 FACILITY CREATE 6 47 DELETE 2 4 6 61 EXTEND 6 91 SET 6 109 SHOW 6 136 TRIM 6 179 Gfile 1 3 Flow Monitor 5 2 FLUSH NAME_CACHE 6 88 Frontend 2 1 G Group Monitor 5 2 H Help 1 2 Ipc Monitor 5 2 I pcrate Monitor 5 2 J J ournal Monitor 5 3 J OURNAL CREATE 6 51 DELETE 6 63 JOURNAL 2 3 Index 2 JOURNAL cont d MODIFY 6 98 SHOW 6 140 J ournal initialization 2 3 K KEY DEFINE 6 57 SHOW 6 142 L Link Monitor 5 3 LINK SET 6 112 SHOW 6 144 Load balancing 2 8 LOG 6 96 SET 6 116 SHOW 6 146 Memory virtual 2 10 MODE SET 6 118 SHOW 6 148 MODIFY JOURNAL 6 98 Monitor Active 5 2 Broadcast 5 2 Calls 5 2 Channel 5 2 Congest 5 2 Connects 5 2 Ddtm 5 2 Event 5 2 Facility 5 2 Flow 5 2 Group 5 2 Ipc 5 2 Ipcrate 5 2 Journal 5 3 Link 5 3 Netbytes 5 3 Netstat 5 3 Partit 5 3 Queues 5 3 Quorum 5 3 Recovery 5 3 Rejects 5 3 Rejhist 5 3 Response 5 3 Rolequor 5 3 Routers 5 3 Monitor cont d Routing 5 3 Rtr 5 3 Stalls 5 3 System 5 3 Tps 5 3 Tpslo 5 3 Traffic 5 3 V2calls 5 4
89. 9 3 Interoperation with RTR Version 2 Using DECnet Reliable Transaction Router is interoperable with RTR Version 2 2D ECO3 or later when running on a platform that supports DECnet that is OpenVMS Compag Tru64 UNIX SUN Windows 95 or Windows NT Note that it is not possible to mix Version 2 and Version 3 routers and backends all router and backend nodes in a facility must be either Version 2 or Version 3 Frontend nodes may be either Version 2 and Version 3 Defining the facility e On RTR Version 2 node s There are no special requirements for including a V3 x frontend in a V2 facility definition Simply add the name of the frontend to the node list specified by the FRONTEND qualifier e On RTR Version 3 node s The default network transport for RTR Version 3 2 is TCP IP Since RTR Version 2 uses DECnet only you must specify that your RTR Version 3 nodes use the DECnet protocol This is achieved by prefixing the RTR V2 nodename with the string dna For example to specify the facility FAX1 on the RTR V3 frontend v3fe for which the two V2 routers VMS1 and VMS are defined use the following command RTR gt create facility FAX1 frontend v3fe router dna VMS1 dna VMS2 e Note that the facility name should contain only UPPER CASE letters on all nodes if the facility includes nodes running RTR V2 The use of the dna prefix assumes that the default network transport is TCP IP The def
90. AIX A minimum of 268436 Kbytes for a single file size 2 12 Starting and Setting Up RTR 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 O for CPU time e On HPUX A minimum of 1024 open file descriptors The START RTR qualifiers LINK and PROCESSES apply only to the OpenVMS platform and the determination of process quotas on UNIX platforms must be done through operating system handling of virtual memory sizing 2 9 Network Transports RTR supports multiple network transports with a default behaviour as follows If an attempt to create a network connection to a remote node fails RTR retries the connection attempt using an alternate transport protocol if one is available The order in which the supported transport protocols are used depends on the host operating system OpenVMS first DECnet then TCP IP All other platforms first TCP IP then DE Cnet If a connection attempt fails on all available protocols the connect fails and is retried at a later time starting again with the first transport protocol If an established link fails RTR automatically initiates a reconnection of the link starting with the first transport protocol for the platform regardless of the transport employed when the link failed 2 9 1 Specifying t
91. AULT_FACILITY The ROUTER qualifier and at least one of FRONTEND or BACKEND must be specified An EXTEND FACILITY command executed on a node where the facility is not defined is interpreted as a CREATE FACILITY command To maintain consistency in a facility the following rules apply when adding nodes or roles or both f a frontend role is added then the node where it is added must know about at least one router of the facility If a backend role is added then the node where it is added must know about all routers of the facility If any router nodes are not known by a backend then problems may occur in achieving quorum Ifa router role is added then the node upon which it is added must know about all backends of the facility If not all backend nodes are known by a router then problems will occur in achieving quorum At least one frontend must be defined on a node that has the router role In order to have a consistent facility definition across all nodes in the facility and thus avoid problems in attaining quorum the command to add a router role must be executed on all relevant nodes that is the node gaining the router role and all backend nodes BACKEND backend list NOBACKEND D Specifies the names of the added nodes that are to act as backends for this facility 6 92 RTR Command Line Interface EXTEND FACILITY Backend list is a list of backend nodes separated by commas If there
92. CILITY ADD FACILITY is retained for compatibility reasons only 6 2 RTR Command Line Interface CALL RTR_ACCEPT_TX CALL RTR_ACCEPT_TX Format Description 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 Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER FORGET NOFORGET INDEPENDENT NOINDEPENDENT NODE node list NODE default node list OUTPUT file spec OUTPUT stdout REASON reason REASON 0 The CALL RTR_ACCEPT_TX command causes a command server to call the rtr_accept_tx routine using values supplied on the command line The numeric status returned from the call is then converted to ts textual representation and displayed The rtr_accept_tx routine itself is described in Application Programmer s Reference Manual The prototype of rtr_accept_tx is rtr_status_t rtr_accept_tx rtr_channel_t channel rtr_acc_flag_t flags rtr_reason_t reason dy Table 6 1 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 1 Parameters for rtr_accept_tx C Parameter Name C Parameter Value Command Line Specification channel CHANNEL_NAME name flags RTR_NO_FLAGS none D RTR_F_ACC_FORGET FORGET reason RTR_NO_REASON NOREASON D reaso
93. 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 command is executed only on the node where the command was issued 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 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used 6 86 RTR Command Line Interface DO Related Commands e SPAWN Example RTR gt DO CLUSTER SHOW TIME This command shows the time on all nodes in a OpenVMS cluster RTR gt DO NODE TR2 TR1 SHOW LOGICAL MYLOGICAL This command examines the logical name MYLOGICAL on nodes TR2 and TR1 RTR gt SET ENVIRONMENT NODE TR2 TR1 RTR gt DO SHOW TIME RTR gt DO SHOW LOGICAL MYLOGICAL The SET ENVIRONMENT command can be used if a series of DCL commands are to be issued on the
94. CREATE command RTR Command Line Interface 6 59 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 the system fails to recognize CREATE as the keyword for the HELP command 6 60 RTR Command Line Interface DELETE FACILITY DELETE FACILITY Format Description Parameters Qualifiers Delete an RTR facility DELETE FACILITY facility name Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The DELETE FACILITY command removes the specified facility on the node where the command is issued After issuing this command applications are able to use the facility Any outstanding transactions using the facility are aborted facility_name The name of the facility to delete The parameter facility_name must be supplied 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 command is executed only on the node where the command was issued Note In environments that do not suppor
95. 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 ANDERS_1 123297 28 9 NODEB 21400724 RTRACP 0 0 0 NODEB 214005F0 ANDERS _1 123298 31 8 Same as TOPTPS except that a given process is always displayed at the same position on the screen that is the list is not sorted by TPS 5 2 34 Monitor Traffic RTR gt Monitor Traffic LINK TRAFFIC 7 JAN 1999 14 38 08 NODE ALL Bytes second Packets sec Messages sec Revd Sent Rcvd Sent Avrg Rcvd Sent Total 13465 5 13213 3 123 8 121 2 239 1 53 3 53 3 NODEA gt NODEA 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NODEA gt NODEB 10718 0 2705 8 95 1 27 5 118 9 24 9 27 2 NODEB gt NODEB 41 7 41 7 1 2 1 2 1 4 Liz 1 2 NODEB gt NODEA 2705 8 10465 8 27 5 92 5 118 8 27 2 24 9 Congestion Abs Rate 35 0 0 0 28 0 7 QUO E 2 2 e e 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 Average packets per second is also shown Uses counters in the Network I O NIO subsystem 5 2 35 Monitor Trans RTR gt Monitor Trans monitoring transactions Thu Mar 4 1999 15 21 38 NODE NODEA Tid Frontend Facility 46d01f10 0 0 0 0 baa09da abf10001 RTRSDEFAULT_FACILITY aborting Tid Router Facility State Tid Backend Facility 46d01f10 0 0 0 0 baa09da abf10001 RTRSDEFAULT_FACILITY
96. 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 command is executed only on the node where the command was issued 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 COUNTER counter name NOCOUNTER D Specifies that the per node counters are also to be displayed Counter name is the name of the counter to be displayed If counter name is omitted then all counters will be displayed Counter name may contain wild card characters FULL NOFULL D Equivalent to specifying COUNTER STATUS 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 161 SHOW RTR STATUS D NOSTATUS Displays the current status of RTR started stopped and so on VERSION NOVERSION D Displays the
97. DCAST_EVENT Dollar is up EVENT_NUMBER 23 SRTR 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 Note that only the event is broadcast there is no associated message RTR gt CALL RTR_BROADCAST_EVENT EVENT 24 RECIPIENT_SPEC DEALER SRTR S OK Normal successful completion The following example shows a broadcast message containing two fields The first field is of type unsigned entered as a hexadecimal number the second field is of type string RTR gt CALL RTR_BROADCAST_EVENT EVENT 24 OxFA9BCO TYPE_OF_ DATA UNSIGNED LENGTH 8 This field of the message is a string SRTR S OK Normal successful completion RTR Command Line Interface 6 9 CALL RTR_CLOSE_CHANNEL CALL RTR_CLOSE_CHANNEL Format Description 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 Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER IMMEDIATE IMMEDIATE RTR DEFAULT_CHANNEL NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The CALL RTR_CLOSE_CHANNEL command causes a command server to call the rtr_close_channel routine using values supplied on the command line The numeric status returned from the cal
98. DE 6 148 NODE 6 150 PARTITION 6 152 PROCESS 6 156 REQUESTER 6 158 RESOURCE MANAGER 6 159 RM 6 159 RTR 6 161 SEGMENT 6 163 SERVER 6 165 TRANSACTION 6 168 SHOW RESOURCE MANAGER 6 159 SHOW RM 6 159 SPAWN DCL command 6 171 Stalls Monitor 5 3 Start Rtr 2 1 START RTR 6 172 STOP RTR 6 177 STRING DISPLAY 6 77 Substitution symbol A 2 A 3 SYMBOLIC DISPLAY 6 81 System Monitor 5 3 T TEXT DISPLAY 6 83 Tps Monitor 5 3 Tpslo Monitor 5 3 Traffic Monitor 5 3 Index 4 TRANSACTION SET 6 125 SHOW 6 168 TRIM FACILITY 6 179 U UNREGISTER RESOURCE MANAGER 6 182 RM 6 182 UNREGISTER RESOURCE MANAGER 6 182 UNREGISTER RM 6 182 V V2calls Monitor 5 4 V2 interoperation 2 15 Virtual memory 2 10 W Windows NT service 2 16 X XA C 1 Commands 6 105 DTC Support C 2 Introduction C 1 Monitor 5 4 MONITOR XA C 1 REGISTER RESOURCE MANAGER 6 105 REGISTER RM 6 105 SHOW RESOURCE MANAGER 6 159 SHOW RM 6 159 UNREGISTER RESOURCE MANAGER 6 182 UNREGISTER RM 6 182
99. DNOTDEF No definition found for a node in the list see log file Explanation Status indicating absence of a definition for a node named in list of back ends for the partition RTR E PRTNODNOTLST Local node must be in the list of back end nodes Explanation Status indicating erroneous absence of the local node from the ordered list of back ends for the partition RTR E PRTNOSRVRS Partition has no servers please start servers and retry Explanation Cannot perform the requested action until servers are attached to the partition Start servers and retry RTR E PRTNOTBACKEND Partition commands must be entered on a backend node Explanation Restriction partition commands must be entered on a BACKEND node RTR E PRTNOTSUSP Unable to resume partition that is not suspended Explanation Status indicating completion of partition resume command where the target partition was not suspended RTR S PRTRESUME Partition resumed Explanation Status indicating successful completion of partition resume command Transaction presentation is now enabled RTR S PRTRSRTRCVY Partition recovery initiated Explanation Completion status indicating that partition recovery was manually initiated by the operator RTR Utility Error Messages D 21 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 delete
100. E BALANCE This command tells RTR to use router load balancing RTR Command Line Interface 6 111 SET LINK SET LINK Format Description Qualifiers Sets various link related options 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 OUTPUT file spec OUTPUT stdout SUSPECT NOSUSPECT The SET LINK command sets options for one or more or links The options are link enabled or disabled link autoisolate link checksum and link inactivity timeout The parameter link name is the node from which connect attempts are to be honored or not Note that disabling the link prevents incoming connections over an established link It only takes effect when new connect attempts are made It does not effect the ability to connect to a node whose link has been disabled The link name can be wildcarded The current state of the link can be displayed with the SHOW LINK STATUS command When looking at connection problems both ends of the link counters should be used with the SHOW LINK COUNTER command AUTOISOLATE NOAUTOISOLATE D Any RTR node may disconnect a remote node if it finds the remote node is unresponsive or congested The normal behavior following such action is automatic network link reconnection and recovery Node autoisola
101. E qualifier lets you increase the number of key definitions available on your terminal The same key can be assigned any number as long as each definition is associated with a different state By default the current key state is the DEFAULT state The current state may be changed by pressing a key that causes a state change that is a key that was defined with the DEFINE KEY STATE command key name Specifies a function key to be assigned a string Table 6 18 describes the valid key names Table 6 18 Key names Key name LK201 VT100 type PF1 PF1 PF1 PF2 PF2 PF2 PF3 PF3 PF3 continued on next page RTR Command Line Interface 6 57 DEFINE KEY Table 6 18 Cont Key names Key name LK201 VT100 type PF4 PF4 PF4 KPO 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 El Find E2 Insert Here ES Remove E4 Select ES Prev Screen E6 Next Screen HELP Help DO Do F6 F7 F20 F6 F7 F20 equivalence string Specifies the string to be processed when the specified key is pressed Typically this is all or part of an RTR command If the string contains spaces or non alphanumeric characters it must be enclosed in quotation marks Qualifiers ECHO D NOECHO Controls whether the command line is displayed after the key has been pressed Do not use
102. ECHO with NOTERMINATE IF_STATE state name NOIF_STATE D Specifies the name of a state to which a key definition applies IF_STATE assigns the key definitions to the specified states A state name may be any appropriate alphanumeric string NOIF_STATE the default assigns the key definition to the DEFAULT state LOCK_STATE NOLOCK_STATE D Controls how long the state set by SET_STATE remains in effect after the specified key is pressed LOCK_STATE causes the state to remain in effect until it is changed explicitly by another function key being pressed that has the SET_STATE attribute NOLOCK_STATE the default causes the state to remain in effect only until the next terminator character is typed or until the next define function key is pressed 6 58 RTR Command Line Interface LOG NOLOG D DEFINE KEY Controls whether a message is displayed indicating that the key definition has been successfully created SET_STATE state name NOSETSTATE D Controls whether changes the current state to state name when you press the key NOSET_STATE pressing the key changes the current key state SET_STATE the default causes the current state to remain in effect TERMINATE NOTERMINATE D Controls whether the specified string is to be terminated processed when the key is pressed T ERMINATE causes the str
103. EL_NAME chamnel name CHANNEL_ NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The CALL RTR_GET_TID command causes a command server to call to the rtr_get_tid routine using values supplied on the command line The transaction id returned from the call is converted to its textual representation and displayed The rtr_get_tid routine itself is described in Application Programmer s Reference Manual The prototype of rtr_get_tid is rtr_status_t rtr_get_tid rtr_channel_t channel rtr_tid flag_t flags void ptid Y Table 6 6 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 6 Parameters for rtr_get_tid C Parameter Name Parameter Value Command Line Specification channel CHANNEL_NAME name flags RTR_NO_FLAGS none D Qualifiers CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use The default channel name is RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER D Specifies that the command is executed on all the nodes in the cluster RTR Command Line Interface 6 13 CALL RTR_GET_TID Examples If neither NODE n
104. E_GAI 1 BM_NCF_EVENTS_RCVD 7 TMBE_TX_REJECTS 0 CF_TR_BE_GAI 1 TM_NCF_EVENTS_RCVD 13 TMBE_TX_RTR_FORGETS 72499 NCF_TR_FQM_LOSS 0 FE_TX_RQ_STARTS 72700 TMBE_CRPS_REQUESTED 0 CF_FE_TR_LOSS 0 FE_TX_RQ_ENQS 72700 RSC_GETTXDST_CALLS 72700 CF_FE_TR_NOCUR 0 FE_TX_RQ_COMMITS 72700 RSC_GETTXDST_SUCCESS 72700 CF_FE_TR_GAIN 1 FE_TX_RQ_ABORTS 0 RSC_GETTXSRV_CALLS 0 CF_BE_TR_LOSS 0 FE_TX_ACCEPTS 72500 RSC_GETTXSRV_SUCCESS 0 CF_BE_TR_GAI 1 FE_TX_REJECTS 0 RSC_GETEVIDST_CALLS 0 CF_FOM_TR_LOSS 0 FE_TX_REPLAYS 0 RSC_GETEVIDST_SUCCESS O QRM_REQ_LINK_QUEUE 0 RT_TX_RQ_STARTS 72700 RSC_GETEVTRCV_CALLS 6 QRM_RSP_LINK_QUEUE 0 RT_TX_RQ_ENQS 72700 RSC_GETEVTRCV_SUCCESS 0 RT_TX_RQ_COMMITS 72700 RSC_FE_NODES 1 RT_TX_RQ_ABORTS 0 RSC_BE_NODES 1 RT_TX_ACCEPTS 72500 RSC_TR_SERVER_CLASSES 1 RT_TX_REJECTS 0 RSC_BE_SERVER_CLASSES 1 BE_TX_RQ_STARTS 72700 RSC_SERVER_CHANS 1 BE_TX_RQ_ENQS 72700 RSC_REQUESTER_CHANS 2 Displays per facility counters Use the FACILITY qualifier to specify a facility if it is not specified then the totals of the counters for all facilities are displayed 5 8 RTR Monitoring 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 gt TR 15000 2065 307 966 0 966 0 TR gt BE 15000 2065 70 998 0 998 0 BE gt TR 0 0 0 0 0 0 0 TR gt FE 15000 0 0
105. HARACTER CHARACTER a D Specifies the character used to draw bar charts The line drawing character set is used to display them By default the character a is used which corresponds to a rectangular block in the character set If NOCHARACTER is given then no characters are displayed and the bar is visible only if attributes have been specified This can be used to draw a scale behind the bar chart DAMPING damping factor NODAMPING D Specifies that the value displayed is to fluctuate more slowly than the raw measured value The default for damping factor is one Damping is only relevant if VALUE CURRENT 6 68 RTR Command Line Interface DISPLAY 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 The default is 50 MAXIMUM max value MAXIMUM 10 D Specifies the maximum value represented on a bar chart The default is 10 MINIMUM min value MINIMUM 0 D Specifies the minimum value represented on a bar chart The default is zero RATE interval NORATE 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 o
106. JTQUOTA job table quota JTQUOTA 5000 D Allows you to specify a quota the job wide logical name table for the RTR ACP The default for job table quota is 1024 LINKS max links LINKS 512 D Specifies the maximum number of nodes with which this node can communicate The default for max links is 512 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used PGFLQUOTA page file PGFLQUOTA max links max processes x 400 16000 default pages D Specifies the maximum number of pages allocated in the paging file for the RTR ACP The paging file quota is the amount of secondary storage available during execution of the RTR ACP image Note that a shortage of virtual memory may produce spurious error messages 6 174 RTR Command Line Interface 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 Requires alt
107. LUSTER 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 command is executed only on the node where the command was issued 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 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 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 e SHOW LOG 6 96 RTR Command Line Interface Examples LOG RTR gt LOG OUTPUT RTRLOG LOG Message check here This command tells RTR to write a log message to the file RTRLOG LOG RTR gt 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 RTR gt LOG NODE hostname Message check HERE This command tells RTR to write defined log message to the log to the hostname on the node li
108. Line Interface EXTEND FACILITY EXTEND FACILITY Format Description Adds new nodes or roles or both to an existing facility definition EXTEND FACILITY facility_name Command Qualifiers Defaults BACKEND backend list NOBACKEND BALANCE NOBALANCE CALL_OUT role list NOCALL_OUT CLUSTER NOCLUSTER FRONTEND frontend list NOFRONTEND NODE node list NODE default node list OUTPUT file spec OUTPUT stdout ROUTER router list NOROUTER The EXTEND FACILITY command extends the configuration of an RTR facility New nodes and roles can be added to a facility definition using the EXTEND FACILITY command Thus a new node can be introduced into a facility or a new role can be added to an existing node for example a router node can be extended to have a backend role Notes New router nodes must have all backend nodes defined and new backend nodes must have all router nodes defined Routers need only be defined with the frontends that they can connect to Frontends need only be defined with the routers they can connect to When using this command the facility being extended may temporarily lose quorum until the affected nodes agree upon the new facility definition During this time server applications will not be presented with any new transactions The RTR MONITOR QUORUM displays a monitor picture which allows the quorum negotiations to be followed after a TRIM or EXTEND of a facility Once quoru
109. Log file A re opened RTR E LINKDISABLED Link disabled connection rejected Explanation The link to this node has been disabled at the remote partner It can be enabled with the command set link enable at the remote node RTR I LIVEAPPL Process A PID A still attached to RTR Explanation Displays the name A and PID B of the processes that are still attached to RTR RTR I LNKDSC Link to node A disconnected Explanation This message is issued once per disconnected network link during the execution of the RTR DISCONNECT LINK command RTR E LOADLIBFAIL Unable to dynamically load the shared library Explanation The RTR ACP was unable to load the shared library dynamically RTR E LOADSYMFAIL Unable to find the symbol in the shared library Explanation The RTR ACP was unable to locate the symbol name in the lib RTR Utility Error Messages D 13 RTR Utility Error Messages RTR E LOCKFAIL Cannot obtain lock for resource A Explanation Failed to obtain lock Enable logging for more information about error RTR S LOGFILSET Logging to A Explanation Displays which log files will be used after issuing a SET LOG command with the FILE or OPERATOR or both qualifiers RTR S LOGFILSUP Logging suppressed Explanation ndicates that logging is successfully suppressed after issuing a SET LOG command without a FILE or OPERATOR qualifier RTR E LOGNOTACT Logging not active Explanation Indicates t
110. ME 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 A 2 Substitution Symbols The text and labels in the DISPLAY commands that are used to define monitor pictures can contain symbols which are substituted when the picture is displayed Table A 2 contains a list of these symbols Table A 2 Substitution symbols Symbol Description TIME Current time DATE Current date NODE_NAME Name of node where values were measured LINK_NAME Name of link for which values were measured FACILITY NAME Name of facility for which value was measured PROCESS ID ID of process for which value was measured PROCESS NAME Name of process for which value was measured IMAGE_NAME Image file name of process for which value was measured FULL_IMAGE_NAME The full file specification of the image for the process for which values were measured The field width for these predefined symbols can be specified by appending a colon and then the required width For example TIME displays the current system time in the form 10 34 03 TIME 5 displays the first five characters of the system time in this case 10 34 If the field width specified is larger than the field then the data is left justified and space filled to the required width A 3 Arithmetic Expressions and Operators When using dat
111. NEL_NAME chamnel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER FORMAT fmt string NOFORMAT INDEPENDENT NOINDEPENDENT LENGTH_OF_FIELD message lengthDepends on data type see description NODE node list NODE default node list OUTPUT file spec OUTPUT stdout TYPE_OF_DATA data type TYPE_OF_DATA STRING The CALL RTR_REPLY_TO_CLIENT command causes a command server to call the rtr_reply_to_client routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_reply_to_client routine itself is described in Application Programmer s Reference Manual The prototype of rtr_reply_to_client is rtr_status_t rtr_reply_to_client rtr_channel_t channel rtr_rep_flag_t flags rtr_msgbuf_t pmsg rtr_msglen_t msglen rtr_msgfmt_t msgfmt y Table 6 11 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call RTR Command Line Interface 6 31 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 message definition parameter list with positional msgfmt qualifiers 1 The actual values used for pmsg msglen and msgfmt are based upon the messa
112. NOFILENAMES FULL NOFULL NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SHOW JOURNAL command shows the disks where the RTR journal files reside and optionally the maximum and allocated number of blocks for each journal file and the journal file name 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 command is executed only on the node where the command was issued 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 FILENAMES NOFILENAMES D FILE adds the journal filenames to the display FULL NOFULL D FULL adds to the display the maximum and allocated number of blocks for each journal file 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used 6 14
113. OG Command Qualifiers Defaults CLUSTER NOCLUSTER FILE file spec list NOFILE NODE node list NODE default node list OPERATOR NOOPERATOR OUTPUT file spec OUTPUT stdout The SET LOG command specifies where RTR writes its log messages You can write log messages to the operator console and to a maximum of four log files Log files must be periodically purged to avoid difficulties with full disks Do this by using SET LOG to specify a new file and deleting the old one If neither the OPERATOR nor the FILE qualifier is specified then logging is suppressed Note Log files must always be accessible even if a node fails 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 command is executed only on the node where the command was issued 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 FILE file spec list NOFILE D Specifies the names of up to four files where the log messages are written The given filename is appended with log NODE node list NODE default node list D Specifies that the command is executed on all
114. OW RM Format Description Parameters Qualifiers Displays resource manager instance RM information This command is available only on UNIX and Windows NT systems SHOW RESOURCE MANAGER resource_name SHOW RM resource_name Command Qualifiers Defaults CLUSTER NOCLUSTER FULL NOFULL NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SHOW RESOURCE MANAGER command displays information for registered RMs This command shows information for one or more RMs registered with the current TM Note This command is available only on UNIX and Windows NT systems Refer to Appendix C XA Support for support information about XA resource_name Specifies the name of the resource manager instance you want to display resource_name may contain wild cards and in which case all matching resources will be displayed If resource_name is omitted all configured resources are displayed 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 command is executed only on the node where the command was issued Note In environments that do not support clustering use of the CLUSTER qualifier will cause the relevant comma
115. Partition Sales DDCDS8 NOV 1991 192759 Server Shadowing and Recovery B 9 C XA Support This appendix explains how RTR may be used with a X OPEN Distributed Transaction Processing DTP conformant Resource Manager C 1 Introduction The X OPEN Distributed Transaction Processing DTP architecture defines a standard interface that lets application programs share resources provided by resource managers The XA interface uses the two phase commit protocol to commit transactions and is a system level bidirectional interface between the transaction manager TM and the resource manager RM In the RTR environment RTR is the transaction manager and database software such as ORACLE8 is the resource manager Without XA an RTR application must deal with replayed transactions after server recovery delivered with rtr_mt_msgl_uncertain the application has to check if the traansaction has been committed to the database With XA the application does not need to be concerned with this problem The XA library is an external interface that enables a transaction manager to coordinate global transactions These can include opening a resource manager starting a transaction rolling back a transaction preparing and committing a transaction and closing a resource manager With XA RTR can connect directly to a resource manager such as ORACLE8 C 1 1 MONITOR XA Monitors the internal status of XA interface activities The command displays coun
116. R 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 command is executed only on the node where the command was issued 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 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 129 SHOW CHANNEL Related Commands e call rtr_open_channel e call rtr_close_channel Examples RTR gt SHOW CHANNEL ALL_WINDOWS 1 Channel type Channel name Owner pid server RTRSDEFAULT_CHANNEL 28879 2 client CLI_CHN 28879 3 client CLI_CHN2 26225 4 1 Display information about all declared channels 2 The channel called RTRSDEFAULT_CHANNEL is open as a server channel 3 The channel called CLI_CHN is open as a client channel
117. R E CANTSTOP RTR could not be stopped Explanation Indicates that RTR cannot be stopped under present circumstances RTR E CHAALROPE Channel A is already open in this window Explanation An RTR channel of this name is already open in this window RTR F CHANOTOPE Channel not opened Explanation Channel was not opened Check channels using the SHOW CHANNEL command RTR E CHNALRDEC Channel A is already declared Explanation The channel specified with the CHANNEL qualifier on a call rtr_open_channel command has already been declared RTR E CHNOTACTIVE Channel does not have active transaction running Explanation No transaction currently active on channel Occurs only in the V2 command environment and is retained for compatibility with previous versions of RTR RTR E CLASSREQ At least one data class definition required Explanation At least one data class definition required in call to rtr_ request_info D 2 RTR Utility Error Messages 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 The application may retrieve the reason for the channel closure by calling the receive_message verb to receive the mt_closed message RTR I CMDIGNORE Command ignored for defined facility role Explanation ndicates that the command is
118. RN_TO_SENDER NORETURN_TO_ SENDER TYPE_OF_DATA data type TYPE_OF_DATA STRING The CALL RTR_SEND_TO_SERVER command causes a command server to call the rtr_send_to_server routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_send_to_server routine itself is described in Application Programme s Reference Manual The prototype of rtr_send_to_server is rtr_status_t rtr_send_to_server rtr_channel_t channel rtr_sen_flag_t flags rtr_msgbuf_t pmsg rtr_msglen_t msglen rtr_msgfmt_t msgfmt dG Table 6 14 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call 6 38 RTR Command Line Interface 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 msglen message definition parameter list with msgfmt positional qualifiers 1 The actual values used for pmsg msglen and msgfmt are based upon the message definition you specify as a command line parameter Qualifiers The command server uses message data specified as command line parameter values to generate a record
119. RTR is started from the Service rather than via a Command Prompt window several files are created in the RTR root directory SrvcIn Txt is created to act as a command line input source SrvcOut Txt acts as a container for console output RTRStart RTR contains the startup commands When the Service stops RTR it recreates SrvcIn Txt and creates RTRStop RTR for stopdown commands Creation of these files is unconditional that is they are created every time RTR is started or stopped whether or not they already exist RTR will thus ignore and overwrite any changes made to one of these files Starting and Setting Up RTR 2 17 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 2 12 1 Role This section discusses how RTR assigns roles to backend node partitions and how routers are selected Assignment for Backend Node Partitions RTR assigns a primary or secondary processing state to a partition or a key range definition consisting of one or more server application channels which may or may not share a common process All such server channels belonging to a given partition will have the same processing state on a given node However the processing state for the same partition will normally be different on different nodes The exception is the case of the standby processing state Because a given partition can have multiple standby nodes several of
120. RTR version Related Commands e STOP RTR e START RTR Example RTR gt SHOW RIR 1 RTR running on node baby home dec com in group develpr 2 1 Show the state and configuration of RTR 2 RTR has been started in group mode for group develpr 6 162 RTR Command Line Interface SHOW SEGMENT SHOW SEGMENT Format Description Qualifiers Display the type and size of routing key segments SHOW SEGMENT Command Qualifiers Defaults CLUSTER NOCLUSTER FACILITY FACILITY FULL NOFULL NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SHOW SEGMENT command displays the routing key segment definitions The routing key definition is common to all servers in a facility The routing key specifies the data within a message sent from clients used to route the message to a particular key range server The position length and data type of each key segment is displayed 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 command is executed only on the node where the command was issued Note In environments that do not support clustering use of the CLUSTER qualifier will cause the relevant command
121. RTR_ MAX_FE_NAM LEN Explanation Status return indicating that the supplied value for the frontend name string exceeded the permitted maximum of RTR_MAX_FE_ NAM_LEN characters RTR E FLDNFND Field A not found Explanation Field not found in call to rtr_request_info RTR 1 FORCEDEXI Forcing RTR application exit process A PID A Explanation Displays the name A and PID B of the processes that were forced to exit due to the execution of a STOP RTR command RTR F FUNCNOTSUP Function not supported Explanation Function not supported RTR GRPMODCHG Group changed from A to A Explanation RTR group changed from A to B RTR I HIGBNDHEX High bound is A hex Explanation Displays the high bound of the server key range RTR E HLBNCPTBL Format of help library A is unknown Explanation The specified help library has an unknown format RTR HLPNOTFND No help available help file A not found Explanation The help file specified by the RTRHELP environment variable cannot be found or cannot be opened RTR E ILLDEVTYP Device A is unsuitable for journals Explanation RTR can only create its journal files on directory structured devices Reissue the CREATE J OURNAL command specifying a disk D 8 RTR Utility Error Messages RTR Utility Error Messages RTR E ILLPARTCHAR Legal characters are alphanumeric and under score Explanation Illegal chars in partition name argument RTR E ILLREMDEV De
122. Reliable Transaction Router System Manager s Manual Order Number AA Q88CE TE June 1999 This manual describes how to configure manage and monitor Reliable Transaction Router Version 3 2 RTR Revision Update Information This manual supersedes Version 3 1D of the System Manager s Manual Software Version Reliable Transaction Router Version 3 2 Compaq Computer Corporation Houston Texas J une 1999 COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING PERFORMANCE OR USE OF THIS MATERIAL THIS INFORMATION IS PROVIDED AS IS AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES EXPRESS IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR PARTICULAR PURPOSE GOOD TITLE AND AGAINST INFRINGEMENT This publication contains information protected by copyright No part of this publication may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation Digital Equipment Corporation 1999 All Rights Reserved The software described in this guide is furnished under a license agreement or nondisclosue agreement The software may be used or copied only in accordance with the terms of the agreement Compaq and the Compaq logo are registered in the United States Patent and Trademark Office The follo
123. S Transaction ID A Explanation Displays the transaction id A in messages relating to transactions RTR log messages E 13 A Active Monitor 5 2 Aggregation of Data Items A 5 Backend 2 1 BAR DISPLAY 6 67 Broadcast Monitor 5 2 C Call Rtr_accept_tx 6 3 rtr_prepare tx 6 22 CALL RTR_BROADCAST_EVENT 6 6 RTR_CLOSE_CHANNEL 6 10 RTR_ERROR_TEXT 6 12 RTR_GET_TID 6 13 RTR_OPEN_CHANNEL 6 15 RTR_RECEIVE_MESSAGE 6 25 RTR_REJ ECT_TX 6 28 RTR_REPLY_TO_CLIENT 6 31 RTR_REQUEST_INFO 6 35 RTR_SEND_TO_SERVER 6 38 RTR_START_TX 6 42 Call out server 2 7 Calls Monitor 5 2 Channel Monitor 5 2 CHANNEL SHOW 6 129 CLEAR 6 45 A 2 CLI call interface RTR_ACCEPT_TX 6 3 rtr_broadcast_event 6 6 RTR_CLOSE CHANNEL 6 10 RTR_ERROR_TEXT 6 12 RTR_GET_TID 6 13 RTR_OPEN_CHANNEL 6 15 RTR_PREPARE_TX 6 22 Index CLI call interface cont d RTR_RECEIVE_MESSAGE 6 25 RTR_REJ ECT_TX 6 28 RTR_REPLY_TO CLIENT 6 31 RTR_REQUEST_INFO 6 35 RTR_SEND_TO SERVER 6 38 RTR_START_TX 6 42 Client 2 2 CLIENT SHOW 6 131 Command procedures 1 3 Command recall 6 104 Congest Monitor 5 2 Connects Monitor 5 2 Create Facility 2 1 CREATE FACILITY 6 47 JOURNAL 2 3 6 51 PARTITION 6 54 D Data items 5 1 A 1 DCL interface 6 1 ddtm Monitor 5 2 DEFINE KEY 6 57 DELETE FACILITY 2 4 6 61 JOURNAL 6 63 PARTITION 6 65 Display Expressions A 3 DISPLAY A 2 BAR 6 67 NUMERIC 6
124. S does not play a role in the determination of RTR ACP quotas RTR uses AUTHORIZE quotas for the command line interface and communication server COMSERV Virtual memory sizing for the RTR ACP are determined through the qualifiers of the START RTR command 2 8 2 UNIX Virtual Memory Sizing The RTR ACP process requires the operator to size the process limits for the ACP before starting RTR on all platforms No direct control of the process quotas of the RTR ACP is offered for UNIX based platforms but log file entries will result if hard limits are found to be less than the preferred values for the RTR ACP The following are the minimum limits for the ACP on the following UNIX platforms e On Compaq Tru64 UNIX A minimum of 1024 open file descriptors A minimum of 1073742 Kbytes for virtual memory address space A minimum of 268436 Kbytes for a single file size 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 O for CPU time e On Sun Solaris A minimum of 256 open file descriptors A minimum of 1073742 Kbytes for virtual memory address space A minimum of 268436 Kbytes for a single file size 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 O for CPU time e OnIBM
125. SACTION Frontend transaction data items TR_TRANSACTION Backend transaction data items BE_TRANSACTION Router transaction data items UNDERLINE Boolean expression NOUNDERLINE D Specifies that the displayed value is underlined if Boolean expression evaluates to True non zero VALUE value type VALUE CURRENT D Specifies how the value is processed before being displayed Value type can be one of the following keywords e CURRENT default display the current value of expression e AVERAGE display the average value of expression since the MONITOR command was issued e MINIMUM display the minimum value of expression since the MONITOR command was issued e MAXIMUM display the maximum value of expression since the MONITOR command was issued Use the MONITOR RESUME command to reset average maximum or minimum values WIDTH field width WIDTH 1 D Specifies the width in number of characters to display a numeric If more characters than width are required then the number will be shifted to the right No data will be lost but columns of numbers will no longer line up If WIDTH 1 is specified the default then numbers are displayed left justified 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 DISPLAY command Y row Y next free row D
126. SPLAY command Related Commands e MONITOR e SHOW DISPLAY e CLEAR e DISPLAY BAR e DISPLAY SYMBOLIC e DISPLAY TEXT Examples See Section A 1 for examples of how to use the DISPLAY STRING command 6 80 RTR Command Line Interface DISPLAY SYMBOLIC DISPLAY SYMBOLIC Format Description Parameters Qualifiers Display a text in a monitor picture depending on the result of an expression evaluation DISPLAY SYMBOLIC expression text string text string Command Qualifiers Defaults BELL Boolean expression NOBELL BLANK Boolean expression NOBLANK BLINK Boolean expression NOBLINK BOLD Boolean expression BOLD REVERSE NOREVERSE UNDERLINE Boolean expression NOUNDERLINE X column Column of previous item Y row Next free row The DISPLAY SYMBOLIC command displays one of the text strings depending on the value of expression The first string is output if the expression s value is zero 0 the second string is output if the expression s value is 1 and so on If the expression has a value for which there is no corresponding entry in the list of texts then the value itself is printed Note that there is a limit of 255 characters on the size of one command to RTR so large numbers of long strings should be avoided The command can be used within a monitor file or issued at the RTR prompt when interactively defining a monitor picture for use in a subsequent MONITOR command expression
127. State declared rcpnam CHAN3 User Events 259 RTR Events 0 Figure B 3 describes the client state changes which appear in the State field Figure B 3 Client States Requester Stale Transiiions B 8 Server Shadowing and Recovery 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 gt show partition router full Facility RTRSDEFAULT_FACILITY State ACTIVE Low Bound 0 High Bound 4294967295 Failover policy fail_to_standby Backends depth States active Primary Main depth Shadow Main Backend partitions RTR gt show partition backend full Partition name RTRSDEFAULT_PARTITION_16777217 Facility RTRSDEFAULT_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 Revrd 0 Failover policy fail_to_standby Key range ID 16777217 Partition name RTRSDEFAULT_PARTITION_16777218 Facility RTRSDEFAULT_FACILITY State active Low Bound nnnn High Bound 2222 Active Servers 0 Free Servers 1 Transaction presentation active Last Revy BE Txns Active 0 Txns Revrd 0 Failover policy fail_to_standby Key range ID 16777218 Figure B 4 describes the partition state changes which appear in the State field Figure B 4 Router Partition States
128. TIME 2 DISPLAY NUMERIC RTR_SOME_DATA_ITEM 3 X 1 Y 3 LABEL SOME DATA ITEM il DISPLAY NUMERIC RTR_ANOTHER_DATA_ITEM 4 X 1 Y 4 LABEL OTHER DATA ITEM ONITOR 5 RTR gt CLEAR X 25 Y 1 6 RTR gt RTR gt DISPLAY TEXT X 25 Y 1 THE NEW PICTURE AT STIME 7 SHOW DISPLAY OUTPUT MYPICTURE MON 8 Any items from previously displayed pictures are cleared A title is displayed on the first line The symbol STIME is substituted by the current system time when the picture is displayed See Section A 2 Substitution Symbols The data item called RTR_SOME_DATA_ITEM is displayed on the third line The data item called RTR_ANOTHER_DATA_ITEM is displayed on the next line Note that if X and Y are omitted the item is displayed on the next free line and in the same column as the previous item The monitor picture is displayed on the screen Figure A 1 shows what would appear on the screen at this point The title is removed from the picture definition A new title is added This technique can also be used to make small alterations to standard monitor pictures The definition of the picture is saved in the text file MYPICTURE MON The saved picture can be redisplayed by entering MONITOR MYPICTURE A 2 Creating Monitor Pictures 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 SO
129. TOR command These may have been read in from a display file using the MONITOR file spec command or entered interactively using DISPLAY commands The item definitions are shown in DISPLAY command format The command SHOW DISPLAY OUTPUT file may be used to create new monitor files ALL NOALL D Specifies that all monitored items are shown 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 X column Y row Specify that the single item in position column row is shown Related Commands e MONITOR e DISPLAY NUMERIC e DISPLAY BAR e DISPLAY TEXT RTR Command Line Interface 6 133 SHOW DISPLAY Examples RTR gt MON CALLS 1 RTR gt 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 Ws WIDTH 9 1 Display the CALLS monitor picture 2 Show all the items contained in the monitor picture 3 Theitems are displayed in DISPLAY command format See the description of the relevant DISPLAY commands for a description of the various qualifiers Examples See Section A 1 Interactive Definition of a Monitor Picture for an example of how to use the SHOW DISPLAY command 6 134 RTR Command Line Interface
130. TR log xi 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 rt rdoc compaq com Include the title of the manual section and page numbers with your comments or suggestions Conventions Table 1 describes the conventions used in this guide xii Table 1 Conventions Used in this Guide Convention Meaning UPPERCASE lowercase Return Ctrl C user input filesystem italic text boldface text y text HTML 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 Commands typed to the RTR CLI are not case sensitive unless enclosed in quote marks A number sign is the default operating system superuser prompt A percent sign is the default operating system user prompt on UNIX systems A dollar sign is the default operating system user prompt on OpenVMS systems In examples a boxed symbol indicates that you must press the named key on the keyboard This symbol indicates that you must press the Ctrl key while you simultaneously press another key in this case C In interactive examples t
131. The expression to be evaluated Expression can either be the name of a single data item or an expression combining several data items using simple arithmetic operations and constants In the latter case the data items must all be of the same type and EXPRESSION must be enclosed in quotation marks BLANK Boolean expression NOBLANK D Specifies that the displayed value is replaced by blanks if Boolean expression evaluates to True non zero BLINK Boolean expression NOBLINK D Specifies that the displayed value blinks if Boolean expression evaluates to True non zero RTR Command Line Interface 6 81 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 visual attributes swapped if Boolean expression evaluates to True non zero 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 is 1 By default items are displayed in the same column as defined by the previous DISPLAY command Y row Y next free row D Specifies the screen row where the item is display
132. This command starts a new transaction with a timout of 5000 milliseconds RTR gt CALL RTR_START_TX TIMEOUT_MS 5000 SRTR S OK Normal successful completion 6 44 RTR Command Line Interface CLEAR CLEAR Format Description Qualifiers Interactively remove one or more displayed items from a monitor picture CLEAR Command Qualifiers Defaults ALL NOALL X column Y row The CLEAR command enables you to interactively remove one or all of the displayed items from a monitor picture The picture can then be redisplayed using the MONITOR RESUME command CLEAR ALL removes all the displayed items from the screen and is useful when commencing interactive definition of a new picture Either ALL or X and Y must be given ALL NOALL D Specifies that all the items are to be removed from the monitor picture This is usually used when commencing the interactive definition of a new picture X column Y row Specify that the item in position column row is to be removed from the monitor picture This enables mistakes to be corrected when interactively modifying monitor pictures It can also be used to remove unwanted items from predefined monitor pictures Related commands e MONITOR e SHOW DISPLAY e DISPLAY NUMERIC e DISPLAY BAR e DISPLAY TEXT RTR Command Line Interface 6 45 CLEAR Examples See Section A 1 Interactive Definition of a Monitor Picture for an exam
133. W LINK Format Description Parameters Qualifiers Display the configuration and status of the links to other nodes 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 OUTPUT stdout STATE NOSTATE The SHOW LINK command shows the configuration and status of the links toRTR nodes If no qualifiers are given a brief display of the links is shown node name Specifies the name of a node the parameters for the link to this node are displayed Node name may contain wild cards and in which case all matching links will be displayed If node name is omitted all known links are displayed 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 command is executed only on the node where the command was issued 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 COUNTER counter name NOCOUNTER D Specifies that the link counters are also to be displayed Counter name is the name of the counter to
134. XTNBE Facility A extended with backend A Explanation The configuration of facility A has been extended to include node B as a frontend RTR I FACEXTNFE Facility A extended with frontend A Explanation The configuration of facility A has been extended to include node B as a frontend RTR I FACEXTNTR Facility A extended with router A Explanation The configuration of facility A has been extended to indude node B as a router RTR I FACLOSTBE Facility A lost Backend node A Explanation A connection has been lost with backend node B on facility A E 4 RTR log messages RTR log messages RTR I FACLOSTFE Facility A lost Frontend node A Explanation This node is no longer a current router on facility A for frontend 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 FACNOTDEC Facility name not matched Explanation Result of a connection attempt to a remote node specifying a facility that does not yet exist on the remote node Check that the facility name and configuration matches on all nodes concerned If connecting toa V2 system facility names must be specified in upper case RTR I FACSTART Facility A started on node A Explanation Facility A initialized on node B RTR I FACSTARTBE Facility A started on node A as Backend Explanation A connection has been established with ba
135. a items and constants as parameters for display commands or as Booleans in the BELL BLANK BLINK BOLD SELECT REVERSE and UNDERLINE qualifiers you may use the operators shown in Table A 3 Creating Monitor Pictures A 3 Creating Monitor Pictures A 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 pes Greater than or equal Not equal Not equal Less than VA 0 Greater than Equal Example A 2 shows how these operators are used Example A 2 Arithmetic Operators Examples RTR gt DISPLAY NUMERIC RTR_SOME_DATA_ITEM 2 1 RTR gt MONITOR RTR gt DISPLAY NUMERIC RTR_SOME_DATA_ RTR gt SELECT RTR_SOME_OTHER_DATA_ITEM gt 42 2 RTR gt MONITOR RTR gt DISPLAY NUMERIC RTR_SOME_DATA_ITE TR gt SELECT RTR_SOME_OTHER_DATA_ITEM gt 42 TR gt BOLD RTR_SOME_OTHER_DATA_ITEM gt 84 _RTR gt UNDERLINE RTR_SOME_OTHER_DATA_ITEM gt 1952 3 RTR gt MONITOR RTR gt DISPLAY SYMBOLIC RTR_SOME_DATA_ITEM zero one RTR gt two three four five six BLINK 4 _R R 1 Twois added to the value of RTR_SOME_DATA_ITEM before displaying it 2 RTR_SOME DATA ITEM is only displayed if RTR SOME OTHER _DATA_ ITEM is greater than 42 3 Same as the one above but displayed in bold if RTR_SOME_OTHER_DATA_ ITEM is greater than 84
136. a partition information SHOW PARTITION Command Qualifiers BACKEND BRIEF CLUSTER FACILITY FULL NODE node list OUTPUT file spec ROUTER Defaults BACKEND NOBRIEF NOCLUSTER FACILITY NOFULL NODE default node list OUTPUT stdout ROUTER The SHOW PARTITION command displays information about key range partitions their states and current transaction activity This information is useful for diagnosing bottlenecks or partition difficulties in RTR The States field of SHOW PARTITION BACKEND can display the following values Table 6 20 Key Range Siates State Meaning wt_tr_ok Server is waiting for routers to accept it wt_quorum Server is waiting for backend to be quorate Icl_rec Local recovery Icl_rec fail Primary server waiting for access to a restart journal Icl_rec_icpl Getting next journal to recover from Icl_rec cpl Processed all journals for local recovery shd_rec Shadow recovery shd_rec fail Shadow server waiting for access to a restart journal shd_rec_icpl Shadow getting next journal to recover from shd_rec cpl Processed all journals for shadow recovery catchup Secondary is catching up with primary standby Server is declared as standby 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 The State field of SHOW PARTITION ROUTER can display th
137. aati avis oa die ee a eG tae eo es Monitor ROUtINQ ooccccccccocooo a a A Monitor RSCBE cuicos a g am aE A e ala Monitor RTR sis oiana to boc at teh a aai a de dd ar Deba dd Monitor Stalls asas nke pu in ca a cd ad RAU a Montor SYSTERN airaa re Vile e Sa EEE EE EO ar EARE E E E E re Monitor TPS ua ia a aa o Goes alte na bs aia Monitor Tratfic citadas dare a e be be dba dk Monitor ran Soo a ao iaa alas Hen anya Monitor VZEALES 2 andara tra ara aa MONITOR XA cd Sag att aad hot ata O oa 6 RTR Command Line Interface 6 1 6 2 NTTOCUCHAI ON ie i e iie ere ai id A Ai wk ale a halen RTR Command Reference 0 0 00 eee eee eee ADOFACIL vos ds orador dirias CALL RTR_ACCEPT_ TX 585 o il rd CALL RTR BROADCAST EVENT coria rod CALL RTR CLOSE CHANNEL asicuaicrisows ica dened sews de CALL RTR_ERROR TEXT ccc cece eee e cece rc CALL RTR_GET TD acarrea CALL RTROPEN CHANNEL ire add CALL RTR PREPARE Tico dodo scr roda Ores os CALL RTR_RECEIVE_MESSAGE c0c cee eee eee o CALL BER REV ECT_TX ois peros ese CALL BEROREPLY TO CLIENT dios an CALL RTR_REQUEST_INFO 0 0 00 cece cece oo CALL RTR_SEND_TO SERVER 0 0 cc cece eee ee cc CALL PER SIA rr e e a a E E e CREATE JOURNAL oca sua sike meali kede ia tata srie me a Nk Bis ke Hal g da CREATE PARTITION siini anita cot tne tae ia a wee aan iaie soe Soe Gas a DEFINE REY siny iea aa aa de aa a a Rae ete AE eae ee DELETE FACILITY abarri idia it ninio mode Ode n
138. access rtr_numseg_t numseg rtr_keyseg_t pkeyseg da Table 6 7 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 7 Parameters for rtr_open_channel C Parameter Name C Parameter Value Example channel CHANNEL_NAME name flags RTR_NO_FLAGS none D RTR_F_OPE_CLIENT CLIENT RTR_F_OPE_SERVER SERVER RTR_F_OPE_BE_CALL_OUT BE_CALL_OUT RTR_F_OPE_NOCONCURRENT NOCONCURRENT RTR_F_OPE_EXPLICIT_PREPARE PREPARE_EXPLICIT RTR_F_OPE_EXPLICIT_ ACCEPT ACCEPT_EXPLICIT RTR_F_OPE_FOREIGN_TM FOREIGN tm_id RTR_F_OPE_SHADOW SHADOW RTR_F_OPE_NOSTANDBY NOSTANDBY RTR_F_OPE_TR_CALL_OUT TR_CALL_OUT facnam CASH FACIL FACILITY_NAME CASHFACIL rcpnam CLI6CHAN RECIPIENT_NAME CLI6CHAN pevtnum All events See EVENTS EVENTSHUSER RTR access J 67T F098 JACCESS3 67TF098 numseg 1 pkeyseg gt ks_type rtr_keyseg_string TYPE_OF_FIELD STRING gt ks length 10 LENGTH_OF_FIELD 10 gt ks_offset 2 JOFFSET_OF_KEY 2 gt ks_lo bound AAAAAAAAAA LOW_BOUND AAAAAAAAAA gt ks_hi_bound NNNNNNNNNN HIGH_BOUND NNNNNNNNNN Qualifiers ACCEPT_EXPLICIT NOACCEPT_EXPLICIT Specifies that the RTR_F_OPE_EXPLICIT_ ACCEPT flag is set in the call to rtr_open_channel 6 16 RTR Command Line Interface CALL RTR_OPEN_CHANNEL ACCESS access NOACCESS D Specifies an access string that is a password All application programs clients an
139. acility ALL Abs Rate 10 20 30 40 50 60 70 80 90 100 Starts 116641 25 1 Enqueues 116641 20 01 Commits 116641 25 6 Aborts 0 0 0 Displays information on a router node It gives an indication of the utilization of the router in terms of transactions and broadcasts routed through this node Useful to monitor performance or locate problems Uses counters in the Transaction Manager TM subsystem 5 2 28 Monitor Routing ROUTING STATISTICS BY FACILITY Thu Apr 15 1999 14 34 20 NODE ALL Transactions Broadcasts Absolute Rate Absolute Rate Total 118489 39 2 68444 994 0 VIP 118489 39 2 68444 994 0 Displays statistics of transaction and broadcast traffic by facility Rate is the number of transactions or broadcasts per second within the monitoring interval 5 16 RTR Monitoring RTR Monitoring 5 2 Standard Monitor Pictures 5 2 29 Monitor RSCBE RTR gt 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 Image Name RTR EXE T delta RSC calls router state 0 send_dcl_to_ master sfranc wait_for_response 1 recv_status_ok sfranc rstart_rvy 1 send_dcl_to_master sfranc rstart_rvy_incomp 1 recv_status_ok sfranc rstart_rvy 1 send_dcl_to_master sfranc rstart_rvy_incomp 1 recv_status_ok sfranc active 1 send_dcl_to_other depth active 1 recv_status_ok depth active 4 15 18 22 1999 seq_nr PRPrPRPRRrEErO Displays backend request
140. action Router Installation Guide for instructions for installing RTR 1 1 Getting Started RTR applications use the API calls described in the Reliable Transaction Router Application Programmer s Reference Manual Before an RTR application can be used RTR must be started on every node in your RTR network You do this is by issuing a START RTR command on each node You may wish to include the START RTR command in a startup command procedure for each node so that RTR is started whenever a node is booted Many applications can use RTR at the same time without interfering with one another This is achieved by defining a separate facility for each application A facility can be thought of as an application s own runtime environment of RTR In addition distributed RTR applications may start and execute many transactions RTR is capable of massively parallel operation Before application processes are started a facility must be defined using the CREATE FACILITY command You may wish to include the CREATE FACILITY command to the command procedure used to start the application The rest of this chapter explains how to use RTR commands The START RTR and CREATE FACILITY commands are described in detail in Chapter 2 and Chapter 6 1 2 Entering Commands RTR is started configured and maintained by using the RTR Command Line Interface CLI The RTR CLI is used to start set up and monitor the operation of RTR
141. al blocks as a percentage of the total are also provided The local journal figures refer to journal usage for the displayed node Standby journals are journals of standby nodes that are being accessed due to restart or catch up situations Under normal conditions standby journal figures are all zero The bar graphs appear under the first line of the display NL_LCL_BLOCKS IN_USE 5 2 16 Monitor Link LINK COUNTERS 8 MAR 1999 14 24 44 NODE ALL LINK CF_PROTOCOL 0 O_WRITING 0 CF_TIMEOUT 0 O_READING 0 CF_LINKEXIT 0 O_WRERROR 0 CF_DISCONNECT 0 O_RDERROR 0 CF_THIRDPARTY 0 O_RDINCMP 0 CF_PATHLOST 0 O_SEQERR 0 CF_RESPONSES_SENT 3 O_BUFOVF 0 CF_QUERIES_RCVD 11 O_READS_ACTIVE 3 CF_RESPONSES_RCVD 2 O_WRITES_ACTIVE 0 CF_QUERIES_SENT 10 O_BYTES_RCVD 44206961 CF_IPT_MSGS_RCVD 16 O_BYTES_SENT 44206996 CF_IPT_MSGS_SENT 16 O_PCKTS_RCVD 412114 CF_LINK_GAIN 4 O_PCKTS_SENT 412114 CF_LINK_LOSS 0 O_MSGS_RCVD 189284 CF_ABORTED 0 O_TMO_SENDS 161307 CF_REJECTEE 1 ORM_REO_LINK_QUEUE 0 CF_ACCEPTED 1 ORM_RSP_LINK_QUEUE 0 CF_CONFTRMED 1 CF_INITIATED 2 ALL gt ALL Displays a number of per link counters The LINK link name qualifier can be used if the values for one specific link are to be displayed otherwise the total values for all links are displayed 5 2 17 Monitor Netbytes LINK TRAFFIC IN BYTES Fri Apr 16 1999 17 41 12 NODE nodea zko dec com Bytes Rcvd Abs Rate Total 592014
142. alifiers CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use 6 28 RTR Command Line Interface 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 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 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 RETRY NORETRY D Use RETRY to specify the flags parameter as RTR_F_REJ RETRY in the call rtr_reject_tx The default for value for RETRY is NORETRY which causes the command server to use the value RTR_NO FLAGS for the flags parameter in the call to rtr_reject_tx 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 comma
143. ames and delete or move the duplicate journal file or b Reissue the CREATE JOURNAL SUPERSEDE command in this case any recovery information in the old journal is lost RTR E DUPLPARTNAME Duplicate partition name Explanation Duplicate partition argument RTR E DUPLRMNAME Duplicate rm partition name Explanation Duplicate partition argument RTR E DUPNODNAM Duplicate node name A Explanation The node name list specified with the FRONTEND ROUTER or BACKEND qualifiers on an CREATE FACILITY command contained the node name A more than once RTR E EMPTYREQ Request_info list is empty Explanation Empty list supplied to rtr_request_info RTR I ENABMOD A mode enabled Explanation Displays the name A of the mode that was enabled after issuing a SET MODE command RTR E ENODNANAM DECnet definition required but not found for node A Explanation A node name was specified in a context that required a successful lookup for the DECnet address but none was available This can occur when DECnet is explicitly specified through use of a node name prefix dna or when DECnet is the only enabled network transport Check the network node name database on the local node and the network name server DNS RTR E ENOIPNAM IP definition required but no host definition found for A Explanation A host name was specified in a context that required a successful lookup for the IP address but none was ava
144. an expression NOBLINK D Specifies that the displayed value blinks if Boolean expression evaluates to True non zero BOLD Boolean expression NOBOLD D Specifies that the item is displayed in high intensity if Boolean expression evaluates to True non zero DAMPING damping factor NODAMPING D Specifies that the value displayed is to fluctuate more slowly than the raw measured value The default for damping factor is one Damping is only relevant if VALUE CURRENT DECIMALS decimal places DECIMALS 0 D Specifies the number of digits to appear after the decimal point when displaying a numeric The default for decimal places is zero that is numbers are displayed as integers 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 RTR Command Line Interface 6 73 DISPLAY NUMERIC RATE interval NORATE 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 This has no effect on the sampling it simply allows the rate to be displayed in another unit For example displaying the start transaction counter with RATE 60 results in transactions per minute being displayed instead of per second REVERSE Boolean expression
145. anation RTR E NODECNET Network unavailable Explanation DECnet was shutdown on local node when the RTR utility was being used RTR F NODEFDEV No default device found for journal creation Explanation The CREATE J OURNAL command failed because rtr was unable to find a suitable default device for a journal RTR E NODISOLATED Node isolated connection rejected Explanation Autoisolation has isolated the node Connection attempts from the isolated node are refused in this state Connections can be enabled by issuing the following commands o on the isolating node s set link enable lt isolated node gt o on the isolated node set node noisolate This status supersedes the V2 condition LINKSHUT RTR Utility Error Messages D 15 RTR Utility Error Messages RTR E NODNA DECnet specified for A but transport protocol unavailable or disabled Explanation DE Cnet 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 Add an entry for the indicated node to your local node name database or to you name server RTR W NODNANAM DECnet is installed but no node name definition found for A Explanation DE Cnet is active and enabled on the local node but the address lookup for the indicated node failed Since other network transports are available you may continue but protocol failover to DECnet will not be possible following this con
146. anation A previously existing journal was found This status may be returned by the CREATE J OURNAL command 1 You have issued an RTR CREATE J OURNAL command without deleting the previous journal Corrective action a Use the SUPERSEDE qualifier with CREATE JOURNAL or b Delete the old journal with the DELETE J OURNAL command RTR F OUFILMIS RTR journal file missing Find missing file or CREATE J OURNAL SUPERSEDE Explanation One of previously initialized RTR journal files for a backend could not be found This status may be returned by the CREATE FACILITY and SHOW JOURNAL commands Probable causes are 1 One of the disks being used for journalling is unavailable or 2 A user has inadvertently deleted an RTR journal file Corrective action either a Bring the missing disk back on line or b Reissue the RTR CREATE JOURNAL SUPERSEDE command to create a new journal in this case any recovery information in the old journal is lost RTR Utility Error Messages D 11 RTR Utility Error Messages RTR F OUFORCHA Journal format has been changed CREATE JOURNAL SUPERSEDE Explanation The journal file s found have an out of date format This status may be returned by the CREATE FACILITY and SHOW J OURNAL commands after a new version of RTR has been installed on a system Corrective action Issue an RTR CREATE JOURNAL SUPERSEDE command RTR W OUINUSE Journal is locked by another user Explanation The jou
147. and INPUT file spec NOINPUT D Specifies an input file containing one or more shell commands to be executed by the spawned subprocess If you specify a command and an input file with the AINPUT qualifier the command string is processed before the input file Once processing of the input file is complete the subprocess is terminated OUTPUT file spec OUTPUT stdout D NOUTPUT Requests that the output from the SPAWN operation is written to the file spec RTR Command Line Interface 6 171 START RTR START RTR Start RTR on one or more nodes Format START RTR Command Qualifiers CLUSTER NODE node list OUTPUT file spec The following qualifiers are only Command Qualifiers ASTLM ast limit BIOLM io buffered BYTLM buffer limit CPULMstime limit DIOLM io direct ENQLM enqueue limit FILLM file limit JTQUOTAS job table quota LINKS max links PARTITIONS max partitions PGFLQUOTA page file PRCLM subprocess limit PRIORITY priority PROCESSES max processes TQELM queue limit WSDEFAULT working set WSEXTENT extent WSQUOTA max working set Description Defaults NOCLUSTER NODE default node list OUTPUT stdout relevant when running on OpenVMS Defaults Dependent on LINKS and PROCESSES values Dependent on LINKS and PROCESSES values BYTLM 1 000 000 CPULM default time limit Dependent on LINKS and PROCESSES values ENQLM 2000 Dependent on LINKS and PROCESSES value
148. and If no SET ENVIRONMENT command has been entered then the command is executed only on the node where the command was issued 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 INACTIVITY_TIMEOUT secs INACTIVITY_TIMEOUT 60 INACTIVITY_TIMEOUT secs specifies the link inactivity timeout value for all current links and also sets the default inactivity timeout value for new links The default value is 60 seconds See SET LINK INACTIVITY_TIMEOUT for further information ISOLATE NOISOLATE D The ISOLATE qualifier is obsolete and is available for compatibility reasons only Use AUTOISOLATE instead Use NOISOLATE to take a node out of the isolated state See the AUTOISOLATE qualifier for further information 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 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 Examples e SHOW NODE e SET LINK RTR gt SET NODE NOISOLATE This command tells RTR to set the executing node non isolated
149. ard monitor pictures in detail 5 2 1 Monitor ACCFAIL Link Acceptance Failures When configuring RTR it can happen that nodes sometimes fail to connect up Whilst the cause of the error can be viewed on the initiator side with the MONITOR NETSTAT picture it can be difficult to pinpoint the problem when looking at the other end of the link The monitor picture ACCFAIL can be used to display the reason for the local node to refuse to accept connections An example Unacceptable Most recent links on which a connection attempt was declined Node ra rk zko dec com 1 i my w ra rk zko dec com i List entries are reused in a cyclical LENGTH K DEC ZKO DMARK Wed Jan 7 1998 10 51 00 node is not configured for the facility node not recognized facility name not matched node not recognized node is not configured for the facility node not recognized facility name not matched node role definitions do not match for facility name not matched node not recognized recent entry is highlighted Some of the errors that can be displayed by ACCFAIL are 5 4 RTR Monitoring RTR_STS_NOTRECOGNISED node not recognized The local node has received a connection request over a link that is not configured in any facility on the local machine If you expected the connection to succeed as the result of having a template link defined check carefully the names displayed in the monitor picture These
150. ards when specifying RECIPIENT SPEC SERVER NOSERVER D Specifies that the RTR_F_OPE_ SERVER flag is set in the call to rtr_open_channel Use this qualifier if you want to declare the channel as a server SHADOW NOSHADOW D The SHADOW qualifier specifies that the RTR_F_OPE_SHADOW flag is set in the call to rtr_open_channel The server is part of a shadow pair STANDBY D NOSTANDBY The NOSTANDBY qualifier specifies that the flag RTR_F_OPE_NOSTANDBY is set in the call to rtr_open_channel and the server may not be or have standby s By default servers may have standby s TR_CALL_OUT NOTR_CALL_OUT D Specifies that the RTR_F_OPE_TR_CALL_OUT flag is set in the call to rtr_open_channel and the server is a router call out server By default a server is not a router call out server 6 20 RTR Command Line Interface 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 Examples e CALL RTR_CLOSE_CHANNEL This command opens a server channel called RTR DEFAULT CHANNEL that may not have concurrent servers explicitly accepts transactions and listens for all RTR events RTR gt CALL RTR_OPEN_CHANNEL SERVER NOCONCURRENT ACCEPT_EXPLICIT EVENTS RTR SRTR S OK Normal successful completion This command open a client chan
151. are the names obtained from the network transport over which the link connection attempt was received and it is with these that a match with a template wildcard specification link must succeed Bear in mind that the name match s performed in a case sensitive manner Names corresponding to TCP links may or may nor contain 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 e RTR_STS FACNOTDEC facility name not matched The connecting link is configured but the facility that it requests does not exist on the local node e RTR_STS NODENOTCNFG node is not configured for the facility The connecting link is configured on the local node but not as part of the requested facility e RTR_STS ROLESMISMATCH node role definitions do not match for this facility The connecting link is configured in the requested facility but with a different role configuration on the local node e RTR_STS TRNOQUO router has no quorum in facility s The router is unable to accept front end connections since it is not quorate This condition will clear up automatically as soon as the router gains connections to sufficient backends 5 2 2 Monitor ACP2APP RTR ACP to Application Messages Node NodeA PID ALL Process name ALL
152. art ACP Explanation The RTR ACP process could not be started when a START RTR command was issued The subsequent message gives more details RTR E ERRSTARCH Unable to start remote client handler Explanation The RTR remote client handler process could not be started when a START REMOTE_CLIENT_HANDLER command was issued The subsequent message gives more details RTR E EVTNAMILL Unknown event name A Explanation The EVENT qualifier on the open channel command specified an unknown event name RTR E EXPSYNILL Expression has illegal syntax A expected n A1 Explanation The expression is invalid because token A was expected but B was found RTR E EXPTOOCOM Expression too complex n A Explanation The expression A is too complex to evaluate Please submit an SPR RTR S FACADDED Facility A added Explanation Displays the name of the facility that was successfully created after issuing an CREATE FACILITY command RTR E FACALREXI Facility already exists A Explanation The facility A specified with the CREATE FACILITY command already exists RTR S FACCREATED Facility A created Explanation Displays the name A of the facility that was successfully created after issuing a CREATE FACILITY command RTR S FACDELETE Facility A deleted Explanation Displays the name of the facility that has been deleted after issuing a DELETE FACILITY command RTR S FACEXTENDED Facility A ex
153. artition on node Gold loses quorum and is in a wait for quorum state Starting and Setting Up RTR 2 19 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 Alternately the roles of backend nodes can be specifically assigned with the PRIORITY_LIST qualifier to the SET PARTITION command In the previous example the PRIORITY_LIST qualifier can be used to insure that when Bronze fails and then returns to participate in the facility it then becomes the active primary member To insure this the following command would be issued on both backend systems immediately after the creation of the partition SET PARTITION test PRIORITY_LIST bronze gold It is recommended that the same priority list order be used on all partition members If a different list is used then the router will determine the sequence number for conflicting members through the order in which those members joined the facility For example if the above command were issued only on Bronze and Gold had the opposite priority list then the router would assign the lower sequence number to the backend that joined the facility first The PRIORITY_LIST feature is very useful in cluster configurations For example Site A and Site B each contai
154. artition_name ks_lo_bound par_one status rtr_open_channel RTR_F_OPE_SERVER 1 amp partition_name Summarizing to fully de couple server applications from the definition of the partitions to be processed write applications that open server channels where only the required partition name is passed Leave the management of the partition characteristics to the system managers and operators Partition Management 3 3 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 commands can be entered in one of two ways e A command line processed by the RTR command line interface for example RTR gt SET PARTITION e Programmed using rtr_set_info Enter partition commands on the backend where the partition is located Note that commands that affect a partition state only take effect once the first server joins a partition Errors encountered at that time will appear as log file entries Using partition commands to change the state of the system causes a log file entry 3 5 1 Command Line Usage Partition management in the RTR command language is implemented with the following command set e RTR gt CREATE PARTITION e RTR gt SET PARTITION RTR gt DELETE PARTITION The name of the facility in which the par
155. as been successfully started after issuing a START REMOTE_CLIENT_HANDLER command RTR S RTRRCHSTOP RTR remote client handler stopped Explanation Indicates that the remote client handler has been successfully stopped after issuing a STOP REMOTE_CLIENT_ HANDLER command RTR S RTRSTART RTR started on node A A Explanation Indicates that RTR has been successfully started after issuing a START RTR command RTR S RTRSTOP RTR stopped on node A A Explanation Indicates that RTR has been successfully stopped after issuing a STOP RTR command RTR E RTRWASSTO RTR has been stopped Explanation RTR had been stopped when the command when a command was issued which requires RTR to be running RTR S SETTRANDONE ld transaction s updated in partition A of facility A Explanation The requested set transaction command was successfully performed RTR W SETTRANROUTER Cannot process this command coordinator router is still available Explanation RTR SET TRAN command cannot change because router is still available RTR Utility Error Messages D 23 RTR Utility Error Messages RTR F SPUJ OUFIL Spurious RTR journal file found remove extra file or CREATE J OURNAL 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 This status may be returned by the CREATE FACILITY and SHOW J OURNAL commands Probable cause
156. as issued 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 CPULM time limit CPULM default time limit D Specifies the maximum amount of CPU time in delta time allocated to the RTR ACP The unit of time 1imit is ten milliseconds When the time expires the RTR ACP is deleted The default value is established at system generation time A time limit limit of O indicates that CPU time is not restricted RTR Command Line Interface 6 173 START RTR DIOLM io direct DIOLM max links max processes x 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 The default for io direct is automatically calculated based on the values for LINKS and PROCESSES ENQLM enqueue limit ENQLM 2000 D Specifies the maximum number of locks that the RTR ACP can have outstanding at any one time The default for enqueue limit is 2000 FILLM file limit FILLM max links max processes 10 default file limit D Specifies the maximum number of files that the RTR ACP can have open at any one time The default value of file limit is automatically calculated based on the values of LINKS and PROCESSES
157. as primary shadow sec act Server is active as secondary shadow remember Primary is running without shadow secondary 5 2 20 Monitor Queues TRANSACTION QUEUES BY PARTITION 15 JAN 1999 12 42 53 NODE NODEA Partition name Processed Queued Txns Msgs Rplys Txn Msg Svrs NODEASNODEBS16842753 5792 5794 0 2 6 3 Shows transaction queues on a partition basis Uses counters from Transaction Manager TM and the Requester Server configurator RSC 5 2 21 Monitor Quorum QUORUM STATUS BY NODE AND FACILITY Tue Apr 6 1999 10 50 24 NODE NODEA node role counts can be inaccurate for incorrectly configured facilities States bad configuration not connected minority uncertain quorate node roles Node Facility State CNF RCH QRT NODEA RIRSDEFAULT_FACILITY TR quorate BE quorate 2 2 2 NODEA shadow TR quorate BE minority ffranc 4 2 1 Quorum states are shown for router TR and backend BE nodes and roles in the columns State The number of nodes seen as configured CNF reachable RCH and quorate QRT are shown for each node in the columns node roles 5 2 22 Monitor Recovery RECOVERY INFORMATION at Tue Apr 6 1999 10 54 50 on NODEA Last Restart Recovery Shadow Recovery Server Recovery Journal Txns Journal Txns Partition id State Backend Scans Recovered Scans Recovered 16777218 active NODEA 1 0 0 0 16777221 active NODEA 1 0 0 0 16777217 active NODEA 1 0 0 0 Shows the progress of transaction recovery Last recovery backend is
158. at RTR does not check if this amount of space is actually available as the disk space specified by MAXIMUM_BLOCKS is used only on demand by RTR when insufficient space is available in the space allocated by the BLOCKS qualifier B 2 Server Shadowing and Recovery 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 The command MODIFY J OURNAL also accepts the BLOCKS and MAXIMUM_ BLOCKS qualifiers J ournal file extension occurs on demand when RTR detects that a write to journal would otherwise fail due to lack of space J ournal file truncation takes place automatically when blocks are freed Refer to MODIFY J OURNAL for the syntax description of the MODIFY J OURNAL command RTR gt show journal files full RTR journal Disk dev rz3a Blocks 2500 Allocated 1253 Maximum 3500 File rtrjnl anders BRONZE J00 RTR gt B 4 Shadow Site Failure and Journaling If a shadow site fails RTR allows transactions to continue to be processed on the remaining site The intermediate transactions processed by the remaining server or servers are retained by RTR when the failed site restarts these transactions are sent to this site as part of a shadow recovery operation thus bringing the failed site back up to date Since the transac
159. at a remote site A pair of partition instances or standby sets thereof cooperate to provide this replication with provision for automatic recovery of a shadow member restarting after a failure Prior to RTR V3 2 the creation and behavior of a partition was tied to the declaration of server application channels Partitions and their characteristics can now be defined by the system operator This has the following advantages e It allows a further decoupling of the application from its operating environment thus reducing application programming requirements e Allows the system operators to make choices concerning the runtime behavior of the system 3 1 2 What is Partition Management Before RTR V3 2 the management of the state of a partition was an entirely automatic function of the distributed RTR system Starting with RTR V3 2 the system operator can issue commands to control certain partition characteristics and to set preferences concerning partition behavior Partition Management 3 1 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 3 2 1 Default Partition Names Unless supplied by one of the methods described below partitions receive automatically gener
160. ated default names They allow system operators access to the partition command set without the need to change existing application programs or site configuration procedures 3 2 2 Programmer Supplied Names An extension to the rtr_open_channel call allows the application programmer to supply a name when opening a server channel The pkeyseg argument specifies an additional item of type rtr_keyseg_t assigning the following values e ks_type rtr_keyseg_partition indicating that a partition name is being passed e code example gt ks lo bound should point to the null terminated string to use for the partition name e code example gt ks_hi_bound must be NULL Using this model the partition segments and key ranges served by the server are still specified by the server when the channel is opened 3 2 3 System Manager Supplied Partition Names 3 2 4 Name Partitions can be defined by the system manager through the use of the code_ example gt create partition system management command or through use of rtr_open_channel flag arguments The system manager can set partition characteristics with this command and applications can open channels to the partition by name See the Section 3 4 for an example of passing a partition name with rtr_open_channel Format and Scope A valid partition name must contain no more than 63 characters in length and can combine alphanumeric characters abc123 the plus sign the underscore _
161. ation is left right or centered in the available width The keyword may be LEFT RIGHT or CENTERED The WIDTH qualifier must be greater than zero for the USTIFY to operate If the available width is smaller than the string truncation will occur 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 REVERSE Boolean expression NOREVERSE D Specifies that the item is displayed with the foreground and background visual attributes swapped if Boolean expression evaluates to True non zero ROWS nr rows ROWS 1 D Specifies how many rows are used to display the item This is only meaningful if SEPARATE is also specified The default number of rows is one SELECT Boolean expression NOSELECT D Displays the item if Boolean expression evaluates to True non zero 6 78 RTR Command Line Interface DISPLAY STRING SEPARATE keyword NOSEPARATE Specifies that the items being monitored relating to keyword are separated from each other and displayed as a list This allows a number of items to be separated in one qualifier 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 TR_TRANSACTION BE_TRANSACTION Frontend transa
162. ault network transport can be changed to DE Cnet by setting the environment variable RTR_PREF_PROT On Windows 95 and Windows NT you can use one of the following statements in your AUTOEXEC BAT set RTR_PREF_PROT RTR_TCP_FIRST set RTR_PREF_PROT RTR_TCP_ONLY set RTR_PREF_PROT RTR_DNA_FIRST set RTR_PREF_PROT RTR_DNA_ONLY These set the choice of network transport to TCP IP with fallback to DECnet TCP IP only DECnet with fallback to TCP IP or DECnet only For Reliable Transaction Router Version 3 2 for OpenVMS refer to Section 2 10 for further information Trouble shooting network connections If the RTR V3 frontend fails to connect with the RTR V2 router node then you can make a basic check by executing a dlogin from the RTR V3 node to the OpenVMS router node If this fails consult your Network Manager For Compaq Tru64 UNIX machines ensure that the DE Cnet library is installed as usr shlib libdna so 1 For Reliable Transaction Router Version 3 2 for OpenVMS the default network transport is DECnet Starting and Setting Up RTR 2 15 Starting and Setting Up RTR 2 10 Network Protocol Selection on OpenVMS 2 10 Network Protocol Selection on OpenVMS e The default network transport protocol on OpenVMS is DECnet You may change the default to TCP IP by removing this line from RTRSSTARTUP COM DEFINE SYSTEM RTR_PREF_PROT RTR_DNA_FIRST If you are using TCP IP you will need to use the node name prefix d
163. avda ala od oa bate DELETE JOURNAL 5 cocina Same ete aa ge elds DELETE PARTITION coa aa ade ee are ea ee aa 6 1 6 1 6 2 6 3 6 6 6 10 6 12 6 13 6 15 6 22 6 25 6 28 6 31 6 35 6 38 6 42 6 45 6 47 6 51 6 54 6 57 6 61 6 63 6 65 vi DISPLAY BA R segrete rie ee hate oo tle ale ane ele hohe oe ee DISPLAY NUMERIC perisi 6 acaG a oo S ar BEADS PoE i aaa aa 1 5 DISPLAY STRING smiren od da ae bard wae tid hale ae od hoe aii Od dak DISPLAY SY DISPLAY TE MBOLIC mirad tem Paces teach Re pao theese a OM icky q ata eh face utes early e gee a sep da E odos esas at FLUSH NAME CACHE s ra deie aada mardi a ded bah Abe bande ade ae rd EXECUTE BAT narma EXTEND FACILIVY a panta ma makina tia Paws oe pe eal ees INITIALIZE JOURNAL iia seria aia re Gas ea Hd ae rete LOG MODIFY JOURNAL sus cuca Cease eR GE a bk ae eee da MONITOR QUIT RECALL REGISTER RESOURCE MANAGER REGISTER RM SCROLL SET ENVIRONMENT ic ca ianei areia tad eee aa ie Pend SETSFACILIDA stc ete E E a eee SET LINK SET LOG SET MODE SET NODE SET PARTIT ION ai iia cs ti aoe Ge ae Rea eee Sons SET TRANSACTION cosita a ed SHOW CHANNEL ict cide ele da al a a Ses SHOW CLIEN Thi g siisi ta A woe dade aa ae ee a ee SHOW DISPLAY siosaia ete Wie iune Wate ee eae a SHOW ENVI RONMENT sarea so taa oe ce Gen eed tada hee a SHOW FACILITY oei ons notes AO oon OR Ee eee ee be ae Eee SHOW JOURNAL cuuvicinoc
164. be displayed If counter name is omitted then all counters will be displayed Counter name may contain wild card characters FACILITY NOFACILITY D Specifies that the names of facilities using the link are also displayed 6 144 RTR Command Line Interface 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 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 STATE NOSTATE D Specifies that a detailed status of the specified link s is displayed Related Commands Example e SET LINK e CREATE FACILITY HOW FACILITY LINK wn RTR gt SHOW LINK FULL IRON Links To Node iron Address iron zuo dec com Status Outgoing message sequence nr 22 Incoming message sequence nr 22 Current receive buffer size 2048 Current transmit buffer size 2048 Current number of link users 1 Write buffer timed out no Write buffer full may be sent no Write buffer allocated yes I O error detected in write no I O error detected in read no Pipe temporarily blocked no Connection broken no Write issued not completed no Read is pendin
165. ble 6 2 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call 6 6 RTR Command Line Interface 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 message definition parameter list with positional msgfmt2 qualifiers evtnum 42 EVENT_NUMBER 42 rcpspc workstat RECIPIENT_SPEC workstat 1 The actual values used for pmsg msglen and msgfmt are based upon the message definition you specify as a command line parameter Qualifiers The command server uses message data specified as command line parameter values to generate a record containing the message data for the pmsg parameter the message length for the msglen parameter and a record type description for the msgfmt parameter CHANNEL_NAMEschannel 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 window from which the call was issued to uniquely identify which channel to use channel_name is not case sensitive The default for 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
166. bstitution in the text is carried out as if a node data item were being displayed This means that the facility name symbol FACILITY_ NAME the link name symbol LINK_NAME and the process related symbols PROCESS ID PROCESS NAME IMAGE NAME FULL_IMAGE_ NAME are always replaced by the text ALL PROCESS NOPROCESS D Specifies that symbol substitution in the text is carried out as if a process data item were being displayed This means that the facility name symbol FACILITY_NAME and the link name symbol LINK_NAME are always replaced by the text ALL The process related symbols PROCESS_ID PROCESS NAME IMAGE _ NAME FULL_IMAGE_NAME are replaced by the text ALL unless MONITOR IDENTIFICATION process id is used In this case they are replaced by the appropriate strings for the process specified by process id REVERSE Boolean expression NOREVERSE D Specifies that the item is displayed with the foreground and background visual attributes swapped if Boolean expression evaluates to True non zero SELECT Boolean expression NOSELECT D Displays the item if Boolean expression evaluates to True non zero 6 84 RTR Command Line Interface 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 tem is
167. cal node but the address lookup for the indicated node failed Since other network transports are available you may continue but protocol failover to TCP will not be possible following this condition D 16 RTR Utility Error Messages RTR Utility Error Messages RTR E NOKEYSEGS You must specify at least one keysegment use KEY 1 IKEY9 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 F NOKEYW Qualifier name is missing append the name to the slash Explanation A slash character is on the command line but is not followed by a qualifier keyword name RTR E NOLICENSE No license installed Explanation Appropriate license is not installed for the required operation RTR F NOLIST List of parameter values not allowed check use of comma Explanation The command does not accept a parameter list RTR F NONPRINTBLE Command line contains a non printable character Explanation Command line contains a non printable character RTR E NOOUTSTND No outstanding operations on channel A Explanation A SYS SYNCH command was issued but there were no outstanding operations on channel A RTR F NOPAREN Value improperly delimited supply parenthesis Explanation A value supplied as part of a parenthesized value list for a parameter qualifier or keyword is missing a delimiting parenthesis RTR E NORMXASWITCH No dtx rm xa_switc
168. causes a command server to execute the rt r_broadcast_event routine and to display the returned status CALL RTR_BROADCAST_EVENT message field1 message field2 message field1 message field2 Specify the message to be sent if any as one or more comma separated parameter values You can use the TYPE_OF_DATA and LENGTH_OF_DATA positional qualifiers on each parameter value to specify the data type and length of each field Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER EVENT_NUMBER evtnum none FORMAT fmt string NOFORMAT LENGTH_OF_FIELD message lengthDepends on data type see description NODE node list NODE default node list OUTPUT file spec OUTPUT stdout RECIPIENT_SPEC rcpspc NORECIPIENT_SPEC TYPE_OF_DATA data type TYPE_OF_DATA STRING The CALL RTR_BROADCAST_EVENT command causes a command server to call the rtr_broadcast_event routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_broadcast_event routine itself is described in Application Programmer s Reference Manual The prototype of rtr_broadcast_event is rtr_status_t rtr_broadcast_event rtr_channel_t channel rtr_bro_flag_t flags rtr_msgbuf_t pmsg rtr_msglen_t msglen rtr_evtnum_t evtnum rtr_rcpspc_t rcpspc rtr_msgfmt_t msgfmt E Ta
169. ckend node B on facility A RTR I FACSTARTFE Facility A started on node A as Frontend Explanation This node is now a current router for frontend B facility A RTR 1 FACSTARTTR Facility A started on node A as Router Explanation A connection has been established with router node B on facility A RTR FACSTOP Facility A stopped on node A Explanation RTR I FACSTOPPED Facility A stopped on local node Explanation RTR I FACTRMBE Facility A modified A no longer a backend Explanation The configuration of facility A has been modified to exclude node B as a backend RTR I FACTRMFE Facility A modified A no longer a frontend Explanation The configuration of facility A has been modified to exclude node B as a frontend RTR 1 FACTRMTR Facility A modified A no longer a router Explanation The configuration of facility A has been modified to exclude node B as a router RTR I IGNREJ ACCEPTTX Ignoring recovered aborted part TX for committed TX Explanation Status indicating that a part TX in aborted state was recovered from journal However the TX is already in committed state on the recovering node so the aborted part TX is ignored This can happen under unusual circumstances such as where the TX has been rejected on one BE and on another BE the same TX has been later accepted whether because of application inconsistency or due to some condition in RTR such as jour
170. cogiosmccr re B 1 B 3 TheRTR Journal SysteM 2 0 ee B 2 B 4 Shadow Site Failure and Journaling 0 00000 ee eee eee B 3 B 4 1 Maximum J ournal SiZ susa geirum eanne r a a a e a B 4 B 5 Standby for SHadoOWS eitea g aoea e ri e ea E E E E a B 4 B 6 Performance cc a aa Sas Wee a a al ae aa re B 4 B 7 Shadows MAGION 2 04 gee dor dc cc rd Dl te eee B 5 B 8 Application Considerations 0 0 00 es B 5 B 9 SOPVer A a iiaa aa Wee eae a he we eet Ge ee a B 6 B 10 Client States socso iaia eia i tes B 8 B 11 Partition States 2 c d udecars drako a da oad e de ee es B 9 C XA Support C 1 INTFOUCLON 250020 di A od eee ee oe C 1 C 1 1 MONITOR XA ie ci d css aiaa re tee Sedona dead aaah done Whe C 1 C 1 2 New Qualifier to CREATE FACILITY Command C 1 C 1 3 Modified RTR APL secs we ge ah parser need eer ee ee C 2 C 1 4 RTR Open Channel ga emaa iu E a e tes C 2 C 2 Microsoft DTG SUPPOF evo iii ee ee aera eee boa de ee ee C 2 D RTR Utility Error Messages E RTR log messages Index Examples 2 1 Local Configuration of each Node 0 000 cece ees 2 2 22 Remote Setup from one Node 00 eee ee ee 2 3 2 3 Reconfiguration Using Delete and Create Facility 2 5 2 4 Reconfiguration Using Extend Facility 000 sees 2 7 2 5 Configuration of Callout Servers 0 0 0 eee eee 2 8 A 1 Interactive Picture Definition 0 00 c eee A 2 A 2 Arithmetic Operato
171. consistency RTR E BADIDTYP Empty node ID encountered at Ox A Explanation This message indicates that errors have been detected in processing of an internal node identifier The presence of this message indicates a serious problem in the configuration of the network name address databases and RTR will likely be unable to operate correctly Quorum and fault tolerance will be adversely affected Check all network databases for consistency of node amp host name and address consistency RTR E BADNETMSG Bad message received from A check network hardware Indications u u u Yu u Yu Yu Explanation This message is logged when RTR in unable to interpret the content of a network message received from a remote RTR ACP process Message corruption is the most likely culprit If the condition persists consider a network health check The indication numbers printed at the end of the message have meaning to RTR support engineers only RTR I BEINQUO Backend is quorate in facility A Explanation The backend role now has quorum in the facility A RTR W BENOQUO Backend has no quorum in facility A Explanation The backend role has lost quorum for facility A RTR E BEREPLAYQDELETED Replay queue for BE deleted Explanation A transaction in progress on a backend has had its replay queue of replies to the client deleted Please report to RTR Engineering RTR E BMHDRVSN Unrecognised broadcast from A for facility A check netwo
172. ction data items Backend transaction data items Router transaction data items TOTALIZE keyword NOTOTALIZE Specifies that the items being monitored relating to keyword are added together and displayed as a total 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 TR_TRANSACTION BE_TRANSACTION Frontend transaction data items Backend transaction data items Router transaction data items UNDERLINE Boolean expression NOUNDERLINE D Specifies that the displayed value is underlined if Boolean expression evaluates to True non zero WIDTH field width WIDTH 0 D Specifies the width in number of characters to display the string If WIDTH 0 is specified the default then the string is displayed as entered If the width is greater than zero then the USTIFY qualifier is activated RTR Command Line Interface 6 79 DISPLAY 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 DISPLAY command Y row Y next free row D Specifies the screen row where the item is displayed top row is 1 By default items are displayed on the next free row after the item defined by the previous DI
173. d RTR 1 PRTSHDOFF Partition A A shadow state set to off by operator A Explanation Written to log file in response to a user request to change the state of partition shadow state RTR PRTSUSCAN Suspend operation cancelled partition resumed by operator Explanation Status indicating that a pending partition suspend operation has been cancelled as a result of an operator command to resume the partition RTR S PRTSUSPENDED Partition suspended use resume to restart transaction presentation Explanation Status indicating successful completion of partition suspend command Transaction presentation is now halted Use resume to restart RTR E PRTSUSTMO Suspend operation timeout partition still suspending Explanation Status indicating that a time out condition was encountered whilst waiting for a partition to be suspended The partition will still be suspending resume the partition to restart presentation of transactions RTR E PTRARDYSUSP Partition already suspended Explanation Status indicating completion of partition suspend command where the target partition was already suspended RTR E PTRSUSPENDING Partition already suspending awaiting completion of current transactions Explanation Status indicating completion of partition suspend command where the target partition was already suspending Be more patient RTR E RCHALRSTA RTR remote client handler already started Explanation The remote clien
174. d according to the operating system environment that the RTR ACP process is using Compaq strongly recommends that you allocate as much virtual memory as possible While there is no penalty for allocating more virtual memory than is used the result of allocating too little can be catastrophic 2 8 1 OpenVMS Virtual Memory Sizing On OpenVMS the following allowances for additional virtual memory should be made e For each link add an additional 202 Kbytes e For each facility an additional 13 Kbytes plus 80 bytes for each link in the facility e For each client or server application process an additional 190 Kbytes for the first channel e For each additional application channel an additional 1350 bytes It is also necessary to prepare for the number of active transactions in the system Unless the client applications are programmed to initiate multiple concurrent transactions this number will not exceed the total number of client channels in the system This should be verified with the application provider In addition it is necessary to determine the size of the transaction messages in use 1 For each front end e Add one Kbyte per active transaction e Add 250 bytes per message per transaction 2 10 Starting and Setting Up RTR Starting and Setting Up RTR 2 8 RTR ACP Virtual Memory Sizing e Add the size of all messages 2 For each transaction router e Allow one Kbyte for each active transaction 3 For each back end e Al
175. d SHOW RM FULL Refer to Appendix C XA Support for support information about XA Parameters resource_name Specifies the name of the resource to be unregistered Resource names can contain up to 32 characters This argument is required Related Commands REGISTER RESOURCE MANAGER e SHOW RESOURCE MANAGER Examples UNREGISTER RM rmi_1 6 182 RTR Command Line Interface A Creating Monitor Pictures The standard monitor pictures provided with RTR described in Chapter 5 are sufficient for most needs You may also create your own monitor pictures to suit particular needs This appendix tells you how to do this The RTR monitor utility provides a means to continuously display the status of RTR and the applications using it The information displayed is composed of named data items which are continuously updated by RTR The data items can be displayed in various formats and combined using simple arithmetic operators and constants Note that in earlier versions of RTR the data items were known as counters and only contained numeric information The name has been changed to indicate that string data may also be retrieved All RTR data items are associated with an information class When entering a data item in a display command it may be prefixed with a string to indicate which class it belongs to This can speed up the processing of monitor commands Information classes are shown in Table A
176. d depends on the key type If the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for high bound is the largest possible value that can fit in the specified key type If the key bound value length is less than the key length given in length_of_key the key bound will automatically be null padded to the required length Note The KEYn keysegdesc qualifier is an alternative to use of the xxx_OF_FIELD qualifier LENGTH_OF_FIELD key field length LENGTH_OF_FIELD 4 D Specifies the length of the key field in the enqueued messages in bytes Use this qualifier only if the key field type is string since the key length is in all other cases implied by the key type The default value for key length is four bytes LOW_BOUND low bound LOW_BOUND min val for key type D Specifies the lower bound of the key range that the server handles The interpretation of low bound depends on the key type If the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for low bound is the smallest possible value that can fit in the specified key type If the key bound value length is less than the key length given in LENGTH_OF _ FIELD the key bound will automatically be null padded to the required length NODE node list NODE default node list D Specifies that the command is executed on all nodes specifi
177. d 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 parameter in the call to rtr_open_channel The channel is opened as a backend call out server CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL Specifies the name of the window s channel for use in subsequent operations on this channel channel_name is not case sensitive The default channel name is RTR DEFAULT CHANNEL CLIENT NOCLIENT Specifies that the RTR_F_OPE_CLIENT flag is set on the call to rtr_open_channel The channel is opened as a client 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 command is executed only on the node where the command was issued 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 CONCURRENT D NOCONCURRENT Specifying NOCONCURRENT sets the RTR_F_OPE_NOCONCURRENT flag in the call to rtr_open_channel and the server may not be concurrent with other servers By default a server may have other concurrent servers EVENTS event nr li
178. de list OUTPUT file spec OUTPUT stdout FACILITY The DELETE PARTITION command removes the specified partition on the node where the command is issued PARTITION_name The name of the partition to delete The parameter partition_name must be supplied It may be specified as partition_name lt or as facility_name partition_name 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 command is executed only on the node where the command was issued 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 FACILITY Specifies the name of the facility from which the partition is being deleted 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 65 DELETE PARTITION
179. displayed the leftmost column is 1 By default items are displayed in the same column as defined by the previous DISPLAY command Y row Y next free row D Specifies the screen row where the item is displayed top row is 1 By default items are displayed on the next free row after the item defined by the previous DISPLAY command Related Commands Examples e MONITOR e SHOW DISPLAY e CLEAR e DISPLAY NUMERIC e DISPLAY BAR e DISPLAY SYMBOLIC See Section A 1 Interactive Definition of a Monitor Picture for examples of how to use the DISPLAY TEXT command RTR Command Line Interface 6 85 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 the NODE and CLUSTER qualifiers the command can be executed on one or more remote nodes Note that the SPAWN command does not have this ability The DO command is only suitable for commands producing line oriented output use SPAWN if you want to execute a local operating system command that produces screen oriented output for example the OpenVMS MONITOR SYSTEM command or screen mode editors Parameters DCL command The operating system command that you want to execute Qualifiers
180. displayed value is replaced by blanks if Boolean expression evaluates to True non zero BLINK Boolean expression NOBLINK D Specifies that the displayed value blinks if Boolean expression evaluates to True non zero RTR Command Line Interface 6 83 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 facility data item were being displayed This means that the link name symbol LINK_ NAME and the process related symbols PROCESS ID PROCESS NAME 1MAGE_ NAME FULL_IMAGE NAME are always replaced by the text ALL The facility name symbol FACILITY_NAME will be replaced by the text ALL unless MONITOR FACILITY facility name is used in this case FACILITY_ NAME is replaced by facility name LINK NOLINK D Specifies that symbol substitution in the text is carried out as if a link data item were being displayed This means that the facility name symbol FACILITY_ NAME and the process related symbols PROCESS ID PROCESS NAME 1MAGE_ NAME FULL_IMAGE_NAME are always replaced by the text ALL The link name symbol LINK_NAME is replaced by the text ALL unless MONI TOR LINK node name is used in which case LINK_NAME is replaced by node name NODE NONODE Specifies that symbol su
181. dition RTR E NODNOTFND Node A not found in configuration check spelling and case Explanation Unable to locate the referenced node in the current configuration Might occur if the address of the node was changed since it joined the configuration and the name was not entered exactly as displayed in show link output RTR E NODNOTKNO Node not known A Explanation The node A is unknown to DECnet RTR E NODTXOPENSTRING Norm open string specified Explanation No open_string were specified on a CREATE RM command while trying to register an underlying RM XA Resource Manager with ACP RTR E NODTXRMLIB No dtx rm lib pathname specified Explanation No xalib path were specified on a CREATE RM command while trying to register an underlying RM XA Resource Manager with ACP RTR E NOFACILIT No facilities have been defined Explanation No facilities have yet been defined with the CREATE FACILITY command RTR E NOFRONTEN No frontends specified Explanation No frontends were specified on a CREATE FACILITY command and the node where the command was executed was specified as being a router RTR I NOHLPENV No help available environment variable RTRHELP not found Explanation The environment variable RTRHELP that defines where the RTR help files are is not defined RTR W NOIPNAM IP networking is installed but no host definition found for A Explanation P networking is active and enabled on the lo
182. e B1 Node B2 If the relative priority sequence number for Node A2 is changed to four it still becomes the primary active server if Node A1 fails because the failover policy indicates a fail_to standby requirement for this facility SET PARTITION test PRIORITY_LIST Node Al Node B1 Node B2 Node A2 After issuing this command the router partition appears as follows Note the change in relative priorities for the backends Router partitions on node SILVER in group test at Tue Mar 23 13 29 41 1999 State ACTIVE Low bound 0 High bound 4294967295 Failover policy fail_to_standby Backends node al node a2 node b1 node b2 States pri_act standby sec_act standby Relative priorities 1 4 2 3 Primary main node al Shadow main node b1 The following SET PARTITION command can be issued to change the facility so that Node B1 will become the primary active server if Node A1 fails SET PARTITION test FAILOVER_POLICY shadow The FAILOVER_POLICY qualifier is intended for use in selecting a new active primary in configurations where shadowing is enabled This qualifier takes precedence over the PRIORITY_LIST qualifier The PRIORITY_LIST qualifier is intended for use in determining the failover order for specific nodes It is most useful in cluster configurations where it can be used to specify the exact failover order for the nodes within the cluster For example in a standby facility on a cluster of four nodes the PRIORITY_LIST qual
183. e 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 command is executed only on the node where the command was issued 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 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 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 e CREATE JOURNAL e MODIFY JOURNAL e SHOW JOURNAL RTR Command Line Interface 6 63 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 Format Description Parameters Qualifiers Delete an RTR PARTITION DELETE PARTITION PARTITION_name Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default no
184. e following values Qualifiers 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 primary is still recovering BACKEND NOBACKEND D Displays information about backend partitions it shows the partition state and low and high bounds BACKEND with FULL provides more detailed information for a partition giving the current queue depth transactions active on a partition This is useful for determining whether a server is processing transactions correctly Last Revy BE shows from which node recovery information may be fetched Txns Revrd shows the number of transactions actually recovered The default is to output brief router and backend information BRIEF NOBRIEF D Brief output gives a one line listing of each partition in the system showing the partition name the facility in which it resides and the partition state Since space on the line is limited partition names my be truncated to fit 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 ha
185. ecified 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 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 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used REPLY_CHECKSUM NOREPLY_CHECKSUM D Specifies that the reply consistency check or Response Matching feature for replayed messages is enabled It is a check for reply consistency during a replay of a reply to client message RTR can enable disable and display this feature 6 110 RTR Command Line Interface SET FACILITY Related Commands e SHOW FACILITY Examples RTR gt 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 for facility FINANCE This command should be used on all the backend and router nodes in the facility RTR gt SET FACILITY FINANC
186. ecuted 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 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 6 54 RTR Command Line Interface 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 for a partition KEY1 KEY2 up to KEY9 If more than nine key segements are required a named partiton can be created using the rtr_open_channel call The syntax of the KEYn qualifier is KEYn type_of_key signed unsigned string length_of_key nnnn offset_of_key nnnn low_bound string nnnn high_bound string nnnn type_of_key Specifies the field type of the key The key type must be one of unsigned signed or string The default is unsigned length_of_key nnnn Specifies the length of the key field in enqueued messages in bytes For signed or unsigned ints length may be either one two four or eight bytes The default value for key length is four bytes offset_of_key nnnn 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
187. ecuted only on the node where the command was issued 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 IMMEDIATE IMMEDIATE RTR DEFAULT_CHANNEL Specifies the closing of a channel immediately without sending of a transaction acknowledgement Use AMMEDIATE RTR_F_CLO_IMMEDIATE to close the channel and recover any accepted transactions on this channel to an alternate server channel 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used This command closes the RTR DEFAULT CHANNEL RTR gt CALL RTR_CLOSE_CHANNEL SRTR S OK Normal successful completion This command closes the channel named dienti RTR gt CALL RTR_CLOSE_CHANNEL CHANNEL_NAME CLIENT1 SRTR S OK Normal successful completion RTR Command Line Interface 6 11 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 Format CALL RTR_ERROR_TEXT C
188. ed top row is 1 By default items are displayed on the next free row after the item defined by the previous DISPLAY command Related Commands e MONITOR e SHOW DISPLAY e CLEAR e DISPLAY BAR e DISPLAY NUMERIC e DISPLAY TEXT Examples See Section A 1 for examples of how to use the DISPLAY SYMBOLIC command 6 82 RTR Command Line Interface DISPLAY TEXT DISPLAY TEXT Format Description Parameters Qualifiers Display text in a monitor picture 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 PROCESS NOPROCESS REVERSE Boolean expression NOREVERSE SELECT Boolean expression NOSELECT UNDERLINE NOUNDERLINE X column Column of previous item Y row Next free row The DISPLAY TEXT displays the specified text in a monitor picture It can be used within a monitor file or issued at the RTR prompt when interactively defining a monitor picture for use in a subsequent MONITOR command text Specifies the text to be displayed This text may contain any of the substitution symbols See Section A 2 Substitution Symbols BELL Boolean expression NOBELL D Sends a bell character to the terminal if Boolean expression evaluates to True non zero BLANK Boolean expression NOBLANK D Specifies that the
189. ed in node list If node list is omitted then the command is executed only on the node where the command was issued RTR Command Line Interface 6 19 CALL RTR_OPEN_CHANNEL OFFSET_OF_KEY lt 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 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 PARTITION_NAME partition name Enables a system manager to specify a particular named partition PREPARE_EXPLICIT NOPREPARE_EXPLICIT Specifies that the flag RTR_F_OPE_EXPLICIT_PREPARE is set in the call to rtr_open_channel RECIPIENT_NAME rcpnam RECIPIENT_NAME null D Specifies an optional name for broadcast reception to be associated with the channel Only broadcasts matching this name are delivered on the channel Note that to receive named events the correct event number must also be specified RECIPIENT_NAME is case sensitive If RECIPIENT NAME is supplied without a qualifier value then its value defaults to the value of CHANNEL_NAME Not supplying the RECIPIENT_ NAME qualifier has the same effect as specifying a null string Wild card characters cannot be used for this qualifier Senders of broadcasts can use wildc
190. ed only on the node where the command was issued 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 JOIN_TXID txid number NOJOIN_TXID The format of the txid number depends on the TXID_TYPE TXID_TYPE Format of txid number RTR 7 integers of 4 bytes each separated by commas DDIM 4 integers of 4 bytes each separated by commas XA Character string up to 128 bytes of length 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 RTR Command Line Interface 6 43 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 transaction in milliseconds The default value is an infinite timeout TIMEOUT_MS specifies an immediate timeout timeout if no message to receive TXID_TYPE txid type TXID_TYPE RTR D Possible values for TXID_TYPE parameter are RTR DDTM and XA Related commands Examples e CAL zo R_REJEC X CAL zo R_ACCEP X
191. ed then the command is executed only on the node where the command was issued 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 SUPERSEDE NOSUPERSEDE D Specifies how to handle the case where a journal already exists If SUPERSEDE is specified then a journal is created whether or not a journal previously existed unless the previously existing journal is currently in use The previous contents of the journal if any are destroyed 6 52 RTR Command Line Interface CREATE JOURNAL If NOSUPERSEDE is specified default then a journal is created only if no journal previously existed Related commands Examples e DELETE JOURNAL e MODIFY JOURNAL e SHOW JOURNAL RTR gt CREATE JOURNAL SUPERSEDE DISK1 BLOCK 1000 MAX_BLOCK 10000 _RTR gt DISK2 BLOCK 2000 MAX_BLOCK 200000 This command deletes any existing journal files and then creates new ones on DISK1 and DISK2 The target sizes of the journal files are 1000 and 2000 blocks and the maximum sizes are 10 000 and 200 000 blocks respectively RTR gt CREATE JOURNAL dev rz3a dev rz2c BLOCK 1000 MAXIMUM_BLOCK 2000 This command creates journal files on dev rz3a and dev rz2c The target sizes of the journal files is 1000 blocks and the maximum size of the journal on dev rz2c is 2000 blocks
192. edure disk 1 disk n Specifies a list of disk names where journal files are modified Refer to the CREATE JOURNAL command for information about disks used for journal files BLOCKSj nr blocks BLOCKS 1000 D Specifies the size of the journal file in blocks This qualifier can be applied locally to each disk or globally for all disks CLUSTER NOCLUSTER D Specifies that the command is executed on all the nodes in the cluster 6 98 RTR Command Line Interface 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 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 MAXIMUM_BLOCKS nr blocks MAXIMUM_BLOCKS 1000 D Specifies the maximum size that the journal file can use This qualifier can be applied locally to each disk or globally for all disks 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 information is written to
193. efault facility RTR DEFAULT FACILITY is used if this qualifier is not specified 6 126 RTR Command Line Interface 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 ABORT COMMIT DONE EXCEPTION Note that one cannot always change a transaction s state from one legitimate transaction state to another Some state changes are not valid The following table shows state changes that are valid Table 6 19 Valid Transaction State Changes NEW STATE Current State COMMIT ABORT EXCEPTION DONE SENDING YES VOTED YES YES COMMIT YES YES EXCEPTION YES YES PRI_DONE YES 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used PARTITION PARTITION partition_name Specifies the name of a partition from which all transactions are running within A partition name must be supplied Use SHOW PARTITION to view the names of the currently active partitions SINCE date Selects only those transact
194. ent 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 The programmer should retrieve this message by using rtr_receive_message The data accompanying the message is of type rtr_status_data_t The completion status of the partition command can be accessed as the status field of the message data 3 6 Managing Partitions To manage partitions a set of commands or program calls are used Information on managing partitions is provided in this section 3 6 1 Controlling Shadowing The state of shadowing for a partition can be enabled or disabled This may be useful in the following circumstances e Enabling site disaster protection for an application partition for the first time e A recovery aid following prolonged outage of a former shadow site The following restrictions apply Shadowing for a partition can be turned off only in the absence of an active secondary site The active member must be running in remember mode The command will fail if entered on either an active primary or secondary with a message to this effect If entered on a standby of either the primary or secondary the command is accepted but fails in the RTR router This failure is recorded with a log file entry at the router Once shadowing is di
195. entation active Txns Active 0 Failover policy fail_to_standby Partition name Facility RTRSDEFAULT_FACILITY Low Bound nnnn Active Servers 0 Transaction presentation active Txns Active 0 Failover policy fail_to_standby SHOW PARTITION RTRSDEFAULT_PARTITION_16777217 State active High Bound mmmm Free Servers 1 Last Revy BE Txns Revrd 0 Key range ID 16777217 RTRSDEFAULT_PARTITION_16777218 State active High Bound 2222 Free Servers 1 Last Revy BE Txns Revrd 0 Key range ID 16777218 RTR Command Line Interface 6 155 SHOW PROCESS SHOW PROCESS Format Description Qualifiers Display information about processes which are using RTR 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 spec OUTPUT stdout The SHOW PROCESS command displays information about the processes using RTR 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 command is executed only on the node where the command was issued Note In environments that do not support cluste
196. er created or changed for it to be used If a user level copy of RTR_DIRECTORY exists it must identify the same RTR home directory as the system level copy or if there is no system level copy the directory containing the currently registered Service program If it does not behavior of RTR is undefined Changing the value of RTR_DIRECTORY or reregistering the service from another directory while RTR is running is dangerous and should be avoided Starting RTR from the Service then stopping it from DOS or the reverse should also be avoided If you put STOP RTR in the UsrStart RTR file it will stop RTR The Service will not detect that RTR has been stopped and will offer only the STOP action button Pressing the STOP button will fix the problem Similarly when the Service stops RTR it searches the RTR home directory for the file UsrStop RTR and if the file exists execute any RTR commands in it User commands from UsrStop RTR are executed before RTR has stopped WARNING If you put QUIT or EXIT in either UsrStart RTR or UsrStop RTR RTR will exit improperly As a result an RTR command server process incorrectly remains active preventing the Service from starting or stopping RTR and preventing the RTR command server from exiting Because the RTR command server executes under the SYSTEM account it cannot be stopped from Task Manager other than by the SYSTEM account Created by the RTR Windows NT Service If
197. er priority ALTPRI privilege to set the priority higher than your current process Specifies the base priority at which the RTR ACP executes The priority value is a decimal number from O through 31 where 31 is the highest priority and O is the lowest Normal priorities range from O through 15 real time priorities range from 16 through 31 Higher priorities result in faster response but lower priorities may be more CPU efficient and give a higher overall throughput PROCESSES max processes PROCESSES 64 D Specifies the maximum number of processes that can use RTR on this node The max processes value is set to the maximum number of processes allowed by OpenVMS The default is 64 TQELM queue limit TQELM 2000 D Specifies the maximum number of timer queue entries that the RTR ACP can have outstanding at any onetime This number includes timer requests and scheduled wakeup requests The default for queue limit is 2000 WSDEFAULT working set WSDEFAULT 2000 D Specifies the default working set size for the image running in the RTR ACP working set cannot be greater than the working set quota specified with the WSQUOTA qualifier The default for working set is 2000 WSEXTENT extent WSEXTENT 20 000 D Specifies the maximum size to which the image running in the RTR ACP can increase its physical memory size The default for extent is 20 000 WSQUOTA max working set WSQUOTA 10 000 D Specifies the
198. erline characters are all valid but the first character of a facility name must be a letter Facility names are not case sensitive The default value for facility_name is RTRSDEFAULT_FACILITY The ROUTER qualifier and at least one of FRONTEND or BACKEND must be specified RTR Command Line Interface 6 47 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 the order of router node definitions when frontend load balancing is not enabled Nodes defined with the ROUTER qualifier have the higher priority and are followed by nodes defined by the ALL_ROLES qualifier For example in this definition RTR CREATE FACILITY ALL_ROLES mynode ROUTER anode bnode The router nodes are in definition order anode bnode mynode for all frontends except mynode Any node that has both frontend and router roles selects its own router first BACKEND backend list NOBACKEND D Specifies the names of the nodes that are to act as backends for this 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 text file containing a backend list on eac
199. ers facility counters link counters or node counters RTR I NOTSTACOMSRV Could not start command server on node A A Explanation Indicates that a command server couldn t be started on the specified node A RTR F NOVALU Value not allowed remove value specification Explanation A value has been specified for a qualifier that does not take a value Remove the value specification D 18 RTR Utility Error Messages 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 effect and the specified value will be ignored RTR E ONLONENOD Only one node allowed if process ID specified Explanation If a process ID is supplied on MONITOR command then only one node may be monitored RTR E ONLYDISP Only DISPLAY command allowed in this context n A Explanation The specified display file contained a command A other than DISPLAY This is sometimes caused by forgetting the continuation character on the end of a line that is to be continued Use MONITOR NERIFY to find the incorrect command RTR W OPENVMSQUAL Qualifier A is not supported on this platform value ignored Explanation A qualifier has been specified on a command line that is effective
200. ess opens RTR client channels using the same FTM on the one node or if different types of FTMs are used on the same node When a process that has open FTM client channels fails then the FTM must be able to find out from RTR what state the transactions are in that were active in that process Thus the FTM must be able to identify itself to RTR in order that RTR can find out what transactions were active for that FTM channel Generally FTM client channels opened in the same process and for the same FTM can have a common TM identifier but FTM client channels opened in separate processes should have different TM identifiers Calling CALL RTR_OPEN_CHANNEL with the FOREIGN_TM qualifier specified will cause a local journal scan to occur if a journal has not already been opened on that node HIGH_BOUND high bound HIGH_BOUND max val for key type D Specifies the upper bound of the key range that the server handles The interpretation of high bound depends on the key type If the key is of type string then it is interpreted as text otherwise it is interpreted as a numeric value The default for high bound is the largest possible value that can fit in the specified key type If the key bound value length is less than the key length given in LENGTH_OF_ FIELD the key bound will automatically be null padded to the required length KEYn keysegdesc Specifies a partition key segment Up to eight key segments may be defined for a partition KEY1
201. esulting 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 nodes where the router role is removed for this facility router list is a list of router nodes separated by commas If there is more than one router node then router list must be enclosed in parentheses router node is either the name of a node or file spec where file spec specifies a text file containing a router list on each line Related Commands SHOW FACILIT K e DELETE FACILITY e CREATE FACILITY e EXTEND FACILI K RTR Command Line Interface 6 181 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 NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout Description The UNREGISTER RESOURCE MANAGER command unregisters an instance of a resource manager The command succeeds only when no facility references it To unregister a resource manager instance you must first delete all facilities that reference it To see what facilities reference a specific resource manager use the comman
202. etwork object most likely because the network was not available A subsequent entry gives more detail on the error RTR will retry the operation later but the operator should investigate the state of the network RTR E OBJ UNKNOWN RTRACP not running on node A Explanation A connection failed because RTR had not been started or had died on the remote node A RTR E OVERFLOW Table has overflowed resize NCF Explanation This is a general status used to indicate an inadequacy in the static reservations for the tables Send SPR with RTRACP dump RTR PATHLOST Node A unreachable retrying Explanation Node A cannot be reached at present This generally means that RTR is trying to reestablish a connection RTR E PROTOCOL Incorrect protocol in optional data Explanation Internal error in messages between RTRACPs May be caused by network packet data loss or corruption so consider a network health check If condition persists submit an SPR 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 E 8 RTR log messages RTR log messages RTR 1 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 pe
203. f change This has no effect on the sampling it simply allows the rate to be displayed in another unit For example displaying the start transaction counter with RATE 60 results in transactions per minute being displayed instead of per second REVERSE Boolean expression NOREVERSE D Specifies that the item is displayed with the foreground and background visual attributes swapped if Boolean expression evaluates to True non zero ROWS nr rows ROWS 1 D Specifies how many rows are used to display the item This is only meaningful if SEPARATE is also specified The default number of rows is one SELECT Boolean expression NOSELECT D Displays the item if Boolean expression evaluates to True non zero SEPARATE keyword NOSEPARATE Specifies that the items being monitored relating to keyword are separated from each other and displayed as a list This allows a number of items to be separated in one qualifier The keyword can be one of the following Keyword Meaning NODE Node data items LINK Link data items FACILITY Facility data items RTR Command Line Interface 6 69 DISPLAY BAR Keyword Meaning PROCESS Process data items PARTITION Partition data items FE_TRANSACTION TR_TRANSACTION BE_TRANSACTION Frontend transaction data items Backend transaction data items Router transaction data items TOTALIZE keyword NOTOTALIZE Specifies that the items bein
204. f data which may need to be transferred during a shadow catchup operation B 7 Shadows in Action The first node on which a shadow server for a particular key range starts is arbitrarily designated by RTR to be the primary site for that key range Initially RTR searches the journals of other backend sites to find any recoverable transactions left over from a previous invocation of the server Once these have been processed or RTR is able to determine that no such transactions exist the server becomes active and available to handle new transactions sent by clients While no other server site for this key range is available the server runs in REMEMBER mode and RTR Saves transactions processed on this site in the RTR journal together with the order in which they should be committed so that when the other site server s start they can be sent to this site When a server starts on a second site it begins processing the transactions saved in the primary site s journal These are deleted from the journal as they are processed When the second site server s have caught up the second site enters SECONDARY state and the original site servers enter ACTIVE state In this mode new transactions are sent to both sites in parallel They are executed first on the primary site and shortly afterwards on the secondary site in equivalent order The primary site commits transactions as soon as it knows that the secondary has hardened i e written to the jou
205. f disks per journal 16 B 5 Standby for Shadows Shadowed sites can either be two nodes within a single cluster or can be two separate clusters In the second case it is also possible to configure standby servers on another node of each of these clusters so that failure of a single node within one of the shadow sites does not stop the shadow site from functioning Multiple concurrent copies of the server processes are allowed on each site This implies that up to four nodes can be configured to serve a particular key range see Figure B 1 Figure B 1 Four Node Shadow Standby Configuration NODEP Shadow Shadow NODEB NODEQ Primay Secondary Standby Seandby CusterC1 ClusterC2 B 6 Performance The performance of a shadow pair compares with a transaction which spans two nodes with the addition of one extra protocol message which is required to ensure that the transactions are presented in the equivalent order B 4 Server Shadowing and Recovery 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 The two partners in a shadow pair should be connected with sufficient bandwidth to cater for the possibly large amounts o
206. facility funds transfer The extended configuration is shown in Figure 2 2 This diagram shows all possible connections The frontend connects to only one router at a time Starting and Setting Up RTR 2 5 Starting and Setting Up RTR 2 4 Changing a Facility Figure 2 2 Extend Configuration Example FRONTENDS ROUTERS BACKENDS FE1 oe BE1 BE2 BE3 FE4 a SVM ONG EX PTW All backend nodes must be informed when router configurations are changed Because TR3 will be a router for the FE3 and FE4 frontends these nodes must also be informed of its presence Likewise TR3 must be informed about FE3 and FE4 Example 2 4 shows the extend facility command used for this reconfiguration 2 6 Starting and Setting Up RTR Starting and Setting Up RTR 2 4 Changing a Facility Example 2 4 Reconfiguration Using Extend Facility RIR RTR gt start rtr node TR3 FE4 RTR gt set environment node 1 _RTR gt FE1 FE2 FE3 TR1 TR2 BE1 BE2 BE3 TR3 FE4 RTR gt extend facility funds_transfer 2 TR gt router TR3 frontend FE3 FE4 TR gt backend BE1 BE2 BE3 Dm RTR gt extend facility funds_transfer 3 RTR gt router TR1 frontend FE4 1 Theset environment is used to send the following command to all nodes in the facility including the new nodes 2 Theextend facility defines the new router TR3 and the new frontend FE4 Because the new router is also connected to the existin
207. fer the status code is converted to text and both are shown For all other message types the contents of the user buffer are displayed hexadecimal and ASCII text CHANNEL_NAMEschannel_name CHANNEL_NAME RTR DEFAULT_CHANNEL Specifies one or more channels from which a message may be received To specify two or more channels enter a comma separated list e g CHANNEL_NAME XCHAN1 CHAN2 CHAN5 Channel names may include wildcard characters channel_name is not case sensitive Entering the qualifier without a value that is CHANNEL is equivalent to CHANNEL RTR DEFAULT_CHANNEL Omitting the qualifier altogether is equivalent to CHANNEL that is receive a message on any defined channel 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 Note that this qualifier sets up the prcvchan parameter on the call to rtr_receive_message 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 command is executed only on the node where the command was issued Note In environments that do not support clustering use of the CLUSTER qualifier will cause the relevant command to
208. fier then the minimum is zero QUORUM_THRESHOLD n QUORUM_THRESHOLD 0 QUORUM_THRESHOLD n sets the minimum number of nodes role combinations that have to be reachable to declare the configuration quorate RTR Command Line Interface 6 109 SET FACILITY 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 Before the rest of the nodes are started it is recommended that this value is reset back to zero the default setting The current value of quorum_threshold can be displayed with the SHOW FACILITY STATE command BALANCE NOBALANCE BALANCE specifies whether router load balancing is to be performed The default behavior NOBALANCE is for a Frontend to connect to the preferred Router Preferred Routers are selected in the order specified in the ROUTER qualifier of the CREATE FACILITY command This preference is subject to the Router being available and quorate See Section 2 6 Router Load Balancing for more information on load balancing 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 sp
209. five for RTR ACP mailbox reads and timer scheduling and a minimum of two per DECNET logical link maintained by RTR For example in a 20 node configuration a router node needs an ASTLM of at least 45 5 20 x 2 In systems where a lot of traffic is expected defining additional ASTLM quota will enable lookahead I O to be booked to channels without RTR ACP being held up in a resource wait The default value of ast limit is automatically calculated based on the value of LINKS and PROCESSES BIOLM io buffered BIOLM max links max processes x 2 10 default io buffered D Specifies the maximum number of system buffered I O operations that the RTR ACP can have outstanding at any one time The default value of io buffered is automatically calculated based on LINKS and PROCESSES values BYTLM buffer limit BYTLM 1 000 000 D Specifies the maximum amount of memory in bytes that the RTR ACP can use for buffered I O operations or temporary mailbox creation This should be sufficiently large to account for lookahead DECNET traffic The default for buffer limit is 1 000 000 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 command is executed only on the node where the command w
210. follows rtr_qualifier_value_t set_qualifiers 2 rtr_partition_failover_policy_t newPolicy set_qualifiers set_qualifiers set_qualifiers set_qualifiers 0 qv_qualifier rtr_partition_failover_policy 0 qv_value amp newPolicy 1 qv_qualifier rtr_qualifiers_end 1 qv_value NULL Legal values for newPolicy are e rtr_partition_fail_to_standby 3 8 Partition Management Partition Management 3 6 Managing Partitions e rtr_partition_fail_to_shadow e rtr_partition_pre32_compatible 3 6 6 Controlling Transaction 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 A killer message presents a situation where server availability is lost because of the presence of a message capable of causing repeated server application failure during recovery This is typically the result of an improperly handled condition or application programming error within the server itself Under such circumstances it may be desirable to sidestep a particular transaction maintain server operation and manually process the transaction at some later time The RTR solution is to establish for a given partition the maximum number of retries for any given transaction presented during recovery Once this limit has been exceeded the offending transaction is removed from the recovery process and is w
211. for partition A A received from backend A new priority A Explanation Log file entry indicating receipt by a router of an operator request to change the priority of the indicated partition RTR S PRTRESUMED Partition A A resumed by operator A Explanation Log file entry indicating successful completion of partition resume command Transaction presentation is now enabled RTR W PRTRSTRCVY Partition A A recovery initiated by operator A Explanation Log message indicating that partition recovery was manually initiated by the operator RTR I PRTSCANJ NL Partition ld scanning journal for node id A Explanation RTR is accessing the journal for node B that may contain relevant recovery information for this key range RTR log messages E 9 RTR log messages RTR E PRTSETFAILTR 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 W PRTSHDRECEXIT Partition A A shadow recovery terminated by operator A Explanation Log message indicating that recovery wait override requested by operator RTR I PRTSHDWOFF Command is set partition shadow state off Explanation This message appears in the router log file indicating what sort of request has been received RTR I PRTSHDWON Command i
212. for the CALL command is the name or part of a name of an RTR API routine This allows the user to type e g rtr call accept instead of rtr call rtr_accept_tx This message is issued if the user has specified a part of an API routine name that matches more than one routine RTR Utility Error Messages D 1 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 GIA line A Explanation Processing definition incomplete or undefined report occurrence together with supporting information on current command to RTR Engineering RTR F BADOUTFIL Cannot open file specified with OUTPUT Explanation The file specified with the OUTPUT qualifier cannot be opened RTR E BADPRTSTATE Disallowed attempt to make an illegal or undefined partition state transition Explanation Returned following an attempt to make an illegal or undefined partition state transition RTR E BADRTRINS RTR is not correctly installed Explanation RTR is not correctly installed Refer to the RTR Installation Guide for details of how to install RTR RTR E BENOTALLO32 Not all back ends are at the minimum required version of V3 2 Explanation Cannot perform the requested action since not all routers are at a minimum version of V3 2 RT
213. g yes ode initiated the connection yes Connection established yes Connection in progress no Node is configured yes Link is in disabled state no Link may be suspect no Facilities n facility steve2 Frontend no Router yes Backend no Router gt Frontend no Frontend gt Router yes Backend gt Router no Router gt Backend no Router quorate no Backend quorate no Router current yes Backend coordinator no This example shows e The name and network address of the partner node e Link status e Name of facility using this link and how the link is used in the facility RTR Command Line Interface 6 145 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 Qualifiers 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 command is executed only on the node where the command was issued Note In environments that do not support clustering use of the CLUSTER qualifier will cause
214. g Up RTR 2 1 Starting and Setting Up RTR 2 2 Setting Up An Example Figure 2 1 Configuration Example Frontends FE Routers TR Backends BE BE1 BE2 BE3 SIM OOG EX0 In this example the application client processes run on the nodes FE1 FE2 and FE3 The servers run on BE1 BE2 and BE3 Nodes TR1 and TR2 are routers and have no application processes running on them This diagram shows all possible connections The frontend connects to only one router at a time Example 2 1 shows the commands that have to be issued on each node to start this configuration Commands are issued first on node FE1 then on FE2 and on FE3 for frontends followed by TR1 and TR2 for routers and finally BE1 BE2 and BE3 for backends Example 2 1 Local Configuration of each Node Q y Ler RTR gt start rtr RTR gt create facility funds_transfer frontend FE1 _RTR gt router TR1 TR2 o tr RTR gt start rtr RTR gt create facility funds_transfer frontend FE1 FE2 FE3 _RTR router TR1 _RTR gt backend BE1 BE2 BE3 5 rtr RTR gt start rtr RTR gt create facility funds_transfer router TR1 TR2 _RTR gt backend BE1 The commands shown in Example 2 1 could also be included in each node s startup script or put in a command procedure used to start the application Note that nodes only need to know about the nodes in the neighbouring layers of the hierarchy thus FE1 does not need
215. g frontend FE3 this node must also be specified as a frontend The new router TR3 is told about all backends with the backend qualifier Note that the extend facility command has been used to create new definitions on TR3 and FE4 and extend the definitions on BE 1 BE2 and BE3 3 Theextend facility command is used to extend the definitions on TR1 and FE4 in order to give FE4 a second router link 2 5 Setting up Callout Servers Callout servers are applications that receive a copy of every transaction passing through the node where the callout server is running Like any other server callout servers have the ability to abort any transaction that they participate in Callout servers are typically used to provide an additional security service in the network transactions can be inspected by the callout server and aborted if they fail to meet any user defined criteria Callout servers can run on router or backend nodes or both Assume that callout servers are to run on the router nodes TR1 and TR2 in the example configuration shown in Figure 2 1 Example 2 5 shows the commands needed to set up callout servers on the routers Starting and Setting Up RTR 2 7 Starting and Setting Up RTR 2 5 Setting up Callout Servers Example 2 5 Configuration of Callout Servers rtr RTR gt set environment node _RTR gt FEL FE2 FE3 TR1 TR2 BE1 BE2 BE3 RTR gt start rtr RTR gt create facility funds_transfer frontend FE1 FE2 FE3
216. g monitored relating to keyword are added together and displayed as a total 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 TR_TRANSACTION BE_TRANSACTION Frontend transaction data items Backend transaction data items Router transaction data items UNDERLINE Boolean expression NOUNDERLINE D Specifies that the displayed value is underlined if Boolean expression evaluates to True non zero VALUE value type VALUE CURRENT D Specifies how the value is processed before being displayed Value type can be one of the following keywords e CURRENT default display the current value of expression e AVERAGE display the average value of expression since the MONITOR command was issued e MINIMUM display the minimum value of expression since the MONITOR command was issued e MAXIMUM display the maximum value of expression since the MONITOR command was issued Use the MONITOR RE SUM values X column 6 70 RTR Command Line Interface command to reset average maximum or minimum DISPLAY 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 DISPLAY command Y row Y ne
217. g or editing the contents of the journal where the partition name can be used to select a subset of the transactions in the journal RTR will not permit a change in the partition name or definition as long as transactions remain in the journal that were processed under the current name or definition for the partition If transactions remain in the journal and you need to change the partition name or definition you can take the following actions e Start appropriate servers to complete processing of the transactions e Remove the transactions from the journal with the SET TRANSACTION command e Replace the RTR journal with the CREATE JOURNAL SUPERSEDE command Note that this will destroy any transactions remaining in the journal and should be done with caution 3 4 Binding Server Channels to Named Partitions For a server application to be able to open a channel to an explicitly created partition the application passes the name of the partition through the pkeyseg argument of rtr_open_channel call It is not necessary to pass key segment descriptors but if the application does so they must be compatible with the existing partition definition You may pass partition characteristics through the flags argument but these will be superseded by those of the existing partition Example RTR gt create partition KEYl type par_one rtr_keyseg_t partition_name partition_name ks_type rtr_keyseg_partition p
218. g to transactions RTR log messages E 11 RTR log messages RTR W RSPFAC 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 W RSPNODE Connection to node A failed reason is 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 F RTRACPFAIL RTR ACP failed diagnostics written to A Explanation The RTR ACP process has failed report occurrence together with supporting information on current command to RTR Engineering RTR 1 SETTRAN RTR SET TRAN command entered facility A partition A tid A state A new_state A since A before A user A Explanation Log file entry recording that an RTR SET TRAN command is issued RTR I SETTRANEND RTR SET TRAN complete with status ld and ld transactions updated in partition A of facility A Explanation Log file entry recording that an RTR SET TRAN command is complete RTR E SRVABOREC Server aborted transaction recovery check database consistency Explanation ndicates that a server aborted a transaction being recovered after an earlier failure RTR E SRVDIEDCOM Server exited after being told to commit check commit was completed Explanation Indicates t
219. ge definition you specify as a command line parameter The command server uses message data specified as command line parameter values to generate a record containing the message data for the pmsg parameter the message length for the msglen parameter and a record type description for the msgfmt parameter Qualifiers ACCEPT NOACCEPT The ACCEPT qualifier sets the flag RTR_F_REP_ACCEPT in the call to reply_to_client It means the transaction is accepted by this server CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use 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 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 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 FORMAT fmt string NOFORMAT D Specifies that a format stri
220. h line BALANCE NOBALANCE D Specifies that load balancing is enabled for the frontend of the transaction router listed with ROUTER See Section 2 6 Router Load Balancing for details on load balancing It has no significance on a backend node and will be ignored if specified The default behavior NOBALANCE is for a frontend to connect to the preferred router Preferred routers are defined by the order specified in the ROUTER qualifier of the CREATE FACILITY command Note that this preference is subject to the router being available and quorate CALL_OUT role list NOCALL_OUT D Specifies which node types are to have call out servers running on them Role list is a list of roles separated by commas If role list contains more than one role then it must be enclosed in parentheses role is one of the keywords ROUTER or BACKEND The default for role list iS ROUTER BACKEND 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 command is executed only on the node where the command was issued 6 48 RTR Command Line Interface CREATE FACILITY Note In environments that do not support clustering use of the CLUSTER qualifier will ca
221. h name specified Explanation No xaswitch were specified on a CREATE RM command while trying to register an underlying RM XA Resource Manager with ACP RTR E NOROUTERS No routers specified Explanation No routers were specified on a CREATE FACILITY command and the node where the command was executed was specified as being a frontend or a backend or both RTR E NORTRPROC No processes using RTR Explanation No processes are currently using RTR RTR E NOSUCHCHN No channel matched A Explanation The requested channel A has not been declared RTR E NOSUCHCOU No counter matched A Explanation The requested counter A does not exist RTR E NOSUCHDIS No such monitor file A Explanation The requested monitor file A does not exist RTR E NOSUCHFACILITY The specified or implied facility does not exist Explanation The requested facility A does not exist See CREATE FACILITY RTR Utility Error Messages D 17 RTR Utility Error Messages RTR E NOSUCHITM Nothing displayed at x A y A Explanation Indicates that invalid coordinates were specified on a CLEAR DISPLAY or SHOW DISPLAY command No item is displayed at point A B RTR E NOSUCHNOD No such node A Explanation The requested node A does not exist RTR E NOSUCHPRC No such process process ID A Ox A Explanation The process with PID A does not exist or is not using RTR RTR E NOSUCHPRCS No such process process ID
222. hange the facility name to ORDERS and resubmit the command 6 104 RTR Command Line Interface REGISTER RESOURCE MANAGER REGISTER RM REGISTER RESOURCE MANAGER REGISTER RM Format Description Parameters Registers an instance of a resource manager RM with RTR REGISTER RESOURCE MANAGER resource_name REGISTER RM resource_name Command Qualifiers Defaults open_string see the Oracle8 Administrator s Reference manual close_string see the Oracle8 Administrator s Reference manual switch_name see the Oracle8 Administrator s Reference manual library_path path to an XA library protocol XA The REGISTER RESOURCE MANAGER command registers multiple resource managers or instances of resource managers up to 16 with the current transaction manager A different resource manager RM instance name is needed for each referenced database Use this command after RTR ACP is started and before RTR facilities that reference this resource manager are created Note This command is available only on UNIX and Windows NT systems Refer to Appendix C XA Support for support information about XA resource_name Specifies the name of the resource to be registered Any application program which uses this resource must specify the same name when it calls rtr_open_channel Resource names can contain up to thirty characters Letters numbers and underline characters are all valid but the first character of a resou
223. hat a server exited after being told to commit a transaction RTR E SRVDIEDREC Server exited during transaction recovery check database consistency Explanation Indicates that a server exited whilst performing recovery of transactions lost on an earlier failure RTR E SRVDIEDVOT Server exited after voting on transaction awaiting transaction result Explanation Indicates that a server exited before completing a transaction RTR 1 STATECHANGED Transaction A journal state is changed from A to A Explanation Log file entry recording transaction s tkj state has changed RTR I TIMEEQUALS Issued at A Explanation Displays the transaction start time A in messages relating to transactions E 12 RTR log messages RTR log messages RTR W TOOMANYNETIDS Too many net IDs for node AT 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 You may be able to operate under this condition but we recommend you review the system configuration and eliminate any unnecessary adapter protocol combinations RTR I TRINQUO Router is quorate in facility A Explanation The router role now has quorum in the facility A RTR W TRNOQUO Router has no quorum in facility A Explanation The router role has lost quorum for facility A RTR 1 TXIDEQUAL
224. hat logging was not active when a SHOW LOG command was issued RTR F MAXPARM Too many parameters reenter command with fewer parameters Explanation A command contained more than the maximum number of parameters allowed This error can be caused by 1 Leaving blanks on a command line where a special character for example a comma or plus sign is required 2 Using symbol names or logical names that when substituted or translated contain embedded blank characters 3 Failing to place quotation marks around a character string with embedded blanks RTR E MAXTOOSMA Maximum number of blocks may not be less than BLOCKS Explanation The number of blocks specified with the MAX_BLOCKS qualifier in the CREATE J OURNAL or MODIFY J OURNAL command was lower than the number of blocks specified with the BLOCKS qualifier RTR E MONCMPERR Syntax error in command at line A in file A Explanation error found compiling a MONITOR definition file RTR E MONNOTACT Monitor is not active first use the MONITOR command Explanation A SCROLL or PRINT command was issued before any monitor picture had been displayed RTR E MSGDATILL Unable to convert string A to A Explanation The string A could not be converted to data type B The subsequent message gives the reason RTR E MSGTOOBIG The number of bytes in message exceeds the maximum of u Explanation RTR W NAMERR Node name to address lookup error Explanation Error enco
225. have the form nodeSfacilitySpartition id RESUME NORESUME D Re executes the last MONITOR command The qualifiers OUTPUT INTERVAL and COUNT may be used with RESUME All other qualifiers are ignored This RTR Command Line Interface 6 101 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 NERIFY NOVERIFY D Specifies that the contents of monitor file spec are echoed on stdout This is useful when developing monitor files to find the exact location of syntax errors Related Commands Examples e SCROLL e PRINT e CLEAR e DISPLAY NUMERIC e DISPLAY BAR e DISPLAY TEXT RTR gt MONITOR CALLS NODE TR2 TR1 INTERVAL 10 1 RTR gt SHOW PROCESS 2 RTR gt MONITOR RESUME 3 1 Display the CALLS picture monitoring nodes TR2 and TR1 every ten seconds 2 TheSHOW PROCESS command is entered interrupting the display 3 Redisplay the CALLS picture using the original parameters RTR gt MONITOR TRAFFIC COUNT 10 OUTPUT PICTURE LIS This command stores 10 images of the TRAFFIC picture in the file PICTURE LIS 6 102 RTR Command Line Interface 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 Same as EXIT RTR Command Li
226. he Link Transport Protocol It is possible to override the protocol failover mechanism by specifying the transport protocol to be employed for a link by naming links to include a transport selecting prefix Prefixing links names with tcp and dna specifies TCP IP or DECnet as the required transports respectively Use of these prefixes causes the local node to employ only the specified transport protocol when attempting a connection on the link to which the prefix has been applied Note that use of a protocol prefix on one node does not prevent a remote node from connecting using some other transport For example to specify the facility FAX1 that only uses the DECnet transport two routers DNET1 and DNET2 two backends SRV1 and SRV2 and many frontends use the following command RTR gt create facility FAX1 frontend dna FEl dna FE2 dna FE3 router dna DNET1 dna DNET2 backend dna SRV1 dna SRV2 Creating a facility that uses only TCP IP would use a command like this RTR gt create facility FINANCE frontend tcp clientl tcp client2 tcp client7 router tcp routrl tcp routr2 backend tcp srvl tcp srv2 Starting and Setting Up RTR 2 13 Starting and Setting Up RTR 2 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 fully known special naming techniques are provided for these conditions
227. he reason field returned in the rtr_status_data_t buffer Status Text The textual status that describes the reject reason 5 2 25 Monitor Response TRANSACTION DURATION AT 10 24 51 Fri Apr 9 1999 Process Image Client Response Time Server Response Time ID Name seconds 0 1 2 3 4 seconds0 1 2 3 4 20413894 SERVER EXE 4 0 000 3 670 20417266 RIR EXE 75 2 200 3 440 20417274 SERVER EXE 4 0 000 1 160 Displays the elapsed time that a transaction has been active on the opened channels of a process On the client transaction duration is measured between the rtr_start_tx or rtr_send_tx call and the receipt of the final rtr_mt_accepted or rtr_mt_rejected message A call to rtr_reject_tx also marks the end of a transaction On the server transaction duration is measured between receipt of a rtr_mt_msgl or rtr_mt_msgl_uncertain message and the receipt of the final rtr_mt_rejected message or rtr_reject_tx call Accepted transaction end times are recorded when the server issues a rtr_receive_message call to request a new transaction for processing RTR Monitoring 5 15 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 VIP 1 1 1 il 1 1 1 il 1 I 1 1 5 2 27 Monitor Routers ROUTER TRANSACTION COUNTERS AT 14 33 29 7 JAN 1999 Node ALL F
228. his typeface indicates input entered by the user In text this typeface indicates the exact name of a command routine partition pathname directory or file This typeface is also used in interactive examples and other screen displays Italic text emphasizes important information indicates variables and indicates complete titles of manuals Italic text also represents information that can vary in system messages for example Internal error number command lines for example PRODUCER name and command parameters in text Boldface text represents the introduction of a new term or the name of a command an argument an attribute or a reason In a prompt square brackets indicate that the enclosed item is the default response For example y means the default response is Yes A vertical bar next to the text indicates changes or additions since the previous version of this document Red HTML text indicates changes or additions since the previous version of this document xiii y Introduction For a general introduction to Reliable Transaction Router Version 3 2 RTR you should read the introductory chapter in the Reliable Transaction Router Application Design Guide Additional information about the Reliable Transaction Router is available in the Reliable Transaction Router Application Programmer s Reference Manual In order to use RTR you must install the RTR software and your application See the Reliable Trans
229. hould be presented for recovery before being written to the journal as an exception Once a transaction has been recorded as an exception it is no longer considered eligible for recovery and will require manual processing by a qualified individual The recovery retry count is partition specific and applies to both local and shadow recovery operations The default is no limit on the number of retries which permits a killer message to bring down all available servers servicing a given partition The recovery retry count should be set prior to starting or restarting the application servers so that the limit is established prior to the start of recovery operations RESTART_RECOVERY Restarts the recovery cycle The recovery cycle can be manually restarted with RESTART This is useful if the operator previously aborted recovery through use of I GNORE_RECOVERY Since this command may result in recovery of transactions from previously inaccessible journals it should not be used if your applications are sensitive to the order in which transactions are processed by the servers RESUME Resume normal operations that is cancel a SUSPEND command If the partition is already in the desired state the command has no effect SHADOW NOSHADOW Turns shadowing on or off for the specified partition Shadowing for a partition can be turned off only in the absence of an active secondary site that is the active member must be running in renember
230. ich causes the command server to use the value RTR_NO FLAGS for the flags parameter in the call to rtr_accept_tx INDEPENDENT NOINDEPENDENT Use the INDEPENDENT qualifier to specify the flags parameter RTR_F_ACC_ INDEPENDENT in the call to rtr_accept_txt 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used REASON reason REASON 0 Use REASON to supply a value for the reason parameter in the call to rtr_accept_tx The default for value for REASON is 0 which causes the command server to use the value RTR_NO_REASON for the reason parameter in the call to rtr_accept_tx 6 4 RTR Command Line Interface Related Commands e CALL mw R_OP _CHANNE E E e CALL po R_REJECT_TX Examples CALL RTR_ACCEPT_TX Accept the current transaction with a reason of 42 RTR gt CALL RTR_ACCEPT_TX REASON 42 SRTR S OK normal successful completion RTR Command Line Interface 6 5 CALL RTR_BROADCAST_EVENT CALL RTR_BROADCAST_EVENT Format Parameters Description The CALL RTR_BROADCAST_EVENT command
231. ified 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 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 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 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 e SET MODE 6 148 RTR Command Line Interface SHOW MODE Examples RTR gt SHOW MODE Group name is develop RTR Command Line Interface 6 149 SHOW NODE SHOW NODE Format Description Qualifiers Shows the node network status the autoisolation state and the node inactivity timer SHOW NODE Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SHOW NODE shows the network status the autoisolation state enabled or disabled and the node inactivity timer CLUSTER NOCLUSTER D Specifies
232. ifier can be used to specify the desired order of failover for those cluster members Some machines within a cluster may be more powerful than other machines This feature allows for the most efficient use of those machines 2 12 2 Router Selection Within the scope of a given facility routers and backends connect to one another However nodes with a specific role do not connect to nodes with the same role i e routers do not connect to other routers Frontends choose only one router to connect to at a given time This router is called the Current Router for that frontend within the scope of a facility A backend connects to all routers defined within a facility The connected router with the lowest network address is designated the master router Internally a node is identified through a structure called the Kernel Net ID The Kernel Net ID is a concatenation of all network addresses a node is known as for all the protocols and interfaces that it supports The master router designation is only Starting and Setting Up RTR 2 21 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 amp list qualifier to the CREATE FACILITY command This list specifically determines the preferred router If the fi
233. ignored on the executing node since it has no significance for the role defined RTR CMDNOTWRK A command not implemented Explanation This command is not currently implemented RTR E CMDRESDEV Command reserved to RTR development Explanation An unsupported command was issued RTR E CMDTOOLON Command too long Explanation Command was longer than 256 characters RTR E CNTCRJ OU Cannot create journal directory Explanation Cannot create journal directory RTR S COMARESEN Commands sent by default to node A Explanation Displays the default nodes for command execution after issuing a SET ENVIRONMENT or SHOW ENVIRONMENT command RTR E COMNOTFOU Command not found A use RECALL ALL Explanation Indicates that the command A requested with RECALL was not in the recall buffer RTR E COMNUMMUS Command number must be between 1 and A Explanation Indicates that the command number requested with RECALL was not in the allowed range 1 to A RTR F CONFLICT Illegal combination of command elements check documentation n A Explanation Two or more keywords qualifiers or parameters that cannot be used in in combination have been in the same command line RTR I DEQDATA Received data A bytes A Explanation Displays the dequeued data B and its length in bytes A RTR F DFSDISK Disk is served by DFS Explanation An attempt was made to create a journal on a disk served by DFS RTR does not support j
234. ilable This can occur when TCP is explicitly specified through use of a node name prefix tcp or when IP networking is the only enabled network transport Check the host name database on the local node and the network name server DNS RTR F ENOTRANSPORTS No network transports available Explanation No network transport are available Most likely cause is the manipulation of the transport protocols allowed to RTR RTR Utility Error Messages D 5 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 E ERRACCMBX Error accessing mailbox Explanation An error occurred whilst accessing a mailbox The subsequent message gives more details RTR E ERRACCNOD Error accessing node A Explanation An error occurred whilst accessing node A If you were using the NODE or CLUSTER qualifier to issue a remote command please check that you are able to execute simple non Rtr remote shell or DECnet commands on the remote node Rtr remote commands will not work unless remote shell software is installed and proxy and rhost settings are correctly configured Also check that both nodes have the same RTR_PREF_PROT value on platforms that can use both DECnet and TCP IP RTR E ERRACCTAB Error accessing tables Exp
235. ile In this case nr updates specifies how many screen images are written to the file FACILITY facility name NOFACILITY D Specifies the name of the facility to be monitored This is only meaningful if at least one facility counter is displayed IDENTIFICATION process id NOIDENTIFICATION D Specifies the hexadecimal process id of the process to be monitored This is only meaningful if at least one process counter is to be displayed INTERVAL delay seconds INTERVAL 2 D Specifies how frequently RTR updates the screen Delay seconds is the number of seconds that RTR waits after completing one screen update before starting the next Note that the interval between updates will always be slightly longer than Delay seconds depending on the complexity of the display and the number of nodes being monitored LINK link name NOLINK D Specifies the node name for the link to be monitored This is only meaningful if at least one link counter is to be displayed NODE node list NODE default node list D Specifies the names of the nodes to be monitored If node list is omitted then the local node is monitored 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 PARTITION partition name NOPARTITION D Specifies the names of the partitions to be monitored Partitions names
236. in use in another partition of the facility Use another name RTR E PRTNAMINUSEINJ NL J ournalled transactions preclude change of partition key range Explanation Transactions exist in the journal that were processed whilst this name was assigned to a different key range Recover or delete these transactions first RTR E PRTNAMNOTFND The named partition does not exist Explanation A call to rtr_open_channel specified a partition name that does not exist D 20 RTR Utility Error Messages 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 successful change to the partition failover policy RTR S PRTNEWPOLWAIT Failover policy stored awaiting servers before taking effect Explanation Status indicating successful change to the partition failover policy but the change will only take effect once servers have been started RTR S PRTNEWPRIO Backend priority set Explanation Status indicating successful change to the backend priority RTR S PRTNEWPRIWAIT Backend priority stored awaiting servers before taking effect Explanation Status indicating successful change to the backend priority but the change will only take effect once servers have been started RTR E PRTNO
237. ing to be terminated when the key is pressed NOTERMINATE the default allows you to press other keys before terminating the st Related Commands e SHOW KEY Examples RTR gt PF3 ring by pressing the RETURN key RTR gt DEFINE KEY PF3 SHOW RTR TERMINATE DEFAULT PF3 key has been defined as SHOW RTR RTR running on node BEl The DEFINE K EY command defines the PF3 key on the keypad to perform a RTR gt D DEFAUL FINE oe El SHOW RTR command DEFAULT refers to the default state EY PF1 HELP SET_STATE GOLD NOTERMINATE ECHO PF1 key has been defined as HELP RTR gt DEFINE KEY PF1 CREATE TERMINATE IF_STATE GOLD ECHO GOLD PF1 key has been defined as CREATE RTR gt PFI RTR gt HELP PFI RTR gt HELP CREATE The CREATE FACILITY command is used to The first DEFI NE KEY command defines the PF1 key to be the string HELP The state is set to GOLD for the subsequent key The NOTERMINATE qualifier instructs the system remain in command input mode when the key is pressed The second DEFINE KEY command defines the use of the PF1 key when the keypad is in the GOLD state When the keypad is in the GOLD state pressing PF1 will cause the current read to be terminated If you press PF1 twice the system displays and processes the HELP
238. ion Server State is only managed at the backend RTR provides a set of comprehensive management utilities to help users closely monitor the flow of a transaction and all three types of states associated with that transaction These utilities help users understand how a transaction migrates from one stage to another and help diagnose problems The RTR SHOW TRANSACTION command can be used to examine a transaction s up to date status on frontend router or backend roles With this command users can see all three types of transaction states of a particular transaction and also understand how the RTR journal and application servers perceive this transaction When a transaction commits or aborts all status associated with Transaction Management 4 1 Transaction 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 The RTR journal saves all of the information about a transaction its transaction journal state the transaction messages records received from the RTR client and the content of a message sent to the server The information will be kept until a transaction is committed and forgotten The RTR SET TRANSACTION command is used to modify a live transaction to change the current state of a transaction to a new state This command can be used to circumvent a difficult situation For example i
239. ion name bounds callout State svrs segs lo hi type RIRSDEFAULT_PARTITION_16777218 active 1 1 A vA gt RIR DEFAULT_PARTITION_16777221 active il ll B pgr RTR DEFAULT_PARTITION_16777217 active 1 1 0 429496 Partitions are shown in the form node facility_partition id or partition name if a partition name has been specified using the SET PARTITION command The number of servers and key segments are shown for each partition The least significant byte of the partition s low and high bound is also shown and callout type if any The partition state meanings are given in Table 5 3 Table 5 3 Monitor Partition States State Meaning wt_tr_ok Server is waiting for routers to accept it wt_quorum Server is waiting for backend to be quorate Icl_rec Local recovery Icl_rec fail Primary server waiting for access to a restart journal Icl_rec_icpl Getting next journal to recover from Icl_rec_cpl Processed all journals for local recovery shd_rec Shadow recovery shd_rec_fail Shadow server waiting for access to a restart journal shd_rec_icpl Shadow getting next journal to recover from shd_rec_cpl Processed all journals for shadow recovery catchup Secondary is catching up with primary standby Server is declared as standby continued on next page 5 12 RTR Monitoring RTR Monitoring 5 2 Standard Monitor Pictures Table 5 3 Cont Monitor Partition States State Meaning active Server is active pri_act Server is active
240. ion should be displayed By default information is displayed for all Facilities FULL none D Specifies a detailed listing of client information RTR Command Line Interface 6 131 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 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 gt SHOW CLIENT FULL 1 Process id 9234 Facility TEST43 2 Channel 500 Flags CLI 3 State declared rcpnam V3TEST 4 User Events 255 RTR Events 05 1 Show the client in detail 2 Theclient s process id and facility name 3 Theclient s channel id and the flags set when the channel was opened 4 The channel state and recipient name for events 5 The user events and RTR events subscribed to 6 132 RTR Command Line Interface SHOW DISPLAY SHOW DISPLAY Format Description Qualifiers Show which items were displayed by the most recently issued MONITOR command or DISPLAY commands SHOW DISPLAY Command Qualifiers Defaults ALL NOALL OUTPUT file spec OUTPUT stdout X column Y row The SHOW DISPLAY command shows which items were displayed by the most recently issued MONI
241. ions whose timestamp is after the specified date Default is the current date Related Commands e SHOW TRANSACTION e DUMP JOURNAL RTR Command Line Interface 6 127 SET TRANSACTION Examples RTR gt SET TRANSACTION 50d01f10 0 0 0 0 2166 522b2001 _RTR gt NEW ABORT CURRENT SENDING PART DB_PART Abort this specified transaction running in the DB_PART partition RTR gt SET TRANSACTION NEW ABORT CURRENT VOTED PART DB_PART For all transactions that are in VOTED transaction state and are running in DB_PART partition and in RTR DEFAULT FACILITY facility abort them 6 128 RTR Command Line Interface SHOW CHANNEL SHOW CHANNEL Format Description Parameters Qualifiers Show the names and state of channels that have been opened using the CLI API 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 The SHOW CHANNEL command shows the channel type client or server the channel name and owner process id for channels opened using the CLI API channel name Specifies the name of the channel to be displayed channel name can contain wild cards If channel name is omitted all declared channels for this window terminal or virtual terminal are displayed ALL_WINDOWS NOALL_WINDOWS Specifies that channels opened in all windows terminals or virtual terminals are shown CLUSTE
242. is issued The frontend will sort the list of routers based on its own random order Randomness ensures that there will be a balance of load in a configuration with a large number of frontends Automatic failback will maintain the load distribution on the routers and failback is controlled at a limited rate so as not to overload configurations with a small number of routers The following points should be born in mind when using load balancing e Frontends connect to a single router per facility e When several routers are configured on the frontend The specified list in the create facility constitutes the preferred search order by default unless balanced is used e Balancing may be individually enabled or disabled on the frontend nodes e Balancing is dynamic The loss or addition of a router node causes the frontend nodes to redistribute their connections 2 8 Starting and Setting Up RTR Starting and Setting Up RTR 2 6 Router Load Balancing e 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 are connecting frontend nodes running RTR Version 2 See CREATE FACILITY and SET FACILITY for more information on balance e Commands to set show load balancing are create facility balance Enables load balancing attribute on the executor node Significant only on router and frontend nodes Disabled by default set facili
243. is running as primary and the secondary goes away A server receives RTR_EVTNUM_SRSHADOWGAIN if it is running as primary and a secondary node starts up A server receives RTR_EVTNUM_SRRECOVERCMPL when it has finished doing recovery operations and is hence ready to start processing new transactions B 3 The RTR Journal System The RTR journal is used for two purposes e RTR stores data about a transaction so that if the server processing a transaction fails for any reason another server can transparently continue from where the previous server failed if it is able to access the same database and journal e RTR also stores data about transactions when a shadow site is known to be missing In this case RTR stores all transaction data which can result in a database update The RTR journal stores this data until the secondary shadow site is available again RTR then transparently replays this data to the shadow site after which the data is deleted from the journal The amount of space required for the journal depends upon the size of the messages in a transaction the number of messages in the transaction the rate of generation of transactions the maximum time a shadow site can be out of commission The MAXIMUM_BLOCKS qualifier on the CREATE J OURNAL command controls how large a journal may become The MAXIMUM_BLOCKS qualifier defines the maximum number of blocks which the journal is allowed to occupy on any one disk Note th
244. ive priority 1 Features Backend partitions on node GOLD in group Shadow NoStandby Concurrent test at Mon Mar 22 14 54 12 1999 Partition name pl Facility RTRSDEFAULT_FACILITY State sec_act Low bound 0 High bound 4294967295 Active servers 0 Free servers 1 Transaction presentation active Last Revy BE bronze Active transaction count 0 Transactions recovered 0 Failover policy fail_to_standby Key range ID 16777216 Master router silver Relative priority 2 Features The following description shows how sequence numbers are initially assigned in a simple partition with two backends named Bronze and Gold and a router named Shadow NoStandby Concurrent Silver Backend A Router e lt O ef g 9 A partition with shadowing enabled is started on node Bronze The partition on Bronze obtains sequence number 1 from the router and becomes the primary Another server on the same partition with the same attributes is started on Gold The partition on Gold obtains sequence number 2 from the router and becomes the secondary Node Bronze crashes and reboots the partition sequence number on Bronze is reset to 0 The partition on Gold goes into Remember When the server starts The partition on Bronze obtains sequence number 3 from the router and becomes the secondary Gold now becomes the primary The network connection from node Silver to node Gold fails The partition on Bronze becomes the primary The p
245. l State High Bo Uents Process id Channel State High Bo User Events Partition Id Partition Id 20828 589825 active mmmm 0 16973824 20828 655362 active ZZZZ 0 16842753 SHOW SERVER Channel Flags State 589825 SRV active 655362 SRV active Facility Flags Low Bound rcpnam Facility Flags Low Bound rcpnam RTR Events RTR Events RTRSDEFAULT_FACILITY SRV aaaa LOWER_SERV 0 RTRSDEFAULT_FACILITY SRV nnnn UPPER_SERV 0 RTR Command Line Interface 6 167 SHOW TRANSACTION SHOW TRANSACTION Format Description Qualifiers Displays information about currently active transactions SHOW TRANSACTION Command Qualifiers Defaults BACKEND NOBACKEND D CLUSTER NOCLUSTER FACILITY FACILITY FRONTEND NOFRONTEND D FULL NOFULL IDENTIFICATION process id NOIDENTIFICATION NODE node lisft NODE default node list OUTPUT file spec OUTPUT stdout ROUTER NOROUTER D The SHOW TRANSACTION command displays transaction information such the transaction 1D facility transaction state frontend user start time and router node BACKEND NOBACKEND D Specifies that information should be listed for transactions in a backend node If none of BACKEND FRONTEND or ROUTER are specified then information for all of them are displayed If either FRONTEND or ROUTER are specified then the default NOBACKEND inhibits display of backend tran
246. l is then converted to its textual representation and displayed The rtr_close_channel routine itself is described in Application Programmer s Reference Manual The prototype of rtr_close_channel is rtr_status_t rtr_close_channel rtr_channel_t channel rtr_clo_flag_t flags a Table 6 4 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 4 Parameters for rtr_close_channel C Parameter Name C Parameter Value Command Line Specification channel CHANNEL_NAME name flags RTR_NO_FLAGS none D Qualifiers CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use channel_name is not case sensitive The default channel name is RTR DEFAULT_CHANNEL You may close all the channels belonging to a window using CLOSE CHANNEL CHANNEL_NAME 6 10 RTR Command Line Interface Examples 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 then the command is ex
247. lanation Indicates that the configuration tables could not be accessed The subsequent message gives more details RTR E ERRCREMBX Error creating mailbox Explanation An error occurred whilst creating a mailbox The subsequent message gives more details RTR E ERRDELMBX Error deleting mailbox Explanation An error occurred whilst deleting a mailbox The subsequent message gives more details RTR E ERRGETNOD Error obtaining information for node A Explanation An error occurred whilst trying to look up node A in the DECnet database The subsequent message gives more details RTR E ERRINIACS Unable to initialize tables Explanation ndicates that the configuration tables could not be initialized The subsequent message gives more details RTR F ERR OUNAM Error in journal file name CREATE JOURNAL SUPERSEDE and submit SPR Explanation An RTR journal file has been found which has an incorrect name format This is probably an RTR bug submit an SPR This status may be returned by the CREATE FACILITY and SHOW J OURNAL commands Reissue the RTR CREATE J OURNAL command before restarting RTR RTR E ERROPEFIL Error opening file A Explanation Displays the name A of a file that the RTR utility was unable to open RTR F ERROPEJ OU Error opening journal file stv A Explanation An error occurred while opening a journal file D 6 RTR Utility Error Messages RTR Utility Error Messages RTR E ERRSTAACP Unable to st
248. letes when the processing of all currently active transactions is complete The optional TIM EOUT qualifier specifies as a number of seconds the time that the command waits for completion If the command times out presentation of new transactions are suspended but there still exist transactions for which servers have yet to complete processing The operator must decide either to reenter the command and wait a further period of time or resume the partition Note that use of this command does not affect any transaction timeout value specified by RTR clients so such transactions may encounter a timeout condition RESUM channels 3 6 2 1 Command Line Example Example usage of the qualifier RTR gt SET PARTITION FACILITY Fa RTR gt if the partition remains suspended E qualifier restarts presentation of transactions to the server application S cility1 SUSPEND TIMEOUT 5 Facilityl Partitionl RTR gt SET PARTITION FACILITY Facility1 RESUME Facilityl Partitionl For a more complete descripti 6 3 6 2 2 Programming Information on see the SET PARTITION command in Chapter To suspend transaction presentation on a partition with a timeout of 30 seconds program the set_qualifier a rtr_qualifier_value_t rtr_partition_state_t rtr_uns_32_t ulTimeoutSecs set_qualifi 0 set_qualifi set_qualifi set_qualifi set_qualifi set_qualifi qv_quali qv_value qv_quali qv_value qv_quali q
249. ll no longer accept connections from frontend systems until it has again achieved quorum The BALANCE qualifier is only valid for frontend systems 2 22 Starting and Setting Up RTR 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 Partitions exist for each distinct range of values in the routing key for which a server is available to process transactions RTR provides for failure tolerance by allowing system operators to start redundant instances of partitions in a distributed network and by automatically managing the state and flow of transactions to the partition instances Partition instances support the following relationships e Concurrency this attribute permits multiple server channels to be connected to an instance of a partition e Standbys multiple instances of a partition distributed over the nodes of a cluster A standby set may have as many members as a cluster has nodes or with some restrictions you may place a standby on any network node At any one time one member of the set is active while the others wait in standby mode to take over in the event of failure of the active member e Shadows shadow instances provide site disaster protection by allowing replication of transaction processing
250. losed in parentheses backend node is either the name of a node or file spec where file spec specifies a text file containing a backend list on each line 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 command is executed only on the node where the command was issued 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 6 180 RTR Command Line Interface 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 name of a node or file spec where file spec specifies a text file containing a frontend list on each line 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 r
251. low one Kbyte per active transaction e Allow fifty bytes for each message of a transaction e Add the size of all replies The total of all the contributions listed will yield an estimate of the likely virtual memory requirements of the RTR ACP A generous additional safety factor should be applied as a final element to the total of virtual memory sizing It is better to grant the RTR ACP resource limits exceeding its real requirements than to risk loss of service in a production environment as a result of insufficient resource allocation The total result should be divided by the virtual memory size in pages to obtain the final virtual memory requirement Process memory and page file quotas should be set to accommodate as least this much memory Process quotas are controlled by qualifiers to the START RTR command START RTR accepts both links and application processes as qualifiers which can be used to specify the expected number of links and application processes in the configuration The values supplied are used to calculate reasonable and safe minimum values for the following RTR ACP process quotas e ASTLM e BIOLM e DIOLM e FILLM e PGFLQUOTA Both LINKS and PROCESSES have high default values e The default value for LINKS is now 512 This value is high but is chosen to protect RTR routers against a failover where the number of front ends is large and the number of surviving routers is small The maximum value for LINKS is 1200 which i
252. m has been attained the participating nodes return to state qrt As with CREATE FACILITY nodes or roles may be specified which are superfluous That is you may specify backend nodes on a node which only has a frontend role and frontend nodes may be specified on a node which only has a backend role This permits a single RTR management command to be issued on many nodes and each node only accepts those parts of the command which are relevant to it For example in a two node facility called facnam the node FE has the frontend role only and node FETRBE that has frontend router and backend roles can be created as follows RTR Command Line Interface 6 91 EXTEND FACILITY Parameters Qualifiers RTR RTR gt SET ENVIRONMENT NODE FE FETRBE RTR gt CREATE FACILITY facnam FRONTEND FE FETRBE ROUTER FETRBE BACKEND FETRBE A new frontend NFE can be added to this facility as follows RIR RTR gt SET ENVIRONMENT NODE FETRBE NFE RTR gt EXTEND FACILITY facnam FRONTEND NFE ROUTER FETRBE facility_name Specifies the name of the facility to be extended Any application program which uses this facility must specify the same name when it calls the rtr_open_channel Facility names can contain up to thirty one characters Letters numbers and underline characters are all valid but the first character of a facility name must be a letter The default value for facility_name is RTRSDEF
253. mand 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 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 IDENTIFICATION process id NOIDENTIFICATION D Specifies the PID of the process for which information should be displayed The default NOIDENTIFICATION displays information for all servers FACILITY FACILITY D Specifies the facility name for which information should be displayed By default information is displayed for all Facilities FULL NOFULL D Specifies a detailed listing of server information 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used 6 166 RTR Command Line Interface Examples RTR gt SHOW SERVER Servers Process id 20828 20828 Facility RTRSDEFAULT_FACILITY RTRSDEFAULT_FACILITY RTR gt SHOW SERVER FULL Servers Process id Channe
254. maximum size to which the image being executed in the RTR ACP process can increase its working set size The default for max working set is 10 000 pages RTR Command Line Interface 6 175 START RTR Related Commands SHOW RT ve e STOP RT zal 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 stopped in an abrupt manner ABORT and any applications using RTR are forced to exit Qualifiers ABORT Specifying ABORT causes RTR to stop regardless of the state of any RTR user applications Applications using RTR are forced to exit Note This qualifier supersedes the NOCONFIRM of earlier versions of RTR 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 command is executed only on the node where the command was issued Note In environments that
255. may also put the DISPLAY commands into a file called a monitor file and then issue a MONITOR monitor file spec command Parameters monitor file spec Specifies a file containing DISPLAY commands Monitor file names are of the form monitor file spec mon This file may specify either a user defined display or one of the standard displays supplied with RTR If monitor file spec contains only the filename portion of a file specification then the RTR utility first searches the platform specific location s for a standard monitor file Qualifiers CLUSTER NOCLUSTER D Specifies that all nodes in the cluster are monitored If neither NODE nor CLUSTI ER is specified then the nodes specified with the latest SET ENVIRONMENT command is monitored If no SET ENVIRONMENT has been issued then the MONITOR command is executed on the node where it was issued 6 100 RTR Command Line Interface 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 gt prompt The default is that RTR updates the screen until CTRL Z CTRL Y or another RTR command is entered The COUNT qualifier may be used when the OUTPUT qualifier is being used to redirect output to a f
256. mbiguous qualifier or keyword supply more characters Explanation Too few characters were used to truncate a keyword or qualifier name to make the keyword or qualifier name unique RTR F ABVERB Ambiguous command verb supply more characters Explanation Too few characters were used to truncate a command name to make the command name unique RTR E ACCTOOBIG ACCESS string is too long Explanation The string supplied with the ACCESS qualifier on the open channel command was too long RTR F ACPINSRES The RTR ACP has insufficient resources details in the rtr log file Explanation The RTR ACP was unable to perform an operation due to an unusual condition This is most probably a resource issue e g when the ACP cannot create a shared memory segment The RTR log file for contains more details of the problem RTR E ACPNOTVIA RTR ACP is no longer a viable entity restart RTR Explanation Indicates that the RTR ACP process has terminated unexpected y RTR ALRDYINSTATE Partition is already in the desired state Explanation Returned following an attempt to change the state of shadowing for a partition when the partition was already in the desired state RTR E AMBIGDISP Ambiguous monitor file name A Explanation The filename A could refer to more than one monitor file Please supply more characters RTR F AMBROUNAM Ambiguous API routine name for CALL supply more characters Explanation The parameter
257. me NOCOUNTER D Specifies that the facility counters are displayed Counter name is the name of the counter If counter name is omitted then all counters are displayed Counter name may contain wild card characters FULL NOFULL D Equivalent to specifying CONFIGURATION STATE and LINK LINKS NOLINKS D Lists all links to connected nodes in the facility including the node where the command is executed The following information is shown for each link Whether the node on this link is active as frontend router or backend roles What kind link is active that is frontend to router router to frontend router to backend backend to router Whether the router and backend roles are quorate Whether the router role is the current router for the frontend Whether the backend role is acting as a load balancing coordinator 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used STATE NOSTATE D Specifies that the state of the facility is displayed On nodes having a backend or router role the quorum status is shown Also the current quorum threshold is sh
258. message is only delivered to the console if the rtr_prepare_ tx is called A call to rtr_prepare tx must be followed at some point by a call to rtr_accept_tx or rtr_reject_tx which in this context implements the commit phase of the 2PC Generally rtr_prepare tx and rtr_accept_tx will be called by the foreign TM directly not by the operator CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use channel_name is not case sensitive The default channel name is RTR DEFAULT_CHANNEL DATA data DATA 0 The data parameter can be used to pass an ASCII string to RTR that will be saved in the local journal This string is not sent to the routers or backends and is used only during recovery when it is passed back to the client application RTR does not interpret or modify this data in any way The maximum size of the data parameter is defined as RTR_MAX_BLOB_LEN and is set to 2048 bytes 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 information is written to the file file
259. mmit sequence number CSN This grouping determines the ordering of transactions submitted to a secondary shadow server txn sec The average rate of transaction starts per second for this partition txn csn average number of transactions which have been grouped under the same commit sequence number CSN since this partition became active This average is computed as the quotient of the txn cnt column and the total number of CSN s RTR Monitoring 5 9 RTR Monitoring 5 2 Standard Monitor Pictures 5 2 13 Monitor IPC RTR gt Monitor IPC Node LENGTH IPC Summary Fri Mar 5 1999 11 18 34 This screen displays usage information on IPC messages byte counts and IO primitives Display units are counts kbytes and calls respectively fea n Outgoing s Incoming s Process Messages kbytes send kbytes Messages recv kbytes rtracp 110334 49744 73437 49744 73434 220299 5616 3123B84F 0 0 0 0 0 0 0 31232395 73282 5569 73280 5569 109930 293144 49685 Displays interprocess communication message information 5 2 14 Monitor IPCRATE RTR gt Monitor IPCRATE Node LENGTH IPC Rates Fri Mar 5 1999 11 18 53 This screen displays rate information on IPC messages byte counts and 10 primitive usage Display units are counts kbytes and calls per second respectively ees ee ee Outgoing s Incoming s Process Message
260. n 2 node clusters The facility is configured such that at Site A Node A1 has the primary active partition and Node A2 has the standby partition At Site B Node B1 is the secondary active partition and Node B2 has the standby of the secondary The partition could be defined such that the standby node Node A2 would become active if the primary node were to fail For example issuing the following command on all four nodes for this partition guarantees that the specified list is followed when there is a failure SET PARTITION test PRIORITY_LIST Node Al Node A2 Node B1 Node B2 Using the SHOW PARTITION command from the router this partition would be as follows Router partitions on node SILVER in group test at Mon Mar 22 17 22 06 1999 State ACTIVE Low bound 0 High bound 4294967295 Failover policy fail_to_standby Backends node al node a2 node b1 node b2 States pri_act standby sec_act standby Relative priorities 1 2 3 4 Primary main node al Shadow main node b1 However the partition could also be configured so that the secondary active node Node B 1 would become the primary node if the original primary system were to fail This is controlled with the FAILOVER_POLICY qualifier to the SET PARTITION command The default is FAILOVER_POLICY STAND BY 2 20 Starting and Setting Up RTR Starting and Setting Up RTR 2 12 How RTR Selects Processing states Roles for Nodes Site A Node A1 Node A2 Router a Nf B Nod
261. n Ge eh ee seb we PRE dee eee xs 1 1 1 2 Entering Commands 00000 cece eee 1 1 1 3 Online HAP awk os od eee ee eee wee ed eee eee ER ee a Cee ees 1 2 1 4 Command Procedures oo 1 3 1 5 Remote Commands 000 ccc eee eee tees 1 3 2 Starting and Setting Up RTR 2 1 Mi sce aniei TS E E NN 2 1 2 2 Setting Up An Example 0 cece 2 1 2 3 Creating a Recovery Journal 0 00000 ee 2 3 2 4 Changing a Facility 6 ec oe eed wee ede eee Sobek ede de ees 2 4 2 5 Setting up Callout Servers 2 eee 2 7 2 6 Router Load Balancing ssa ss caua hoes ees ah ed eee eee es a 2 8 2 7 RTR PRIVINCQES o itii a taa at weak ceca e ead 2 9 2 8 RTR ACP Virtual Memory SiZing 0000 eects 2 10 2 8 1 OpenVMS Virtual Memory SiZing 000 a 2 10 2 8 2 UNIX Virtual Memory SiZiINg 2 ke 2 12 2 9 Network Transports s sesi 2d estan the gad aie eee aa bea 2 13 2 9 1 Specifying the Link Transport Protocol 00000 cease 2 13 2 9 2 Using RTR with DHCP and Internet Tunnels 2 14 2 9 3 Interoperation with RTR Version 2 Using DECnet 2 15 2 10 Network Protocol Selection on OpenVMS 000000 eee eee 2 16 2 11 Running RTR as a Service on Windows NT 00 00 eee eee 2 16 2 11 1 Customizing the RTR Windows NT Service 0000005 2 17 2 11 2 Files Created by the RTR Windows NT Service 2 17 2 12 How RTR Selects Processing states Roles for Nodes
262. n a situation where two shadowed servers are configured the system administrator might decide not to replay recover all transactions in a shadowed RTR journal after a failure The SET TRANSACTION command could set specified transactions in a PRI_DONE or remember state to a DONE state and avoid the delay of transactions being remembered from a journal for fast recovery The SET TRANSACTION command should only be used by experienced RTR system administrators as the command introduces the risk of corrupting or losing transactions if used incorrectly It can be used on the backend only and the RTR log file must be turned on for this command Log file entries are made for all transaction state changes for debugging and auditing purposes 4 1 0 1 Command Line Examples An example of the use of the SET TRANSACTION command RTR gt start rtr RTR gt set log file settran RTR gt set transaction state PRI_DONE new_state DONE facility Facilityl partition Partitionl This example would set all transactions with the wildcard in the current state of PRI_DONE remember to DONE on the facility Facilityl and the partition Partition1 The log file settran would record the transaction state changes The changes could be viewed with the SHOW TRANSACTION command or the DUMP JOURNAL command In a shadow recovery situation this would clear the journal of remember transactions and provide for a fast recovery of access to the database if needed For
263. n_value REASON reason_value Issuing the CALL RTR_ACCEPT_TX command in preference to using the ACCEPT qualifier with the CALL RTR_SEND TO SERVER or CALL RTR_ REPLY_TO CLIENT commands is only necessary when you wish to specify an acceptance reason other than the default value of zero using the REASON qualifier RTR Command Line Interface 6 3 CALL RTR_ACCEPT_TX Qualifiers CHANNEL_NAMEschannel_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 window from which the call was issued to uniquely identify which channel to use 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 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 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 FORGET NOFORGET Use FORGET to specify the flags parameter as RTR_F_ACC FORGET in the call rtr_accept_tx The default for value for FORGET is NOFORGET wh
264. na if you specifically want DE Cnet transport to be used This is required for example when connecting to Version 2 2D ECO6 nodes as described in Section 2 9 3 of these Notes and Section 2 7 of the System Manager s Manual If you are using DECnet as the default you will need to use the node name prefix tcp to connect to other nodes using TCP IP transport If the value of the logical RTR_PREF_PROT is changed the new value takes effect only after RTR has been restarted e Reliable Transaction Router Version 3 2 for OpenVMS can use either Compaq TCP IP Services for OpenVMS or TCPware Version 5 1 as the TCP IP transport layer 2 11 Running RTR as a Service on Windows NT Once the RTR as Service has been installed see Installation Guide RTR may be started or stopped from the Control Panel Services panel using the START and STOP buttons provided e Tostart RTR Press the START button e To stop RTR Press the STOP button Note Pressing START and STOP or the reverse in quick succession within five or so seconds depending on the speed of your computer may cause undesirable results This is because the Service executes quickly making available the other action button but the requested RTR action may not have completed when the second action button is pressed It is therefore possible for example that the STOP action may be blocked by an incomplete START action Although the Service will claim to be STOPped
265. nal RTR log messages E 5 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 F INCOMPAT Incompatible RTR versions Explanation Attempt to start up an incompatible version of RTR on the same network with shared facilities RTR F INTERFERENCE Group system interference Start RTR from other account Explanation Internal error Send SPR RTR 1 OUEXCWRIT Exception written to journal for transaction A previous state A reason status A Explanation ndicates that an exception record has been written for the specified transaction Manual intervention is required in order to see the transaction through to completion RTR W OUFILFUL RTR journal file full use MODIFY JOURNAL to increase size Explanation The RTR journal file is becoming full Either reduce the number and size of concurrently active transactions or increase the size of the journal file using MODIFY JOURNAL MAXIMUM_BLOCKS RTR F OUHDRERR RTR journal record header error CREATE J OURNAL SUPERSEDE and submit SPR Explanation An inconsistency has been found in a record header within the RTR journal Corrective action 1 Reissue the RTR CREATE J OURNAL SUPERSEDE command 2 Restart RTR 3 Submit an SPR RTR E J OUNOTAVA Error during
266. nce The System Manager s Manual is intended for persons who perform system management functions to configure test monitor and maintain RTR applications The reader is assumed to be familiar with their operating system but not necessarily experienced with RTR operations New users of RTR are encouraged to read the first chapters of the Application Programmer s Reference Manual for a overall description of RTR Structure of Document The manual contains the following chapters and appendices Chapter 1 is an introduction to the RTR Command Line Interface CLI and tells you how to use local and remote commands and command procedures Chapter 2 explains how to start and configure RTR Chapter 3 describes RTR s Partition Management Chapter 4 gives an overview of RTR s Transaction Management tools Chapter 5 describes how the RTR monitor is used to continuously observe the performance and operation of RTR and applications using RTR Chapter 6 describes how to use the CLI interface to RTR API calls and contains a complete description of all RTR commands listed alphabetically Appendix A tells you how to create your own monitor pictures for special monitoring needs Appendix B describes server shadowing and recovery Appendix C describes how to use RTR with XA and ORACLE Appendix D contains a list of all the error messages that can be returned by the RTR CLI Appendix E contains a list of all messages that RTR can write to the R
267. nd is executed only on the node where the command was issued RTR Command Line Interface 6 55 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 If OUTPUT or file spec is omitted then the standard or default output is used Related Commands e CREATE FACILITY e SET PARTITION 6 56 RTR Command Line Interface DEFINE KEY DEFINE KEY Format Description Parameters Assign a string to a keyboard function key 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 This command lets you assign a string to a function key possibly overriding any predefined function that was bound to that key When you then press the key the RTR Utility enters the currently associated string into your command line The RTR DEFINE KEY command is similar to the OpenVMS DCL DEFINE KEY command A key definition remains in effect until you redefine the key or exit from the RTR Utility You can include key definitions in command procedures e g in the RTR Utility initialization file The IF_STAT
268. nd to be executed on the local node only RTR Command Line Interface 6 159 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 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 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 e REGISTER RESOURCE MANAGER e UNREGISTER RESOURCE MANAGER Examples RTR gt SHOW RM rmi_1 full Resource Manager RMI Name Nashua RMID yyy XA Switch Xaosw Library path 2 ZZZ Facilities associated with this RM Nashua 6 160 RTR Command Line Interface SHOW RTR SHOW RTR Format Description Qualifiers Display the configuration and status of RTR 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 The SHOW RTR command displays the configuration and status of RTR CLUSTER NOCLUSTER
269. nd was issued 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 REASON reason REASON 0 Use REASON to supply a value for the reason parameter in the call to rtr_reject_tx The default for value for REASON is 0 which causes the command server to use the value RTR_NO REASON for the reason parameter in the call to rtr_reject_tx Related Commands e CALL zel R_OPEN_CHANNEL e CALL ve R_ACCEPT_TX RTR Command Line Interface 6 29 CALL RTR_REJECT_TX Examples Reject the current transaction with a reason of 42 RTR gt CALL RTR_REJECT_TX REASON 42 SRTR S OK normal successful completion 6 30 RTR Command Line Interface CALL RTR_REPLY_TO_CLIENT CALL RTR_REPLY_TO_CLIENT Format Parameters Description The CALL RTR_REPLY_TO_CLIENT command causes a command server to execute the rtr_reply_to_client routine and to display the returned status CALL RTR_REPLY_TO_CLIENT message field1 message field2 message field1 message field2 Specify the message to be sent as one or more comma separated parameter values You can use the TYPE_OF_DATA and LENGTH_OF_DATA positional qualifiers on each parameter value to specify the data type and length of each field Command Qualifiers Defaults ACCEPT NOACCEPT CHAN
270. nder system UIC group one System UIC s cannot be used in group mode RTR Utility Error Messages D 25 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 Check your program and refer to the RTR Application Programmer s Reference Manual for permissible values RTR F UNRROUNAM Unrecognised api routine name for CALL Explanation The parameter for the CALL command is the name or part of a name of an rtr api routine This allows the user to type e g rtr call accept instead of rtr call rtr_accept_tx This message is issued if the user has specified a part of an api routine name that does not match the name of an rtr api routine RTR F VALREQ Missing qualifier or keyword value supply all required values Explanation A value must be specified for the keyword or qualifier RTR F VALTOOBIG Ox A is too big for A byte number Explanation A value has been specified that cannot be stored in the number of bytes specified Specify a smaller value or a larger number of bytes RTR E VERMISMAT RTR version mismatch Explanation Indicates that utilities and or sharable images being used are intended for a different version of RTR t
271. nding operation when the partition is deleted prior to completion of the operation RTR W PRTLCLRECEXIT Partition A A local recovery terminated by operator A Explanation Log message indicating that recovery wait override requested by operator RTR I PRTNEWFPOL Failover policy for partition A A set to A by operator A Explanation Log file entry indicating acceptance of an operator request to change the failover policy of the indicated partition Also appears when RTR automatically switches to pre V3 2 compatibility mode RTR I PRTNEWFPOLBE Failover policy change for partition A A received from router A new policy TAT Explanation Log file entry indicating receipt by a backend of an operator request to change the failover policy of the indicated partition Also appears when RTR automatically switches to pre V3 2 compatibility mode RTR I PRTNEWFPOLTR Failover policy change for partition A A received from backend A new policy TA Explanation Log file entry indicating receipt by a router of an operator request to change the failover policy of the indicated partition Also appears when RTR automatically switches to pre V3 2 compatibility mode RTR 1 PRTNEWPRI Priority for partition A A set to A by operator A Explanation Log file entry indicating acceptance of an operator request to change the backend priorities of the indicated partition RTR 1 PRTNEWPRITR Priority change
272. ndow from which the call was issued to uniquely identify which channel to use 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 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 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 GETITM item name item name No default Specifies the getitm parameter in the rtr_request_info call INFCLA infoclass No default Specifies the infcla parameter in the rtr_request_info call 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used SELITM item name No default Specifies the selitm parameter in the rtr_request_info call SELVAL item value No default
273. ne b Issue an RTR CREATE J OURNAL command D 12 RTR Utility Error Messages RTR Utility Error Messages RTR S OURNALINI Journal has been created on device A Explanation Confirms that the RTR journal has been successfully created on device A after issuing the CREATE J OURNAL command RTR S OURNALMOD Journal has been modified on device A Explanation Confirms that the RTR journal has successfully modified the size requirements on device A after issuing the MODIFY J OURNAL command RTR E KEYTYPEVAL Key type value for A missing try one of string signed unsigned Explanation The type clause of the key qualifier requires a value try one of string signed unsigned RTR F KNLEXECFAIL Knl_exec delivered pid of O starting A on node AIA Explanation ndicates that knl_exec failed when trying to start a command server RTR E KRINUSE Key range already in use respecify the key Explanation A call to rtr_open_channel to create a partition specified a key range that is already in use Respecify the key range RTR E KRINUSEINJ NL J ournalled transactions preclude change of partition name Explanation Transactions exist in the journal that were processed whilst this key range was assigned a different name This equates to an attempt to change the partition name which is not allowed Recover or delete these transactions first RTR I LFILREOPE Log file A A reopened Explanation
274. ne Interface 6 103 RECALL RECALL Format Description Parameters Qualifiers Examples Display a previously entered command for subsequent command editing RECALL command specifier Command Qualifiers Defaults ALL NOALL When you enter commands to the RTR Utility they are stored in a recall buffer for later use with the RECALL command Commands can be recalled by either entering the first few characters of the command or the command number The RECALL ALL command can be used to list the last twenty commands When you recall a command the RTR Utility displays the command but does not execute it If you want to execute the command as it appears press RETURN You can also use the command editing facility to make changes in the command line and then press RETURN to process the revised version of the command command specifier Specifies either the command number or the first few characters of the command you want to recall If command specifier is omitted then the most recently entered command is recalled ALL NOALL D Displays all the commands and their numbers available for recall RTR gt CREATE FACILITY QUOTES FRONT FE3 ROUTER TR2 1 RTR gt SHOW FACILITY LINK 2 RTR gt RECALL CREATE 3 RTR gt CREATE FACILITY QUOTES FRONT FE3 ROUTER TR2 4 RTR gt CREATE FACILITY ORDERS FRONT FE3 ROUTER TR2 5 1 Create facility QUOTES 2 Check the links 3 Recall the CREATE FACILITY command 4 C
275. nel called FINICHAN RTR gt CALL RTR_OPEN_CHANNEL CLIENT CHANNEL FIN1CHAN SRTR S OK Normal successful completion RTR Command Line Interface 6 21 CALL RTR_PREPARE_TX CALL RTR_PREPARE_TX Format Description The CALL RTR_PREPARE_TX command causes a command server to execute the rtr_prepare_tx routine and to display the returned status CALL RTR_PREPARE_TX Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL DATA data DATA 0 NODE node list NODE default node list OUTPUT file spec OUTPUT stdout REASON reason REASON 0 The CALL RTR_PREPARE_TX command causes a command server to call the rtr_prepare_tx routine using values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_prepare_tx routine itself is described in Application Programmer s Reference Manual The prototype of rtr_prepare_tx is rtr_status_t rtr_prepare_tx rtr_channel_t channel rtr_pre_flag_t flags rtr_reason_t reason rtr_msgbuf_t pmsg rtr_msglen_t msglen a Table 6 8 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 8 Parameters for rtr_prepare_tx C Parameter name C Parameter Value Command Line Specification channel flags reason pmsg msglen CHANNEL_NAME name
276. net connect objects has been exceeded Please use NCP to raise the maximum number of objects on this node RTR E TOOMANYSELITM More then one selitm specified in data class A Explanation More then one selitm specified in data class on call to rtr_request_info RTR E TOOMUCDAT Too much data to be monitored Explanation An attempt was made to monitor too many processes Please submit an SPR RTR E TOOSMALL A may not be less than A Explanation The value of qualifier A must be greater or equal to B RTR 1 TRMCENTRYNFND Notermcap entry for terminal type A Explanation No such entry was found in the termcap file for the terminal type For UNIX platforms please check that the environment variables TERM and or TERMCAP if used are correct Also check that the TERMCAP file if used has a valid entry for your terminal type NOTE These entries are case sensitive The default terminal type is vt100 RTR E TRNOTALLO32 Not all routers are at the minimum required version of V3 2 Explanation Cannot perform the requested action since not all routers are at a minimum version of V3 2 RTR F TRUNCATED Buffer too short for msg Explanation Buffer too short for message message truncated RTR F TXNOTACT Notx currently active on chan Explanation No transaction currently active on channel RTR E UICNOTGRP UIC A cannot be used in GROUP mode Explanation A SET MODE GROUP command was issued while running u
277. ng SHOW RTR COUNTER QRM Send SPR with RTRACP dump RTR F QCROVERFLOW QCR table has overflowed Explanation This status is used to indicate an inadequacy in the static reservations for the internal query context descriptors Send an SPR E 10 RTR log messages 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 F RAEOVERFLOW No more RAEs Explanation This status is used to indicate an inadequacy in the static reservations for the internal response acceptor elements Make a note of all QRM counters using SHOW RTR COUNTER QRM Send SPR with the corresponding RTRACP dump RTR F RDEOVERFLOW RDE table has overflowed Explanation This status is used to indicate an inadequacy in the static reservations for the internal response dispatch elements Make a note of all QRM counters using SHOW RTR COUNTER QRM Send SPR with the corresponding RTRACP dump RTR E REQDIED Client exited incomplete transaction aborted Explanation ndicates that a client exited before completing a transaction RTR E REQDIEDPREP Client exited after calling rtr_prepare tx transaction unresolved Explanation Indicates that a client exited after preparing a transaction RTR E REQDIEDVOT Client exited after i
278. ng a fmt string parameter LENGTH_OF_FIELD field length Enter the size of the message field that you want to define The default for string types is the length of the message entered plus one for the zero termination byte The default for signed and unsigned types is four This is a positional qualifier it must immediately follow the message field that it refers to 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RECIPIENT_SPEC rcpspc Enter a string specifying the recipient name The wild card characters and are permitted RECIPIENT_SPEC is case sensitive TYPE_OF_DATA STRING SIGNED UNSIGNED TYPE_OF_DATA STRING D Enter the data type of the message field that you want to define The default is the string type This is a positional qualifier it must immediately follow the message field that it refers to Examples This command broadcasts user event number 23 to all channels having a null string rconam the default A message is sent with the broadcast 6 8 RTR Command Line Interface CALL RTR_BROADCAST_EVENT RTR gt CALL RTR_BROA
279. ng should be sent with this message If FORMAT 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 FORMAT without fmt string 6 32 RTR Command Line Interface 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 ASW SL SIGNED 4 SL SL UNSIGNED 1 UB SL UNSIGNED 2 UW SL UNSIGNED UL SL Refer to Application Programmer s Reference Manual section Defining a Message Format Description for information on constructing a fmt string parameter INDEPENDENT NOINDEPENDENT Use the INDEPENDENT qualifier to specify the flags parameter RTR_F_ACC_ INDEPENDENT in the call to rtr_reply_to client LENGTH_OF_FIELD field length Enter the size of the message field that you want to define The default for string types is the length of the message entered plus one for the zero termination byte The default for signed and unsigned types is four This is a positional qualifier it must immediately follow the message field that it refers to NODE node list NODE default node list D Specifies that the command is executed on all nodes specified
280. nk and the number of bytes received and sent per second are displayed For each link displays the connection status in detail with the link state up or down and architecture type of remote node such as VAX 1386 Alpha and so on Displays the status of server partitions Shows the partition identifiers key ranges and key segments and the status of the servers active recovering and so on Shows transaction queues on a partition basis Tracks by facility the configuration reachability and quorum status of one or more nodes Displays memory used by each RTR subsytem Displays the status of server recovery procedures such as waiting for quorum catching up transactions and so on Displays the last rtr_mt_re jected message received by each running process Displays the last ten rtr_mt_rejected messages received by the selected process Displays the elapsed time that a transaction has been active on the opened channels of a process Displays router failback operations including both a summary and detail by facility A detailed picture of the various data items displayed in the QUORUM picture separated by roles If a quorum problem is encountered this picture may be useful for problem diagnosis Displays information on a router node It gives an indication of the utilization of the router in terms of transactions and broadcasts routed through this node Useful to monitor performance or locate problems Displays sta
281. o dia co eee e ee ee eee DES SHOW KEY SHOW LINK SHOW LOG SHOW MODE 0600 iia Seek Pi ae PEON eR PUAN a Ee SHOW NODE coisicagis data Aaa ra Od oe SHOW PARTITION coco tect o canes be ioe dae Dee ieee ee re eas SHOW PROCESS gt ute dee aed eee bade eee eR De eR eed ees SHOW REQUESTER sucia ey eee eee eee e wed Gea da ele SHOW RESOURCE MANAGER SHOW RM 000 0 2 eae SHOW RTR SHOW SEGMENT ii detec ana dae aot aa ke ea lec eek a ee aus we a SHOW SERVER ccc e al ews eee ele Pee ee Bae wee be SHOW TRANSACTION jcc cst cc adeir ede ea ea ee ewe ees SPAWN START RTR 6 67 6 72 6 77 6 81 6 83 6 86 6 88 6 89 6 90 6 91 6 95 6 96 6 98 6 100 6 103 6 104 6 105 6 107 6 108 6 109 6 112 6 116 6 118 6 120 6 122 6 125 6 129 6 131 6 133 6 135 6 136 6 140 6 142 6 144 6 146 6 148 6 150 6 152 6 156 6 158 6 159 6 161 6 163 6 165 6 168 6 171 6 172 STOP aie axe cities AR 6 177 ERIM FACIEVIIY pcan tent a ee ee eee ed oe RES eS 6 179 UNREGISTER RESOURCE MANAGER UNREGISTER RM 6 182 A Creating Monitor Pictures A 1 Interactive Definition of a Monitor Picture oooocccccnonn A 2 A 2 Substitution SYMDOIS a gass carr a a a ches A 3 A 3 Arithmetic Expressions and Operators 00 00 cece A 3 B Server Shadowing and Recovery B 1 Primary and Secondary Roles 0000 c cece eee eee B 1 B 2 Automatic Feat res osorno a Be EEE EES B 1 B 2 1 Shadow EVeNtS cevp
282. o rtr_start_tx requires a join TX parameter Also the formatlD field of the join TXID must be set to a valid value not RTR_XID_FORMATID_ NONE RTR F INVKSLENGTH Invalid ks length argument Explanation Invalid ks length argument RTR Utility Error Messages D 9 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 the format string or a mismatch in the number of bytes specified by the format string and the message length argument RTR F INVMSGLEN Invalid msglen argument Explanation Invalid msglen argument RTR E INVMSGSIZE Signed and unsigned data must be 1 2 or 4 bytes Explanation RTR F INVNUMSEG Invalid numseg argument Explanation Invalid numseg argument RTR E INVOBJ CT Specified object type invalid for managed object request Explanation Status return indicating that an invalid management object type was the target of an rtr_set_info command Check your program and the RTR Application Programmer s Reference Manual for valid managed object types RTR F INVOP4CLI Invalid operation for client channel Explanation Invalid operation for client channel RTR F INVOP4SRV Invalid operation for server channel Explanation Invalid operation for server channel RTR F INVPKEYSEG Invalid pkeyseg argument
283. o that which is currently running on the system This message can however be ignored when it is displayed after issuing the first STOP RTR command after having just installed a new RTR release RTR I WFPROCESS Waiting for A to start up Explanation Displays the name A of the operation that completed on a channel after issuing a SY S SY NCH command RTR E WILNOTALL Wild cards not allowed Explanation Wildcards and are not allowed RTR E WTTR Not in contact with sufficient router nodes please retry later Explanation Returned by a set partition command when either inquorate or no routers available to process the command Try again later when none of the above conditions exist D 26 RTR Utility Error Messages 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 E ABODEAREQ Transaction aborted that was started by client that has since exited Explanation Indicates that a transaction has been aborted that was started by a client that has since exited RTR E ABODEASRV Transaction aborted that was accepted by a server that has since exited Explanation Indicates that a transaction has been aborted that was sent to a server that has since exited RTR E ACCERR Rejecting connect attempt from unconfigured node A Explanation Node A which has not been configured as part of any RTR facility is t
284. o_server reply_to_client prepare_tx accept_tx reject_tx broadcast_event set_user_handle get_tid request_info set_info error_text set_wakeup receive_message user wakeup client 1 SS calls 9 0 server 1 0 OOS S S active 1 0 fail 0 SS E aae 3 3 o a ola oo Se 3 fail 2 PID 2162 Fri Feb 12 1999 ESSAGES t_opened t_closed t_msg1 t_msgl_uncertain t_msgn t_reply t_rettosend t_prepared t_accepted t_rejected t_user_event t_rtr_event t_prepare t_request_info t_set_info t_closed timeout 2 RTR Monitoring 5 2 Standard Monitor Pictures Process name client 1 0 CO EAS eS Se other ALL 16 38 05 server pend 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Displays the total number of RTR API calls and their outcome for the processes on all the nodes being monitored Use the ID ENTIFICATION process id qualifier to display the values for one specific process otherwise the total values for all processes are displayed 5 2 7 Monitor Channel RTR CHANNELS BY TYPE PER PROCESS Fri Feb 12 1999 16 41 13 Node nodea ID 2162 Process 2162 I mage Client Serv Pri 1 0 er Call out Sby Router Backend 0 0 0 Displays the channels opened by RTR CALL RTR_OPEN_ CHANNEL comands 5 2 8 Monitor Connects Connection St Node nodea zuo dec com Executive summary Number of links up
285. ocation and size of the journal using the CREATE JOURNAL command The CREATE JOURNAL command must be issued on each node where an application server will run That is on each backend node and on any router nodes where router call out servers will run It must be issued after installing RTR and before creating any facilities It may be issued again later to alter the size or location of the journal to improve performance Use the MODIFY JOURNAL command to adjust journal sizes Cautionary Note for Journals e The CREATE JOURNAL SUPERSEDE command deletes the contents of any existing journal files If transaction recovery is required DO NOT ISSUE this command after a failure e Do not make backup copies of journal files without first making the original journal file read only or the journal files will be considered spurious by RTR because it sees journal files that it did not create In this case RTR will issue a RTR F SPUJOUFIL error message Starting and Setting Up RTR 2 3 Starting and Setting Up RTR 2 3 Creating a Recovery Journal e 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 e Track duplicate copies of journal files in the log file to prevent RTR seeing more than the one it created and issuing the SPUJ OUFIL error message e If it is determined that a jou
286. of the journal disk set Explanation A disk was specified as part of a MODIFY JOURNAL command which was not part of the original disk set specified in the CREATE J OURNAL command RTR E DTXNOSUCHRM Thereis no such RM registered Explanation There is no such RM registered RTR W DTXREADONLY The transaction branch was read only and has been committed Explanation The RM will simply return an warning indicating the transaction branch was read only and has been committed already RTR E DTXRMBUSY DTX RM is still in use by RTR Explanation the DTX RM is still referenced by at least one RTR facility or open channel RTR E DTXRMEXISTS The DTX RM has already been registered Explanation The RM has already been registered RTR E DTXTOOMANYRMS Too many RMs or instances of an RM have been registered Explanation The RTR ACP has registered too many gt 16 RM instances D 4 RTR Utility Error Messages RTR Utility Error Messages RTR F DUP OUFIL Duplicate RTR journal file found remove duplicate file or CREATE J OURNAL SUPERSEDE Explanation A duplicate RTR journal file has been found This status may be returned by the CREATE FACILITY and SHOW J OURNAL commands Probable cause System management error A user has copied a journal file or a disk containing a journal file RTR can now see both the original and the copy and does not know which to use Corrective action either a Check the log for the relevant filen
287. ommand Line Interface 6 39 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 for the qualifiers SIGNED UNSIGNED STRING and LENGTH The following table shows permitted values for these qualifiers when using FORMAT without fmt string Table 6 15 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 SL UNSIGNED 2 UW SL UNSIGNED 4 UL SL Refer to Application Programmer s Reference Manual section Defining a Message Format Description for information on constructing a fmt string parameter LENGTH_OF_FIELD field length Enter the size of the message field that you want to define The default for string types is the length of the message entered plus one for the zero termination byte The default for signed and unsigned types is four This is a positional qualifier it must immediately follow the message field that it refers to 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 informati
288. ommand Qualifiers Defaults OUTPUT file spec OUTPUT stdout STATUS status code none Description The CALL RTR_ERROR_TEXT command causes a command server to call the rtr_error_text routine using the value supplied on the command line The rtr_error_text routine itself is described in Application Programmer s Reference Manual The prototype of rtr_error_text is char rtr_error_ text rtr_status_t sts i Table 6 5 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 5 Parameters for rtr_error_text C Parameter Name Parameter Value Command Line Specification sts 42 42 parameter Qualifiers 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 STATUS status code No default Specifies the sts parameter in the rtr_request_info call Examples This command shows the text associated with error number 4849722 RTR gt CALL RTR_ERROR_TEXT STATUS 4849722 error text normal successful completion 6 12 RTR Command Line Interface CALL RTR_GET_TID CALL RTR_GET_TID Format Description 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 Command Qualifiers Defaults CHANN
289. ommand resulting in the removal of all roles is equivalent to a DELETE FACILITY command A frontend role can be removed from a node with the router role as long as there is at least one other frontend defined A backend role can be removed from a node with the router role as long as at least one other backend is defined A command to remove a backend role should be executed on all router nodes to avoid problems with inconsistent facility definitions If a router role is removed then the node from which it is removed will discard its knowledge of other backends and frontends in the facility If the router role is re added to the node using EXTEND FACILITY this information will have to be specified again In order to have a consistent facility definition across the nodes of the facility avoiding problems with attaining quorum the command to remove a router role must be executed on all relevant nodes This means executing the command on the node losing the router role plus all backend and frontend nodes which know about this router As with CREATE or MODIFY FACILITY nodes or roles may be specified which are superfluous That is you may specify backend nodes on a node which only has a frontend role and frontend nodes may be specified on a node which only has a backend role This permits a single RTR management command to be issued on many nodes and each node only accepts those parts of the command which are relevant to it When using
290. on fails The default action is to allow a standby of the primary to become the new primary Optionally RTR can be set to change state so that the secondary becomes primary and a standby of the old primary if any becomes the new secondary 6 122 RTR Command Line Interface 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 of either a local or remote journal this command can be used to override the default RTR behaviour It instructs RTR to skip the current step in the recovery process Since this command bypasses parts of the recovery cycle use it with caution and only when availability is more important than consistency in your application databases PRIORITY_LIST backend node list Sets a relative priority that is used by RTR when selecting a backend member to make active Enter a list of the backends in your configuration in decreasing order of priority the relative order of the list will be taken into consideration when RTR is determining on which node to make a partition active It is not an error to enter different versions of the priority list at different backends but this is not recommended It is recommended to suspend partitions before changing the priority list RECOVERY_RETRY_COUNT n The recovery retry count indicates the maximum number of times that a transaction s
291. on is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used READONLY NOREADONLY The READONLY qualifier sets the flag RTR_F_SEN READONLY in the call rtr_send_to_server RETURN_TO_SENDER NORETURN_TO_SENDER The RETURN_TO_SENDER qualifier sets the flag RTR_F_SEN_RETURN_TO SENDER in the call rtr_send_to_server TYPE_OF_DATA STRING SIGNED UNSIGNED TYPE_OF_DATA STRING D Enter the data type of the message field that you want to define The default is the string type This is a positional qualifier it must immediately follow the message field that it refers to 6 40 RTR Command Line Interface CALL RTR_SEND_TO_SERVER Examples This command sends a message to a server The message is type string the default RTR gt CALL RTR_SEND_TO_SERVER Get that info for me please SRTR S OK Normal successful completion RTR Command Line Interface 6 41 CALL RTR_START_TX CALL RTR_START_TX Format Description The CALL RTR_START_TX command causes a command server to execute the rtr_start_tx routine and to display the returned status CALL RTR_START_TX Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER JOIN_TXID txid number NOJOIN_TXID NODE node list NODE default node list OUTPUT file spec OUTPUT stdout TIMEOUT_MS timoutms TIMEOUT_MS 0 TXID_TYPE txid type TXID_TYPE RTR
292. onfirmed by A Explanation A connection request has been confirmed by RTRACP running on node A RTR I CNCTLOST Connection to A lost Explanation DE Cnet connection with node A lost RTR W CNCTREJ BY Connection request rejected by A Explanation RTRACP on node A rejected a connect request from this node RTR W CNCTREJ FR Connection request from A rejected Explanation RTRACP on node A made a connect request which had to be rejected RTR E COMDEAREQ Transaction committed that was started by client that has since exited Explanation Indicates that a transaction has been committed that was started by a client that has since exited RTR E COMDEASRV Transaction committed that was accepted by a server that has since exited Explanation ndicates that a transaction has been committed that was sent to a server that has since exited RTR I COMJOUSEA Commencing journal search for transactions on facility A needing recovery Explanation J ournal search is starting This message appears when RTR is started RTR E COMSRVFAIL Command server failed diagnostics written to A Explanation An instance of the RTR command server process has failed report occurrence together with supporting information on current command to RTR Engineering RTR log messages E 3 RTR log messages RTR I CONNALIAS Link A connected as A Explanation Support for internet tunnels allows for the configuration of
293. or 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 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 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used This command shows the transaction id active on channel CLIENT1 RTR gt CALL RTR_GET_TID CHANNEL CLIENT1 SRTR S OK normal successful completion tid e100b810 0 0 0 0 3bc5 6eb02001 6 14 RTR Command Line Interface CALL RTR_OPEN_CHANNEL CALL RTR_OPEN_CHANNEL Format Description 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 Command Qualifiers ACCEPT_EXPLICIT ACCESS access BE_CALL_OUT CHANNEL_NAMEschannel name CLIENT CLUSTER CONCURRENT EVENTS event nr list
294. or tuning capacity planning and locating configuration and application errors The information displayed is composed of named data items which are continuously updated by RTR These data items can be displayed in various formats and combined using simple arithmetic operators and constants The monitor is invoked with the RTR MONITOR command RTR monitor displays a monitor picture that is periodically updated See Section 6 2 for the full syntax of the MONITOR command A monitor picture contains elements that are either text such as labels and titles or variables derived from data items Monitor pictures can be defined either interactively at the RTR gt prompt or defined in a file called a monitor file You can use monitor files that are provided with RTR and you can create your own See Appendix A for information about creating monitor files 5 2 Standard Monitor Pictures A number of standard monitor pictures are supplied with RTR These cover most of the usual monitoring requirements You may define your own monitor pictures or alter the standard ones to suit your particular needs Table 5 1 contains a list of the standard monitor pictures To display one of these pictures use the following command at the RTR prompt RTR gt MONITOR picture name The files for standard monitor pictures are installed on your system when RTR is installed The location of these files is platform specific The filenames are the picture name appended wi
295. ournals on DFS supported disks RTR I DISABMOD A mode disabled Explanation Displays the name A of the mode that was disabled after issuing a SET MODE command RTR Utility Error Messages D 3 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 DISPLAY 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 W DISKMNTVER Disk is currently under mount verification Explanation An attempt was made to create a journal on a disk which is in mount verification Try later RTR W DISKMOUFOR Disk is mounted foreign Explanation An attempt was made to create a journal on a disk which is mounted foreign Please check disk for proper mount status RTR W DISKNOTMOU Disk is not mounted Explanation An attempt was made to create a journal on a disk which is not mounted Please check disk for proper mount status RTR W DISKSSM Disk is member of shadow set Explanation An attempt was made to create a journal on a disk which is a member of a shadow set RTR cannot locate journal on individual shadow set members RTR W DISKSWL Disk is software write locked Explanation An attempt was made to create a journal on a disk which is software write locked RTR E DSKNOTSET Specified disk not part
296. ovided to facilitate testing For example clients may be tested before the corresponding servers have been written by manually entering the server s API calls 6 1 Introduction The commands that invoke the RTR API calls are similar to the call names For example the rtr_accept_tx call is invoked using CALL RTR_ACCEPT_TX at the CLI level Where possible command qualifiers have been given the same names as the parameters to the API calls See the Application Programmer s Reference Manual for details about the parameters to API calls Most commands can be issued on remote nodes by using the NODE node list or CLUSTER qualifiers or by preceding them with the SET ENVIRONMENT command to specify nodes where commands are to be executed Commands such as DEFINE KEY are intended for local execution only Output from each command can be redirected to another device or file using the OUTPUT qualifier Because the RTR command utility keeps parameter checking to a minimum what if questions can be answered quickly without having to write test programs Note In a mixed RTR Version 2 and Version 3 environment you cannot execute commands remotely with the NODE qualifier 6 2 RTR Command Reference This section describes in detail each command in the RTR command utility The command descriptions are presented in alphabetical order RTR Command Line Interface 6 1 ADD FACILITY ADD FACILITY See CREATE FA
297. own default quorum value is shown as zero and the minimum broadcast rate if it has been set RTR Command Line Interface 6 137 SHOW FACILITY On a frontend this qualifier can be used to find out whether the node is currently connected to a router Related Commands e CREATE FACILITY e DELETE FACILITY e SHOW LINK Examples RTR gt SHOW FACILITY FULL NODE BRONZE 1 Facility FUNDS_TRANSFER 2 Configuration 3 Frontend no Router yes Backend yes Router call out no Backend call out no Load balance no Quorum check off no State 4 FE gt TR unused Router quorate yes Backend quorate yes Quorum threshold Q Min broadcast rate 0 Links 5 Link to bronze Frontend no Router yes Backend yes Router gt Frontend no Frontend gt Router no Backend gt Router yes Router gt Backend yes Router quorate yes Backend quorate yes Router current no Backend coordinator yes Link to airola 6 Frontend yes Router no Backend no Router gt Frontend yes Frontend gt Router no Backend gt Router no Router gt Backend no Router quorate no Backend quorate no Router current no Backend coordinator no 1 Show all facilities in detail 2 The facility s name 3 The facility s configured roles on this node In this example the node is a router and a backend load balancing router callouts and backend callouts are not enabled 4 The facility s state The
298. ple of how to use the CLEAR command 6 46 RTR Command Line Interface CREATE FACILITY CREATE FACILITY Format Description Parameters Create an RTR facility and ready it for transaction traffic 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 FRONTEND frontend list NOFRONTEND NODE node list NODE default node list OUTPUT file spec OUTPUT stdout REPLY_CHECKSUM NOREPLY_CHECKSUM RESOURCE_MANAGER resource list ROUTER router list NOROUTER The CREATE FACILITY command configures defines on a node an RTR facility and readies it for transaction traffic that is establishes links to other the participating nodes The command must be issued on all participating nodes before any application programs using the facility are started Note Router nodes must have all backend nodes defined and Backend nodes must have all router nodes defined Routers need only be defined with the frontends that they can connect to Frontends need only be defined with the routers they can connect to facility_name Specifies the name of the facility to be created Any application program which uses this facility must specify the same name when it calls rtr_open_channel Facility names can contain up to thirty one characters Letters numbers and und
299. r createfacil or at the RTR prompt rtr RTR gt execute createfacil or RTR gt createfacil 1 5 Remote Commands Most RTR commands can be issued either locally the default or on one or more remote nodes To be able to issue commands to a remote node you must have an account on that node with the necessary access privileges Refer to your operating system documentation for information on how to set up the access privileges To specify the remote node names explicitly RTR gt command node node list To specify remote nodes implicitly if for example the command is to be executed in every node of a clustered environment use a command of the following form RTR gt command cluster Examples RTR gt start rtr node nodeA nodeB nodeC Introduction 1 3 Introduction 1 5 Remote Commands This command starts RTR on the three nodes Note The CLUSTER and NOCLUSTER command qualifiers refer to cluster support These qualifiers are for operating systems that fully support clustering Use of the CLUSTER qualifier on systems that do not have clustering causes the relevant command to be executed on the local node only For example Windows 95 systems do not support clustering If several commands need to be executed remotely on the same nodes then the set environment command can be used to save typing For example RIR RTR gt set environment node nodeA nodeC RTR gt stop rtr This example show
300. r manner to the VOTED to COMMIT situation described above the server has been separated from the other participating servers and all other participants aborted this transaction use this command to manually abort the local transaction branch Note that this command is only applicable if there is no coordinating router running and servers are separated from the rest of the RTR network If this is not the case RTR rejects the command 4 State COMMIT changed to state DONE Transaction Management 4 3 Transaction 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 After the SET TRANSACTION command is executed the DUMP JOURNAL command can be used to verify the result 4 4 Transaction Management 9 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 5 1 Introduction The RTR monitor provides a means to continuously display the status of RTR and the applications using it It can be used to check the correct operation of an RTR network showing information useful f
301. rations e Any physical reference to the transaction which is unique to the executing server e g Channel Id system time DB key etc should not be passed back to the client for future references within its subsequent messages as this could lead to inconsistent handling when a different server is involved in shadow operations This consideration is also valid for recovery of non shadowed servers B 9 Server States The current state of a server can be examined as follows RTR gt show server full Servers Process id 13340 Facility RIRSDEFAULT_FACILITY Channel 131073 Flags SRV State active Low Bound High Bound 87 13 rcpnam RTRSDEFAULT_CHANNEL User Events 0 RTR Events 0 Partition Id 16777216 Process id 13340 Facility RIRSDEFAULT_FACILITY Channel 196610 Flags SRV State active Low Bound 88 13 High Bound Of rcpnam CHAN2 User Events 0 RTR Events 0 Partition Id 16777217 Figure B 2 gives an State field B 6 Server Shadowing and Recovery overview of the server state changes which appear in the Server Shadowing and Recovery B 9 Server States Figure B 2 Server States DD COS8 NOV 1991 172335 Server Shadowing and Recovery B 7 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 gt show client full Clients Process id 13340 Facility RTRSDEFAULT_FACILITY Channel 458755 Flags CLI
302. rce name must be a letter The default value for resource_name iS RTRSDEFAULT_RESOURCE Related Commands e UNREGISTER RESOURCE MANAGER e SHOW RESOURCE MANAGER RTR Command Line Interface 6 105 REGISTER RESOURCE MANAGER REGISTER RM Examples RTR gt REGISTER RM rmi_1 open_string 0racle_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 screen is to be scrolled Can be one of LEFT RIG HOM of the screen amount Specifies the number of rows columns by which the screen is scrolled Amount is ignored if direction is specified as HOME Related Commands Examples MONITOR HT UP DOWN or HOME E scrolls the picture so that its top left corner coincides with the top left corner RTR gt MONITOR TPS INTERVAL 10 1 RTR gt SCROLL UP 10 2 RTR gt SCROLL HOME 3 Display the TPS picture This picture displays each process using RTR on a separate line If there is insufficient space on the screen to display them all the SCRO processes
303. ring use of the CLUSTER qualifier will cause the relevant command to be executed on the local node only COUNTER counter name NOCOUNTER D Specifies that the process counters are also to be displayed counter name is the name of the counter to be displayed If counter name is omitted then all counters will be displayed counter name may contain wild card characters IDENTIFICATION process id NOIDENTIFICATION D Specifies the process about which information is required The default NOIDENTIFICATION displays all processes using RTR FULL NOFULL D Equivalent to specifying COUNTER 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 6 156 RTR Command Line Interface 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 gt SHOW PROCESS Processes Process id Process Name 326 RTR Command Line Interface 6 157 SHOW REQUESTER SHOW REQUESTER See SHOW CLIENT The SHOW REQUESTER command has been replaced by SHOW CLIENT and is retained for compatibility reasons only 6 158 RTR Command Line Interface SHOW RESOURCE MANAGER SHOW RM SHOW RESOURCE MANAGER SH
304. ription Qualifiers Sets various facility related options 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 list OUTPUT file spec OUTPUT stdout REPLY_CHECKSUM NOREPLY_CHECKSUM The SET FACILITY command sets the router load balancing and quorum characteristics of a facility BROADCAST_MINIMUM_RATE Bps BROADCAST_MINIMUM_RATE 1000 BROADCAST_MINIMUM_RATE nnnn specifies the minimum rate in bytes per second to which flow control can reduce broadcast traffic on outgoing facility links from the node concerned For example consider a facility has 100 frontends and 99 of them are able to receive data at a rate of 2KB per second but one frontend has become congested and is not able to receive any This can result in all the frontends slowing down to the rate that the slowest can accept Specifying BROADCAST_MINIMUM_RATE 2000 on the router ensures that the 99 frontends receive their broadcasts and that RTR attempts to send the broadcasts to the congested frontend However broadcasts for the congested frontend are discarded if absolutely necessary rather than slowing down all frontends to the rate that the slowest can accept Specifying BROADCAST_MINIMUM_RATE without a value gives a default 1000 bytes per second if you do not use the quali
305. ritten to the journal as an exception record Subsequent processing of this transaction requires manual intervention by someone qualified to evaluate and correct the situation in both the application and in RTR Once the application status is understood the set transaction command can be used to update the journal thus insuring that the final state of any manually transacted exceptions are accurately reflected in future recovery operations The recovery retry count indicates the maximum number of times that a transaction should be presented for recovery before being written to the journal as an exception Once a transaction has been recorded as an exception it is no longer considered eligible for recovery and requires manual processing by a qualified individual The recovery retry count is partition specific and applies to both local and shadow recovery operations The default is no limit on the number of retries which permits a killer message to bring down all available servers servicing a given partition The recovery retry count should be set before starting or restarting the application servers so that the limit is established prior to the start of recovery operations 3 6 6 1 Command Line Example RTR gt SET PARTITION RECOVERY_RETRY_COUNT 3 Facilityl Partitionl For more information on the SET PARTITION command see Chapter 6 3 6 6 2 Programming Information To set the partition transaction recovery limit program the set_qualifier
306. rk Indications u u u A Explanation A node has received an unrecognised broadcast event from the indicated node If the sending and receiving nodes are running compatible versions of RTR the cause of this might be message corruption If the condition persists consider performing a network health check RTR F BRODISBLO Broadcast message s discarded because of network blockage Explanation One or more broadcast messages had to be discarded because the network throughput is not fast enough Reduce broadcast rate or increase communications link capacity RTR F BRODISCAC Broadcast message s discarded because of memory cache congestion Explanation One or more broadcast messages had to be discarded because local memory was exhausted Reduce the rate at which broadcasts are sent or increase the efficiency of broadcast processing by the recipient applications E 2 RTR log messages 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 I CLUENABLED RTR cluster A is enabled using A Explanation Information message indicating whether RTR is making use of any specific cluster software RTR S CNCTACCFR Connection request from A accepted Explanation A connection request from RTRACP running on node A has been accepted RTR S CNCTCFRM Connection c
307. rnal the order in which the transaction is to be committed In the event of a failure at this point the remaining site executes a short tidy up operation and as soon as it has done this and determined that the other site is really down it reverts to the REMEMBER state and carries on processing new transactions autonomously saving the transaction information in its journal for when the other site restarts The execution order is determined for transactions issued to concurrent servers on a particular node by recording the order in which the individual servers issue rtr_accept_tx calls RTR knows that at the time a correctly written server application calls rtr_accept_tx it has already accessed and hence locked any database records it uses and that it will release these records after RTR causes the rtr_accept_tx call to complete Any conflicting transaction would not be able to issue rtr_accept_tx concurrently Hence a correct serialisation order for issuing the transactions on the shadow site can be determined B 8 Application Considerations Although applications need not be directly concerned about Shadowing matters certain points must be taken into consideration when implementing performance boosting optimizations e Anything specific to the executing node should not be stored in the database since this would lead to diverging copies Server Shadowing and Recovery B 5 Server Shadowing and Recovery B 8 Application Conside
308. rnal is SPURIOUS by means other than improper copying then a backup copy followed by a destruction of the transactions contained in a journal can be performed by the CREATE JOURNAL SUPERCEDE command 2 4 Changing a Facility RTR facilities can be altered either by deleting and re creating them using the delete facility create facility commands Alternatively you can use the extend facility and trim facility commands With sufficient redundancy in a system facility modification can be carried out with minimal interruption to the application Note The RTR facility defines the nodes used by an application and the roles frontend router backend they may assume You do not need to change facility definitions in the event of node or link failures In the example in Figure 2 1 assume that the FE3 node is being removed from the FUNDS TRANSFER facility Since FE3 is a frontend for this facility only the routers TR1 and TR2 need be reconfigured The routers can be reconfigured one after another so that the service provided to the remaining frontends FE1 and FE 2 is not interrupted Example 2 3 shows the delete facility and create facility commands that are issued from node BE 1 for example in order to achieve this reconfiguration 2 4 Starting and Setting Up RTR Starting and Setting Up RTR 2 4 Changing a Facility Example 2 3 Reconfiguration Using Delete and Create Facility rtr RTR g
309. rnal is currently in use by another user This status may be returned by the CREATE J OURNAL and DELETE J OURNAL commands Corrective action either Wait for the other user to complete and reissue the command RTR E J OUNOTAVA Error during recovery A from A journal A Explanation RTR transaction manager requested recovery from a remote journal but the request could not be delivered to the node hosting the journal In a non clustered standby configuration this indicates that local recovery after a server failure could not be completed No user action required since the transaction manager will attempt to send the recovery query again once it has detected that the remote journal has become available RTR F OUNOTFOU Journal not found Explanation No RTR journal files can be found This status may be returned by the CREATE FACILITY DELETE J OURNAL and SHOW J OURNAL commands Either 1 You have not issued an RTR CREATE J OURNAL command 2 All journal disks are offline 3 The journal files have already been deleted RTR F OUNOTINI Journal has not been created CREATE JOURNAL Explanation No RTR journal files can be found This status may be returned by the CREATE FACILITY and SHOW J OURNAL commands Either 1 You have not issued an RTR CREATE J OURNAL command 2 All journal disks are offline 3 The journal files have been inadvertently deleted Corrective action either a Bring the journal disk on li
310. roduction of the SEPARATE TOTALIZE and AVERAGE qualifiers has superseded the qualifiers FACILITY LINK PARTITION NODE and PROCESS These superseded qualifiers are no longer described here however they are still supported expression The string you want to display enclose it in quote marks name of a single RTR data item AVERAGE keyword NOAVERAGE Expression can be the 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 RTR Command Line Interface 6 77 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_TRANSACTION Router transaction data items BLANK Boolean expression NOBLANK D Specifies that the displayed value is replaced by blanks if Boolean expression evaluates to True non zero BLINK Boolean expression NOBLINK D Specifies that the displayed value blinks if Boolean expression evaluates to True non zero BOLD Boolean expression NOBOLD D Specifies that the item is displayed in high intensity if Boolean expression evaluates to True non zero JUSTIFY keyword JUSTIFY LEFT D Specifies whether justific
311. rs Examples 00 00 cece eee A 4 vii Figures 2 1 2 2 A 1 B 1 B 2 B 3 B 4 Tables viii i 4 19 5 1 5 2 5 3 IA ISA AA ee ae ee e id ce id vilo ad il call cl cl e P 6 19 6 20 6 21 6 22 6 23 6 24 6 25 A 1 Configuration Example 0 i 04 68260204 red be ee SPa eG eed eed Extend Configuration Example 00000 e eee eee ees Interactively Defined Monitor Picture 000 eevee Four Node Shadow Standby Configuration 45 Server States ganean g aa hee Gee i bak o ea Boar Pelee ee we Client States cui Peewee aa G Ea Ea eee in hee ede ved Router Partition States irsi cc aea ani ai oda aa wemi gt ai ian dew ans Conventions Used in this Guide 0 eee ee Valid Transaction State Transitions s a s asasan aaa Standard Monitor PiCtures o ooooooooooo MONITOR GROUP FieldS 0 000 e eects Monitor Partition States 0 0 Monitor Recovery States 0 00 cee es MONITOR REJ ECTS Fields 3 csc 0 04 p00 se eae eae eee news MONITOR REJ HIST FieldS 0 000 c cece es Parameters for rtr_accept_tX ai eiii saie aoai iia eee Parameters for rtr_broadcast_event 0 0 cee eee ee Generated Format StringS 0 000 eee Parameters for rtr_close_channel 0 0 c eee eee ee Parameters for rtr_error text 0 0 cece ees Parameters for rtr_get tid 0 0 cee ee ee Parameters for rtr_open_channel 0
312. rst router specified is not available the next one on the list is chosen When the facility is created on the frontend the list of routers specified can be a subset of the routers contained within the entire facility This can be used to prevent a frontend from selecting a router that is reserved for other frontend systems Fail back of routers is supported This means that if the preferred router was not available and it became available later the frontend would automatically fail back and connect to its preferred router Router connectivity can also be controlled through the use of the BALANCE qualifier either on the CREATE FACILITY command or on the SET FACILITY command When the BALANCE qualifier is used the list of routers specified in the router list is randomized making the preferred router a random selection within the list Assume the following command is issued from a frontend RTR CREATE FACILITY test FRONTEND Z ROUTER A B C The frontend attempts to select a router based on the priority list A B C with A being the preferred router If the BALANCE qualifier is added to the end of this command then the preferred router is randomly selected from the three nodes This random list exists for the duration of the facility After the facility is stopped a new random list is made when the facility is created again The exception to this is if a router does not have quorum sufficient access to backend systems then that router wi
313. rsue in selecting the new primary site in the event of a failure e FAILOVER_POLICY STANDBY causes RTR to choose a standby of the failed primary if any to become the new primary If there is more than one standby the operator may addition use the priority list feature described above to control which standby is preferred Depending on the size of the journal of the failed primary there will be a hold up in the processing of transactions whilst the journal is recovered This is the default behaviour e FAILOVER_POLICY SHADOW instructs RTR to make the active secondary if any the new primary A standby of the failed primary if any will be elected to become the new secondary This option gives the shortest fail over time but will move the primary to a different cluster that you may have located at a different site e FAILOVER_POLICY COMPATIBLE_PRE_V32 is a mode that will operate with configurations that contain RTR routers running versions of the software prior to V3 2 This mode will be automatically adopted if such routers exists in or join the configuration 3 6 5 1 Command Line Example An example use of the FATLOVER_POLICY qualifier RTR gt SET PARTITION FAILOVER_POLICY SHADOW Facilityl Partitionl For more information see the SET PARTITION command in Chapter 6 3 6 5 2 Programming Information To set the partition failover policy program the set_qualifier argument of the rtr_set_info call as
314. rying to establish connection This could be a misconfiguration problem or simply a problem with the setting up of the DNS service if DECnet OSI is running RTR F ACPINSRES The RTR ACP has insufficient resources details in the rtr log file Explanation The RTR ACP was unable to perform an operation due to an unusual condition This is most probably a resource issue e g when the ACP cannot create a shared memory segment The RTR log file for contains more details of the problem RTR E ALRDCNCTD Remote node already connected Explanation This can be a reason for rejecting a connect request Submit an SPR RTR E ALRINPRGS Connection already in progress Explanation This can happen if both ACPs simultaneously try to connect to each other Submit an SPR RTR E BADENVVARIABLE Environment variable A has bad value A Explanation Log file message indicating that an environment variable has been defined with an illegal value RTR log messages E 1 RTR log messages RTR E BADIDSIZ Bad node ID size A detected at Ox A Explanation This message indicates that errors have been detected in processing of an internal node identifier The presence of this message indicates a serious problem in the configuration of the network name address databases and RTR will likely be unable to operate correctly Quorum and fault tolerance will be adversely affected Check all network databases for consistency of node amp host name and address
315. s and indicate an occurrence of a single wild character RTR F TIOSYS FAILURE General failurein TIO Explanation General failure in terminal I O RTR F TIO BADROWCOL The terminal is defined as rows A and cols A Explanation Cannot use the terminal rows or columns is set to 0 For UNIX platforms please use stty a to check rows and columns Then use a command like stty rows 50 cols 132 to set them correctly RTR E TOOBIG A may not be greater than A Explanation The value of qualifier A must be less or equal to B RTR F TOOMANCHA Too many channels already opened Explanation Too many channels already opened D 24 RTR Utility Error Messages RTR Utility Error Messages RTR E TOOMANCHN Too many channels Explanation Displayed when a SYS DCL_TX_PRC command is issued and the channel table is full RTR F TOOMANDIS Too many disks specified in journal definition Explanation Explanation Too many disks were specified in journal definition The RTR journal can be defined to use up to a maximum of sixteen disks User Action Issue the CREATE J OURNAL command specifying a smaller number of disks RTR F TOOMANREC Too many records for one entry in the journal Explanation An attempt was made to write more than 65534 records to one entry transaction in the journal RTR E TOOMANYOBJ Max DECnet objects exceeded raise and retry command Explanation The executor limit on the number of DEC
316. s kbytes send kbytes Messages recv kbytes rtracp 44 19 29 19 29 86 2 3123B84F 0 0 0 0 0 0 0 31232395 28 2 28 2 41 110 18 Displays interprocess communication rate information for messages 5 2 15 Monitor Journal JOURNAL USAGE ON NODE NODEA AT 10 36 05 Tue Apr 6 1999 LOCAL JOURNAL STANDBY JOURNAL S JNL_LCL_BLOCKS_IN_USE 128 JNL_RMT_BLOCKS_IN_USE 0 13 0 JNL_LCL_NR_BLOCKS 992 JNL_RMT_NR_BLOCKS 992 JNL_LCL_TOP_BLOCKS_USED 128 JNL_RMT_TOP_BLOCKS_USED 0 JNL_LCL_BLOCKS_AVAILABLE 864 JNL_RMT_BLOCKS_AVAILABLE 0 JNL_LCL_TX_ENTRIES il JNL_RMT_TX_ENTRIES 0 JNL_LCL_TX_RECORDS 2 JNL_RMT_TX_RECORDS 0 JNL_LCL_MEMORY_BYTES 530121 JNL_RMT_MEMORY_BYTES 4197 JNL_LCL_DISK_READS 31 JNL_RMT_DISK_READS 33 JNL_LCL_BLOCKS_READ 992 JNL_RMT_BLOCKS_READ 1056 JNL_LCL_DISK_WRITES 12 JNL_RMT_DISK_WRITES 0 JNL_LCL_BLOCKS_WRITTEN 14 JNL_RMT_BLOCKS_WRITTEN 0 JNL_LCL_ENTRIES_TOTAL 201 JNL_RMT_ENTRIES_TOTAL 3 JNL_LCL_RECORDS_TOTAL 398 JNL_RMT_RECORDS_TOTAL 9 JNL_LCL_RECORDS_READ 21 JNL_RMT_RECORDS_READ 0 JNL_LCL_REC_BYTES_READ 8006 JNL_RMT_REC_BYTES_READ 0 JNL_LCL_NONTX_ENTRIES 5 JNL_RMT_NONTX_ENTRIES 0 JNL_LCL_OPEN_JOURNALS 2 5 10 RTR Monitoring 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 journ
317. s JTQUOTA 5000 LINKS 512 PARTITIONS 80 Dependent on LINKS and PROCESSES values PRCLM 10 PRIORITY 6 PROCESSES 64 TQELM 2000 WSDEFAULT 2000 WSEXTENT 20000 WSQUOTA 10000 The START RTR command starts RTR on one or more nodes When RTR is started on a node a detached process called the RTR ACP is created This process performs transaction and communication activities for all users of RTR running on that node The START RTR command must be issued before adding RTR facilities or starting application programs that use RTR When running on OpenVMS the quota qualifiers affect the way the RTR ACP is created The default values wi Il suffice for many applications The values for quota qualifiers take effect independently of SYSGEN settings This means that RTR can be started with different quotas without rebooting the system The quota qualifiers are similar to those which can be specified with the DCL RUN D ED command If you use obsolete RTR Version ETACH 2 qualifers with the START RTR command a warning is issued Qualifers affected are partitions cache_pages and relations Warnings are also generated if an OpenVMS qualifer is used on a non OpenVMS platform 6 172 RTR Command Line Interface Qualifiers START RTR ASTLM ast limit ASTLM max links max processes x 2 10 default ast limit D Specifies the AST limit for the RTR ACP The value for ast 1imit must include
318. s been entered then the command is executed only on the node where the command was issued 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 FACILITY FACILITY D Specifies the facility name for which information should be displayed By default information is displayed for all Facilities FULL NOFULL D Gives a detailed listing of server partition information The following items are displayed e Key segment low and high bounds e Counts of the active and free servers bound to the partition e Counts of the active and recovered transactions for the partition RTR Command Line Interface 6 153 SHOW PARTITION Examples e The state of transaction presentation one of active suspended or suspending e 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 server data because a callout server uses server not router data structures A callout server actually runs on the router identified for its facility NODE node list NODE default node list D Specifies that the command is executed on all nodes specified in node 1ist 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
319. s desired The recovery cycle can also be manually restarted with the RESTART_RECOVERY qualifier This may be useful if the operator previously aborted automated recovery Since this command can result in recovery of transactions from previously inaccessible journals do not use this if your applications are sensitive to the order in which transactions are processed by the servers 3 6 3 1 Command Line Example Example of the qualifiers RTR gt SET PARTITION FACILITY Facilityl IGNORE_RECOVERY Facilityl Partitionl RTR gt RTR gt SET PARTITION FACILITY Facilityl RESTART_RECOVERY Facilityl Partitionl A complete description of the qualifiers to the SET PARTITION command can be found in Chapter 6 3 6 3 2 Programming Information To terminate the current recovery state program the set_qualifier argument of rtr_set_info as follows rtr_qualifier_value_t set_qualifiers 2 rtr_partition_state_t newState rtr_partition_state_exitwait qv_qualifier rtr_partition_state qv_value amp newState qv_qualifier rtr_qualifiers_end qv_value NULL set_qualifiers 0 set_qualifiers 0 set_qualifiers 1 set_qualifiers 1 To restart recovery specify newState as rtr_partition_state_recover 3 6 4 Controlling the Active Site RTR lets the system operator to deploy a range of shadow and standby partitions in order to provide the desired degree of application resilience to failures By default RTR au
320. s node Explanation A connection could fail between a router and a frontend or a backend if the link is in the closed state This could happen if the link has been suspected of causing congestion to the rest of the network This state can also be reset by system manager intervention RTR F LNQOVERFLOW LNQ table has overflowed Explanation This status is used to indicate an inadequacy in the static reservations of the per link congestion queue header blocks Send an SPR RTR E LOADLIBFAIL Unable to dynamically load the shared library Explanation The RTR ACP was unable to load the shared library dynamically RTR E LOADSYMFAIL Unable to find the symbol in the shared library Explanation The RTR ACP was unable to locate the symbol name in the lib RTR I LOGFILENT A A A Explanation Displays the time date A node name B and user name C associated with the subsequent error message RTR E LRCERROR Found a LRC error in incoming message Explanation The checksum also known as Linear Redundancy Check was wrong in an incoming message RTR W MESFLOCON Message flow congestion on link to node A for facility A Explanation RTR internode communication has become congested New messages are waiting for the congestion to clear RTR F NETSHUT Network has been shutdown or has become unusable A automatic retry will follow Explanation This status results when someone stops DECnet on a node running RTR Migh
321. s set partition shadow state on Explanation This message appears in the router log file indicating what sort of request has been received RTR PRTSUSPCAN Suspend cancelled for partition A A operator A partition resumed by operator Explanation Log file entry indicating that a pending partition suspend operation has been cancelled as a result of an operator command to resume the partition RTR S PRTSUSPEND Partition A A suspended by operator A Explanation Log entry indicating that partition has become suspended as the result of operator intervention RTR E PRTSUSPTMO Suspend timeout for partition A A operator A after A seconds partition still suspending Explanation Log entry indication that a command to suspend a partition timed out The partition will still be suspending resume the partition to restart presentation of transactions RTR W PRTWAITJ NL Partition ld waiting for access to journal for node A Explanation RTR cannot access one or more journals that may contain relevant recovery information for this key range The journal referenced could be one of many unavailable journals Either RTR should be started up on the missing backend or the facility should be trimmed and the server restarted RTR F QAROVERFLOW No more QARs left Explanation This status is used to indicate an inadequacy in the static reservations for the internal query acceptor records Make a note of all QRM counters usi
322. s the use of the set environment command to stop rtr on Node A and Node C More details concerning the commands used in the above examples are contained in Section 6 2 1 4 Introduction 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 2 1 Introduction Before RTR applications can run RTR must be started and the application s facility must be defined on each node of the application s environment This is done by issuing the start rtr and create facility commands on each participating node There are several ways to accomplish this e You can log on to each node in turn and issue the commands interactively e You can log on to one node and use the remote command capability to configure all the nodes from one session e You can include the necessary commands in a startup script or command file on each node so the commands are automatically executed when the nodes are booted The first two methods are more suited to a development or test environment the last method more suited to a production environment The remaining sections contain examples of the commands that are used to start and configure RTR Section 6 2 gives syntax details of the RTR commands 2 2 Setting Up An Example The following example assumes that RTR is started on the eight node system shown in Figure 2 1 Starting and Settin
323. s unchanged from earlier versions of RTR on OpenVMS e The default value for PROCESSES is 64 This value is large for front end and router nodes but is sized for back ends hosting applications Back ends with complex applications may have to set this higher The maximum value for PROCESSES is the OpenVMS allowed maximum Warning messages are generated if the requested or default memory quotas conflict with the system wide WSMAX parameter or if the calculated or specified page file quota is greater than the remaining free page file space e The default values for LINK and PROCESSES require a large page file RTR issues a warning if insufficient free space remains in the page file to accommodate RTR so choose values appropriate for your configuration Starting and Setting Up RTR 2 11 Starting and Setting Up RTR 2 8 RTR ACP Virtual 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 For further information on the START RTR qualifiers see the START RTR command in the Command Reference section Once the requirements have been determined for the START RTR qualifiers of PGFLQUOTA or LINK and PROCESSES then RTR should be started with these qualifiers set to ensure the appropriate virtual memory quotas are set Note The AUTHORIZE utility of OpenVM
324. sabled 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 on any of its standbys 3 6 1 1 Command Line Example RTR gt SET PARTITION FACILITY Facilityl SHADOW Facilityl Partitionl For further information see the SET PARTITION command in Chapter 6 3 6 1 2 Programming Information To enable shadowing program the set_qualifier argument of rtr_set_info as follows rtr_qualifier_value_t set_qualifiers 2 rtr_partition_state_t newState rtr_partition_state_shadow set_qualifiers set_qualifiers set_qualifiers set_qualifiers qv_qualifier rtr_partition_state qv_value amp newState qv_qualifier rtr_qualifiers_end 0 0 I 1 qv_value NULL To disable shadowing specify newState as rtr_partition_state_noshadow Partition Management 3 5 Partition Management 3 6 Managing Partitions 3 6 2 Controlling Transaction Presentation Transaction presentation is the process of passing transactions to idle server channels for processing Whil e transaction presentation is active new transactions are started on the first free server channel for the appropriate partition Use the SUSPI END qualifier to the sS ET PARTITION command to halt the presentation of new transactions to servers on the backend where the command is entered The command comp
325. saction information The Invocation field of SHOW TRANSACTION BACKEND FULL shows the following information Table 6 24 Transaction Invocation Types Type Meaning ORIGINAL Original transaction REPLAY Replayed transaction RECOVERY Shadow recovery transaction 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 command is executed only on the node where the command was issued 6 168 RTR Command Line Interface 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 If none of BACKEND FRONTEND or ROUTER are specified then information for all of them are displayed If either BACKEND or ROUTER are specified then the default NOFRONTEND inhibits display of frontend transaction information IDENTIFICATION process id NOIDENTIFICATION D Specifies the PID of the process for which information is displayed The default NOIDENTIFICATION displays information for all processes FACILITY FACILITY D Specifies the
326. same nodes Example RTR gt DO NODE TR2 TR1 ps This command displays the processes running on Compaq Tru64 UNIX nodes TR2 and TRI RTR Command Line Interface 6 87 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 Network links could become unstable if a Distributed Name Service DNS was configured improperly or the service was slow in responding During extreme DNS latency RTR could time out the connections to nodes waiting for a DNS response To avoid these problems RTR has implemented an internal node name to id cache this reduces RTR s exposure to degraded name servers The contents of the cache can be deleted the command FLUSH NAME_CACHE FLUSH NAME_CACHE may be used if the network has been reconfigured or nodes have changed their addresses Qualifiers 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 command is executed only on the node where the command was issued
327. spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 23 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 rtr_accept_tx call or rtr_reject_tx which follows a call to rtr_prepare_tx iS ignored The default for value for REASON is 0 Related commands e CAL zel R_OPEN_CHANNE E e CAL ve R_REJECT_TX Examples Prepare the current transaction with a reason of 42 RTR gt CALL RTR_PREPARE_TX REASON 42 SRTR S OK normal successful completion 6 24 RTR Command Line Interface CALL RTR_RECEIVE_MESSAGE CALL RTR_RECEIVE_ MESSAGE Format Description 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 Command Qualifiers Defaults CHANNEL_NAMEschannel name CHANNEL_NAME RTR DEFAULT_CHANNEL CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout TIMEOUT_MS timoutms TIMEOUT_MS infinite The CALL RTR_RECEIVE_MESSAGE command causes a command server to call the rtr_receive_message routine using
328. ssuing rtr_accept_tx awaiting transaction result Explanation Indicates that a client died after accepting but before completion of a transaction RTR W ROLESMISMATCH Node role definitions do not match for this facility Explanation The facility exists but the definition of the role for the remote node is not the same as the one in the local node The system manager has probably incorrectly defined the facilities on the two nodes concerned RTR E ROUTERUNAVAILTMO FE discarded transaction due to router unavailability timeout Explanation n rare circumstances a transaction can be aborted by an RTR frontend with the status RTR_STS_ROUTERUNAVAILTMO This can occur if an RTR client application has accepted the transaction but the link to the router is lost before the RTR frontend has received a response from the router If no RTR router becomes available for more than 8 minutes then the transaction will be aborted by the frontend This is to prevent the transaction being duplicated by RTR since the router will unanimously decide the outcome of accepted transactions that have lost their frontends after about 10 minutes The correct procedure in this case is for the client application to check whether the transaction has been completed once the link to a router is re established RTR I RQEQUALS Transaction client was A on node A Explanation Displays the process name of the client A and its node address B in messages relatin
329. st RTR Command Line Interface 6 97 MODIFY JOURNAL MODIFY JOURNAL Format Description Parameters Qualifiers Specifies the desired and maximum allowed sizes of RTR s recovery journal 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 default node list OUTPUT file spec OUTPUT stdout The MODIFY J OURNAL command specifies how the size of RTR recovery journal files on the specified disks can be modified The target or desired size is specified using the BLOCKS qualifier The maximum_allowed size is specified using the MAXIMUM_BLOCKS qualifier BLOCKS and MAXIMUM_BLOCKS are a positional qualifiers so journal files need not be the same size on each disk RTR only uses journal files on nodes that are configured to run servers that is on backends and on routers with call out servers Note that the MODIFY JOURNAL command does not cause immediate journal file extension Actual file size modifications take place on demand by the RTRACP within the limits defined by the MODIFY J OURNAL command The MODIFY J OURNAL command assumes that a journal already exists for the node If a journal does not exist an error message is output In contrast to the CREATE J OURNAL command the MODIFY J OURNAL command is normally entered interactively not automatically from a startup command proc
330. st NOEVENTS D The EVENTS qualifier specifies that broadcast events are received on the channel To subscribe to all user and RTR events enter the qualifier with no arguments Enter EVENTS RTR to receive the full range of RTR events only Enter EVENTS USER to receive the full range of USER events only Specify particular ranges of event numbers using arguments in the following format EVENTSSRTR n TO m USER p TO q where n m p and q are event numbers The default is to listen to no events RTR Command Line Interface 6 17 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 application must specify the facility name when using the RTR CLI The default facility name is RTR DEFAULT FACILITY FOREIGN_TM tm_id NOFOREIGN_TM D Valid for client channels only This indicates that the global coordinating Transaction Manager TM is a Foreign TM denoted as FTM and that all TXs on this channel will be coordinated by the FTM If this qualifier is set then calls to rtr_start_tx on this channel must supply a value for the jointxid parameter which is the TXID of the TX A TM identifier can also be passed in as parameter It must be in the range of O to 65535 Default value is 0 It is recommended that operators or script programs using nested transactions specify a TM identifier particularly if more than one proc
331. subsequent MONITOR command Note that the introduction of the SEPARATE TOTALIZE and AVERAGE qualifiers has superseded the qualifiers FACILITY LINK PARTITION NODE and PROCESS These superseded qualifiers are no longer described here however they are still supported Parameters expression Specifies the quantity to be displayed Expression can either be the name of a single data item or an expression combining several items using simple arithmetic operations and constants In the latter case EXPRESSION must be in quotes 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 6 72 RTR Command Line Interface DISPLAY NUMERIC 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_TRANSACTION Router transaction data items BELL Boolean expression NOBELL D Sends a bell character to the terminal if Boolean expression evaluates to True non zero BLANK Boolean expression NOBLANK D Specifies that the displayed value is replaced by blanks if Boolean expression evaluates to True non zero BLINK Boole
332. sure that the change takes effect on all nodes in the RTR facility or facilities However in an off line situation where an RTR facility has not been created RTR will simply update the transaction state in place in the RTR journal The RTR log file must be turned on before using the SET TRANSACTION command to record the state changes See the SET LOG command There are eight legitimate situations where you can change a transaction s state See Table 6 19 transaction id Specifies a particular transaction or transactions whose transaction state you want to change The transaction_id format is the same as that displayed by DUMP JOURNAL and SHOW TRANSACTION commands If no transaction_id is specified then all transactions that satisfy the specifying qualifiers are processed by the command BEFORE daie Selects only those transactions whose timestamp is before the specified date Default is the current date STATE current_state Selects a particular transaction or a set of transactions that are in the specified state transaction state This qualifier is required and the state value must be specified Value of state may be one of the following SENDING VOTED COMMIT EXCEPTION PRI_DONE Use the DUMP JOURNAL or SHOW TRANSACTION command to help you find what is the current state of a particular transaction FACILITY FACILITY RTR DEFAULT_FACILITY D Specifies the name of a facility for selecting transactions The d
333. t stop rtr node FE3 1 RTR gt delete facility funds_transfer node TR2 2 RTR gt create facility funds_transfer node TR2 3 _RTR gt frontend FE1 FE2 _RTR gt router TR2 RTR gt delete facility funds_transfer node TR1 4 RTR gt create facility funds_transfer node TR1 5 _RTR gt frontend FE1 FE2 _RTR gt router TR1 1 RTR is stopped on node FE3 the node being excluded from the network In order to prevent transactions being interrupted or aborted application processes should be stopped in an orderly manner before issuing the stop rtr command Alternatively a stop rtr abort command will force application processes using RTR to exit aborting or interrupting any outstanding transactions 2 The facility is deleted on node TR2 Any frontends that were connected to TR2 will connect to the remaining router node TR1 3 The facility is created on node TR2 excluding node FE 3 from the frontend list This facility has started when the start message appears in the RTR log 4 The facility is deleted from node TR1 Frontends FE1 and FE2 now connect to router TR2 5 The new facility is created on node TR1 again excluding node FE 3 from the frontend list The frontends now distribute their connections to the router nodes TR1 and TR2 according to the load sharing algorithm The system is again fully operational In the example in Figure 2 1 assume that a new router node TR3 and new frontend FE4 are being added to the
334. t act as routers for this facility Router list is a list of router nodes separated by commas If there is more than one router node then router list must be enclosed in parentheses If NOBALANCE is specified with the CREATE FACILITY command then the order in which router nodes are specified with the ROUTER qualifier defines the preferred routing order Router node is either the name of a node or file spec where file spec specifies a text file containing a router list on each line Related commands DELETE FACILITY e EXTEND FACILITY e SHOW FACILITY e TRIM FACILITY RTR Command Line Interface 6 49 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 Format Description Parameters Create RTR s recovery journal 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 stdout SUPERSEDE NOSUPERSEDE The CREATE J OURNAL command creates RTR s recovery journal files on the specified disks The target size of the files is specified using the BLOCKS qualifier 512 byte blocks The RTR journaling system will attempt to keep the journal file to this
335. t also occur if the network fails or otherwise becomes unusable RTR log messages E 7 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 The search will continue after a short interval RTR W NODENOTCNFG Node is not configured for the facility Explanation Result of a connection attempt to a remote node where the connecting link is not configured in the requested facility at the remote node RTR W NODISOLAT Isolating A node suspected of causing congestion Explanation The remote node A has been diagnosed as causing network congestion RTR will isolate the node from the rest of the network RTR W NOFECREDIT Nocredit for FE connect acceptance Explanation The router has no credit left to accept any more frontends right now Other routers can be tried RTR E NOTCONFIGURED RTR not configured on A to recognize this node Explanation This means that none of the facilities defined on the local node A defined a valid role for the remote node to permit a connection RTR E NOTRECOGNISED Node not recognized Explanation Result of a connection attempt to a remote node where no facility references the connecting link at the remote node RTR E OBJ NOTDECL RTR network object could not be established will try again later Explanation A log file entry indicating that RTR was unable to establish its n
336. t clustering use of the CLUSTER qualifier will cause the relevant command to be executed on the local node only 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RTR Command Line Interface 6 61 DELETE FACILITY Related Commands e CREATE FACILITY e SHOW FACILIT K 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 Format Description Qualifiers Delete an RTR journal DELETE JOURNAL Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The DELETE JOURNAL command deletes a previously created RTR journal on the node where the command is issued The DELETE JOURNAL command will fail if a journal does not exist or if a journal has been created but is currently in use The command causes the previous contents of the journal if any to be destroyed CLUSTER NOCLUSTER D Specifies that th
337. t fac_output lis The first command works for OpenVMS systems but not on UNIX The second command uses single quotation marks outside of double quotations to be correctly interpreted on UNIX systems 1 3 Online Help You can get information about the RTR CLI by using the HELP command Entering the following command rtr help displays a complete list of help topics on your terminal If you require additional information then enter the topic directly on the same line for example Q rtr help show The help command can also be used to find out about errors returned by RTR The folowing sequence returns the error identifier Q rtr help errors error identification 1 2 Introduction 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 AS TEL RTR gt start rtr SRTR F RTRALRSTA rtr already started RTR gt help errors rtralrsta Errors RTRALRSTA RTR already started Explanation RTR was already running when the START RTR command was executed This error message is displayed by the RTR utility RTR gt 1 4 Command Procedures RTR commands can also be written in a command file and then executed as a procedure using the EXECUTE file spec or file spec commands For example rtr execute createfacil or rt
338. t handler was already running when the START REMOTE_CLIENT_ HANDLER command was executed RTR E RCHNOTSTA RTR remote client handler not started Explanation The remote client handler had not been started when a command was issued which requires it to be running RTR E RCHWASSTO RTR remote client handler has been stopped Explanation The remote client handler had been stopped when a command was issued which requires it to be running RTR S REASONSTS Reason status A Explanation Displays the contents A of the RSNSTS field of the TXSB after calling a RTR V2 system service via the DCL interface RTR E RMSTRINGLONG Resource manager open or close string too long Explanation Resource manager open or close string too long D 22 RTR Utility Error Messages RTR Utility Error Messages RTR E RTRALRSTA RTR already started Explanation RTR was already running when the START RTR command was executed RTR S RTRLOGENT A Explanation The RTR LOG command was used to make an entry in the RTR LOG RTR I RTRNOTRUN RTR not running Explanation Message created specifically for the STOP RTR command if RTR is not currently running so that the IVP does not report a fatal message RTR E RTRNOTSTA RTR not running Explanation RTR had not been started when a command was issued which requires RTR to be running RTR S RTRRCHSTART RTR remote client handler started Explanation Indicates that remote client handler h
339. taining the string SYSTEM or conflicts may occur RTR gt set mode group develpr NOGROUP sets RTR into NOGROUP mode 6 118 RTR Command Line Interface 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 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 Examples e SHOW MODE RTR gt SET MODE GROUP This command tells RTR to enter GROUP mode RTR gt SET MODE NOGROUP This command tells RTR to enter NOGROUP mode RTR Command Line Interface 6 119 SET NODE SET NODE Format Description Qualifiers Sets various node related options SET node Command Qualifiers Defaults AUTOISOLATE NOAUTOISOLATE CLUSTER NOCLUSTER INACTIVITY_TIMEOUT secs JINACTIVITY_TIMEOUT 60 ISOLATE NOISOLATE NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SET NODE command sets the automatic isolation characteristics and the link timeout default of a node AUTOISOLATE NOAUTOISOLATE D Any RTR node may disconnect a remote node if it finds the remote node is unresponsive or congested The normal behavior following such action is
340. tended Explanation Displays the name A of the facility that was successfully extended or created after issuing an EXTEND FACILITY command RTR E FACNAMBLA Facility name is blank Explanation An empty string was specified where a facility name was expected RTR E FACNAMILL Facility name A contains illegal character A Explanation Facility name A contains the illegal character B Legal characters are capital letters A to Z numbers 0 to 9 dollar and underscore _ RTR Utility Error Messages D 7 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 MZ RTR E FACTABFUL The FAC table is full Explanation This message is displayed when an CREATE FACILITY command is issued It indicates that the maximum number of FACILITY to LINK relations has been reached RTR S FACTRIMMED Facility A trimmed Explanation Displays the name A of the facility that was successfully trimmed after issuing a TRIM FACILITY command RTR E FDBTABFUL TheFDB table is full Explanation This message is displayed when an CREATE FACILITY command is issued It indicates that the maximum number of facilities has already been reached RTR E FENAMELONG Frontend name string length greater than
341. ters containing information such as the number of XA calls call status success or failure and the number of read only transactions Provides counts for the open close start end prepare commit rollback and recovery commands Command Syntax MONITOR XA C 1 2 New Qualifier to CREATE FACILITY Command The CREATE FACILITY command has a new qualifier that references the defined resource manager All resource managers that will be accessed by a facility must be specified All transactions to these resource managers are recovered when the facility is created Command Syntax CREATE FACILITY facility_name frontend backend router resource_manager RM_1 RM_2 where XA Support C 1 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 1 3 Modified RTR API An application written to use RTR with XA does not need all existing RTR application programming interface statements In particular there is no longer a need to include code to handle rtr_mt_msgl_uncertain messages C 1 4 RTR Open Channel RTR relies on the server application to specify which RM it is attached to using the open channel API The server must submit an RM instance name with open string to the RTR open channel API before accessing the desired database
342. th mon You type the filename without mon when starting the display RTR Monitoring 5 1 RTR Monitoring 5 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 recent entry is highlighted acp2app Displays counts of messages and number of bytes from RTRACP to the application as viewed from a specific node active Displays a list of RTR processes and for each process the number of transactions they have started the number of transactions they have completed and the number of transactions that are still active app2acp Displays counts of messages and number of bytes from the application to RTRACP as viewed from a specific node broadcast Displays information about RTR user events by process including number of user events enqueued received and discarded calls Displays the total number of RTR API calls and their success or failure for the processes on all the nodes being monitored All RTR message are also show by message type Pending messages are ones that an application has not received yet Use the IDENTIFICATION process id qualifier to display the values for one specific process otherwise the total values for all processes are displayed channel Displays the roles of
343. the channels declared by an application This can be useful as a debugging tool in the early stages of application development congest Displays a sorted list of nodes responsible for causing the most congestion since RTR was last started and the instantaneous state connects Displays connection status summary including the number of links up and down and a list of links with state up or down architecture network transport and fail reason if any ddtm Displays counts of RTR calls to DECdtm as viewed from a specific node for all PIDs processes and images dtx Displays counts of RTR DTX calls including open start prepare rollback commit and close as viewed from a specific node for all PIDs processes and images dtxrec Displays a summary of DECdtm transaction recovery DTX as viewed from a specific node for all PIDs processes and images event Displays event routing data by facility Information includes events in transit and destination information showing number of events enqueued processed and discarded facility Displays a number of per facility data items The FACILITY qualifier can be used to say which facility should be monitored If this is not specified then the totals of the data items for all facilities are displayed flow Displays the flow control counters frontend Displays frontend status and counts by node and facility including frontend state current router reject status retry count and quorum
344. the relevant command to be executed on the local node only 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 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 e SET LOG 6 146 RTR Command Line Interface SHOW LOG Example RTR gt 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 Line Interface 6 147 SHOW MODE SHOW MODE Format Description Qualifiers Displays the current RTR mode SHOW MODE Command Qualifiers Defaults CLUSTER NOCLUSTER NODE node list NODE default node list OUTPUT file spec OUTPUT stdout The SHOW MODE command shows the currently running user group for RTR For nogroup system mode a null group name is displayed SET MODE command for further information about modes CLUSTER NOCLUSTER D Specifies that the command is executed on all the nodes in the cluster If neither NODE nor CLUSTER is spec
345. 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 NOROUTER D Displays information about router partitions it shows the partition state and partition low and high bounds It can be used to quickly determine the current primary node for a given partition Using ROUTER with FULL provides more detailed information such as the main shadow and standby servers for the partitions as seen from the router Partition bounds are shown as ASCII characters if there is a translation otherwise as hexadecimal digits Only the least significant four bytes are shown The following example shows a router partition RTR gt SHOW PARTITION ROUTER Facility Low Bound High Bound Primary Main RTRSDEFAULT_FACILITY 0 4294967295 depth RTR gt SHOW PARTITION ROUTER FULL Facility RTRSDEFAULT_FACILITY State ACTIVE Low Bound 0 High Bound 4294967295 Failover policy fail_to_standby Backends depth States active Primary Main depth Shadow Main The following examples show two backend partitions RTR gt SHOW PARTITION BACKEND Partition name Facility State RTRSDEFAULT_PARTITION_16777217 RTRSDEFAULT_FACILITY active RTRSDEFAULT_PARTITION_16777218 RTRSDEFAULT_FACILITY active RTR gt SHOW PARTITION BACKEND FULL 6 154 RTR Command Line Interface Partition name Facility RTRSDEFAULT_FACILITY Low Bound aaaa Active Servers 0 Transaction pres
346. tion allows a node the isolator to disconnect a congested or unresponsive remote node the isolatee in such a way that when the congested node attempts to reconnect it receives an instruction to close all its network links and cease connection attempts A node in this state is termed isolated Some applications require that a node which is suspected of causing congestion that is not processing network data sufficiently quickly is isolated from the rest of the network so as to cause minimum disruption The node autoisolation feature meets this requirement 6 112 RTR Command Line Interface SET LINK Remote node autoisolation may be enabled at the isolator where it applies to all links using SET NODE AUTOISOLATE or for specific links only with the SET LINK AUTOISOLATE command An isolated node isolatee remains isolated until you carry out both of the following actions e Enable the link to the isolated node on all nodes that have isolated it that is set link isolated node enabl e Exit the isolated state on the isolated node that is set node noisolate Autoisolation is disabled at the isolator using the NOAUTOISOLATE qualifier CHECKSUM NOCHECKSUM D CHECKSUM specifies that checksum calculations for data packets over network links are performed This qualifier is by default set to NOCHECKSUM This command is useful for diagnosing errors over network links To see the checksum state use the SHOW LINK STATE command
347. tions are stored in the RTR journal it must be created with enough disk space in reserve to store data for the longest expected outage It can be calculated using Nr transaction messages per second multiplied by transaction message length 70 multiplied by seconds of outage 5 file overhead The overhead required when calculating journal size comes from internal journal data block stamping of approximately 3 In addition there is internal transaction data per client to server transactional message and some further data per transaction concerning voting and transaction completion Also note that RTR prevents further transactional data being written to the journal when it is nearly full but continues to allow deletes from the journal deletes also cause data to be written to the journal Ten segments are held in reserve for storing information about deleted transactions even when RTR cannot accept further transactions because the journal is full Warning If the journal disk becomes full transactions are aborted until the shadow partner re starts and empties the journal of transactions to be replayed Server Shadowing and Recovery B 3 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 Number o
348. tistics of transaction and broadcast traffic by facility Displays the most recent calls history for the RSC subsystem on a backend node Displays various per node data items Displays in real time any network links that are currently stalling in their outbound traffic and provides a history of the stalls that the various links encountered during their lifetime Displays the state of critical resources within the RTR environment If a resource has exceeded a predefined threshold a warning indicator is displayed Displays the rate of transaction commits carried out by each process using RTR Displays low end of the rate of transaction commits carried out by each process using RTR continued on next page RTR Monitoring 5 3 RTR Monitoring 5 2 Standard Monitor Pictures Table 5 1 Cont Standard Monitor Pictures Picture name Description traffic trans v2calls xa 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 Average packets per second is also shown Displays transactions for a frontend router and backend Shows RTR Version 2 verb usage through the interoperability subsystem The screen layout is identical to the RTR Version 2 monitor calls picture Displays XA counter information including success and failure as well as call and readonly counters The following sections describe the more commonly used stand
349. tition resides may be specified with the FACILITY command line qualifier or as a colon separated prefix to the partition name for example F acility1 Partition1 Detailed descriptions of the command syntax are given in the Command Line Reference section of this manual and are summarized in the discussions below Examples in the following sections use a partition name of Partition1 in the facility name of Facilityl 3 5 2 Programmed Partition Management Partition commands are programmed using rtr_set_info Usage of the arguments are as follows e pchannel Supplies the address of a rtr_channel_t to receive the channel opened in the event of a successful call e Flags must be RTR_NO_FLAGS e Verb must be the value verb_set from the enumeration rtr_verb_t e Object must be rtr_partition_object e select_qualifiers should identify the facility and partition by name for example rtr_qualifier_value_t select_qualifiers 3 select_qualifiers qv_qualifier rtr_facility_name select_qualifiers qv_value your_facility_name_here select_qualifiers qv_value your_partition_name_here qv_qualifier rtr_qualifiers_end 0 0 1 1 2 2 qv_value NULL select_qualifiers qv_qualifier rtr_partition_name select_qualifiers select_qualifiers e The set_qualifier list expresses the required change in partition behaviour or characteristic 3 4 Partition Management Partition Managem
350. to know about BE1 Superfluous node names are ignored This allows you to issue the same CREATE FACILITY command on every node to simplify the maintenance of startup command procedures 2 2 Starting and Setting Up RTR 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 Example 2 2 Remote Setup from one Node rtr RTR gt set environment node _RTR gt FEl FE2 FE3 TR1 TR2 BEl BR2 BR3 RTR gt start rtr RTR gt create facility funds_transfer frontend FE1 FE2 FE3 _RTR gt router TR1 TR2 _RTR gt backend BE1 BE2 BE3 You can enter the commands shown in Example 2 2 on any of the nodes in the configuration However you must have an account with the necessary privileges on the other nodes To find out if RTR has been started on a particular node use the SHOW RTR command To find out which facilities have been created if any and how they are configured you can use the SHOW FACILITY and SHOW LINK commands The full syntax of these commands is given in Chapter 6 2 3 Creating a Recovery Journal RTR writes data to journal files to be able to recover that is replay partially executed transactions after a backend node failure For performance reasons the journal may be spread across several disks Specify the l
351. to server messages and declared state for routers 5 2 30 Monitor RTR RTR gt Monitor RTR RTR COUNTERS 7 JAN 1999 14 35 05 NODE ALL ACP_WAKEUPS 310484 QRM_QCXTS ACP_WAKE_REQS 859200 QRM_QIRS CM_BYTES_PRESENT 1048576 QRM_RAES CM_BYTES_IN_USE 51968 QRM MAXQUOTA CM_FREECHCPCKT 3738 QRM_CURQUOTA TIM_TIMER_SETS 238349 QRM_RDES TIM_TIMER_CANCELS 34165 ORM_QARS TIM_TIMER_DELIVERS 204174 QRM_QUERIES_SENT TM_ORM_QUERIES_SENT 0 QRM_QUERIES_RCVD TM_ORM_QUERIES_RCVD 0 QORM_RESPONS_SENT NCF_REJECTEE 1 QRM_RESPONS_RCVD NCF_REJECTER 1 QRM_RETRIES NCF_FACILITY_UP 2 QRM_TIMEOUTS NCF_FACILITY_DOWN 0 RSC_ALLOC_MEM 2098 Displays various per node counters 48 0 0 278718 278718 18 0 481308 481308 3082 3092 7 0 RTR Monitoring 5 17 RTR Monitoring 5 2 Standard Monitor Pictures gt 30s Tot 0 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 lt 3s lt 10s lt 30s Total 5467 0 0 327148 2 33 23 1 0 TR1 gt TR1 29 0 0 3718 0 0 0 0 0 TR1 gt FE2 509 0 0 20707 0 4 4 0 0 TR1 gt BE1 303 0 0 13707 0 3 3 0 0 TR2 gt TR2 111 0 0 11682 0 0 0 0 0 TR2 gt BE1 504 0 0 22743 0 18 8 1 0 FEl gt FEl 64 0 0 6645 0 0 0 0 0 FEl gt FE2 373 0 0 18890 0 2 2 0 0 FE1 gt BE1 310 0 0 24487 0 0 0 0 0 FE2 gt FE2 231 0 0 18900 0 0 0 0 0 FE2 gt BEL 284 0 0 22503 1 1 1 0 0 FE2 gt TRI 536 0 0 28166 0 0 0 0 0 FE2 gt FEL 396 0 0
352. tomatically manages the assignment of active and standby roles to the available partition instances The operator can assign a relative priority to each backend on which a partition instance exists Enter priority as a list of backend node names with the highest priority first in decreasing order See the command example Section 3 6 4 1 Suspend transaction presentation before entering or changing the priority list 3 6 4 1 Command Line Example RTR gt SET PARTITION PRIORITY_LIST BE1 BE2 BE3 Facilityl Partitionl For more information on the SET PARTITION command see Chapter 6 Partition Management 3 7 Partition Management 3 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_qualifiers 0 set_qualifiers 0 set_qualifiers 1 set_qualifiers 1 qv_qualifier rtr_partition_be_priority_list qv_value amp szNodeList qv_qualifier rtr_qualifiers_end qv_value NULL 3 6 5 Controlling Failover In a system configured for maximum fault tolerance employing both shadows and standbys there is a choice to be made in case of the failure of the primary site The qualifier to the SET PARTITION command of FAILOVER_POLICY allows the system operator to select one of the following policies that RTR should pu
353. ty no balance Toggles the attribute setting on the executor node show facility configuration Shows the current setting of the load balance attribute show facility link Ona frontend shows the current router node On a router shows the frontends connected and the current load coordinating backend node show facility balance On a router node shows the current number of frontends connected and the current credit On the coordinating backend node shows the total number of routers frontends and credit given out Useful for troubleshooting frontend connection problems 2 7 RTR Privileges RTR supports two levels of rights or privileges rtroper and rtrinfo on UNIX platforms RTRSOPERATOR and RTR INFO on OpenVMS and RtrOperator and Rtrl nfo on Windows NT In general rtroper or RTR OPERATOR is required to issue any command that affect the running of the system and rtrinfo or RTR INFO is required for using monitor and display commands Setting RTR Privileges on UNIX Systems On UNIX machines RTR privileges are determined by the user id and group membership For RTR users and operators create the group rtroper and add RTR operators and users as appropriate The root user has all privileges need to run RTR Users in the group rtroper also have all privileges with respect to RTR but may not have sufficient privilege to access resources used by RTR such as shared memory or access to RTR files
354. untered whilst looking up a node address details follow in a subsequent message text D 14 RTR Utility Error Messages 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 nodes specified with this and all previous CREATE FACILITY commands would exceed the limit specified with the LINKS qualifier when RTR was started RTR E NFW Operation requires SETPRV privilege Explanation SETPRV privilege is required to execute a remote command RTR E NOACTION No object management action specified check argument set_qualifiers Explanation Status return indicating that no action was supplied along with an object management request Check your program RTR I NOAPPSRV No application server channels currently declared Explanation Indicates that no application server channels are currently declared and hence the requested information cannot be output RTR E NOBACKEND No backends specified Explanation No backends were specified on a CREATE FACILITY command and the node where the command was executed was specified as being a router RTR S NOCHANGES No changes made Explanation The modifications specified resulted in no changes being required RTR F NOCHANOPEN No channel is currently open Explanation RTR E NOCLASS If selitm specified please specify a data class Expl
355. use 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 frontend node then frontend list must be enclosed in parentheses Frontend node is either the name of a node or file spec where file spec specifies a text file containing a frontend list on each line 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 information is written to the file file spec If OUTPUT or file spec is omitted then the standard or default output is used RESOURCE_MANAGER resource list Specifies a list of defined resource managers that this facility may reference Server applications using this facility and resource manager will receive any recovered transactions when the facility is created See Appendix C for further information REPLY_CHECKSUM NOREPLY_CHECKSUM D Specifies that the reply consistency check or Response Matching feature for replayed messages is enabled It is a check for reply consistency during a replay of a reply to client message RTR can enable disable and display this feature ROUTER router list NOROUTER D Specifies the names of the nodes tha
356. ut condition if the partition remains suspended TIMEOUT See description for SUSPEND Related Commands e CREATE PARTITION e SHOW PARTITION 6 124 RTR Command Line Interface SET TRANSACTION SET TRANSACTION Format Description Sets various transaction related options 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 spec OUTPUT stdout PARTITION partition_name SINCE date today USER username all users Note The SET TRANSACTION command could damage your journal and database integrity if used incorrectly Ensure that you fully understand the reason and impact for changing a transaction state before altering your RTR system The SET TRANSACTION command allows you to modify the state of a transaction or set of transactions stored in the RTR journal This command is complementary to the DUMP JOURNAL and SHOW TRANSACTION commands in that it gives capability of reading and modifying the status of a transaction status in the RTR journal For example if a shadow recovery is known to be unnecessary you may want to clean up the RTR journal to prevent the committed transactions in the journal from being replayed Using the SET TRANSACTION command the RTR administrator is able to delete that set of transactions from
357. v_value Is 0 Ly LT 2 2 rgument of the rtr_set_info call as follows set_qualifiers 3 newState 30 rtr_partition_state_suspend fier rtr_partition_state amp newState rtr_partition_cmd_timeout_secs amp ulTimeoutSecs fier rtr_qualifiers_end NULL fier Note that the timeout is an optional element To resume transaction presentation specify newState aS rtr_parti 3 6 3 Controlling Recovery ition_state_resume The purpose of RTR automated recovery is to ensure the best possible consistency of application databases acros s a distributed computing environment To achieve this RTR relies in part on information stored in the journals of the participating systems Should one or more automated recovery may stall their journals This is good fr when viewed from an applicat 3 6 Partition Management of these systems be unavailable at recovery time or fail awaiting availability of these systems and om the point of view of data consistency but bad ion availability perspective 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 Since this command bypasses parts of the recovery cycle use it with caution in cases where availability above consistency in application databases i
358. valid value was specified for the partition failover policy RTR I PRTCREATE Partition created Explanation Message returned via rtr_open_channel upon successful partition creation RTR E PRTDEFNCONFLICT Name and key information refer to different partitions Explanation A call to rtr_open_channel specified both the partition name and key information but these refer to different partitions 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 E PRTMODRMBR Partition must be in remember mode on the active member Explanation Restriction partition must bein remember mode on the active member before shadowing can be turned off Also returned if an attempt is made to restart recovery whilst not in remember mode RTR E PRTMODSUSP Partition not suspended please suspend and retry the operation Explanation Completion status indicating a partition command was rejected as the partition was not in the prerequisite state Suspend the partition first RTR E PRTNACTIVE Partition cannot be deleted so long as it has active servers or transactions Explanation Partition cannot be deleted so long as it has active servers or transactions RTR E PRTNAMINUSE Partition name already in use use another name Explanation A call to rtr_open_channel specified a partition name that is already
359. values supplied on the command line The numeric status returned from the call is then converted to its textual representation and displayed The rtr_receive_message routine itself is described in Application Programmer s Reference Manual The prototype of rtr_receive_message is tr_msgsb_t pmsgsb T rtr_status_t rtr_receive_message rtr_channel_t pchannel rtr_rcv_flag_t flags rtr channel_t prcvchan rtr_msgbuf_t pmsg rtr_msglen_t maxlen rtr_timout_t timoutms r Table 6 9 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call Table 6 9 Parameters for rtr_receive_message C Parameter Name C Parameter Value Command Line Specification pchannel displayed flags RTR_NO_FLAGS none D prevchan CHANNEL channel_name pmsg message displayed if any maxlen RTR_MAX_MSGLEN reasonable limit for display timoutms TIMEOUT_MS timoutms pmsgsb relevant fields displayed RTR Command Line Interface 6 25 CALL RTR_RECEIVE_MESSAGE Qualifiers 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 For message types that place a status code and reason code in the user buf
360. vice A contains a node specification Explanation RTR cannot create its journal files on remote systems Re issue the CREATE J OURNAL command for local disk RTR E INSUFPRIV Insufficient privileges to run RTR Explanation More privileges required to run the RTR utility RTR F INSVIRMEM Insufficient virtual memory Explanation The application was unable to allocate additional virtual memory RTR F INVCHANAM Invalid chanam argument Explanation Invalid chanam argument RTR F INVCHANNEL Invalid channel argument Explanation Invalid channel specified RTR F INVDEVNAM Invalid device name length Explanation Invalid device name length RTR F INVDSDEF Msglen not consistent with len derived from msgfmt Explanation Invalid DSDEF format argument RTR F INVEVTNUM Invalid evtnum argument Explanation Invalid evtnum argument RTR F INVEVTRAN Invalid evtnum range Explanation Invalid evtnum range RTR E INVFILNAM Invalid file name A Explanation The specified filename A is invalid RTR F INVFLACLI Invalid flag for dient channel Explanation Invalid flag for dient channel RTR F INVFLASRV Invalid flag for server channel Explanation Invalid flag for server channel RTR F INVFLAGS Invalid flags argument Explanation Invalid flags argument RTR F INVJ OINTXID Invalid join transaction argument Explanation If the RTR_F_OPE_FOREIGN_TM flag was specified in the call to rtr_open_channel then the call t
361. wing are trademarks of Compaq Computer Corporation AlphaGeneration AlphaServer AlphaStation Compaq Internet Personal Tunnel DEC DECconnect DECdtm DECnet DIGITAL OpenVMS PATHWORKS POLYCENTER Reliable Transaction Router TruCluster Tru64 UNIX VAX and VM Scluster The following are third party trademarks AIX and IBM are registered trademarks of International Business Machines Corporation Encina is a registered trademark of Transarc Corporation Hewlett Packard and HP UX are registered trademarks of Hewlett Packard Company Intel is a trademark of Intel Corporation Microsoft Microsoft Access Microsoft SQL Server Internet Explorer MS DOS Visual Basic Visual C Windows Windows 95 Windows 98 and Windows NT are trademarks or registered trademarks of Microsoft Corporation Netscape Netscape Communicator and Netscape Navigator are registered trademarks of Netscape Communications Corporation Oracle ORACLE7 PL SQL SQL Net AND SQL Plus are trademarks or registered trademarks of Oracle Corporation Solaris SPARCstation SUN SunOS and Sunlink are trademarks or registered trademarks of Sun Microsystems Inc UNIX is a registered trademark in the United States and other countries licensed exclusively through X Open Company Ltd This document was prepared using VAX DOCUMENT Version 2 1 Contents Prelate lt hae ek cee we a Thats ae ts nee ea data xi 1 Introduction 1 1 Getting Started 2s sien coh ve Se
362. xt free row D Specifies the screen row where the item is displayed top row is 1 By default items are displayed on the next free row after the item defined by the previous DISPLAY command Related Commands Examples e MONITOR e SHOW DISPLAY e CLEAR e DISPLAY NUMERIC e DISPLAY SYMBOLIC e DISPLAY TEXT See Section A 1 for examples of how to use the DISPLAY BAR command RTR Command Line Interface 6 71 DISPLAY NUMERIC DISPLAY NUMERIC Display a number in a monitor picture Format DISPLAY NUMERIC expression Command Qualifiers AVERAGE keyword BELL Boolean expression BLANK Boolean expression BLINK Boolean expression BOLD Boolean expression DAMPING damping factor DECIMALS decimal places LABEL text RATE interval REVERSE Boolean expression ROWS nr rows SELECT Boolean expression SEPARATE keyword TOTALIZE keyword UNDERLINE Boolean expression VALUE value type WIDTH field width X column Y row Description Defaults none NOBELL NOBLANK NOBLINK NOBOLD NODAMPING DECIMALS 0 NOLABEL NORATE NOREVERSE ROWS 1 NOSELECT none none NOUNDERLINE VALUE CURRENT WIDTH 1 Column of previous item Next free row The DISPLAY NUMERIC command displays the specified expression as a number in a monitor picture It can be used within a monitor file or issued at the RTR prompt when interactively defining a monitor picture for use in a
363. y a key name with the ALL qualifier If no state is specified all key definitions in the current state are displayed FULL NOFULL D Requests that all qualifiers associated with a definition are displayed By default only the state of the definition and the definition itself are displayed 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 IF_STATE state name NOIF_STATE D Specifies the name of a state for which the specified key definitions are displayed State names can be any appropriate alphanumeric string State names are created with the DEFINE KEY command If you omit the IF_STATE qualifier or use NOIF_STATE key definitions in the current state are displayed 6 142 RTR Command Line Interface SHOW KEY Related Commands DEFINE KEY Examples RTR gt SHOW KEY FULL DEFAULT PF1 defined as DEFAULT KPO 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 defined as SCROLL RIGHT 1 DEFAULT KP8 defined as SCROLL UP 1 GOLD KP2 defined as SCROLL DOWN 10 GOLD KP4 defined as SCROLL LEFT 10 GOLD KP6 defined as SCROLL RIGHT 10 GOLD KP8 defined as SCROLL UP 10 RTR Command Line Interface 6 143 SHOW LINK SHO

Compaq AA-Q88CE-TE User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents