Installation
2.6 Journal Issues
2.6.1 Removing the Old Journal
To verify that the new journal is running correctly, use the DUMP JOURNAL command to verify that transactions are processing as expected, and to be sure that all transactions have completed before bringing down RTR to install RTR Version 3.
There is no need to save the old journal file once all transactions have cleared.
2.6.2 Journal Compatibility
RTR Version 2 journal files are incompatible with RTR Version 3 journal files. No tools exist to migrate RTR Version 2 journal files to the RTR Version 3 journal file.
2.6.3 Location and Naming Conventions
With RTR, the journal records transactions for use during recovery when required. You specify the disk location for the journal file with the CREATE JOURNAL command. This is unchanged for RTR Version 3.
However, the location and naming conventions for the journal have changed for RTR Version 3.
In RTR Version 2, journal files reside on each
dev:[RTRJNL]filename
In RTR Version 3, journal files reside on each
dev:[RTRJNL.SYSTEM]nodename.Jnn
Group names are used for naming RTR journal files.
2.7 Rights and Privileges
You need the same rights and privileges to manage the RTR environment and RTR applications in Version 3 as in Version 2.
To manage RTR, you must have one of the following OpenVMS system rights or privileges: OPER, SETPRV, RTR$OPERATOR. To use the RTR API rtr_request_ info, you must have the following right: RTR$INFO.
To run an application, you must have the following OpenVMS privilege:
TMPMBX.
2.8 Memory and Disk Requirements
Generally, RTR Version 3 may make more demands on system memory than RTR Version 2, which can cause performance reduction. Adding more memory may be useful in improving performance.
Table
