Running Version 2 Applications
6.1 Comparison of OpenVMS API and Portable API
Table 6–1 OpenVMS API and Portable API Comparison
OpenVMS API (Version 2) | Portable API (Version 3) |
|
|
$dcl_tx_prc( ) | rtr_open_channel( ) |
$start_tx( ) | rtr_start_tx( ) [optional] |
$commit_tx( ) | rtr_accept_tx( ) |
$abort_tx( ) | rtr_reject_tx( ) |
$vote_tx( ) | rtr_accept_tx( ) |
| rtr_reject_tx( ) |
$deq_tx( ) | rtr_receive_message( ) |
$enq_tx( ) | rtr_send_to_server( ) |
| rtr_reply_to_client( ) |
| rtr_broadcast_event( ) |
$dcl_tx_prc( ) (SHUT) | rtr_close_channel( ) |
$get_txi( ) | rtr_request_info( ) |
$set_txi( ) | rtr_set_info( ) |
ASTPRM (on asynch calls) | rtr_set_user_handle( ) |
- | rtr_error_text( ) |
- | rtr_get_tid( ) |
- | rtr_prepare_tx( ) |
- | rtr_set_wakeup( ) |
|
|
OpenVMS API calls are obsolete and supported only on OpenVMS systems.
6.2 Recompiling and Relinking
There is no need to recompile and relink RTR Version 2 applications to run them on RTR Version 3.
To link RTR application programs, include the following line in the linker options file:
SYS$SHARE:LIBRTR/SHARE
An existing RTR Version 2 application will run on RTR Version 3.
However, if the application is recompiled, you must supply all parameters for any RTR call. For example, the $ENQ_TX service has eleven parameters, some of which were optional in RTR Version 2. All eleven must be supplied if the application is recompiled with RTR Version 3.
Note
If recompiling an RTR Version 2 application not written in C, use appropriate include files from the RTR Version 2 kit to ensure correct compilation. With the RTR Version 3 API, C is the only language for which a header file is provided.