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

Manual


Abstract

Updates that apply to DB2® Cloning Tool Version for z/OS® 3.1 User's Guide (SC19-3493-02)

Content

The most recent update is listed first.




Update 7
Date of change: 9/16/2014
Topics: Multiple
Change description: After applying APAR PM97563, you can implement the Log Apply process when performing table space cloning between DB2 subsystems on different LPARs or on different z/OS sysplexes. Previously, Log Apply was supported only when cloning between subsystems on the same LPAR of a z/OS sysplex. The following topics and messages were added or updated in support of this feature:

- Topic: Chapter 19 "Using LOG-APPLY to make consistent copies of table spaces and index spaces"

- Topic: “COPY command”

- Topic: “SET command”

- Topic: “Table space cloning”

- Topic: “Verify Source TCP/IP Server job settings”

- Topic: “Using image copies to clone table spaces and index spaces”

- Topic: "Messages"

Topic 1: Using LOG-APPLY to make consistent copies of table spaces and index spaces

The following is an updated version of “Chapter 19: Using LOG-APPLY to make consistent copies of table spaces and index spaces”.

Chapter 19. Using LOG-APPLY to make consistent copies of table spaces and index spaces

The LOG-APPLY keyword allows the DB2 log records written to the source objects to be applied to the target objects during target job processing. Any updates made to the source objects in the time between submitting the source job and running the target job are applied to the target objects. LOG-APPLY provides you with a way to consistently clone a set of related DB2 objects from source table spaces to target table spaces without stopping them or making them unavailable for updates. The LOG-APPLY procedure will vary depending on whether you are cloning between or within subsystems on the same LPAR of a z/OS sysplex, or if you are cloning between DB2 subsystems on different LPARs or on different z/OS sysplexes.

  • When cloning across multiple LPARs, LOG-APPLY runs on the target job after the source job has completed. A target TCP/IP server job is required for the source job, and a source TCP/IP server job is required for the target job. The target TCP/IP server job connects to the target DB2 subsystem; the source TCP/IP server job connects to the source DB2 subsystem.
  • When cloning within the same or different LPAR, you can use LOG-APPLY to copy image copy data sets from the source subsystem to the target subsystem. The target TCP/IP server must be specified if copying across LPARs.
  • When cloning within the same LPAR. The LOG-APPLY process runs in the target job, but does not need a Source TCP/IP server job.

You can minimize the amount of time it takes to process DB2 logs by specifying a QUIESCE as part of LOG-APPLY and by running the target job as soon as possible after the source job completes.

Restriction: Logs cannot be applied for LOBs, XML spaces, and index spaces.

System requirements

During customization of DB2 Cloning Tool, you must select the required tasks and steps to create the database and tables needed for LOG-APPLY.

Before you begin

If you use the ISPF interface to build and generate the cloning jobs, you do not need to follow the steps in this procedure; DB2 Cloning Tool includes the required syntax and DDs as part of the generation process. However, you should carefully review the following steps for other requirements and instructions for rebuilding indexes.

Summary of steps

1. Add LOG-APPLY and other keywords and their required parameters to the COPY and SET commands.

2. Add DDs to the source job. Add or set up the optional parameters to the COPY and/or SET commands for rebuilding indexes. For more information, see “Options for rebuilding indexes.”

3. Add DDs to the target job.

4. Submit the following jobs, depending on whether you are cloning within the same or different LPARs:

  • If you are cloning within the same LPAR:

    1. Submit the source job.

    2. Submit the target job.

  • If you are cloning across multiple LPARs:

    1. Submit the source and target TCP/IP server jobs (if not currently running). The source TCP/IP server job is required when cloning across LPARs using LOG APPLY.

    2. Submit the source job.

    3. Submit the target job.


JCL library members CKZ5SRC and CKZ5TRG contain examples of setting up a job using log apply.

Source job changes
Make the following changes to your source job in order to apply DB2 logs:

  • Add the LOG-APPLY subcommand with the LA-ENABLE(Y) and ZPARM-MEMBER keywords' and their parameters to the COPY command; refer to “COPY command syntax” on page 458 for information about the keywords and parameters. If you are cloning across multiple LPARs, you must specify the USE-TCPIP (Y) parameter in the LOG-APPLY keyword.
  • Add the following DDs to the source job:

    //BSDS01 DD DISP=SHR,DSN=hlq.BSDS01

    //BSDS02 DD DISP=SHR,DSN=hlq.BSDS02

    where hlq should be set to the high level qualifier for the source subsystem.

  • Ensure that the source subsystem DB2 SDSNEXIT library is in the STEPLIB for the source job.

Source TCP/IP Server Job (required when using LOG-APPLY across multiple LPARs)

CKZTCPSS, the Source TCP/IP Server job, is required for LOG-APPLY when the source and target DB2 systems are on different LPARs. Configure the JCL for the Source TCP/IP server job and submit it to run on the same LPAR where the source DB2 subsystem is running. The DB2 Cloning Tool target job connects to the Source TCP/IP server job that is running on the same LPAR as the source DB2, and then instructs the server to do the following:

  • Connect to the source DB2 subsystem
  • Determine the logs records that need to be extracted
  • Read those log records, and process them for delivery to the target job
  • Send the log records back to the target job via TCP/IP


CKZTCPSS, the Source TCP/IP Server job, must be started before submitting the target job that will make the spaces accessible on the target DB2 subsystem. When submitted, the target job applies the log records to the copied data sets, bringing the cloned objects to a consistent point in time.

SET Commands for the source TCP/IP server job include:

  • SOURCE-TCPIP-SERVER-JOB – specify the source TCP/IP server job
  • SOURCE-TCPIP-SERVER-PORT – specify the connection port in the source TCP/IP server
  • SOURCE-TCPIP-STC-NAME – specify the TCP/IP address space name in the target job
  • SOURCE-CONNECT-DB2-ON-CLIENT-CONNECT –specify whether or not to disconnect from DB2 on TCP/IP disconnect
  • SOURCE-IP-VERSION6 – Specify N to indicate IP v4

