Syntax and options of the RECOVER control statement

The RECOVER utility control statement, with its multiple options, defines the function that the utility job performs.

You can create a control statement with the ISPF/PDF edit function. After creating it, save it in a sequential or partitioned data set. When you create the JCL for running the job, use the SYSIN DD statement to specify the name of the data set that contains the utility control statement.

Start of changeSyntax diagramEnd of change

Read syntax diagramSkip visual syntax diagram RECOVER LISTlistdef-nameobjectdsnum-speclist-options-specrecover-options-specrecover-from-multi-specrecover-from-specobjectPAGEpage-numberCONTINUE CLONE1 LOCALSITERECOVERYSITELOGRANGESYESLOGRANGESNO2
Notes:
  • 1 CLONE is not allowed with recover-from-multi-spec or recover-from-spec.
  • 2 Use the LOGRANGES NO option only at the direction of IBM® Support. This option can cause the LOGAPPLY phase to run much longer and, in some cases, apply log records that should not be applied.

object:

Read syntax diagramSkip visual syntax diagramTABLESPACEdatabase-name. table-space-nameINDEXSPACEdatabase-name. index-space-nameINDEXcreator-id. index-name

list-options-spec:

Read syntax diagramSkip visual syntax diagramBACKOUTNOBACKOUTYES1TORBAX'byte-string'VERIFYSETYESVERIFYSETNOENFORCEYESENFORCENOSCOPEUPDATEDSCOPEALLTOLOGPOINTX'byte-string'VERIFYSETYESVERIFYSETNOENFORCEYESENFORCENOSCOPEUPDATEDSCOPEALLnon-LOGONLY-options-specLOGONLY
Notes:
  • 1 If you specify BACKOUT YES, any options in the non-LOGONLY-options-spec are ignored.

non-LOGONLY-options-spec:

Read syntax diagramSkip visual syntax diagram REUSE CURRENTCOPYONLY1 PARALLEL( num-objects)TAPEUNITS(num-tape-units)RESTOREBEFOREX'byte-string'FROMDUMP1DUMPCLASS( dcl)FLASHCOPY_PPRCPNOPMNOPMPREFPMREQ ALTERNATE_CP( copy-pool)1
Notes:
  • 1 CURRENTCOPYONLY, FROMDUMP, and ALTERNATE_CP are not allowed with recover-from-multi-spec or recover-from-spec.

recover-options-spec:

Read syntax diagramSkip visual syntax diagram object dsnum-specTOCOPYdata-setimage-copy-spectocopy-options-specTOLASTCOPYtocopy-options-specTOLASTFULLCOPYtocopy-options-specERRORRANGE

Start of changerecover-from-multi-specEnd of change

Read syntax diagramSkip visual syntax diagramTABLESPACEdatabase-name.table-space-namedsnum-specFROMdatabase-name.table-space-namedsnum-specINDEXSPACEdatabase-name.index-space-namedsnum-specFROMdatabase-name.index-space-namedsnum-specINDEXcreator-id.index-namedsnum-specFROMcreator-id.index-namedsnum-specVERIFYSETYESVERIFYSETNOENFORCEYESENFORCENOTORBAX' byte-string'TOLOGPOINTX' byte-string'non-LOGONLY-options-specLOGONLY

Start of changerecover-from-specEnd of change

Read syntax diagramSkip visual syntax diagramTABLESPACEdatabase-name.table-space-namedsnum-specFROMdatabase-name.table-space-namedsnum-specINDEXSPACEdatabase-name.index-space-namedsnum-specFROMdatabase-name.index-space-namedsnum-specINDEXcreator-id.index-namedsnum-specFROMcreator-id.index-namedsnum-specTOCOPYdata-setimage-copy-spectocopy-options-specTOLASTCOPYtocopy-options-specTOLASTFULLCOPYtocopy-options-spec

Start of changedsnum-specEnd of change

Read syntax diagramSkip visual syntax diagramDSNUMALLDSNUMinteger1
Notes:
  • 1 DSNUM integer is not valid for nonpartitioned indexes unless the data set that is specified for TOCOPY is a FlashCopy® image copy.

tocopy-options-spec

