Skip to Content
Information
Space announcement We are no longer updating this space, and you cannot comment on this space. The RECOVERY PLUS for IMS component is now documented in BMC AMI Backup and Recovery for IMS.

Creating an Archive Image copy

An Archive Image copy is created as an output of a special Point-in-time (PIT) recovery. To produce an output Archive IC, use the keyword TYPERUN=ARCHIVIC. This process is like the simulate recovery (TYPERUN=SIMULATE), where the output databases are not created.

Related topics

Using-the-Archive-Image-Copy-utility

An Archive IC is a batch image copy. You can create archive image copies for multiple databases in one execution but only one output of Archive Image copy for a database, area, or a partition is allowed at a time. If you request more than one Archive IC then the additional copy request is ignored. The Archive Image copy data set must be uncompressed.

An Archive IC is created only for the source or the main database. All the primary and secondary indexes, and ILDSs for HALDB are generated by the BMC Secondary Index utility or any other Index rebuild utility.

Creating an Archive IC does not cause a database outage because an Archive IC does not require a DBRC authorization or stopping (DBR) the database. However, the process must run with DBRC(Y).

The Archive IC creation process involves the following actions to create the same environment at the time of recovery, as existed when the Archive IC was created:

  • Recording all the database definitions, DBRC definitions, and database dynamic allocation information (AMSPDS).
  • Saving any exit programs, such as the partition selection exit or the randomizer routine used in the DBD.
  • Copying the DBD definitions from the DBDLIBs in case of a IMS non-managed ACB environment.
  • Retrieving the database definitions from the catalog by using the Catalog API DFS3CATQ, generating the DDL for the database definition in case of a managed ACB environment.

You can copy up to 10 PSB members from the //PSBLIB or //IMS concatenation libraries to the resource file and can be restored during the Recovery step. You can also copy any logical DBDs that exist in the requested PSBs that refer to the databases for which the Archive Image copies are requested.

Creating the Archive Image copy.png

Prerequisites for creating an Archive Image copy

The following components must be available before creating an Archive Image copy:

  • All recovery assets, such as image copy, change accumulation, or log data sets required for a successful recovery for the selected PIT time stamp are available and recorded in the RECON.
  • All exit routines, such as a partition selection routine or the randomizer routine used in the DBD or a partition definition are present in the STEPLIB and not in the Linklist, LPA, or any other location.

  • The AMSPDS members are present for all the database data sets, indexes, and ILDSs.

    Warning

    Important

    The Archive IC creation job abends if the AMDPDS member for a DSG or an area is not found, and the corresponding registered data set does not exist. One separate member is required for each DSG or area, index, or ILDS. Multiple IDCAMS definitions in one member are not allowed.

  • Pre-allocate and provide the ARU Directory data set using the DD card //ARUDIR.
  • Include DBDLIB in the JCL in case of a non-managed ACB environment. To copy PSB members, you must provide a PSBLIB either as a separate library with a DD name //PSBLIB or in a //IMS concatenation.
  • IMS Catalog must be available in case of a managed ACB environment.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

RECOVERY PLUS for IMS 5.1