Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Copy for Db2 13.1.

Using the SHRLEVEL option

The SHRLEVEL value you specify might impact space status, the ability to update the space, JCL maintenance, and recovery performance.

Important

There are restrictions on the value you specify for SHRLEVEL when making copies of catalog or directory spaces in the database DSNDB01 or DSNDB06. See Copying-special-case-catalog-and-directory-table-spaces for more information.

The following sections discuss how BMC AMI Copy treats the log range for a space or partition and the advantages and disadvantages of using SHRLEVEL REFERENCE, SHRLEVEL CHANGE, SHRLEVEL ANY, and SHRLEVEL CONCURRENT.

Important

It is not normally necessary to back up the BMC table spaces that contain the BMCHIST table. However, if you choose to back them up, you should use SHRLEVEL CHANGE. The BMC table spaces BMCSYNC and BMCUTIL should be backed up and you should always use SHRLEVEL CHANGE when making these copies. The BMCXCOPY table should be backed up and SHRLEVEL CHANGE or SHRLEVEL CONCURRENT should be specified when copying its indexes. Any SHRLEVEL can be used to backup the table space.

This section contains the following topics:

Related topics

QUIESCE-BEFORE-and-QUIESCE-AFTER

RESETMOD

SHRLEVEL

 

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