Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

NGT Recover in a data sharing environment

Before you convert from a non-data-sharing environment to a data sharing environment, you should consider the following points:
  • When you are specifying a recovery, you can use TORBA or TOLOGPOINT keywords interchangeably.

    If you are specifying a point in time before the conversion to a data sharing environment, you should specify an RBA value. If you are specifying a point in time after the conversion to a data sharing environment, you should specify an LRSN value.

  • If BSDS passwords are used in a data sharing environment, NGT Recover will work only if all of the passwords for the group are the same.

    OPNDB2ID will work under data sharing only if all Resource Access Control Facility (RACF) IDs for the members of the group are the same. The BSDS authorizations must also be the same.

  • NGT Recover supports recovery in a data sharing environment by using log records written before data sharing was enabled. You can recover table spaces by using image copies that were made before data sharing was enabled.

  • The DB2 RECOVER utility does not support recovery after data sharing is disabled if the recovery requires log records that were created while data sharing was active (For more information, see DB2 for z/OS Data Sharing: Planning and Administration).

    NGT Recover does support such recovery requests. However, if you re-enable data sharing and any table spaces or indexes have not been copied since before data sharing was originally enabled, BMC recommends that you copy them. Failure to do so may render those objects unrecoverable.

Related topic

Was this page helpful? Yes No Submitting... Thank you

Comments