Procedure on the Destination System

1. Integrate any saved PLId to port maps into the devices file:

   /usr/Realman/RealityVersion/files/devices	(UNIX)

   or

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

2. On UNIX, copy any saved printer interface scripts into: $REALROOT/files/interfaces.
3. On UNIX, check that any RPQs that were installed on the old system are available on the new system. If not, contact Northgate support.
4. Create a new database using the mkdbasecommand - see Set-up After Installation in the appropriate installation guide. The new database must be large enough to hold the data transferred, as noted after saving the source database.
5. Restore any customised database configuration by integrating the contents of your saved configuration files with those in the directory/folder:

   DatabasePath/configs/config			(UNIX)

   or

   DatabasePath\configs\config			(Windows)

6. Log on to the SYSMAN account. Then load the FILE-SAVE tape and ensure that it is online.
7. Enter the following sequence of commands to restore your system/database:

   ASSIGN =TAPE n n = tape unit No.
   T-REW
   T-FWD
   T-RDLBL 1
   T-FWD
   ACCOUNT-RESTORE * (O

8. If upgrading from a version earlier than Reality V9.1, load the system tools. Enter the following sequence of commands:

   T-DEVICE n $REALROOT/files/upgfile.rti             n = tape unit No.
   ASSIGN = TAPE n
   T-REW
   INSTALL

   Follow the prompts to install the upgrade bootstrap. Then enter

   CLEAR-ASSIGN

9. Run SYS-UPDATE, responding to the prompts as described in SYS-UPDATE Details.
10. Integrate any customised system file items that were saved from the source system/database.
11. Carry out FILE-SAVE and VERIFY-SAVE.
12. Start Transaction Processing, if required.
13. Enable logons (use ENABLE-LOGONS from TCL, or the unlockdbase host command).

SYS-UPDATE Details

When you run SYS-UPDATE, you are prompted to enter the release of Reality from which you are transferring.

The following prompt is then displayed:

Restore from a different machine type? (Y/N) :

At this prompt enter Y if you are transferring from a host with a different binary format; otherwise, enter N. Reality hosts have the following binary formats:

For example, if transferring data from Solaris to AIX, enter N; if transferring from AIX to Linux, enter Y; and so on.

DataBasic Conversion

During SYS-UPDATE, cataloged DataBasic programs in POINTER-FILE are upgraded if necessary. Accounts BASIC.CONVERSION and UPGRADE.ACCOUNT are populated by this process.

If the transfer is from a release prior to RealityX 4.0 or ROS 7.2, the DataBasic object code is converted. If the SYS-UPDATE process cannot determine the byte order of the source system the following prompt is displayed:

Unable to determine BYTE ORDER of item to be upgraded.
Please enter - 'R' if from a Byte Reversed, ie RX, NT or DGUX system.
          or - 'N' if from a Byte Normal system.
'S' will suppress this message and log item(s) with error code 16.

If you see this prompt, enter a response based on the table of binary formats shown above.

RUN SYSBP UPGRADE.BASIC.OBJECT

The format of basic object code changed on release 4.x. All cataloged Basic programs are checked and converted to the 4.x format if possible. The converter attempts to find the original object item ($item-id) that was used to produce the cataloged image and verify that the compilation date and times match. If successful, the converter converts the original object item to 4.x format and recatalogs it. If the correct object cannot be found, the pointer file item is 'decataloged', converted and recataloged.

An account 'BASIC.CONVERSION' is created to maintain a record of the conversion process and allow any problems to be investigated. In the account are the following three files:

CONVERTER.LOG

An entry is made in this file for each basic program item found in pointer file that needed conversion. The error codes in attribute 3 are decoded through a data section 'XLATE', but fall into three groups. Any codes between 1 and 9 are represent successful conversions with informational messages. Codes 10 through 20 represent failures to convert with associated messages. Any other codes correspond to errors produced by the CONVERT.OBJECT or CATALOG verbs.

PRIOR.PF

A copy of the pointer file item is placed in this file prior to conversion.

PRIOR.OBJ

A copy of the $ item is placed here prior to conversion, but with the same item-id as the pointer file item.

The command

LIST CONVERTER.LOG PROBLEMS

lists any items that failed to convert. The main reason for conversion failure is prior corruption of the pointer file item that has gone unnoticed because the item is no longer used. After resolving any errors the account should be saved to tape and may be deleted from the system.

Changing Lower- to Upper-Case Dates

• For each user that needs uppercase dates, set the UCASEDATES and UCASEDAYS options in their operating environment.
• Add the following commands to the LOGON program for each account that needs uppercase dates:

  SET-OPTION UCASEDATES
  SET-OPTION UCASEDAYS

• Configure Reality to use only upper-case dates:
  1. Logto the DENAT account on the database. The following menu is displayed:

                              MAIN MENU
     
               1. Language table maintenance.
               2. Error message file maintenance.
               3. Character tables maintenance.
               4. List file names.
               5. Make alphabet
               6. Exit to TCL.
               7. Logoff.
                   Enter selection:
     

  2. Selection option 6 (Exit to TCL).
  3. Enter:

     :ED ENGLISH CLASS0
     Top
     .MU87-98
     .FI
     'CLASS0' filed in file 'ENGLISH'.

  4. Then enter:
  5. :LOAD-LANG ENGLISH CLASS0Language number or name:0[9100] 'L0' loaded. : OFF

  The next time a logon or process is performed the dates will all be in uppercase.