OUTCOPY specification

This topic describes the OUTCOPYDDN and RECOVERYDDN specifications that are included in the OUTCOPY specification.

The syntax diagram for the OUTCOPY specification is in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.

You can specify OUTCOPY to make copies of the object or object data set being recovered. For each object or data set that you process, you can request up to four image copies. The default is no copies. If you are recovering to the real Db2 data sets and you request image copies, you can choose which copies, if any, to register in the SYSIBM.SYSCOPY table (or BMCXCOPY table for indexes). However, if you are using the INDEPENDENT OUTSPACE option to recover to non Db2 data sets and you request image copies, you cannot register those copies.

Output copies are produced in the new SYSTEMPAGES YES format when possible.

Example-3-Creating-and-dynamically-allocating-output-copies

EATTR

OUTCOPY-specification-for-IMPORT

When you use the OUTCOPY ONLY facility, you can register the copies if you do not use OBIDXLAT or INCOPY or specify DROPRECOVERY.

If the output copies that you want to make are allocated in the JCL, the OUTCOPYDDN and RECOVERYDDN options specify the DD names for those data sets. If the output copies are dynamically allocated, the OUTCOPYDDN and RECOVERYDDN options refer to the appropriate OUTPUT descriptor names. For more information, see OUTCOPYDDN-specification and RECOVERYDDN-specification. The copies that you want to register are specified by the REGISTER option (INCOPY-specification).

When you create an OUTCOPY and want to force the copy to the cylinder-managed space of an extended address volume (EAV), specify the SPACE keyword.

Important

You can use BMC AMI Recover to automatically size the OUTCOPY files generated by BMC AMI Recover. For more information, see Automatic-sizing-of-output-copies-dynamically-allocated-on-DASD.

How the copies are made depends on whether the object is partitioned or nonpartitioned.

If the object is partitioned, and OUTCOPY BYPART is specified or a specific DSNUM is coded in the object specification, a separate output copy is made for each partition. If you specified OUTCOPY ASCODED and DSNUM ALL with the RECOVER command, a single output copy is made for the object as a whole.
For more information about using OPTIONS OUTCOPY BYPART, see OUTCOPY.
If the object is nonpartitioned and you are recovering multiple data sets by specifying DSNUM ALL, each output copy is for all of the data sets. If you are recovering multiple data sets by specifying each one individually with DSNUM integer, a separate output copy is made for each data set.

OUTCOPY NO

OUTCOPY NO is the default and specifies that no output copies are required.

OUTCOPY YES

OUTCOPY YES specifies that you want image copies or DSN1COPY-type copies of the table space or index (or data set) being recovered. You can make up to four image copies or up to four DSN1COPY-type copies. A DD statement or an OUTPUT command statement must exist for each copy. The ddnames for the copy DD statements are specified by the OUTCOPYDDN and RECOVERYDDN options.

Important

You cannot use the OUTCOPY YES option to produce Instant Snapshot copies.

OUTCOPY ONLY

OUTCOPY ONLY does not affect the table space, index, or data set named in the RECOVER command statement and enables you to build copies without stopping the object for access and without actually reading the space, thereby avoiding DASD contention. You can use this option to build copies for a shadow version of the object, to build a migration image, or to build a registered copy for the named object’s recovery.

Important

If you use OUTCOPY ONLY to register a copy of a space at a point in time that is prior to existing incremental copies, the full copy will have a later TIMESTAMP, but a lower START_RBA than the associated incremental copies. Subsequent use of the IBM MODIFY utility to do an age-based DELETE from SYSCOPY might delete some of the incremental copies without deleting the associated full copy that was created by BMC AMI Recover. The resulting gap in the incremental copies can cause errors in a subsequent recovery that uses the remaining incremental copies. We recommend using the BMC AMI Copy MODIFY command to ensure that a consistent set of recovery resources is maintained in this situation.

The following restrictions apply to the OUTCOPY ONLY option:

You cannot use the OUTCOPY ONLY option with the point-in-time recovery option BACKOUT.
You cannot register an OUTCOPY ONLY copy to the same log point as an existing full copy for the same space or index. OUTCOPY ONLY copies cannot be registered if INCOPY, INLOG, or OBIDXLAT is specified except when DROPRECOVERY is also specified.
You cannot generate a cabinet copy.

You can combine this option with an R+/CHANGE ACCUM product ACCUM command statement involving the same object, but only if the recovery does not include TORBA, TOLOGPOINT, or TOCOPY options. For more information about the ACCUM command statement, see the R+/CHANGE ACCUM documentation.

If copies are registered, they are registered as SHRLEVEL REFERENCE if any one of the following options is specified:

TORBA or TOLOGPOINT to a quiesce point of the table space
TORBA or TOLOGPOINT to a system-wide quiesce point resulting from an ARCHIVE LOG MODE(QUIESCE) command
TOCOPY to a SHRLEVEL REFERENCE incremental copy
TORBA or TOLOGPOINT to a system shut down in a non-data-sharing environment

For all other cases, copies are registered as SHRLEVEL CHANGE.

HIDDEN

