RESTORE integrates one or more BACKUP /INCREMENTAL files into a corresponding database. The transaction number in the first incremental backup must be one more than the current transaction number of the database. Otherwise, MUPIP RESTORE will terminate with an error and refuse to perform the restore.
The format of the RESTORE command is:
RE[STORE] [/qualifier] file-spec file-list
The file-specification identifies the name of the database file that RESTORE uses as a starting point. The transaction number in the database must match the starting transaction number of each successive input to the RESTORE. If the BACKUP /INCREMENTAL was created using /TRANSACTION=1, create a new database with MUPIP CREATE and do not access it, except the standalone MUPIP commands INTEG /FILE, EXTEND, and SET before initiating the RESTORE.
The file-list specifies one or more files produced by BACKUP /INCREMENTAL to RESTORE into the database. The file-specification are separated by commas (,) and must be in sequential order, from the oldest transaction number to the most recent transaction number. RESTORE may take its input from an RMS , including magnetic tape devices. When using an input file on a magnetic tape, use DCL to MOUNT specifying the same /BLOCKSIZE= as the one used to make the tape.
/[NO]E[XTEND]
Specifies whether RESTORE should extend the database file automatically if it is smaller than the size required to load the data. M activity between backups may automatically extend a database file. Therefore, the database file specified as the starting point for a RESTORE may require an extension before the RESTORE. If the database needs an extension and the command specifies /NOEXTEND, MUPIP displays a message. The message provides the sizes of the input and output database files and the number of blocks by which to extend the database. If the RESTORE specifies more than one incremental backup with a file list, the database file may require more than one extension.
By default, RESTORE automatically extends the database file.