Target job changes
Make the following changes to your target job in order to apply DB2 logs:
  • Ensure that the source subsystem DB2 SDSNEXIT library is in the STEPLIB for the target job.
  • Add the following DDs to the target job. The data set names are required to be as shown.

    //SYSINCKZ DD DISP=SHR,DSN=hlq.LOGAPCTL(membername)

    //SYSOUT DD SYSOUT=*

    //INFOM DD SYSOUT=*

  • Add the following two DDs to the target job for rebuilding indexes:

    //ddnameI DD DISP=SHR,DSN=hlq.indsn(mbr)

    where ddname is the DD specified in the TARGET-JOB-INDEX-REBUILD keyword. You must append an I to ddname. hlq.indsn(mbr) is the data set location and member name of the template you edited.

    //ddnameO DD DISP=OLD,DSN=hlq.outdsn(mbr)

    where ddname is the DD specified in the TARGET-JOB-INDEX-REBUILD keyword. You must append an O to ddname. hlq.outdsn(mbr) is the data set location and member name where you want the utility job to be saved. This DD will contain the output from the generated REBUILD INDEX job.

  • If you are cloning across multiple LPARs, parameters used by the target job for TCP/IP communications to the source TCP/IP server job are passed to the target job from the source job using the SYNCDB2 data set. Include these parameters for the SET command:
    • SOURCE-TCPIP-SERVER-PORT - Connection port in the source TCP/IP server
    • SOURCE-TCPIP-STC-NAME - TCP/IP address space name in the target job
    • SOURCE-TCPIP-SERVER-IP – IP of the source TCP/IP server job

Options for rebuilding indexes

Indexes can be cloned or they can be rebuilt. Several alternative options for creating and submitting the JCL to rebuild indexes are described in this topic.

Note: If the indexes are not included in the LISTDEF or included using the copy command keyword ALWAYS-COPY-INDEXSPACES(Y), they are not refreshed and therefore must be rebuilt using job templates; refer to the steps in Method 1.

Method 1: Using job templates and the JOB-TEMPLATE command to rebuild indexes
For more information about job templates, refer to Chapter 20, “Using job templates”.

  1. Add JOB-TEMPLATE ( inddname1, outddname1) to the COPY command.
  2. Modify the sample templates. Make a copy of either the CKZJOBI (recommended) or CKZJOBR template in the SCKZJCL library and modify it for your site. The template contains the statements used to build the REBUILD INDEX utility job. Instructions for updating the template are contained in the member. Two template pairs can be specified, one using REBUILD INDEX (ALL) TABLESPACE and another using REBUILD INDEXSPACE.
  3. When you submit the source job, the rebuild JCL is created and placed in outddname1 as specified in the JOB-TEMPLATE command.
  4. To rebuild the indexes, submit the JCL in outddname1.

Method 2: Using TARGET-JOB-INDEX-REBUILD-DDN to rebuild indexes

This method can rebuild indexes defined as COPY NO and can be submitted as part of the target job, if desired.

  1. Add TARGET-JOB-INDEX-REBUILD-DDN to the source job.
  2. Modify the sample template:
    a. Make a copy of the CKZJOBI member (required for PGM(SRCIMCPY)) in the SCKZJCL library and modify it for your site. This template contains the statements used to build the REBUILD INDEX utility job. Instructions for updating the template are contained in the member.

    b. Add the following two DDs to the target job for rebuilding indexes:
    //ddnameI DD DISP=SHR,DSN=hlq.indsn(mbr)
    where ddname is the DD specified in the TARGET-JOB-INDEX-REBUILD keyword. You must append an I to ddname. hlq.indsn(mbr) is the data set location and member name of the template you edited.
    //ddnameO DD DISP=OLD,DSN=hlq.outdsn(mbr)
    where ddname is the DD specified in the TARGET-JOB-INDEX-REBUILD keyword. You must append an O to ddname. hlq.outdsn(mbr) is the data set location and member name where you want the utility job to be saved. This DD will contain the output from the generated REBUILD INDEX job.


3. (Optional) If you want the index rebuilds to be submitted as part of target job, specify SET command REBUILD-INDEXES-EXECUTE(Y) in the source job.

4. (Optional) If you want indexes defined as COPY NO to be rebuilt, specify the LOG-APPLY command REBUILD-COPY-NO-INDEXES(Y) in the source job.

5. When the target job is executed, the job to rebuild indexes is generated and placed in the ddnameO output data set specified in the target job. If you did not specify the job to be submitted as part of the target job, submit the job to rebuild indexes.

Topic 2: COPY command

A new optional parameter has been added to the LOG-APPLY keyword of the COPY command section of Chapter 23. DB2 Cloning Tool Subsystem Cloning commands

The following is an updated version of the “In the LOG-APPLY keyword description” section of the COPY command. A restriction for using LOG-APPLY when the source and target DB2 are on the same LPAR has been removed:

LOG-APPLY is required when image copies are used as input to the cloning process; it is used to apply logs to the image copies and bring the cloned objects to the desired consistent point in time. Additional parameters can be used to specify the consistent point of the cloning process.

  • Required: Yes, if PGM (SRCIMCPY) is specified.
  • Restrictions: For cloning using PGM(ADRDSSU) or (EMCAPI), logs cannot be applied for LOBs, XML spaces, and index spaces. For cloning using PGM(SRCIMCPY), logs cannot be applied for XML spaces.

The following is an addition to the list of parameters applicable to the LOG-APPLY keyword list in the COPY command syntax section:

USE-TCPIP(Y)

The following is an addition to the list of parameter definitions applicable to the LOG-APPLY keyword in the COPY command and keyword definitions section:

USE-TCPIP(Y|N) - This parameter specifies whether or not use TCP/IP to communicate with the source DB2 subsystem when cloning between DB2s on two different LPARs This parameter is required for cross LPAR log apply.

  • Default: N
  • Required: No
  • Restrictions: Specify in the SOURCE job
  • Short form: USETCP

