The maintenance process involves the following tasks:

Generate to the Base System

Use the build/generate processes to ensure all code changes are generated to the base system.

Transfer to the Primary System

When you are ready, carry out a RTU transfer and configure to the primary system. On the RTU Transfer Startup Screen, specify the name of the segment, name of the three Configuration sets and name of the RTU file as you did above procedures. The rest of the RTU screens are handled as for a normal transfer. The configure process handles the reorganization processes in the same way that it did before RDB was introduced and the database availability rules are the same as they would be if RDB was not in use.

When reorganization starts, the Enterprise Application Environment configure process locks and unlocks the database as it did before and the unlock indicates you can bring the system back up within the normal (DMSII) restrictions on using the database. With RDB involved, the period of locking are a little longer because of processes needed to accommodate reorganization of the secondary database.

Transfer to the Secondary System

This step should follow as soon as possible after every transfer to the primary system. You have to run the RTU utility. On the first RTU screen, specify the name of the primary system Configuration set in the Generate Set used for generate field and the name of the secondary system Configuration set in the Configure Generate Set field. Ensure that the RDB Generate Set field is left blank. The data on the rest of the screens is simply entered as required for a normal transfer and configure.

Implementing the Configuration Set Changes

Changes might be made to any of the three Configuration sets at any time; however, you should ensure that an RTU extract is completed each time (including where changes are made to the base system only). Changes to the primary and secondary system Configuration set is not implemented until the RTU/configure processes are completed.