Read syntax diagramSkip visual syntax diagram REUSE CURRENTCOPYONLY ENFORCEYESENFORCENONOSYSCOPYINLCOPYFCCOPYFLASHCOPY_PPRCPNOPMNOPMPREFPMREQ

image-copy-spec:

Read syntax diagramSkip visual syntax diagramTOVOLUMECATALOGvol-serTOSEQNOinteger

Option descriptions

You can specify a list of objects by repeating the TABLESPACE, INDEX, or INDEXSPACE keywords. If you use a list of objects, the valid keywords are: DSNUM, TORBA, TOLOGPOINT, LOGONLY, PARALLEL, and either LOCALSITE or RECOVERYSITE.

The options TOCOPY, TOLASTCOPY, TOLASTFULLCOPY, TORBA and TOLOGPOINT are all referred to as point-in-time recovery options.

LIST listdef-name
Specifies the name of a previously defined LISTDEF list name. The utility allows one LIST keyword for each control statement of RECOVER. The list can contain a mixture of table spaces and index spaces. RECOVER is invoked once for the entire list.

This utility does not support lists that specify more than 32,000 objects. Partitions of table spaces or index spaces that are included by the PARTLEVEL keyword count as separate objects.

This utility only processes clone data if the CLONE keyword is specified. The use of CLONED YES on the LISTDEF statement is not sufficient.

The partitions or partition ranges can be specified in a list.

TABLESPACE database-name.table-space-name
Specifies the table space (and optionally, the database to which it belongs) that is to be recovered.
You can specify a list of table spaces by repeating the TABLESPACE keyword. You can recover an individual catalog or directory table space in a list with its IBM-defined indexes.
database-name
Is the name of the database to which the table space belongs.

The default value is DSNDB04.

table-space-name
Is the name of the table space that is to be recovered.
INDEXSPACE database-name.index-space-name
Specifies the index space that is to be recovered.
database-name
Specifies the name of the database to which the index space belongs.

The default value is DSNDB04.

index-space-name
Specifies the name of the index space that is to be recovered.
INDEX creator-id.index-name
Specifies the index in the index space that is to be recovered. The RECOVER utility can recover only indexes that were defined with the COPY YES attribute and subsequently copied.
creator-id
Optionally specifies the creator of the index.

The default value is the user identifier for the utility.

index-name
Specifies the name of the index in the index space that is to be recovered. Enclose the index name in quotation marks if the name contains a blank.
DSNUM
Identifies a partition within a partitioned table space or a partitioned index, or identifies a data set within a nonpartitioned table space that is to be recovered. Alternatively, the option can recover the entire table space or index space.

Start of changeYou cannot specify a logical partition of a nonpartitioned index. You cannot specify a single data set of a nonpartitioned index unless the data set that is specified for TOCOPY is a FlashCopy image copy. However, to ensure consistency, all data sets of a nonpartitioned index should be recovered to the same point in time. End of change

ALL
Specifies that the entire table space or index space is to be recovered.
integer
Specifies the number of the partition or data set that is to be recovered. The maximum value is 4096.
For a partitioned table space or index space:
The integer is its physical partition number.
For a nonpartitioned table space:

Find the integer at the end of the data set name. The data set name has the following format:

catname.DSNDBx.dbname.tsname.y000z.Annn
catname
Is the VSAM catalog name or alias.
x
Is C or D.
dbname
Is the database name.
tsname
Is the table space name.
y
Is I or J.
z
Is 1 or 2.
nnn
Is the data set integer.
Start of changeFROMEnd of change
Start of changeIndicates a redirected recovery. Use the following format:
target-object FROM source-object
target-object
The target object. This object must already be defined. Identify this object by using the TABLESPACE, INDEXSPACE, or INDEX options as indicated in the syntax diagram.
source-object
The source object. Identify this object by using the format indicated in the syntax diagram.

Source and target objects must reside in the same Db2 subsystem or data sharing group. Source and target objects can reside in different databases. Source and target objects must be one of the following types:

  • Universal table space (UTS)
  • Index space or index over a UTS
  • XML UTS with a base table that resides in a UTS
  • Auxiliary index space or index over an XML UTS with a base table that resides in a UTS
  • LOB table space with a base table that resides in a UTS
  • Auxiliary index space or index over a LOB table space with a base table that resides in a UTS
