Restoring changed objects

Use these steps to restore changed objects on your existing system.

Testing objects to preserve

This example assumes that you are not making permanent changes to volatile objects (such as database files) on your new system. When you restore, you will be overlaying test objects.

It also assumes that after you build your initial new system, you will not restore programs from the existing system to the new system during synchronization (because those programs are already converted on your new system).

If you need to preserve test objects or if programs change on your existing system, you need to make special plans for your restore procedures.

To restore the changed objects that you saved, perform these steps on your test system:

To avoid any problems with inadequate authority, sign on as the security officer (QSECOFR).
Place your system in a restricted state.
To restore the saved user profiles, use the Restore User Profile (RSTUSRPRF) command:
```
RSTUSRPRF USRPRF(*ALL) DEV(tape-device)
    ENDOPT(*LEAVE)
```
Locate the printout of the job log from your save operation. Use it to determine which libraries the system saved. If you do not have the job log, you can use the Display Tape (DSPTAP) command to display the contents of the save tapes:
```
DSPTAP DATA(*SAVRST) OUTPUT(*PRINT)
```
Use one of the following methods to restore objects from the Save Changed Objects tape. The first method is easier and quicker:
- For all libraries on the save tapes, type the following command:
```
RSTOBJ(*ALL) DEV(tape-device) SAVLIB(*ANY) 
OMITLIB(QGPL QUSRSYS) ENDOPT(*REWIND) MBROPT(*ALL)
```
  If you have changes in the QGPL and QUSRSYS libraries, type the following command for QGPL and QUSRSYS:
```
RSTOBJ OBJ(*ALL) DEV(tape-device) OBJTYPE(*ALL)
   SAVLIB(library-name) ENDOPT(*LEAVE) MBROPT(*NEW)
```
- For each library on the save tapes, type the following command:
```
RSTOBJ OBJ(*ALL) DEV(tape-device) OBJTYPE(*ALL)
   SAVLIB(library-name) ENDOPT(*LEAVE) MBROPT(*ALL)
```
Notes:
- For both the QGPL library and the QUSRSYS library, you must specify MBROPT(*NEW). This prevents overlaying new system files with old system files.
- Do not specify ALWOBJDIF(*ALL). Normal restore processing with the default ALWOBJDIF value protects you from accidentally overlaying critical information. ALWOBJDIF(*ALL) is intended only when you are initially loading information from one system to another.
- If your new system has a different auxiliary storage pool (ASP) configuration from your existing system, you might need to specify the SAVASP and RSTASP parameters.
To restore document library objects that you saved in step 6 in the Steps for saving changed objects topic, type the following command:
```
RSTDLO DLO(*ALL) DEV(tape-device) ENDOPT(*LEAVE)
```
Notes:
- Do not use this restore command unless your save tapes contain only changed document library objects (DLOs). If you restore all DLOs from your existing system, you will overlay IBM-supplied objects that are used for System i® Access.
- This command does not restore mail that has changed. Mail gets restored in step 8.
- Changes to calendars are restored when you restore the QUSRSYS library.
- If you have DLOs in more than one ASP, you need to run the Restore Document Library Object (RSTDLO) command for each ASP. You specify the SAVASP and RSTASP parameters.
To restore mail that you saved in step 7 in the Steps for saving changed objects topic, use the RSTDLO command as follows:
```
 RSTDLO DLO(*MAIL)
```
To restore the changed directory objects that you saved in step 8b in the Steps for saving changed objects topic, type the following command:
```
RST DEV('/QSYS.LIB/tape-device.DEVD')
  OBJ(('/*' *INCLUDE) ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT))
```
Use the Display Job Log to print your job log:
```
DSPJOBLOG OUTPUT(*PRINT)
```
Review it carefully. Whenever you restore changed objects, you are likely to encounter situations that you will need to recover manually. If you plan to synchronize your system several times, you might find it useful to create a log that describes synchronization problems and their resolutions. This will help to reduce your synchronization time in the future.
After you resolve any problems that occurred with restored objects, use the Restore Authority (RSTAUT) command to restore private authorities.
Note: You should wait to restore authority until after you resolve any problems because some problem resolution steps might require you to restore new objects.
Restart the controlling subsystem and make the system available for more testing.