Compaq AAR-88LB-TE manual Specifying a Preferred Transport, Supported Products

Page 24

Network Issues

4.3 Specifying a Preferred Transport

4.3 Specifying a Preferred Transport

During installation, the system manager can specify either transport, using logical names RTR_DNA_FIRST or RTR_TCP_FIRST. For example, in the RTR$STARTUP.COM file (found in SYS$STARTUP), the following line specifies DECnet as the default transport:

$ DEFINE/SYSTEM RTR_PREF_PROT RTR_DNA_FIRST

To set the default transport to TCP/IP, remove (comment out) this definition from RTR$STARTUP.COM and restart RTR. For the change to take immediate effect, you must undefine the old logical name before restarting RTR.

You can also change the above command in RTR$STARTUP.COM to the following:

$ DEFINE/SYSTEM RTR_PREF_PROT RTR_TCP_FIRST

When creating a facility using TCP/IP as the default, you can specify

dna.nodename to override TCP/IP and use DECnet for a specific link. Similarly, when using DECnet as the default, you can specify tcp.nodename to use TCP/IP for a specific link. If the wrong transport has been assigned to a link, you must trim all facilities to remove nodes using the link (use the TRIM FACILITY command) to remove the link, then add the nodes back into the facility specifying the correct transport.

To run the DECnet protocol exclusively, use the following definition for the RTR preferred protocol logical name:

$ DEFINE/SYSTEM RTR_PREF_PROT RTR_DNA_ONLY

For examples of this command syntax, see the section on Network Transports in the Reliable Transaction Router System Manager's Manual.

4.3.1 Supported Products

Network products supported are listed in the RTR Version 3 Software Product Description.

4–2Network Issues

Image 24
Contents Reliable Transaction Router Migration Guide JuneOperating System Compaq Computer Corporation Houston, TexasFirst Printing, December Revised, June Contents InstallationNetwork Issues Preface8 Problem Diagnosis and Reporting System Management6 Running Version 2 Applications Performance TipsIndex Tables Page Preface AudienceOrganization of This Guide Related Documents Readers CommentsConventions monospace Page 1.1 Why Migrate? IntroductionIntroduction 1.1 Why Migrate? 1.2 Goals and Nongoals1.3 Reading Guidelines Installation 2.1 Cleaning Up the Old Version 2 EnvironmentInstallation 2.2 Preserving the Old Environment 2.2 Preserving the Old Environment2.3 Can Both RTR Version 2 and Version 3 Coexist On the Same Node? 2.5 Process Quotas2.6 Journal Issues Installation 2.5 Process QuotasTable 2-1 OpenVMS Limits Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal 2.7 Rights and Privileges2.8 Memory and Disk Requirements 2.6.2 Journal Compatibility2.9 Rollback to RTR Version 2.8 Memory and Disk RequirementsDEASSIGN/SYSTEM/EXEC RTRSHR Table 2-2 OpenVMS Disk RequirementsPage 3.2 Command Server Process Architectural Changes3.1 RTR Daemon Process 3.3 The Shared Library LIBRTR.EXE3.4 The ACP Process 3.5 Interprocess Communication3.6 Shared Memory Parameters 3.7 Counters3.8 Quorum Issues Architectural Changes 3.8 Quorum Issues3.9 Server-Process Partition States Page Network Issues 4.1 DECnet Support4.2 TCP/IP Support Network Issues 4.3 Specifying a Preferred Transport 4.3 Specifying a Preferred Transport4.3.1 Supported Products System Management 5.1 OpenVMS Quotas5.2 Startup 5.3 Creating Facilities5.4 Interoperability 5.5 MonitoringSystem Management 5.4 Interoperability 5.5.1 RTR Version 2 Screens5.5 Monitoring 5.5.3 User Parsing of Monitor Output5.5.4 User Customized Monitors Table 5-3 New RTR Version 3 Monitor Pictures5.6 Remote Command Support 5.9 Using RTR Version 2 Command Procedures5.10 Command Line Interface Support for RTR Version 2 API 5.11 Interpreting Output from SHOW Commands5.12 Comparing RTR Version 2 and Version 3 Utility Commands System Management 5.11 Interpreting Output from SHOW CommandsTable 5-4 Cont. Changed SHOW COMMANDS Table 5-5 Obsolete OpenVMS RTR Utility Commands5.12 Comparing RTR Version 2 and Version 3 Utility Commands Table 5-6 Cont. New OpenVMS RTR Utility CommandsRunning Version 2 Applications 6.1 Comparison of OpenVMS API and Portable API6.2 Recompiling and Relinking Running Version 2 Applications6.1 Comparison of OpenVMS API and Portable API Table 6-1 OpenVMS API and Portable API ComparisonRunning Version 2 Applications 6.2 Recompiling and Relinking 6.2.1 RTR Version 2 Applications Running on RTR Version6.3 Running Applications Installed with Privileges 6.3 Running Applications Installed with Privileges6.4 Application Level Interoperability 6.5 Support for $GETTXI6.8 Current Issues 6.6 Threaded Applications6.7 DDTM Support Running Version 2 Applications 6.6 Threaded ApplicationsPage Performance Tips 7.1 Process Quotas7.2 Journal Sizing 7.3 RTR Startup Qualifiers7.6 Simultaneous Multiprocessing Performance Tips 7.6 Simultaneous MultiprocessingProblem Diagnosis and Reporting 8.2 RTRERROR.LOG File8.1 RTR Operator Log 8.3 Dump File8.6 Contents of the RTR Journal File Problem Diagnosis and Reporting 8.4 Producing and Directing a Trace1. Enter the SHOW PROCESS RTRACP/CONTINUOUS OpenVMS command 4. Enter the OpenVMS ANALYZE/SYSTEM SET PROCESS RTRACP commandIndex