Restriction: Catalog objects, directory objects, objects with clone relationships, and hash-organized table spaces are not supported as source or target objects.

The current characteristics and attributes of the source and target objects, such as page size, data set size, and table definitions, must be the same.

Redirected recovery has the following restrictions on specifying the same object multiple times:

  • A source object cannot also be a target object, even in a different object pair (or FROM specification). This restriction applies even if the partitions and pieces do not overlap.
  • An object cannot be listed more than once as a target object.
  • An object cannot be listed more than once as a source object.

When redirected recovery of an entire nonpartitioned index (NPI) is needed from a specific (source) FlashCopy image copy, do not use TOCOPY with a list of pieces, as this specification is not allowed. Instead, request a space-level redirected recovery with DSNUM ALL (the default) and specify TOLOPOINT with the RBA or LRSN value from the SYSIBM.SYSCOPY.PIT_RBA column. For FlashCopy image copies with consistency, this RBA or LRSN is the point of consistency. For FlashCopy image copies without consistency, this RBA or LRSN is the point after creation of the FlashCopy image copies.

Related information:
End of change
PAGE page-number
Start of changeSpecifies a particular page that is to be recovered. You cannot specify this option if you are recovering from a concurrent copy, FlashCopy image copy or system-level backup.
page-number is the number of the page, in either decimal or hexadecimal notation. For example, both 999 and X'3E7' represent the same page. PAGE is invalid with the LIST specification.
CONTINUE
Specifies that the recovery process is to continue. Use this option only if an error causes RECOVER to terminate during reconstruction of a page. In this case, the page is marked as broken. After you repair the page, you can use the CONTINUE option to recover the page, starting from the point of failure in the recovery log.

Contact IBM Support before you run the RECOVER utility with the PAGE CONTINUE keywords.

End of change
TORBA X'byte-string'
Specifies, in a non-data-sharing environment, a point on the log to which RECOVER is to recover. Specify an RBA value. The recovery process ends with the last log record whose relative byte address (RBA) is not greater than X'byte-string'. If X'byte-string' is the RBA of the first byte of a log record, that record is included in the recovery.

The RBA is a string of up to 20 hexadecimal characters, which represent the 6-byte RBA format or the extended 10-byte RBA format. Values are padded on the left with zeros if needed. Any 6-byte values are immediately converted to 10-byte format. All further RECOVER processing uses the 10-byte format.

In a data sharing environment, use TORBA only when you want to recover to a point before the originating member joined the data sharing group. If you specify an RBA after this point, the recovery fails.

For a NOT LOGGED table space, the value must be a recoverable point.

Uncommitted work by units of recovery that are active at the specified RBA are backed out by RECOVER so that each object is left in a consistent state.

TOLOGPOINT X'byte-string'
Specifies a point on the log to which RECOVER is to recover. Specify either an RBA or an LRSN value.

The RBA or LRSN is a string of 12 or 20 hexadecimal characters, which represent the 6-byte RBA format or the extended 10-byte RBA format. In a data-sharing environment, a 6-byte LRSN value must be greater than X'00FFFFFFFFFF' and a 10-byte value must be greater than X'0000FFFFFFFFFFFFFFFF'.

For a NOT LOGGED table space, the value must be a recoverable point.

Uncommitted work by units of recovery that are active at the specified LRSN or RBA will be backed out by RECOVER, leaving each object in a consistent state.

REUSE
Specifies that RECOVER is to logically reset and reuse Db2-managed data sets without deleting and redefining them. If you do not specify REUSE, Db2 deletes and redefines Db2-managed data sets to reset them.

If you are recovering an object because of a media failure, do not specify REUSE.

If a data set has multiple extents, the extents are not released if you use the REUSE parameter.

CURRENTCOPYONLY
Specifies that RECOVER is to improve the performance of restoring concurrent copies (copies that were made by the COPY utility with the CONCURRENT option) by using only the most recent primary copy for each object in the list.

