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

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