Before you restore libraries to the system auxiliary
storage pool (ASP), decide which libraries to restore.
- You should restore only the libraries in your system ASP. Do not
restore the libraries that are already on your system in user ASPs.
If you are not sure which libraries are currently on your system,
type
DSPOBJD OBJ(*ALL) OBJTYPE(*LIB).
Note: When you
install the operating system, the system creates the QGPL library and the
QUSRSYS library. You should still restore these libraries to restore the
data from your saved copy.
- Plan your restore sequence. If you restore in the wrong
sequence, your journaling environment might not be started again or some objects
might not restore successfully. For example,
journals must be restored before the journaled objects. If journals and objects
are in the same library, the system restores them in the correct order. If
they are in different libraries, or the objects are integrated file system
objects, you must restore them in the correct order. Similarly, physical files
must be restored before their dependent logical files and SQL materialized
query tables (MQTs). If some of the dependent files are missing or stored
in a different library, you can do a deferred restore of those files.
- Choose the commands or menu options you will use. You
can restore libraries by name or in a group, such as *NONSYS.
If you restore
libraries in a group, omit the libraries in your user ASPs.
- Type the restore commands or menu options that you have chosen. In the example shown in Figure 1,
libraries were saved using SAVLIB(*ALLUSR). One way to restore them is to
type the following command:
RSTLIB SAVLIB(*ALLUSR) DEV(media-device-name)
OMITLIB(ORDLIB TRANLIB $JRNLB $RCVRB)