When you specify CURRENTCOPYONLY for a concurrent copy, RECOVER builds a DFSMSdss RESTORE command for each group of objects that is associated with a concurrent copy data set name. If the RESTORE fails, RECOVER does not automatically use the next most recent copy or the backup copy, and the object fails. If you specify DSNUM ALL with CURRENTCOPYONLY and one partition fails during the restore process, the entire utility job on that object fails.

If you specify CURRENTCOPYONLY and the most recent primary copy of the object to be recovered is not a concurrent copy, Db2 ignores this keyword.

For objects in the recovery list whose recovery base is a system-backup, the default is CURRENTCOPYONLY.

PARALLEL

Specifies the maximum number of objects in the list that are to be restored in parallel from image copies on disk or tape. RECOVER attempts to retain tape mounts for tapes that contain stacked image copies when the PARALLEL keyword is specified. In addition, to maximize performance, RECOVER determines the order in which objects are to be restored. PARALLEL also specifies the maximum number of objects in the list that are to be restored in parallel from system-level backups that have been dumped to tape. The processing may be limited by DFSMShsm.

Start of changeIf you specify TAPEUNITS with PARALLEL, you control the number of tape drives that are dynamically allocated for the recovery function. The total number of tape drives that are allocated for the RECOVER job is the number of dynamically allocated tape drives, which is determined as follows: End of change

  • The specified value for TAPEUNITS.
  • The value that is determined by the RECOVER utility if you omit the TAPEUNITS keyword. The number of tape drives that RECOVER attempts to allocate is determined by the object in the list that requires the most tape drives.

Start of changeIf you omit PARALLEL, one object is recovered at a time.End of change

If you specify PARALLEL, you cannot specify TOCOPY, TOLASTCOPY, or TOLASTFULLCOPY.

(num-objects)
Specifies the number of objects in the list that are to be processed in parallel. If storage constraints are encountered, you can adjust this value to a smaller value.

If you specify 0 or do not specify TAPEUNITS keyword, RECOVER determines the optimal number of objects to process in parallel.

TAPEUNITS
Specifies the number of tape drives that the utility should dynamically allocate for the list of objects that are to be processed in parallel. If you omit this keyword, the utility determines the number of tape drives to allocate for the recovery function.

The TAPEUNITS option does not apply to recovery from system-level backups. In this case, DFSMShsm determines the number of tape drives that are used for the recovery.

(num-tape-units)
Start of changeSpecifies the number of tape drives to allocate. If TAPEUNITS is not specified, or TAPEUNITS(0) is specified, RECOVER uses the minimum number of tape units needed to avoid monopolizing tape resources. Specify a TAPEUNITS value that is the maximum RECOVER can consume. RECOVER TAPEUNITS has a max value of 32767. End of change
RESTOREBEFORE X'byte-string'
Specifies that RECOVER is to search for an image copy, concurrent copy, or system-level backup (if yes has been specified for the SYSTEM_LEVEL_BACKUPS subsystem parameter) with an RBA or LRSN value earlier than the specified X'byte-string' value to use in the RESTORE phase.

The RBA or LRSN is a string of 12 or 20 hexadecimal characters, which represent the 6-byte RBA format or the extended 10-byte RBA format. Any 10-byte values are immediately converted to 6-byte format. All further RECOVER processing is performed with the 6-byte format.In a data-sharing environment, a 6-byte LRSN value must be greater than X'00FFFFFFFFFF' and a 10-byte value must be greater than X'0000FFFFFFFFFFFFFFFF'.

To avoid specific image copies, concurrent copies, or system-level backups with matching or more recent RBA or LRSN values in START_RBA, the RECOVER utility applies the log records and restores the object to its current state or the specified TORBA or TOLOGPOINT value. The RESTOREBEFORE value is compared with the RBA or LRSN value in the START_RBA column in the SYSIBM.SYSCOPY record for those copies. For system-level backups, the RESTOREBEFORE value is compared with the data complete LRSN.

If you specify a TORBA or TOLOGPOINT value with the RESTOREBEFORE option, the RBA or LRSN value for RESTOREBEFORE must be lower than the specified TORBA OR TOLOGPOINT value. If you specify RESTOREBEFORE, you cannot specify TOCOPY, TOLASTCOPY, or TOLASTFULLCOPY.

