IBM Support

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 11
Date of change: September 2016
Topics: Multiple
Change description: The following PDF details additional documentation changes related to APAR PI63601:
CKZ_320_Sept2016_P4.pdfCKZ_320_Sept2016_P4.pdf


Update 10
Date of change: September 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI63601:
CKZ_320_Sept2016_P3.pdfCKZ_320_Sept2016_P3.pdf


Update 9
Date of change: September 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI69034:
CKZ_320_Sept2016_P2.pdfCKZ_320_Sept2016_P2.pdf


Update 8
Date of change: September 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI63601, adding the ALTER-FOR-XML-LOB-COLUMNS keyword, which can be used for DDL processing to avoid column mismatches when the source table space has XML or LOB columns and has been altered since the XML or LOB columns were defined.
CKZ_320_September.pdfCKZ_320_September.pdf



Update 7
Date of change: September 2016
Topics: Multiple
Change description: The following topics were added or updated as part of APAR PI47359.
  • Topic: "Using the log apply process to make consistent copies of table spaces and index spaces"
  • Topic: "Messages"

Topic 1: "Using the log apply process to make consistent copies of table spaces and index spaces"
Update the restrictions as follows:
Restrictions
  • Logs cannot be applied for LOBs, XML spaces, and index spaces.
  • Log apply processes that require additional data sets or additional volumes are not supported.
  • DB2 Cloning Tool manages extent size during log apply processing, and does not verify the value of the subsystem parameter MGEXTSZ, which controls whether secondary extent allocations for DB2-managed data sets are to be sized according to a sliding scale.
  • Extent size and allocation for user-defined table and index spaces is controlled by the size that is specified when the data set is allocated. During the log apply process, extents are allocated by VSAM processing.

Topic 2: "Messages"
Add the following messages:
    CKZ52001E Subtask subtask_number, function_name failed, rc return_code, rsn reason_code, dsn data_set_name
    Explanation: A CONNECT, DISCONNECT, FORMAT, or EXTEND failure occurred while processing a target object. Processing terminates.
    User response: Contact IBM® Software Support.

    CKZ52002E Subtask subtask_number, Extent requested and SECQTY is 0, dsn data_set_name
    Explanation: During the log apply process, the target data set required an additional extent, but the object related to the data set was defined with SECQTY 0. The data set is not extended. Processing terminates.
    User response: Disable log apply processing, or create the target object with SECQTY -1 or n and start the cloning process from the beginning.

    CKZ52003E Subtask subtask_number, Maximum extents reached, dsn data_set_name
    Explanation: During the log apply process, the target data set reached the maximum number of extents. The data set is not extended. Processing terminates.
    User response: Disable log apply processing, or create the target object with SECQTY -1 or n and start the cloning process from the beginning.




Update 6
Date of change: June 2016
Topics: Messages
Change description: For APAR PI47179, the following messages were added to the ISPF interface:

    CKZ456I Operation canceled by user
    Explanation: The CANCEL command was entered to cancel the last operation.
    User response: No action is required.

    CKZ457W The log apply parameters were successfully updated for the selected profiles, except the ones that are displayed on this panel
    Explanation: The log apply parameters were not updated for the profiles that are displayed on this panel. The list of reasons why this might happen are:
    • The profiles do not allow update access.
    • The profiles are not at the current version.
    • An internal error of VSAM data repository routine occurred.
    User response: Check that the profiles that are displayed on this panel can be edited.

    CKZ458E The log apply parameters cannot be updated for any of the selected profiles
    Explanation: The log apply parameters were not updated for the profiles that are displayed on this panel. The list of reasons why this might happen are:
    • The profiles do not allow update access.
    • The profiles are not at the current version.
    • An internal error of VSAM data repository routine occurred.
    User response: Check that the profiles that are displayed on this panel can be edited.

    CKZ459E No profiles are displayed
    Explanation: The primary command that was entered acts on the profiles that are listed on the panel, but no profiles are listed.
    User response: Modify the Profile Like or Creator Like fields to display the desired profiles and retry the command.




Update 5
Date of change: June 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI62208. A new LOG-APPLY summary report was added to summarize the log apply activity for the target job log.
CKZ_320_June.pdfCKZ_320_June.pdf




Update 4
Date of change: May 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI55873. Several new keywords were added to the LOG-APPLY command to allow you to better control the log apply process. In addition, the ISPF interface was updated with several new parameters for the COPY and SET commands.
CKZ_320_May.pdfCKZ_320_May.pdf




Update 3
Date of change: April 2016
Topics: Multiple
Change description: The following PDF details the documentation changes related to APAR PI55447, which adds support for cloning from a system-level backup (SLB) that was created by using a HSM FRBACKUP command:
CKZ_320_April.pdfCKZ_320_April.pdf




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, 2016

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: 29 November 2016