You can now use migration-only copies to migrate data to another system. Because these copies are registered differently than normal copies, they do not interfere with the image copies used for recovery.

Use the HIDDEN option to create hidden full copies. These copies are not used for recovery. They are also not used as the basis of an incremental copy.

REGISTER

Use this option to indicate how many, if any, copies you want to register in the SYSIBM.SYSCOPY table. Index copies are registered in the BMCXCOPY table.

You can make and register up to four copies, all with the same log point and the same SYSIBM.SYSCOPY time stamp. The first copy specified by ddname with the OUTCOPYDDN option is registered as the local site primary copy. Similarly, the second copy is registered as the local site backup copy. The third and fourth copies specified with RECOVERYDDN are registered as recovery site primary and backup copies.

Important

You cannot make a backup copy without a primary copy. You can, however, make and register a recovery site copy without making a local site copy.

Value	Description
REGISTER ALL	REGISTER ALL is the default and specifies that you want to register all of the copies that BMC AMI Recover makes for the object in the SYSIBM.SYSCOPY or BMCXCOPY table.
REGISTER NONE	If you specify OUTCOPY YES REGISTER NONE, BMC AMI Recover makes up to four DSN1COPY-type copies.
*REGISTER (DDNameList)*	OUTCOPY YES REGISTER (DDNameList) specifies by ddname those image copies that you want to register in the SYSIBM.SYSCOPY or BMCXCOPY table. The ddname list is optionally enclosed in parentheses and the ddnames must be separated by commas. For each name in the list, there must be a ddname, ddname prefix, or output descriptor specified in OUTCOPYDDN/RECOVERYDDN explicitly or implicitly as the default value. Important The entire OUTCOPYDDN/RECOVERYDDN specification can be omitted and BMC AMI Recover will use the default ddnames. Also note, REGISTER allows the use of any form of the defaults (BMCCPY or BMCCY, BMCCPZ or BMCCZ, and so on) to refer to the default ddnames. Both forms have the same meaning for the REGISTER specification if the corresponding ddname in OUTCOPYDDN/RECOVERYDDN is defaulted. For more information RECOVERYDDN-specification and Copy-data-set-ddname-construction-for-JCL-allocated-data-sets.

RESETRTS

Use RESETRTS to have BMC AMI Recover reset the copy Db2 real-time statistics (RTS) if the copy is registered when you specify OUTCOPY YES or OUTCOPY ONLY.

Warning

You should specify RESETRTS only if the OUTCOPY you are making is a copy that approximately represents the current state of the space. If you specify RESETRTS for a copy corresponding to a different point in time, the RTS might give misleading information about the time of the last copy and the changes made since the copy.

Several examples of how you might use RESETRTS follow:

You might use RESETRTS if you want to make a copy of your system at a specified point in time, such as at midnight. Because making GROUP YES SHRLEVEL REFERENCE copies of the whole system is not usually practical, another approach is to issue an ARCHIVE LOG MODE(QUIESCE) command to get a system-wide point of consistency. You can then use BMC AMI Recover OUTCOPY to make copies of all of the spaces at the point of consistency. While BMC AMI Recover makes copies with OUTCOPY, the system is available for update. Using this method, you get consistent copies of the whole system at the desired point in time with minimal outage. This approach is sometimes referred to as the stealth copy procedure. You should know when you use this procedure that the copy is very close to the current state of the system, and you should use RESETRTS to reset the RTS copy statistics.
You might want to use RTS to trigger utility runs. For example, you might want to make a copy if RTS shows that the last copy was made more than 2 days ago. When you use BMC AMI Recover to recover a space and make an OUTCOPY, BMC AMI Recover resets the RTS copy statistics and updates the RTS timestamp for the last copy. However, if you run BMC AMI Recover OUTCOPY ONLY and do not specify RESETRTS, BMC AMI Recover does not reset RTS because the space was not updated and the output copy does not necessarily match the space. For example, the current date and time might be 10 AM on October 15, but the OUTCOPY might be for 10 PM on October 12.

TAG tagName

Specify TAG to tag copies with a name that can be used for selecting objects for use with the BMC AMI Copy EXPORT command. Only image copies for table spaces are tagged.

Tag names are presented as 1 to 32 characters, followed by a generation number in parentheses. The generation number can be (0), (+1), or (-n). Generation numbers are used as follows:

(0)—uses the highest generation of the tag.
(+1)—uses the highest generation of the tag, plus 1.
(-n)—uses the highest generation of the tag, less n generations.

Spaces and punctuation marks are not allowed in the tag name. Specify the generation number as in the following example: WEEKLY_EXPORT(+1).

SPACE (primary, secondary) allocation unit

Specify SPACE to set the output allocation parameters for the named descriptor in OUTCOPYDDN. This use of SPACE overrides the SPACE specification in the corresponding OUTPUT descriptor. Specify SPACE TRK to allocate the output in tracks. Specify SPACE CYL to allocate the output in cylinders. The default value for this option is CYL. Specify the values in parentheses, as in the following example: SPACE (200,100) CYL. If no SPACE specification is provided, the default is (5,5) CYL.

OUTCOPY specification

On this page