Updates to DB2 Cloning Tool V3.2 User's Guide

Product documentation


Abstract

Updates that apply to the DB2® Cloning Tool for z/OS® V3.2 User's Guide (SC27-6556-00).

Content

The most recent update is listed first.



Update 2
Date of change: December 2015
Topics: Multiple
Change description:
APAR PI50046(+PI52285) eliminates an erroneous message that appears when using the ISPF interface and specifying REBUILD-INDEXES-EXECUTE, and modifies several messages related to DATA-MOVER PGM(SRCIMCPY). The following doc changes were made:

  • Topic: "Set command defaults" in "Using the ISPF interface"
  • Topic: "SET command and keyword definitions" in "DB2 Cloning Tool Table Space Cloning commands"
  • Topic: "Messages"

Topic 1: "Set command defaults" in "Using the ISPF interface"
The following field is modified as follows:

REBUILD-INDEXES-EXECUTE
Specify YES in this field to submit index rebuilds as part of the target job.

Topic 2: "SET command and keyword definitions" in "DB2 Cloning Tool Table Space Cloning commands"
Revise the keyword description as follows:

REBUILD-INDEXES-EXECUTE ( Y | N )
When set to Y, the REBUILD-INDEXES-EXECUTE parameter indicates that index rebuilds are to be submitted as part of the target job.

- Default: N
- Required: No
- Restrictions: None

Topic 3: "Messages"
The following message was changed:

CKZ410I DATA-MOVER PGM was changed to "SRCIMCPY". Therefore the following values of keywords were set: LA-ENABLE(Y), FUZZY-COPY(Y), DATA-MASKING(N), SUBTASK-DATASET-EXTENSIONS(N), USE-RUNTIME REPOSITORY(N)



Update 1
Date of change: November 2015

Topics: Multiple

Change description: For APAR PI49719, the MIGRATED-DSN parameter was added to the COPY-BY-DSN command to allow you to specify how migrated data sets can be handled. The following doc changes were made:

  • Topic: "Planning for subsystem cloning by data set"
  • Topic: "COPY-BY-DS command syntax"
  • Topic: “COPY-BY-DS command and keyword definitions”
  • Topic: "Messages"

Topic 1: "Planning for subsystem cloning by data set"

Update the following bullet point under “Tips for cloning subsystem by data set” paragraph in this topic:

Migrated data sets that are included by matching a RENAME-MASKS (source) mask name will cause the underlying COPY to fail (i.e., ADRDSSU COPY). If you want to clone data sets that have been migrated, you must recall them in a separate step before the cloning. To determine if the data sets that you want to clone have been migrated, first run the COPY-BY-DS command with the SIMULATE option. This option generates a report that lists the data sets to be cloned, along with any data sets that are migrated and therefore ineligible to be cloned. Examine the report and recall any migrated data sets that you want to clone. Any migrated data sets that you do not want to clone can be excluded from the copy by using either the EXCLUDE-SRCNAME-MASKS keyword with a list of the migrated data sets or masks that will match only the migrated data sets, or by using the MIGRATED-DSN(SKIP) keyword to exclude (skip) all migrated data sets.

Topic 2: "COPY-BY-DS command syntax"

Add the following to the "COPY-BY-DS command syntax" topic:

Optional keywords:

MIGRATED-DSN( ERROR | SKIP )

Topic 3: "COPY-BY-DS command and keyword definitions"

The following parameter description was added:

MIGRATED-DSN( ERROR | SKIP )

This option specifies how processing proceeds when a data set that matches a rename mask is not excluded by an entry in the EXCLUDE-SRCNAME-MASKS keyword, and the data set has been migrated. Migrated data sets cannot be copied by COPY-BY-DS. The MIGRATED-DSN keyword provides an alternative to the EXCLUDE-SRCNAME-MASKS keyword to exclude migrated data sets. ERROR causes the command to terminate if there are any migrated data sets that have not been excluded. SKIP causes the command to skip any migrated data sets that have not been excluded.

· Default: ERROR

· Required: No

· Restrictions: None

Topic 4: "Messages"

The following message was changed:

CKZ06530E Migrated data sets (number_of_migrated_data_sets) prevent further processing

Explanation: Migrated data sets cannot be copied. The number of migrated data sets remaining after EXCLUDE processing is provided in the message. A list of the migrated data sets that are not excluded will be displayed.

User response: Either recall the migrated data sets or exclude them from processing. The migrated data sets can be excluded by using the EXCLUDE-SRCNAME-MASKS keyword or the MIGRATED-DSN(SKIP) keyword.

The following message was added:

CKZ06529I Migrated data sets (number_of_migrated_data_sets) will not be copied due to MIGRATED-DSN(SKIP)

Explanation: Migrated data sets will not be copied because MIGRATED-DSN(SKIP) was specified. The number of migrated data sets remaining after EXCLUDE processing is provided in the message.

User response: No action is required.


Publication number

SC27-6556-00

Copyright date

2006, 2015

Original publication date

2015/11/30

Document information


More support for:

DB2 Tools for z/OS
DB2 Cloning Tool

Software version:

3.2.0

Operating system(s):

z/OS

Reference #:

7018361

Modified date:

2016-01-04

Translate my page

Content navigation