Topic 3: SET command

New parameters have been added to the SET command section of Chapter 23. DB2 Cloning Tool Subsystem Cloning commands.

The following is an addition to the list of parameters applicable to the list in the “SET command syntax” section:


[ SOURCE-TCPIP-SERVER-JOB ( Y | N ) ]


[ SOURCE-TCPIP-SERVER-PORT ( port ) ]


[ SOURCE-TCPIP-STC-NAME ( started task name ) ]

[ SOURCE-CONNECT-DB2-ON-CLIENT-CONNECT ( Y | N ) ]


[ SOURCE-IP-VERSION ( n ) ]

The following is an addition to the list of parameter definitions applicable to the list in the “SET command and keyword definitions” section:

SOURCE-TCPIP-SERVER-JOB ( Y | N ) ]
This parameter distinguishes the source TCP/IP server job from the source job and target job.

  • Default: N
  • Required: No
  • Restrictions: Specify in the SOURCE-SERVER job
  • Short form: STCPJOB
  • Jobs: Source, TCP/IP server

SOURCE-TCPIP-SERVER-PORT ( port )
This parameter allows you to specify the connection port that the source TCP/IP server is to use. Use this parameter to override the default and/or PARMLIB specification. Valid values are 1 to 65535.
  • Default: 5099
  • Required: No
  • Restrictions: Specify in the SOURCE or SOURCE-SERVER jobs
  • Short form: STSPORT
  • Jobs: Source, TCP/IP server

SOURCE-TCPIP-SERVER-IP ( ip )
This parameter specifies the connection IP address for the LPAR on which the source TCP/IP server is executing.
  • Default: None
  • Required: No
  • Restrictions: Specify in the SOURCE job
  • Short form: SSIP
  • Jobs: Source, TCP/IP server

SOURCE-TCPIP-STC-NAME ( started task name )
This parameter allows you to specify the name of the source TCP/IP address space that the TCP/IP source server connects to. Specify a valid z/OS started task name.
  • Default: TCPIP
  • Required: No
  • Restrictions: Specify in the SOURCE-SERVER jobs
  • Short form: STSNAME
  • Jobs: TCP/IP server

SOURCE-CONNECT-DB2-ON-CLIENT-CONNECT ( Y | N )

The SOURCE- CONNECT-DB2-ON-CLIENT-CONNECT parameter can be used to allow the source TCP/IP server job to connect to DB2 only when a client connect occurs. When this parameter is set to Y, the source TCP/IP server disconnects from DB2 when the client disconnects. This allows the source TCP/IP server to be run as a started task; the source TCP/IP server job can be started at IPL and left running. If a DB2 connect error occurs when the source job is running the source TCP/IP server job, the source TCP/IP server job ends with a return code of 8, and must be restarted.

  • Default: N
  • Required: No
  • Restrictions: Specify in the SOURCE-SERVER job
  • Short form: SCDOCC
  • Jobs: TCP/IP server

SOURCE-IP-VERSION ( Y | N )
The SOURCE-IP-VERSION parameter specifies the version of TCP/IP used on the source TCP/IP server. N (the default) specifies IPv4. Y specifies IPv6.

  • Default: N
  • Required: No
  • Restrictions: Specify in the SOURCE-SERVER job
  • Short form: SIPV6
  • Jobs: TCP/IP server

Topic 4: Table space cloning

Additional options have been added to the panel displayed in the “Table space cloning” section of Chapter 21: Using the ISPF interface. The new options are as follows:

1 Source and Target DB2 subsystems

2 Source job

3 Target job

4 Report job

5 TCPIP Server job

6 Source TCPIP Server job Required for cross LPAR log apply

Topic 5: Verify Source TCP/IP Server job settings

The following new topic is an addition to the “Table space cloning” section in Chapter 21, “Using the ISPF interface”. This topic follows the “Verify the TCP/IP server job settings” topic.

The Source TCP/IP server job is required only when you are using LOG-APPLY while cloning across multiple LPARs; it facilitates communication between the target job and source DB2 subsystem. The job cards and DDs for the TCP/IP job may have already been specified in the user defaults; verify that the settings are correct.

Topic 6: Chapter 18. Using image copies to clone table spaces and index spaces

Remove the following restriction from the list of restrictions in “Chapter 18. Using image copies to clone table spaces and index spaces”:

· Cloning from image copies can only be done when the source and target DB2 subsystems are on the same LPAR.

The following is an updated version of the “Procedure” section of “Chapter 18. Using image copies to clone table spaces and index spaces”. This updated procedure includes an updated step for cloning across multiple LPARs:

Procedure