FROMDUMP
Specifies that only dumps of the database copy pool are used for the restore of the data sets.
DUMPCLASS (dcl)
Indicates the DFSMShsm dump class to use to restore the data sets.
The FROMDUMP and DUMPCLASS options that you specify for the RECOVER utility override the RESTORE/RECOVER and DUMP CLASS NAME installation options that you specify on installation panel DSNTIP6.
Start of changeFLASHCOPY_PPRCPEnd of change
Start of changeSpecifies the behavior for DFSMShsm or DFSMSdss FlashCopy requests when both of the following conditions are true:
  • The Db2 production volumes are primary volumes in a Metro Mirror (Peer-to-Peer Remote Copy or PPRC) relationship.
  • The recovery base is a system-level backup or FlashCopy image copy.

If the FLASHCOPY_PPRCP option is not specified, the value of the FLASHCOPY_PPRC subsystem parameter is used as the default.

NO
FlashCopy is not allowed to move data from the system-level backup or FlashCopy image copy to the Db2 production volumes. The primary volumes in PPRC pairs are not allowed to become FlashCopy targets.
PMNO
PMNO means Preserve Mirror No. PMNO specifies the following behavior:
  • The Db2 production volumes can be FlashCopy target volumes.
  • PPRC pairs are allowed to go into duplex pending status when the FlashCopy image copy or any data sets from the system-level backup are restored.
PMPREF
PMPREF means Preserve Mirror Preferred. PMPREF specifies the following behavior:
  • The Db2 production volumes can be FlashCopy target volumes.
  • The preferred behavior is that the volume pairs not go into duplex pending status when the FlashCopy image copy or any data sets from the system-level backup are restored.
PMREQ
PMREQ means Preserve Mirror Required. PMREQ specifies the following behavior:
  • The Db2 production volumes can be FlashCopy target volumes.
  • The mirror must be preserved, and the volume pairs must not go into a duplex pending status when the FlashCopy image copy or any data sets from the system-level backup are restored.
End of change
Start of changeALTERNATE_CPEnd of change
Start of changeIndicates which system-level backups RECOVER can use. RECOVER is to consider only those system-level backups that are associated with the specified copy pool.

If the ALTERNATE_CP option is omitted from the utility control statement, all system-level backups are candidates for a recovery base. RECOVER uses the most recent system-level backup before the recovery point.

(copy-pool)
A string value to be used for the copy pool name. This value can be up to 14 characters. RECOVER uses the following copy pool names:
  • DSN$copy-pool$DB for the database copy pool
  • DSN$copy-pool$LG for the log copy pool
End of change
LOGONLY
Specifies that the target objects are to be recovered from their existing data sets by applying only log records to the data sets. Db2 applies all log records that were written after a point that is recorded in the data set itself.

To recover an index space by using RECOVER LOGONLY, you must define the index space with the COPY YES attribute.

Use the LOGONLY option when the data sets of the target objects have already been restored to a point of consistency by another process offline, such as DFSMSdss concurrent copy.

LOGONLY is not allowed on a table space or index space with the NOT LOGGED attribute.

TOCOPY data-set
Specifies the particular image copy data set that Db2 is to use as a source for recovery.

data-set is the name of the data set.

If the data set is a full image copy, it is the only data set that is used in the recovery. If it is an incremental image copy, RECOVER also uses the previous full image copy and any intervening incremental image copies.

If you specify the data set as the local backup copy, Db2 first tries to allocate the local primary copy. If the local primary copy is unavailable, Db2 uses the local backup copy.

If you use TOCOPY or TORBA to recover a single data set of a nonpartitioned table space, Db2 issues message DSNU520I to warn that the table space can become inconsistent following the RECOVER job. This point-in-time recovery can cause compressed data to exist without a dictionary or can even overwrite the data set that contains the current dictionary.

If you use TOCOPY with a particular partition or data set (identified with DSNUM), the image copy must be for the same partition or data set, or for the whole table space or index space. If you use TOCOPY with DSNUM ALL, the image copy must be for DSNUM ALL. You cannot specify TOCOPY with a LIST specification. If the image copy is a Flash Copy image copy data set, and the object is partitioned, you must specify the number of the partition that is to be recovered on the DSNUM parameter.

