Compaq AAR-88LB-TE manual Running Version 2 Applications 6.2 Recompiling and Relinking

Page 33
Running Version 2 Applications

Running Version 2 Applications

6.2 Recompiling and Relinking

6.2.1RTR Version 2 Applications Running on RTR Version 3

Linking Version 2 applications

Existing RTR Version 2 applications will run if they have been linked against RTRSHR. (RTRSHR has been superseded by LIBRTR.EXE. Existing RTR Version 2 application executables will run without relinking since RTR$STARTUP.COM defines RTRSHR as a logical name that points to LIBRTR.EXE.)

However, as RTRSHR.EXE is no longer distributed, change the linker options file referencing RTRSHR (that is, change SYS$SHARE:RTRSHR/SHARE to SYS$SHARE:LIBRTR/SHARE). After making this change, you can remove SYS$SHARE:RTRSHR.EXE from your system.

If you are linking on a system where RTR Version 2 was never installed, always use SYS$SHARE:LIBRTR/SHARE.

Event status

With RTR Version 2, an application could pass event status as a parameter when calling $ENQ with the RTR$M_BROADCAST flag set. This broadcast $ENQ was delivered with the event status stored in the RTR$L_EVT_ STATUS field of the RTR$_EVT data structure, and passed as a parameter to the broadcast AST.

When running RTR Version 2 applications on RTR Version 3, event status is not passed from sender to receiver. All User events received by an RTR Version 2 application have the event status parameter set to 0 as shown in the following table:

If the sender is:

Then:

 

 

A Version 2 application

RTR Version 3 does not pass event status.

A Version 3 application

There is no event status.

 

 

Channel number

In some cases, RTR Version 2 returned the error status RTR$_INVALCH if an operation was attempted using an invalid channel number (for example, 0), and RTR$_CHNOTALLOC for potentially valid channel numbers that have not been declared. RTR Version 3 always returns RTR$_CHNOTALLOC.

RTR STOP/ABORT

If an RTR STOP RTR/ABORT command is issued with RTR Version 2, RTR executes an AST in the context of any applications that have an RTR channel open. The applications exit with the status RTR$_RTRWASSTO.

In RTR Version 3, there is no difference in behaviour between the commands STOP RTR and STOP RTR/ABORT. If either of these commands is entered, RTR is always stopped. Any application with an RTR channel open receives an error status on any RTR operation in progress on that channel, but

the application is not terminated. The application must handle the error correctly. (The error status returned in this case is RTR$_NOACP, the same status that is returned if the RTR ACP fails for any reason.)

Running Version 2 Applications 6–3

Image 33
Contents June Reliable Transaction Router Migration GuideOperating System Compaq Computer Corporation Houston, TexasFirst Printing, December Revised, June Installation ContentsNetwork Issues PrefaceSystem Management 8 Problem Diagnosis and Reporting6 Running Version 2 Applications Performance TipsIndex Tables Page Preface AudienceOrganization of This Guide Related Documents Readers CommentsConventions monospace Page Introduction 1.1 Why Migrate?Introduction 1.1 Why Migrate? 1.2 Goals and Nongoals1.3 Reading Guidelines 2.1 Cleaning Up the Old Version 2 Environment Installation2.2 Preserving the Old Environment Installation 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 2.7 Rights and Privileges Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal2.8 Memory and Disk Requirements 2.6.2 Journal Compatibility2.8 Memory and Disk Requirements 2.9 Rollback to RTR VersionDEASSIGN/SYSTEM/EXEC RTRSHR Table 2-2 OpenVMS Disk RequirementsPage Architectural Changes 3.2 Command Server Process3.1 RTR Daemon Process 3.3 The Shared Library LIBRTR.EXE3.5 Interprocess Communication 3.4 The ACP Process3.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 5.1 OpenVMS Quotas System Management5.2 Startup 5.3 Creating Facilities5.5 Monitoring 5.4 InteroperabilitySystem Management 5.4 Interoperability 5.5.1 RTR Version 2 Screens5.5.3 User Parsing of Monitor Output 5.5 Monitoring5.5.4 User Customized Monitors Table 5-3 New RTR Version 3 Monitor Pictures5.9 Using RTR Version 2 Command Procedures 5.6 Remote Command Support5.10 Command Line Interface Support for RTR Version 2 API 5.11 Interpreting Output from SHOW CommandsSystem Management 5.11 Interpreting Output from SHOW Commands 5.12 Comparing RTR Version 2 and Version 3 Utility CommandsTable 5-4 Cont. Changed SHOW COMMANDS Table 5-5 Obsolete OpenVMS RTR Utility CommandsTable 5-6 Cont. New OpenVMS RTR Utility Commands 5.12 Comparing RTR Version 2 and Version 3 Utility Commands6.1 Comparison of OpenVMS API and Portable API Running Version 2 ApplicationsRunning Version 2 Applications 6.2 Recompiling and Relinking6.1 Comparison of OpenVMS API and Portable API Table 6-1 OpenVMS API and Portable API Comparison6.2.1 RTR Version 2 Applications Running on RTR Version Running Version 2 Applications 6.2 Recompiling and Relinking6.3 Running Applications Installed with Privileges 6.3 Running Applications Installed with Privileges6.4 Application Level Interoperability 6.5 Support for $GETTXI6.6 Threaded Applications 6.8 Current Issues6.7 DDTM Support Running Version 2 Applications 6.6 Threaded ApplicationsPage 7.1 Process Quotas Performance Tips7.2 Journal Sizing 7.3 RTR Startup QualifiersPerformance Tips 7.6 Simultaneous Multiprocessing 7.6 Simultaneous Multiprocessing8.2 RTRERROR.LOG File Problem Diagnosis and Reporting8.1 RTR Operator Log 8.3 Dump FileProblem Diagnosis and Reporting 8.4 Producing and Directing a Trace 8.6 Contents of the RTR Journal File1. Enter the SHOW PROCESS RTRACP/CONTINUOUS OpenVMS command 4. Enter the OpenVMS ANALYZE/SYSTEM SET PROCESS RTRACP commandIndex