Procedure on the Source system

Source Database on Reality Host Platforms (UNIX or Windows)

  1. Save any customised database configuration files.

    • On UNIX releases, they are located in the directory DatabasePath/configs/config.

    • On Windows systems, they are located in the Windows folder DatabasePath\configs\config.

  2. Save any PLId to port maps from:
    $REALROOT/files/devices  (UNIX)

    or

    Remove

    drive:\Realman\RealityVersion\files\devices	(Windows)

  3. 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.

  4. 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.

  5. 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.

  6. Note the numbers of any RPQs that are installed - this is typically only for NEC Applications.

  7. 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.

  8. On a UNIX host, save any printer interface scripts from $REALROOT/files to a safe location.

Source Database on Series 18/19 Reality Proprietary Hardware

  1. 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.

  2. 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.

  3. 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.

  4. 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..

  5. 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.