Start of changeIf the image copy data set is a z/OS® generation data set, supply a fully qualified data set name, including the absolute generation and version number. If the NOSYSCOPY option is specified, you can specify a generation data set with a relative generation number. End of change

If the image copy data set is not a generation data set and more than one image copy data set with the same data set name exists, use one of the following options to identify the data set exactly:

Start of changeNOSYSCOPYEnd of change
Start of changeSpecifies that the full image copy data set is not registered in the SYSIBM.SYSCOPY catalog table. RECOVER will not verify the image copy.

You can specify a generation data set with a relative generation number. For example, you can specify 'DSNC000.DBPAY.TSPAY.FULL(0)'.

Restriction: Concurrent image copies are not supported.
INLCOPY
The specified data set is an inline image copy that was created by a REORG or LOAD REPLACE job; therefore, the data set might have duplicated and out-of-order pages.
FCCOPY
The specified data set is a FlashCopy image copy that was created by a COPY, REORG TABLESPACE, REORG INDEX, LOAD, or REBUILD INDEX job with the FLASHCOPY YES or CONSISTENT options.
End of change
TOVOLUME
Identifies the image copy data set.
CATALOG
Indicates that the data set is cataloged. Use this option only for an image copy that was created as a cataloged data set. (Its volume serial is not recorded in SYSIBM.SYSCOPY.)

RECOVER refers to the SYSIBM.SYSCOPY catalog table during execution. If you use TOVOLUME CATALOG, the data set must be cataloged. If you remove the data set from the catalog after creating it, you must catalog the data set again to make it consistent with the record for this copy that appears in SYSIBM.SYSCOPY.

vol-ser
Identifies the data set by an alphanumeric volume serial identifier of its first volume. Use this option only for an image copy that was created as a noncataloged data set. Specify the first vol-ser in the SYSCOPY record to locate a data set that is stored on multiple tape volumes.
TOSEQNO integer
Identifies the image copy data set by its file sequence number. integer is the file sequence number.
TOLASTCOPY
Specifies that RECOVER is to restore the object to the last image copy that was taken. If the last image copy is a full image copy, it is restored to the object. If the last image copy is an incremental image copy, the most recent full copy along with any incremental copies are restored to the object.
If the image copy is a Flash Copy image copy data set, and the object is partitioned, you must specify the number of the partition that is to be recovered on the DSNUM parameter.
TOLASTFULLCOPY
Specifies that the RECOVER utility is to restore the object to the last full image copy that was taken. Any incremental image copies that were taken after the full image copy are not restored to the object.
If the image copy is a Flash Copy image copy data set, and the object is partitioned, you must specify the number of the partition that is to be recovered on the DSNUM parameter.
ERROR RANGE
Start of changeSpecifies that all pages within the range of reported I/O errors are to be recovered. Recovering an error range is useful when the range is small, relative to the object that contains it; otherwise, recovering the entire object is preferred. You cannot specify this option if you are recovering from a concurrent copy, FlashCopy image copy or system-level backup.

In some situations, recovery using the ERROR RANGE option is not possible, such as when a sufficient quantity of alternate tracks cannot be obtained for all bad records within the error range. You can use the IBM Device Support Facility, ICKDSF service utility to determine whether this situation exists. In such a situation, redefine the error data set at a different location on the volume or on a different volume, and then run the RECOVER utility without the ERROR RANGE option.

You cannot specify ERROR RANGE with a LIST specification.

End of change
VERIFYSET
Specifies whether RECOVER verifies that all related objects that are required for a point-in-time recovery are included in the RECOVER statement.
YES
The recovery set is verified. VERIFYSET YES is the default.
NO
The recovery set is not verified. By specifying VERIFYSET NO, you can break up a point-in-time recovery into multiple jobs or avoid recovering objects that have changed since the selected recovery point.

VERIFYSET applies to point-in-time recoveries of base objects and the following related objects:

  • LOB objects
  • XML objects
  • History objects
  • Archive objects

Start of changeFor redirected recovery, VERIFYSET applies to the target objects.End of change

The VERIFYSET option does not apply to point-in-time recoveries of catalog and directory objects. VERIFYSET NO behavior is always in effect for point-in-time recoveries of catalog and directory objects.

