Compaq AAR-88LB-TE manual Running Applications Installed with Privileges, Support for $GETTXI

Page 34
6.3 Running Applications Installed with Privileges

Running Version 2 Applications

6.3 Running Applications Installed with Privileges

6.3 Running Applications Installed with Privileges

With RTR Version 2, RTR calls execute in kernel mode; with RTR Version 3, RTR runs in application process mode, normally user mode.

6.3.1 Running Clients That Share Channels

With RTR Version 2, clients that start up and declare channels could use the flag INHNOSRVWT (inhibit-no server-wait) to proceed without waiting. (It lets $DCL_TX_PRC/REQ complete before servers have been declared.) With RTR Version 3, to perform a similar operation, an application must have either the OPER or RTR$OPERATOR process right.

6.4 Application Level Interoperability

With RTR Version 2, application level interoperability worked only with both applications running on the same operating system. With the upgrade to RTR Version 3, applications using the RTR Version 3 API can run on any supported operating system, and RTR Version 2 and RTR Version 3 applications can run in the RTR Version 3 environment. Table 6–2 provides information on application interoperability.

Table 6–2 Application Interoperability

Application Feature

Description

 

 

Mixing Version 2 and

You cannot mix RTR Version 2 and RTR Version 3 calls in

Version 3 style calls

the same application.

Transaction identification

In RTR Version 3, unless your application uses only

 

the RTR Version 2 API and DECnet, the size of the

 

transaction identification is larger than in RTR Version 2

 

(28 bytes compared to 8 bytes).

Version 2 and Version 3 applications talking to one another

RTR Version 2 and RTR Version 3 applications can directly communicate using RTR calls.

The DSDEF feature for data marshalling

A new feature in RTR Version 3 is DSDEF, with which an application can specify data marshalling requirements. With RTR Version 3, you can specify data format and RTR Version 3 can do format translations where required. See the Reliable Transaction Router Application Programmer's Reference Manual for more information.

6.5 Support for $GETTXI

The $GETTXI system service to return transaction information is not available in RTR Version 3. The RTR Version 3 equivalent is rtr_request_info. Applications that used $GETTXI must either remove $GETTXI or convert to RTR Version 3 calls. This change was required because of significant change to RTR data structures between RTR Version 2 and RTR Version 3.

6–4Running Version 2 Applications

Page 33 Page 35
Image 34
Page 33 Page 35
Contents Operating System Reliable Transaction Router Migration GuideJune Compaq Computer Corporation Houston, TexasFirst Printing, December Revised, June Network Issues ContentsInstallation Preface6 Running Version 2 Applications 8 Problem Diagnosis and ReportingSystem Management Performance TipsIndex Tables Page Audience PrefaceOrganization of This Guide Readers Comments Related DocumentsConventions monospace Page 1.1 Why Migrate? Introduction1.2 Goals and Nongoals Introduction 1.1 Why Migrate?1.3 Reading Guidelines Installation 2.1 Cleaning Up the Old Version 2 Environment2.3 Can Both RTR Version 2 and Version 3 Coexist On the Same Node? Installation 2.2 Preserving the Old Environment2.2 Preserving the Old Environment 2.5 Process QuotasInstallation 2.5 Process Quotas 2.6 Journal IssuesTable 2-1 OpenVMS Limits 2.8 Memory and Disk Requirements Installation 2.6 Journal Issues 2.6.1 Removing the Old Journal2.7 Rights and Privileges 2.6.2 Journal CompatibilityDEASSIGN/SYSTEM/EXEC RTRSHR 2.9 Rollback to RTR Version2.8 Memory and Disk Requirements Table 2-2 OpenVMS Disk RequirementsPage 3.1 RTR Daemon Process 3.2 Command Server ProcessArchitectural Changes 3.3 The Shared Library LIBRTR.EXE3.6 Shared Memory Parameters 3.4 The ACP Process3.5 Interprocess Communication 3.7 CountersArchitectural Changes 3.8 Quorum Issues 3.8 Quorum Issues3.9 Server-Process Partition States Page 4.1 DECnet Support Network Issues4.2 TCP/IP Support 4.3 Specifying a Preferred Transport Network Issues 4.3 Specifying a Preferred Transport4.3.1 Supported Products 5.2 Startup System Management5.1 OpenVMS Quotas 5.3 Creating FacilitiesSystem Management 5.4 Interoperability 5.4 Interoperability5.5 Monitoring 5.5.1 RTR Version 2 Screens5.5.4 User Customized Monitors 5.5 Monitoring5.5.3 User Parsing of Monitor Output Table 5-3 New RTR Version 3 Monitor Pictures5.10 Command Line Interface Support for RTR Version 2 API 5.6 Remote Command Support5.9 Using RTR Version 2 Command Procedures 5.11 Interpreting Output from SHOW CommandsTable 5-4 Cont. Changed SHOW COMMANDS 5.12 Comparing RTR Version 2 and Version 3 Utility CommandsSystem Management 5.11 Interpreting Output from 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.1 Comparison of OpenVMS API and Portable API 6.2 Recompiling and RelinkingRunning Version 2 Applications 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.4 Application Level Interoperability 6.3 Running Applications Installed with Privileges6.3 Running Applications Installed with Privileges 6.5 Support for $GETTXI6.7 DDTM Support 6.8 Current Issues6.6 Threaded Applications Running Version 2 Applications 6.6 Threaded ApplicationsPage 7.2 Journal Sizing Performance Tips7.1 Process Quotas 7.3 RTR Startup Qualifiers7.6 Simultaneous Multiprocessing Performance Tips 7.6 Simultaneous Multiprocessing8.1 RTR Operator Log Problem Diagnosis and Reporting8.2 RTRERROR.LOG File 8.3 Dump File1. Enter the SHOW PROCESS RTRACP/CONTINUOUS OpenVMS command 8.6 Contents of the RTR Journal FileProblem Diagnosis and Reporting 8.4 Producing and Directing a Trace 4. Enter the OpenVMS ANALYZE/SYSTEM SET PROCESS RTRACP commandIndex
Top Page Image Contents