Documentation Comments
Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.
RealityV15.1Online Documentation (MoTW) Revision 7
Procedure on the Source System (Transferring a Database) (M6960CR+Source.htm)
Save any customised database configuration files.
On RealityX Release 3.1C, these are located in the UNIX directory DatabasePath/config (where DatabasePath is the location of the database).
On later UNIX releases, they are located in the directory DatabasePath/configs/config.
On Windows systems, they are located in the Windows folder DatabasePath\configs\config.
$REALROOT/files/devices (UNIX)or
drive:\Realman\RealityVersion\files\devices (Windows)Save to elsewhere in the database any system file items that you have customised. Customised files often include SYSPROG-PL, PROCLIB, BP, SYSBP, SYSBP.MSGS, SYSPL, SYS.BASLIB, BASIC-COMPILERS and NEWAC. It is advisable to save the whole contents of these files if in doubt about what has been customised within them.
FILE-SAVE and VERIFY-SAVE.
Label the save as "[Reality Pre-Update Save]" with all relevant versions and dates.
Caution
These saves should be retained indefinitely; at least until the next version or release upgrade.
Note: This file save will be restored to a new database on the destination host, so you must use a compatible format. Where possible use a compressed virtual tape drive, or both source and destination systems must have compatible drives and media.
Use the POVF verb to display the total size of the database. Note this size to ensure that the database created on the destination system is sufficiently large.
Note the numbers of any RPQs that are installed - this is typically only for NPS Applications.
If Transaction Handling is enabled, use the command plog -h to display details of the raw log configuration. Take a note of the raw log size and the buffer size.
On a UNIX host, save any printer interface scripts from $REALROOT/files to a safe location.
Carry out a FILE-SAVE and a VERIFY-SAVE of the database.
Label the save as "[Reality Pre-Update Save]" with all relevant versions and dates.
Apply custom patch 008 (if transferring to UNIX) or 10 (if transferring to Windows) to make multi-reel file saves compatible with the destination database.
Save to elsewhere in the database any system file items that you have customised. Customised files often include SYSPROG-PL, PROCLIB, BP, SYSBP, SYSBP.MSGS, SYSPL, SYS.BASLIB, BASIC-COMPILERS and NEWAC. It is advisable to save the whole contents of these files if in doubt about what has been customised within them.
FILE-SAVE and VERIFY-SAVE the database.
Note: This file save will be restored to a new database on the destination host, so you must use a compatible format.
Use the POVF verb to display the total size of the database. Note this size to ensure that the database created on the destination system is sufficiently large.