1. Make the following source job changes:

  • Add DATAMOVER(PGM(SRCIMCPY) and its required parameters to the COPY command.
  • Add LOG-APPLY and the required parameters for cloning from source image copies to the COPY command.
  • Add DDs to the source job as specified in “Source job changes for cloning from image copies”.
  • Ensure that the source subsystem DB2 SDSNEXIT library is in the STEPLIB for the source job.
  • Add or set up the optional parameters to the COPY and/or SET commands for rebuilding indexes. For more information, see “Options for rebuilding indexes when cloning table spaces and index spaces from image copies.”

2. Submit the following jobs, depending on whether you are cloning within the same or different LPARs:
  • If you are cloning within the same LPAR:

    1. Submit the source job.

    2. Submit the target job.

  • If you are cloning across multiple LPARs:
    1. Submit the target TCP/IP server job (if not currently running). The target TCP/IP server job is required when cloning across LPARs.
    2. Submit the source job.
    3. Submit the target job.

Topic 7: Messages

The following messages were added or changed:

CKZ2029I – Log apply process was unable to connect to the server.

Explanation: The Log apply process failed to connect to the server to output for output.

User Response: Ensure that the DB2 Cloning Server is active.

CKZ53626I Server Source IPv4 is ipaddr
Explanation: This message is informational.
User Response: None.

CKZ53627I Server Source IPv6 is ip6addr
Explanation: This message is informational.
User Response: None.

CKZ53628E SET Error, jjj and kkk are Incompatible.
Explanation: This is a user error. Specify one or the other of these parameters, but not both.

· jjj = the first parameter

· kkk = the second parameter

User Response: Correct the input and resubmit the job.

CKZ53629I SET Command Server IPv4 is ipaddr
Explanation: This message is informational.
User Response: None.

CKZ53630I SET Command Server IPv6 is ip6addr
Explanation: This message is informational.
User Response: None.

CKZ53631E xxx SET Command(s) Found in the yyy TCPIP Job
Explanation: This is a user error. Source server commands cannot be in the target server and vice-versa.

· xxx = the server job the SET command(s) belong to

· yyy = the server job the SET command(s) were found in

User Response: Correct the input and resubmit the job.

CKZ54909E Log Apply Init Call Failed, RC=rrr, RS=sss
Explanation: A severe error occurred when log apply was processing a source server request.

· rrr = return code

· sss = reason code

User Response: Contact Technical Support if unable to resolve this error.

CKZ66901E Subtask nn, ACK Expected from sss, Receive Type ttt
Explanation: An ack was expected from the remote TCP/IP connection for the specified receive type.

· nn = subtask number

· sss = remote DB2 subsystem

· ttt = receive message type

User Response: Contact Technical Support if unable to resolve this error.

CKZ66902E Packet Format Error, ttnn,p1,p2'
Explanation: There is an error in the packet received from the remote DB2 subsystem.

· ttnn = error type and decimal qualifier
tt values include:

o BL block number receive error

o CK TCP/IP packet checksum error

o GM group accessed by minilog not found

o MM space group cannot be found

o RM number of records doesn't match array length

o UN unknown block type received

o UT unexpected type from server

o XB no blocks found

o XG group block should first from server

· p1 = parameter 1

· p2 = parameter 2

User Response: Contact Technical Support if unable to resolve this error.

CKZ66903I ttt, ddd
Explanation: Successfully processed.

· ttt = Explanation

· nnn = number of records in decimal

User Response: None

CKZ67145E TCPIP Server Received Block with a Format Error Processing Log Pages, sss
Explanation: Invalid TCP/IP header received, the connection has been shut down. sss is the reason code.
User Response: Contact Technical Support if unable to resolve this error.





Update 6
Date of change: 8/3/2014
Topics: Multiple
Change description: For APAR PM98340, the OBJECT-MISMATCH-RETURN-CODE command was added to DB2 Cloning Tool Table Space Cloning. The following topics and messages were added or updated in support of this feature:
- Topic: "Object attributes"
- Topic: "COPY command syntax"
- Topic: "COPY command and keyword definitions"
- New topic: "Specifying OBJECT-MISMATCH-RETURN-CODE defaults" in the "Using the ISPF Interface chapter"
- Topic: "Messages"

1. Topic: “Object attributes"

Add the following to the "Object attributes" topic:

If DB2 Cloning Tool Table Space Cloning detects a mismatch, a warning message with a return code of 4 is generated in the output. You can override the return codes that are assigned to specific mismatch types by using the OBJECT-MISMATCH-RETURN-CODE keyword in the COPY command. The return code and the warning message that is issued can be 0 (informational message), 4 (warning message), or 8 (error message).

2. Topic: “COPY command syntax"

Add the following to the "COPY command syntax" topic:

Optional keywords:
[ OBJECT-MISMATCH-RETURN-CODE ( mismatchtype1,returncode1,
. . . mismatchtypen,returncoden ) ]

3. Topic: “COPY command and keyword definitions"

Add the following to the "COPY command and keyword definitions" topic:

OBJECT-MISMATCH-RETURN-CODE( mismatchtype1,returncode1, . . . mismatchtypen,returncoden )

This keyword allows you to change the return code associated with a particular object mismatch. Mismatches are detected after the source and target objects are identified and before the copy starts.

Individual mismatches may be assigned a return code of 0, 4, or 8. If the return code is 0, an informational message is issued and the object is treated as if there is no mismatch. If the return code is 4, warning message is issued. If the return code is 8, an error message is issued and no copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The default return code is 4 if the mismatch return code command is not specified.

mismatchtype must be one of the following:

TS_CCSID
TS_DSSIZE
TS_PARTITIONS
TS_PGSIZE
TS_NTABLES
TS_SEGSIZE
TS_TYPE
TS_ORGANIZATIONTYPE
TS_CLONE
TS_HASHSPACE
TP_COMPRESS
TP_FORMAT
TB_COLCOUNT
TB_EDPROC
TB_HASHKEYCOLUMNS
CL_COLNO
CL_COLTYPE
CL_LENGTH
CL_SCALE
CL_DEFAULT
CL_FLDPROC
CL_SOURCETYPEID
CL_SEQTYPE
CL_CYCLE
CL_CACHE
CL_START
CL_MINVALUE
CL_MAXVALUE
CL_INCREMENT
CL_HASHKEY_COLSEQ
IX_UNIQUERULE
IX_COLCOUNT
IX_PGSIZE
IX_INDEXTYPE
IX_PIECESIZE
IX_NR_PARTS
IX_CLUSTERING
IX_HASH
IX_SPARSE
IX_UNIQUE_COUNT
IX_COLNO
IX_COLSEQ
IX_ORDERING
IP_LIMITKEY

Note: If you specify IX_COLNO, IX_COLSEQ, and IX_ORDERING, you must also specify CHECK-INDEX-KEYS(YES).

returncoden must be 0, 4, or 8.

- Default: If the mismatch return code command is not specified, the default return code is 4.
- Required: No
- Restrictions: None
- Short form: OMMRC

4. New topic: "Specifying OBJECT-MISMATCH-RETURN-CODE defaults" in the "Using the ISPF Interface chapter":

Add the following topic:

Specifying OBJECT-MISMATCH-RETURN-CODE defaults:
In most cases, attributes of the source and target table spaces and index spaces must match for a successful cloning. However, you can override the default return codes for specific object mismatches.

About this task
If a return code is not specified for a mismatch, the default return code of 4 is used. Object mismatches are detected after the source and target objects are identified, and before any copies are started.

Procedure
1. Enter A in the Command line and press Enter. The Select Object Mismatch Type panel is displayed.
2. Use the S line command to select one or more mismatch types from the displayed list of possible mismatch types.
3. When you have finished selecting all the mismatch types, press Enter. The DB2 tablespace OBJECT-MISMATCH-RETURN-CODE Command panel is displayed.
4. The return code for each selected mismatch type defaults to 4. To specify a different return code for a mismatch type, update the code in the RC column next to the mismatch type.


5. Topic: “Messages"

The following messages were added or changed:


CKZ53594I Object mismatch set for mismatch_type , return_code .
Explanation: This message is informational. It displays the object mismatch type and return code that was specified in the COPY command.
User response: No action is required.

CKZ53595E Illegal syntax in OBJECT-MISMATCH-RETURN-CODE command.
Explanation: An invalid parameter was entered in the OBJECT-MISMATCH-RETURN code command.
User response: Specify a valid mismatch code and return code in the command and resubmit the job.

CKZ53596E OBJECT-MISMATCH-RETURN-CODE has one or more duplicates.
Explanation: The same mismatch code was entered more than once in the OBJECT-MISMATCH-RETURN-CODE command. A mismatch code can be specified only once.
User response: Remove the duplicate mismatch code from the command and resubmit the job.


CKZ54762E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier.second_source_object_qualifier = source_attribute_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_decimal_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User response: Correct the object and resubmit the job.

CKZ54762I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_decimal_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User response: No action is required.

CKZ54762W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_decimal_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54763E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_halfword_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_halfword_decimal_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54763I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_halfword_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_halfword_decimal_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54763W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_halfword_decimal_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_halfword_decimal_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54767E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54767I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier.second_source_object_qualifier = source_attribute_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54767W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier = source_attribute_value and target_DB2_ssid.first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54769E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54769I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54769W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54772E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = halfword_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = halfword_target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54772I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = halfword_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = halfword_target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54772W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = halfword_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = halfword_target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54773E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54773I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54773W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54778E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = decimal_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = decimal_target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54778I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = decimal_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = decimal_target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH=RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54778W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. source_value = decimal_source_attribute_value and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. target_value = decimal_target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54782E object_type mismatch, attribute compared_attribute, sourceDB2.first_source_object_qualifier. second_source_object_qualifier = source_attribute_value and targetDB2. first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User response: Correct the object and resubmit the job.

CKZ54782I object_type mismatch, attribute compared_attribute, sourceDB2.first_source_object_qualifier. second_source_object_qualifier = source_attribute_value and targetDB2. first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User response: No action is required.

CKZ54782W object_type mismatch, attribute compared_attribute, sourceDB2.first_source_object_qualifier. second_source_object_qualifier = source_attribute_value and targetDB2. first_target_object_qualifier. second_target_object_qualifier = target_attribute_value
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User response: Correct the object and resubmit the job.

CKZ54783E Data set data_set_name has failed object match checking with a return code of 8 and will not be copied to subsystem target_subsystem_ID
Explanation: The data set that is listed in the message failed object mismatch checking and cannot be copied.
User Response: Correct the object and resubmit the job.

CKZ54786E object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value (in hexadecimal) and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value (in hexadecimal)
Explanation: This message is an error. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifies a return code override of 8 for this attribute. No copies are performed, regardless of the setting for ALLOW-COPY-ON-MISMATCH. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.

CKZ54786I object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value (in hexadecimal) and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value (in hexadecimal)
Explanation: This message is informational. An object attribute does not match between the source and target table space or index space. The OBJECT-MISMATCH-RETURN-CODE command was included and specifiesa return code override of 0 for this attribute. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: No action is required.

CKZ54786W object_type mismatch, attribute object_attribute_compared, source_DB2_ssid.first_source_object_qualifier. second_source_object_qualifier. halfword_source_value = source_attribute_value (in hexadecimal) and target_DB2_ssid. first_target_object_qualifier. second_target_object_qualifier. halfword_target_value = target_attribute_value (in hexadecimal)
Explanation: This message is a warning. An object attribute does not match between the source and target table space or index space. This message is the default message if the OBJECT-MISMATCH-RETURN-CODE command was not specified, or if OBJECT-MISMATCH-RETURN-CODE was specified with a return code of 4. The details of the object, the attribute that was compared, and the source and target values are listed in the message.
User Response: Correct the object and resubmit the job.



Update 5
Date of change: 5/21/2014
Topics: Multiple
Change description: For APAR PI15215, a command was added to remove utility information from SYSUTILX for the target DB2 subsystem. The following topics and messages were added or updated in support of this feature:
- Topic: "DB2UTILXCLEAN"
- Topic: "DB2UTILXCLEAN command syntax"
- Topic: "DB2UTILXCLEANcommand and keyword definitions"
- Topic: "DB2UTILXCLEAN step JCL examples"
- Topic: "Step JCL example to identify objects with UT status"
- Topic: "Cloning a DB2 subsystem"
- Topic: "Parameter files and parameter descriptions"
- Topic: Chapter 9, "Cloning a DB2 subsystem"
- Topic: "DB2UTILXCLEAN command defaults"
- Topic: "Messages"


1. New topics in Chapter 23, "DB2 Cloning Tool Subsystem Cloning commands for DB2UTILXCLEAN"

The attached PDF contains the new topics for the DB2UTILXLEAN command description, syntax, and JCL examples.

CKZ-1261_docchanges_DB2UTILXCLEANcommandreference.pdfCKZ-1261_docchanges_DB2UTILXCLEANcommandreference.pdf

2: Topic: Chapter 9, "Cloning a DB2 subsystem"

The attached PDF contains the changes to Chapter 9, "Cloning a DB2 subsystem". Changes were made throughout to support the new command.

CKZ-1261_docchanges_Chaper9CloningDB2subsystems.pdfCKZ-1261_docchanges_Chaper9CloningDB2subsystems.pdf

3. Topic: "Parameter files and parameter descriptions" in the "Subsystem cloning using the DB2 Cloning Tool stored procedure" chapter

Add the following to the "Parameter files and parameter descriptions" topic under "CPARM parameters for pairs of subsystems or data sharing groups":

CLEAN-SYSUTILX
Specifies whether SYSUTILX is to be cleaned out as part of the cloning. The cleaning out of SYSUTILX is done by using a job with the DB2UTILXCLEAN command. Valid values are YES | Y (generate the DB2UTILXCLEAN job) or NO | N (do not generate the DB2UTILXCLEAN job). If this parameter is not specified, the default is NO (to not clean out SYSUTILX).

4. New topic: DB2UTILXCLEAN command defaults
Add the following topic to the "Setting subsystem cloning defaults" topic in Chapter 21, "Using the ISPF Interface":

DB2UTILXCLEAN command defaults
DB2UTILXCLEAN removes all entries from SYSUTILX. This command should be specified when utilities might be running or registered in SYSUTILX when the source DB2 subsystem is cloned.

The following values can be set on the subsystem cloning DB2UTILXCLEAN command defaults panel. These values are used strictly as defaults for DB2UTILXCLEAN command parameters when you are creating a new subsystem cloning profile. The parameter values can later be edited in the profile.

Clean SYSUTILX
Enter YES in this field if utilities might be running or registered in SYSUTILX when the source DB2 subsystem is cloned. If SYSUTILX is not cleaned out, the source DB2 subsystem can become corrupted when the target DB2 subsystem cleans up the entries in SYSUTILX with a –TERM UTIL command. The DB2UTILXCLEAN command cleans out the target SYSUTILX and its indexes.

If utilities were running or registered in SYSUTILX when the source DB2 subsystem was cloned, target objects might be in UT status after the cloning. These objects can be identified and the UT status can be removed by using the sample REXX exec provided in the CKZDUTCL member of SCKZJCL.

5. Topic: “Messages"

Remove the following messages:

CKZ25110E ERROR ACCESSING LINEAR DATA SET; DDNAME: ddname R15=nnnn ERROR=error FUNCTION=function
LOC=location RBA OF RECORD: rba

CKZ25142I DSNDB01.tsname DDNAME=ddname IS EMPTY

Add the following messages:

CKZ25108E UNABLE TO LOAD PROGRAM: program name
Explanation: The indicated program name was not found. Processing terminates.
User response: Check that the job's //STEPLIB library is correct. If unable to resolve the problem, contact IBM Software Support.

CKZ25201I hh:mm:ss DB2UTILXCLEAN STARTED - PROGRAM REV=rrr | hh:mm:ss DB2UTILXCLEAN COMPLETED; RETURN CODE=nnn
Explanation: This is an informational DB2UTILXCLEAN processing message.
User response: No response is required.

CKZ25201I hh:mm:ss DB2UTILXCLEAN STARTED - PROGRAM REV=rrr | hh:mm:ss DB2UTILXCLEAN COMPLETED; RETURN CODE=nnn
Explanation: This is an informational DB2UTILXCLEAN processing message.
User response: No response is required.

CKZ25203I DDNAME=ddname ALLOCATED FOR DSN=data_set_name
Explanation: The ddname that is listed in the message text was dynamically allocated for the indicated data set.
User response: No response is required.

CKZ25204E DDNAME MISSING: ddname
Explanation: The ddname that is listed in the message text was specified for DB2 Cloning Tool to use, but is missing. Processing terminates.
User response: Either correct the specified ddname, or add the appropriate ddname to the job's JCL.

CKZ25205E ALLOCATION FAILED FOR DSN: data_set_name
Explanation: Dynamic allocation for a data set failed. The associated z/OS messages are displayed. Processing terminates.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25205W DEALLOCATION FAILED FOR DDNAME: ddname
Explanation: Dynamic deallocation for the ddname that is listed in the message failed. The associated z/OS messages are displayed. Processing continues.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25207W ERROR CALLING CKZ01HEX; FUNCTION: function R15=nnnn
Explanation: An error occurred while CKZ01HEX was attempting to print a record. Processing continues.
User response: If unable to determine the reason for the failure, contact IBM Software Support.

CKZ25208E UNABLE TO LOAD PROGRAM: program_name
Explanation: The program name that is listed in the message text was not found. Processing terminates.
User response: Check that the job's //STEPLIB library is correct. If unable to resolve the problem, contact IBM Software Support.

CKZ25209E ERROR ACCESSING JOURNAL FILE; LOC=location
Explanation: A VSAM error occurred accessing a file. Processing terminates.
User response: Refer to the associated CKZVSEnnE error messages. If unable to resolve the problem, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25211E JOURNAL type RECORD NOT FOUND
Explanation: An expected record was not found in the DB2 Cloning Tool journal file. Processing terminates.
User response: Verify that the same value was used for the DB2-NAME keyword that was used with the prior DB2UPDATE command for this DB2 subsystem or data sharing group. If unable to resolve the problem, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25212E JOURNAL type RECORD IS WRONG VERSION
Explanation: The identified journal record does not match the expected format. The record is printed. Processing terminates.
User response: Verify that different releases of DB2 Cloning Tool were not run using the same journal data set. If unable to resolve the problem, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25220E NO DB2 CATALOG NAME
Explanation: A DB2 catalog name was not found in the journal DB2 control record.
User response: Contact IBM Software Support. Have available the listing that contains these messages.

CKZ25230I OPTIONS IN EFFECT FOR THIS EXECUTION: merged options
Explanation: This informational message indicates how DB2UTILXCLEAN will handle the options. The displayed options are derived from the INI file and any overriding specifications in the command input.
User response: No action is required.

CKZ25231E DB2UPDATES WERE ALL SIMULATIONS, SIMULATION MUST BE SPECIFIED
Explanation: All DB2UPDATE runs were simulations, so this run must be a simulation. Processing terminates.
User response: Run with simulation (SIM) specified.

CKZ25251E REQUIRED KEYWORD MISSING: keyword
Explanation: A keyword that is required for processing was omitted. Processing terminates.
User response: Specify the required keyword.

CKZ25253E KEYWORD: keyword MAXIMUM LENGTH: length EXCEEDED
Explanation: The operand entered for a keyword exceeded the maximum length that is allowed for the operand. length is the maximum allowed length for the keyword. Processing terminates.
User response: Correct the length of the keyword's operand.

CKZ25254E KEYWORD HAS MORE THAN 1 OPERAND; ONLY 1 ALLOWED: keyword
Explanation: Multiple operands were detected for a keyword; only one operand is allowed. Processing terminates.
User response: Correct the keyword to use one operand.

CKZ25256E NOTHING SPECIFIED FOR KEYWORD: keyword
Explanation: A keyword was entered without an appropriate operand. Processing terminates.
User response: Specify an appropriate operand for the keyword.

CKZ25258E INVALID VALUE IN KEYWORD: keyword VALUE: value error_text
Explanation: The value in the keyword that is listed in the message is invalid. error_text indicates the problem that was detected with the value. Processing terminates.
User response: Correct the value that is specified in the keyword.

CKZ25301I hh:mm:ss SYSUTILX CLEAN STARTED - PROGRAM REV=rrr | hh:mm:ss SYSUTILX CLEAN COMPLETED; RETURN CODE=return_code
Explanation: This message is a SYSUTILX CLEAN processing informational message.
User response: No action is required.

CKZ25303I DDNAME=ddname ALLOCATED FOR DSN=data_set_name
Explanation: ddname was dynamically allocated for the indicated data set.
User response: No action is required.

CKZ25304E OPEN FAILED FOR DDNAME=ddname
Explanation: Open failed for the ddname that is listed in the message. Processing terminates.
User response: Contact IBM Software Support. Have available the listing that contains this message.

CKZ25305E ALLOCATION FAILED FOR DSN: data_set_name
Explanation: Dynamic allocation for a data set failed. The associated z/OS messages are displayed. Processing terminates.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25305W DEALLOCATION FAILED FOR DDNAME: ddname
Explanation: Dynamic deallocation for a ddname failed. The associated z/OS messages are displayed. Processing continues.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25307W ERROR CALLING CKZ01HEX; FUNCTION: function R15=nnnn
Explanation: An error occurred while CKZ01HEX was attempting to print a record. Processing continues.
User response: If unable to determine the reason for the failure, contact IBM Software Support.

CKZ25308E UNABLE TO LOAD PROGRAM: program_name
Explanation: The indicated program name was not found. Processing terminates.
User response: Check that the job's //STEPLIB library is correct. If unable to resolve the problem, contact IBM Software Support.

CKZ25321E DDNAME=ddname IS ALREADY ALLOCATED
Explanation: The ddname is already allocated and it must not be.
User response: Ensure that the ddname is not allocated in the JCL. If it is not in the JCL, contact IBM Software Support. Have available the listing that contains this message.

CKZ25322I SPACE=spacename DSN=data_set_name HAS BEEN CLEANED
Explanation: All data was removed from the data set.
User response: No action is required.

CKZ25323I DATA FROM DDNAME=ddname IS BEING USED
Explanation: Data is being used from the file allocated to ddname.
User response: No action is required.

CKZ25324I SPACE=spacename HAS attribute
Explanation: The identified table or index space has the indicated attribute.
User response: No action is required.

CKZ25331E DSNUGICR UTILITY EXECUTION FAILED
Explanation: The invoked DSNUGICR utility failed.
User response: Contact IBM Software Support. Have available the listing that contains this message.

CKZ25341E UNABLE TO DETERMINE IF EXTENDED RBA IS ENABLED FOR DSNDB01.tsname
Explanation: It cannot be determined whether the indicated table or index space in the DB2 directory has been enabled for extended RBA. It is not possible to properly clean the table or index space. Processing terminates.
User response: Contact IBM Software Support. Have available the listing that contains this message.

CKZ25401I hh:mm:ss EXTENDED RBA CHECKER STARTED - PROGRAM REV=rrr | hh:mm:ss EXTENDED RBA CHECKER COMPLETED; RETURN CODE=return_code
Explanation: Informational EXTENDED RBA CHECKER processing message.
User response: No action is required.

CKZ25403I DDNAME=ddname ALLOCATED FOR DSN=data_set_name
Explanation: The ddname that is listed in the message was dynamically allocated for the indicated data set.
User response: No action is required.

CKZ25405E ALLOCATION FAILED FOR DSN: data_set_name
Explanation: Dynamic allocation for a data set failed. The associated z/OS messages are displayed. Processing terminates.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM Software Support. Have available the listing that contains these messages.

CKZ25405W DEALLOCATION FAILED FOR DDNAME: ddname
Explanation: Dynamic deallocation for a ddname failed. The associated z/OS messages are displayed. Processing continues.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact
IBM Software Support. Have available the listing that contains these messages.

CKZ25407W ERROR CALLING CKZ01HEX; FUNCTION: function R15=nnnn
Explanation: An error occurred while CKZ01HEX was attempting to print a record. Processing continues.
User response: If unable to determine the reason for the failure, contact IBM Software Support.

CKZ25410E ERROR ACCESSING LINEAR FILE; DDNAME=ddname R15=nnnn ERROR=nnn FUNCTION=function LOC=location RBA OF RECORD: X'nnnnnnnn_nnnnnnnn'
Explanation: A VSAM error occurred accessing the indicated file. Processing terminates.
User response: If unable to resolve the problem, contact IBM Software Support. Have available the listing that contains this message.

CKZ25442I DSNDB01.tsname DDNAME=ddname IS EMPTY
Explanation: The indicated table or index space in the DB2 directory is empty.
User response: No action is required.

CKZRX306E modid Write to CMDOUT failed; return code = return_code
Explanation: The REXX program was unable to write to the output file allocated to the CMDOUT DD statement. Processing terminates.
User response: Ensure that the DCB attributes for the CMDOUT file are correct. Ensure that there is sufficient space that is given to the output file. If unable to resolve the problem, contact IBM Software Support. Have available the listing that contains this message.

CKZRX321I modid Using DB2 SSID= ssid
Explanation: The REXX program will use the indicated DB2 ssid. The ssid value is obtained from the argument string that is provided to the REXX program.
User response: No action is required.

CKZRX322E modid DSN command failed; return code= return_code
Explanation: The invocation of the DB2 DSN command processor failed. return_code is the return code from the invocation.
User response: Verify that the correct DB2 ssid is being used, that the job is running on the same system as the DB2 system, and that the correct STEPLIB is being used. If unable to resolve problem, contact IBM Software Support. Have available the listing that contains this message.

CKZRX323I modid Number of commands written to CMDOUT: number _of_commands
Explanation: The number of start commands that were written to CMDOUT DD statement.
User response: No action is required.

CKZRX324I modid There are no objects with UT status
Explanation: There are no DB2 objects found that have UT status, therefore no start commands need to be generated.
User response: No action is required.

CKZRX325I modid Start commands generated for:
Explanation: This message precedes a list of the database.spacename objects that have UT status, and that start commands have been generated for.
User response: No action is required.

CKZRX399E modid Exec error condition has occurred: error_data
Explanation: The REXX program had an internal error. error_data identifies the statement in error. Processing terminates.
User response: Contact IBM Software Support. Have available the listing that contains this message.



Update 4
Date of change: 3/25/2014
Topics: Multiple
Change description: For APAR PM97209, the UTILITY-COMMAND-EXECUTE-PERCENT SET command was added to DB2 Cloning Tool Table Space Cloning. The following topics and messages were added or updated in support of this feature:
- Topic: "SET command syntax"
- Topic: "SET command and keyword definitions"
- Topic: "Messages"

Download the attached PDF document for a complete description of the changes.
CKZ-1723_PM97209_UTILITY-COMMAND-EXECUTE-PERCENT.pdfCKZ-1723_PM97209_UTILITY-COMMAND-EXECUTE-PERCENT.pdf




Update 3
Date of change: 3/19/2014
Topics: Multiple
Change description: For APAR PI11424, keywords were added to the BCSCLEAN command to allow you to remove orphaned target catalog entries and other data sets from the target catalog. The following topics and messages were added or updated in support of this feature:
- Topic: "Function authorization requirements"
- Topic: "BCSCLEAN"
- Topic: "BCSCLEAN command syntax"
- Topic: "BCSCLEAN command and keyword definitions"
- Topic: "BCSCLEAN step JCL examples"
- Topic: "Parameter files and parameter descriptions"
- Topic: "Messages"

Download the attached PDF document for a complete description of the changes.
CKZ-1539_CKZ-1758_BCSCLEAN.pdfCKZ-1539_CKZ-1758_BCSCLEAN.pdf




Update 2
Date of change: 3/3/2014
Topics: Multiple
Change description: APAR PI06815 adds the ability to use image copies as the source for table space cloning. The following topics and messages were added or updated in support of this feature:
- New topic: “Chapter 18. Using image copies to clone table spaces and index spaces”
- Topic: "SET command defaults" in the "Using the ISPF Interface" topic
- Topic: "COPY command defaults" in the "Using the ISPF Interface" topic
- Topic: “COPY command"
- Topic: “COPY command and keyword definitions"
- Topic: “SET command"
- Topic: “SET command and keyword definitions"
Topic: “Messages"

Double-click the following PDF file for a description of all the documentation changes:
CKZ-236_CKZ-1755_SourceImageCopy.pdfCKZ-236_CKZ-1755_SourceImageCopy.pdf



Update 1
Date of change: 2/6/2014
Topics: Multiple
Change description: For APAR PI08497, add the following information and messages to the user guide. The following topics were updated in support of this addition:
  • Topic: “DB2SQL”
  • Topic: “Messages”

1. Topic: “DB2SQL”

Add the following paragraph:

When the DB2SQL command runs, a user-defined index on the DB2 catalog that takes an extent before the DB2SQL command completes can create problems. User-defined indexes on the DB2 catalog are logically part of the DB2 catalog, but they are treated by DB2 as non-system objects. If DB2 needs to extend a user-defined index, it uses the STOGROUP definitions in effect at that time. If the updates to the STOGROUP definitions have not been completed, DB2 might produce an error when attempting to extend the user-defined index.


2. Topic: “Messages"

Add the following messages:


CKZ05653I VOLSER pair: source volserl/target volser FCWITHDRAW indicated the relationship no longer existed
Explanation: The FCWITHDRAW for the volumes indicated that there was no FlashCopy relationship between the two volumes. There is a small window between the check for FlashCopy relationships on the volumes and when the FlashCopy WITHDRAW is done. If the relationship ends between the check and FlashCopy WITHDRAW, this message is displayed to document the event.
User response: No action is required.

CKZ24633I New | Old DB2 STOGROUP already created | dropped: stogroup-name .
Explanation: New name DB2 STOGROUPS have already been created, or old name DB2 STOGROUPS have already been dropped. Processing continues.
User response: No action is required.

CKZ24634I Volume volser in STOGROUP stogroup-name is not a source volume New STOGROUP new-stogroup-name
Explanation: A volser in DB2 STOGROUP stogroup-name is not a source volume of the cloning. The new DB2 STOGROUP new-stogroup-name being created will have this volume. Processing continues.
User response: No action is required. You might want to verify that the volser is intended to be used in the DB2 STOGROUP. Manually remove the volume from the DB2 STOGROUP if desired.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS
DB2 Cloning Tool

Software version:

3.1.0

Operating system(s):

z/OS

Reference #:

7023876

Modified date:

2014-09-16

Translate my page

Machine Translation

Content navigation