ENFORCE
Specifies whether the CHKP and ACHKP pending states are set for a point-in-time recovery when only a subset of the related objects (BASE, LOB, XML, and RI) are recovered to a point in time.
YES
CHKP and ACHKP are set when these conditions occur.

For catalog and directory objects, ENFORCE YES is the default and cannot be overridden.

NO
CHKP and ACHKP are not set.

Start of changeFor redirected recovery, ENFORCE applies to the target objects.End of change

Start of changeSCOPEEnd of change
Start of changeIndicates which objects in the specified LISTDEF list are to be recovered. The SCOPE option applies only when the TORBA option or the TOLOGPOINT option is specified.
UPDATED
Indicates that only those objects that have changed since the specified recovery point are recovered. Objects in the list that have not changed since the recovery point are not processed by the RECOVER utility. The following objects are exceptions:
  • Indexes in information COPY-pending status
  • Table spaces in COPY-pending status
  • Any objects in RECOVER-pending status
Those objects are recovered even if they have not changed since the specified recovery point.

The SCOPE UPDATED option can potentially improve recovery time, because RECOVER does not waste time processing objects that have not changed and therefore do not need to be recovered.

If you run RECOVER SCOPE UPDATED at the table-space level and any partition has changed since the recovery point, the entire table space is recovered.

SCOPE UPDATED is the default value.

ALL
All objects in the list are recovered.

For example, if an object has not been updated, but the underlying page set has an I/O error, you can specify SCOPE ALL so that the object is recovered.

End of change
CLONE
Indicates that RECOVER is to recover only clone table data in the specified table spaces, index spaces or indexes that contain indexes on clone tables. This utility will only process clone data if the CLONE keyword is specified. The use of CLONED YES on the LISTDEF statement is not sufficient.
LOCALSITE
Specifies that RECOVER is to use image copies from the local site. If you specify neither LOCALSITE or RECOVERYSITE, RECOVER uses image copies from the current site of invocation. (The current site is identified on the installation panel DSNTIPO under SITE TYPE and in the macro DSN6SPRM under SITETYP.)
RECOVERYSITE
Specifies that RECOVER is to use image copies from the recovery site. If you specify neither LOCALSITE or RECOVERYSITE, RECOVER uses image copies from the current site of invocation. (The current site is identified on the installation panel DSNTIPO under SITE TYPE and in the macro DSN6SPRM under SITETYP.)
LOGRANGES YES
Specifies that RECOVER should use SYSLGRNX information for the LOGAPPLY phase. This option is the default.
LOGRANGES NO
Specifies that RECOVER should not use SYSLGRNX information for the LOGAPPLY phase. Use this option only under the direction of IBM Support.

This option can cause RECOVER to run much longer. In a data sharing environment this option can result in the merging of all logs from all members that were created since the last image copy.

This option can also cause RECOVER to apply logs that should not be applied. For example, assume that you take an image copy of a table space and then run REORG LOG YES on the same table space. Assume also that the REORG utility abends and you then issue the TERM UTILITY command for the REORG job. The SYSLGRNX records that are associated with the REORG job are deleted, so a RECOVER job with the LOGRANGES YES option (the default) skips the log records from the REORG job. However, if you run RECOVER LOGRANGES NO, the utility applies these log records.

BACKOUT
Specifies whether a log-only backout is to be used to recover objects to a prior point in time. A log-only backout might decrease the amount of time that an object is unavailable during a point-in-time recovery if the specified recovery point is relatively recent.
NO
Specifies that backout processing is not to be used.

BACKOUT NO is the default behavior.

YES
Specifies that RECOVER is to use the log to back out changes that were made since the recovery point. (The recovery point is specified by the TOLOGPOINT or TORBA options.) The changes are backed out from the current state of the object. No image copy is restored. Any uncommitted work at the specified recovery point is backed out so that the objects are transactionally consistent.

If you specify BACKOUT YES, the recovery point must be within the most recent Db2 system checkpoints that are recorded in the BSDS for each member. Otherwise, the recovery cannot proceed and returns an error.

If you specify the BACKOUT keyword without YES or NO, YES is the default. (If you do not specify the BACKOUT keyword, BACKOUT NO is the default.)

Related information: