db2 cloning tool user's guide - ibm.com · v ersion 3 release 2 ibm db2 cloning t ool for z/os...

Version 3 Release 2

IBM Db2 Cloning Tool for z/OSUser's Guide

SC27-6556

IBM

Note:Before using this information and the product it supports, read the "Notices" topic at the end of this information.

Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download the latest edition fromthe Db2 Tools Product Documentation page.

March 29, 2019 edition

This edition applies to Version 3 Release 2 of Db2 Cloning Tool for z/OS (product number 5655-N15) and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2006, 2019; Copyright Rocket Software Inc., 2006, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

http://www-304.ibm.com/support/docview.wss?uid=swg27020910

Contents

About this information . . . . . . . . ix

Chapter 1. Db2 Cloning Tool overview. . 1What's new in Db2 Cloning Tool . . . . . . . 1

New and changed functions . . . . . . . . 1Deprecated functions . . . . . . . . . . 6

What does Db2 Cloning Tool do? . . . . . . . 7Cloning definitions . . . . . . . . . . . 8Why clone a Db2 subsystem? . . . . . . . . 8Can I clone a Db2 subsystem without Db2Cloning Tool? . . . . . . . . . . . . . 8Db2 support . . . . . . . . . . . . . 8Volume copy products supported by Db2 CloningTool . . . . . . . . . . . . . . . . 9

Db2 Cloning Tool features and benefits . . . . . 10Service updates and support information . . . . 11Product documentation and updates . . . . . . 11Accessibility features . . . . . . . . . . . 12

Chapter 2. Preparing to customize Db2Cloning Tool . . . . . . . . . . . . 13Set up your environment prior to customization . . 14Function authorization requirements . . . . . . 17Use of the U.S.A. EBCDIC code set . . . . . . 19Filtering pattern masks . . . . . . . . . . 20Worksheets: Gathering required data set names . . 21APF authorizing load libraries . . . . . . . . 24Worksheets: Gathering parameter values for ToolsCustomizer . . . . . . . . . . . . . . 25

Chapter 3. Starting and preparing ToolsCustomizer for use . . . . . . . . . 57Starting Tools Customizer . . . . . . . . . 57Modifying Tools Customizer user settings . . . . 58

Chapter 4. Customizing Db2 CloningTool . . . . . . . . . . . . . . . . 63Roadmap: Customizing Db2 Cloning Tool for thefirst time . . . . . . . . . . . . . . . 63Roadmap: Customizing a new version of Db2Cloning Tool from a previous customization . . . 64Roadmap: Recustomizing Db2 Cloning Tool . . . 65Specifying the metadata library for the product tocustomize . . . . . . . . . . . . . . . 66Discovering Db2 Cloning Tool informationautomatically . . . . . . . . . . . . . . 68Creating and associating Db2 entries . . . . . . 70Defining parameters . . . . . . . . . . . 72

Defining Db2 Cloning Tool parameters . . . . 72Defining LPAR parameters . . . . . . . . 74Defining Db2 parameters . . . . . . . . . 75

Generating customization jobs . . . . . . . . 77Submitting customization jobs . . . . . . . . 78Browsing parameters . . . . . . . . . . . 80

Copying Db2 entries . . . . . . . . . . . 80Removing Db2 entries . . . . . . . . . . . 82Deleting Db2 entries . . . . . . . . . . . 82Displaying customization jobs . . . . . . . . 83Maintaining customization jobs . . . . . . . . 83Using Tools Customizer in a multiple-LPARenvironment . . . . . . . . . . . . . . 84

Chapter 5. After customizing Db2Cloning Tool using Tools Customizer . 85Reviewing the CKZINI PARMLIB member variables 85Verifying successful customization. . . . . . . 86

Using the Installation Verification Process . . . 86Adding Db2 Cloning Tool to the Db2 AdminLaunchpad . . . . . . . . . . . . . . 87Exporting and importing ISPF cloning profiles andsubsystem information . . . . . . . . . . 87

EXPORT command syntax . . . . . . . . 88IMPORT command syntax . . . . . . . . 90

Db2 version migration considerations. . . . . . 91

Chapter 6. Planning for copying andrenaming volumes. . . . . . . . . . 93Selection of source and target volumes . . . . . 93Volume relationship conflicts . . . . . . . . 96Ensure RACF and ACF authorities. . . . . . . 96Data set renaming considerations . . . . . . . 96Target ICF catalog considerations . . . . . . . 96Location of the source and target ICF catalogs . . . 97Target data set ICF catalog aliases . . . . . . . 98Considerations for DFSMS pervasive encryption . . 98Return code choices . . . . . . . . . . . 98Cloning a Db2 subsystem. . . . . . . . . . 99

Chapter 7. Setting up to copy byvolume with FlashCopy, SnapShot, orTimeFinder/Clone . . . . . . . . . 103Db2 Cloning Tool process for volume FlashCopy,SnapShot, or TimeFinder/Clone . . . . . . . 103Steps for volume FlashCopy, SnapShot, orTimeFinder/Clone. . . . . . . . . . . . 104

Chapter 8. Setting up to copy byvolume with an onsite mirror tool . . 107Db2 Cloning Tool process for user-created targetvolume clones . . . . . . . . . . . . . 107Steps for user-created target volumes . . . . . 108Db2 Cloning Tool process for EMCTimeFinder/Mirror target volume clones . . . . 110Steps for EMC TimeFinder/Mirror target volumeclones . . . . . . . . . . . . . . . . 110

iii

Chapter 9. Cloning Db2 subsystems 115Db2 offline cloning . . . . . . . . . . . 116

Db2 offline cloning procedure . . . . . . . 116Steps for Db2 offline cloning . . . . . . . 117Db2 offline cloning with removal of datasharing members procedure . . . . . . . 119Steps for Db2 offline cloning with removal ofdata sharing members . . . . . . . . . 120Db2 offline cloning with target becomingnon-data sharing procedure . . . . . . . 122Steps for Db2 offline cloning with targetbecoming non-data sharing. . . . . . . . 123

Db2 online cloning . . . . . . . . . . . 125Status of transactions in flight . . . . . . . 126Db2 online cloning procedure . . . . . . . 127Steps for Db2 online cloning . . . . . . . 128Db2 online cloning with removal of datasharing members procedure . . . . . . . 132Steps for Db2 online cloning with removal ofdata sharing members . . . . . . . . . 134Db2 online cloning with target becomingnon-data sharing procedure . . . . . . . 138Steps for Db2 online cloning with targetbecoming non-data sharing. . . . . . . . 140

Chapter 10. Subsystem cloning usingthe Db2 Cloning Tool storedprocedure . . . . . . . . . . . . . 147About the Db2 Cloning Tool stored procedure . . 147Migrating the stored procedure from Db2 CloningTool V3.1 . . . . . . . . . . . . . . . 148Steps for cloning a Db2 subsystem using the storedprocedure . . . . . . . . . . . . . . 150Parameter files and parameter descriptions . . . 150Calling the stored procedure . . . . . . . . 163Using a REXX EXEC to call the stored procedure 164Verifying the cloning . . . . . . . . . . . 165

JCL members generated by the stored procedure 166Building and running the verified cloning . . . . 167Stored procedure results set . . . . . . . . 167Recloning a Db2 system . . . . . . . . . . 168Stored procedure example: Cloning a non-datasharing subsystem. . . . . . . . . . . . 168Stored procedure example: Cloning by data set . . 169Stored procedure example: Cloning from asystem-level backup . . . . . . . . . . . 171Stored procedure example: Cloning from Db2system-level backup dump tapes . . . . . . . 172Stored procedure example: Cloning from Db2system-level backup dump tapes across sysplexes . 174

Chapter 11. Db2 Cloning Tool TableSpace Cloning overview. . . . . . . 177What does Db2 Cloning Tool Table Space Cloningdo? . . . . . . . . . . . . . . . . . 177Why you should use Db2 Cloning Tool Table SpaceCloning . . . . . . . . . . . . . . . 178Db2 Cloning Tool Table Space Cloning features andbenefits . . . . . . . . . . . . . . . 179

Db2 Cloning Tool Table Space Cloning terminology- Db2 objects vs. VSAM objects . . . . . . . 179Use of the U.S.A. EBCDIC code set . . . . . . 180

Chapter 12. Planning for copying Db2table spaces by data set . . . . . . 181Considerations for in-progress read/write activityor Db2 utilities . . . . . . . . . . . . . 181Considerations for the Db2 Cloning Tool TableSpace Cloning cloning process. . . . . . . . 181

Subsystem copy rules . . . . . . . . . 181Renaming table spaces and index spaces . . . 182Implicitly created objects . . . . . . . . 182Identity columns . . . . . . . . . . . 183LOBs, BLOBs, CLOBs, and DBCLOBs . . . . 183XML considerations . . . . . . . . . . 183DDF and TCP/IP considerations . . . . . . 184Object attributes . . . . . . . . . . . 185Object compatibility checking . . . . . . . 186APF authorization . . . . . . . . . . . 187Ensure RACF and ACF authorities . . . . . 187Missing target table spaces and index spaces 187Considerations for target objects created usingDEFINE NO. . . . . . . . . . . . . 188Considerations for DFSMS pervasive encryption 189Non-SMS managed volumes . . . . . . . 191Space processing order . . . . . . . . . 192How Db2 Cloning Tool Table Space Cloningstarts and stops table spaces and index spaces . 192Message output . . . . . . . . . . . 193

Considerations for Db2 Version 9.1 and later . . . 194Considerations for data set renaming . . . . . 195Considerations for using FUZZY-COPY . . . . 195Considerations for generating target object DDLusing PROCESS-DDL. . . . . . . . . . . 195

Sample DDL processing scenarios . . . . . 197Considerations for using catalog prefetch topopulate the object cache . . . . . . . . . 198

Considerations for caching indexes . . . . . 199Using a local TCP/IP server to populate thetarget cache for multiple source copy jobs . . . 200

Return code choices . . . . . . . . . . . 201Plans and packages . . . . . . . . . . . 201Dropped and altered tables . . . . . . . . . 201Copying versioned objects . . . . . . . . . 202

Chapter 13. Db2 Cloning Tool TableSpace Cloning function overview . . . 203Source job overview . . . . . . . . . . . 203Target job overview . . . . . . . . . . . 203TCP/IP server job overview (optional) . . . . . 204Report job overview (optional) . . . . . . . 204Source job details . . . . . . . . . . . . 204

Source job - Init phase I . . . . . . . . . 204Source job - Discovery phase II . . . . . . 205Source job - Eligibility phase III . . . . . . 205Source job - Copy phase IV. . . . . . . . 206

Target job details . . . . . . . . . . . . 207TCP/IP server job details (optional) . . . . . . 208Report job details (optional) . . . . . . . . 210

iv Db2 Cloning Tool User's Guide

CKZFIX job details (optional) . . . . . . . . 213Runtime repository functionality overview . . . 213

Chapter 14. Setup procedures forcopy by data set with FlashCopy,SnapShot, or TimeFinder/Clone . . . 215Setup for scenario 1: FlashCopy, SnapShot, orTimeFinder/Clone - All target table spaces andindex spaces already exist in Db2 catalog . . . . 215

Step 1: Create target Db2 table spaces and indexspaces in the target Db2 catalog . . . . . . 215Step 2: Set up and execute source job(CKZ1SRC) . . . . . . . . . . . . . 216Step 3: Set up and execute target job (CKZTRG) 220

Setup for scenario 2: FlashCopy, SnapShot, orTimeFinder/Clone - Some or all target table spacesand index spaces do not exist in Db2 catalog . . . 223

Step 1: Create target Db2 table spaces and indexspaces in the target Db2 catalog (if required) . . 224Step 2: Set up and execute source job(CKZ2SRC) . . . . . . . . . . . . . 225Step 3 (Optional): Create missing target tablespaces and index spaces . . . . . . . . . 229Step 4: Set up and execute optional FIX job(CKZFIX). . . . . . . . . . . . . . 230Step 5: Set up for a re-run of the source job . . 231Step 6: Set up and execute target job (CKZTRG) 231

Chapter 15. Set up procedures forcopy by data set for all othermethodologies . . . . . . . . . . . 235Setup for scenario 3: Other copy methodologies -all target table spaces and index spaces alreadyexist in Db2 catalog . . . . . . . . . . . 235

Step 1: Verify/create target Db2 table spaces andindex spaces in target Db2 catalog . . . . . 235Step 2: Set up and execute source job(CKZ3SRC) . . . . . . . . . . . . . 236Step 3 (Optional): Set up and execute stop targetjob (CKZSTPT) . . . . . . . . . . . . 240Step 4 (Optional): Set up and execute stopsource job (CKZSTPS) . . . . . . . . . 241Step 5: Set up and execute non-Db2 CloningTool Table Space Cloning job to execute data setcopies outside Db2 Cloning Tool Table SpaceCloning . . . . . . . . . . . . . . 242Step 6 (Optional): Set up and execute job tore-start source Db2 table spaces and indexspaces (CKZSTRS) . . . . . . . . . . . 242Step 7: Set up and execute target job (CKZTRG) 243

Setup for scenario 4: Other copy methodologies -some or all target table spaces and index spaces donot exist in Db2 catalog . . . . . . . . . . 247

Step 1: Create target Db2 table spaces and indexspaces in target Db2 catalog . . . . . . . 247Step 2: Set up source job (CKZ4SRC) . . . . 248Step 3 (Optional): Set up stop target job(CKZSTPT) . . . . . . . . . . . . . 253Step 4 (Optional): Set up stop source job(CKZSTPS) . . . . . . . . . . . . . 254

Step 5: Set up non-Db2 Cloning Tool TableSpace Cloning job to execute data set copiesoutside Db2 Cloning Tool Table Space Cloning . 255Step 6 (Optional): Set up job to re-start sourceDb2 table spaces and index spaces (CKZSTRS) . 255Step 7 (Optional): Create missing target tablespaces and index spaces . . . . . . . . . 256Step 8 (Optional): Set up job to make copiedVSAM objects available to target Db2 (CKZFIX) . 257Step 9: Set up for a re-run of the source job . . 258Step 10: Set up and execute target job(CKZTRG) . . . . . . . . . . . . . 258

Chapter 16. Procedures for cloningDb2 table spaces and index spaces. . 263Copy procedure 1: FlashCopy, SnapShot, orTimeFinder/Clone setup - when all target tablespaces and index spaces already exist in Db2catalog . . . . . . . . . . . . . . . 263

Step 1: Verify/create target Db2 table spaces andindex spaces in target Db2 catalog . . . . . 263Step 2 (Optional): Submit TCP/IP server job . . 264Step 3 (Optional): Submit source TCP/IP serverjob . . . . . . . . . . . . . . . . 264Step 4: Submit source job . . . . . . . . 264Step 5: Submit target job . . . . . . . . 264

Copy procedure 2: FlashCopy, SnapShot, orTimeFinder/Clone setup - when some or all targettable spaces and index spaces do not exist in Db2catalog . . . . . . . . . . . . . . . 265

Step 1: Verify/create target Db2 table spaces andindex spaces in target Db2 catalog . . . . . 265Step 2 (Optional): Submit TCP/IP server job . . 265Step 3 (Optional): Submit source TCP/IP serverjob . . . . . . . . . . . . . . . . 266Step 4: Submit source job . . . . . . . . 266Step 5: Create missing target Db2 table spacesand index spaces - manually or using non-Db2Cloning Tool Table Space Cloning Tool . . . . 267Step 6: Submit FIX job on target z/OS system(CKZFIX). . . . . . . . . . . . . . 267Step 7: Rerun source job . . . . . . . . . 267Step 8: Submit target job . . . . . . . . 267

Copy procedure 3: All other copy methodologies -All target table spaces and index spaces alreadyexist in Db2 catalog . . . . . . . . . . . 268

Step 1: Verify/create target Db2 table spaces andindex spaces in target Db2 catalog . . . . . 268Step 2 (Optional): Submit TCP/IP server job . . 268Step 3 (Optional): Submit source TCP/IP serverjob . . . . . . . . . . . . . . . . 269Step 4: Submit source job . . . . . . . . 269Step 5: Submit job CKZSTPT to stop target Db2table spaces and index spaces . . . . . . . 269Step 6: Submit job CKZSTPS to stop source Db2table spaces and index spaces . . . . . . . 269Step 7: Submit non-Db2 Cloning Tool TableSpace Cloning job to copy VSAM objects . . . 269Step 8: Submit job CKZSTRS to start source Db2table spaces and index spaces . . . . . . . 269Step 9: Rerun source job . . . . . . . . . 270

Contents v

||

Step 10: Submit target job . . . . . . . . 270Copy procedure 4: All other copy methodologies -some or all target table spaces and index spaces donot exist in Db2 catalog . . . . . . . . . . 270

Step 1: Verify/create target Db2 table spaces andindex spaces in target Db2 catalog . . . . . 271Step 2 (Optional): Submit TCP/IP server job . . 271Step 3 (Optional): Submit source TCP/IP serverjob . . . . . . . . . . . . . . . . 271Step 3: Submit source job . . . . . . . . 271Step 5: Create missing target Db2 table spacesand index spaces . . . . . . . . . . . 272Step 6: Submit job CKZSTPT to stop target Db2table spaces and index spaces . . . . . . . 272Step 7: Submit job CKZSTPS to stop source Db2table spaces and index spaces . . . . . . . 273Step 8: Submit non-Db2 Cloning Tool TableSpace Cloning job to copy VSAM objects . . . 273Step 9: Submit job CKZSTRS to restart sourceDb2 table spaces and index spaces . . . . . 273Step 10: Submit FIX job on target z/OS system(CKZFIX). . . . . . . . . . . . . . 273Step 11: Rerun the source job to prepare targetjob . . . . . . . . . . . . . . . . 273Step 12: Submit target job . . . . . . . . 274

Chapter 17. Using data masking withtable space cloning. . . . . . . . . 275Source job changes . . . . . . . . . . . 276Specifying the masking rule . . . . . . . . 277

MASKRULE(STATIC, numeric | “date_or_time” |“string”) . . . . . . . . . . . . . . 277MASKRULE(MASK, “pattern”, start, end) . . . 278MASKRULE(PATTERN, “pattern”, “use_sources”) 280MASKRULE(RANDOM, “min”, “max”,“check_bounds”)MASKRULE(RANDOM, "min_timestampz","max_timestampz", "min_timezone","max_timezone", "check_bounds") . . . . . . 282MASKRULE(USEREXIT, module) . . . . . . 283MASKRULE(SEQUENCE, initial_value,increment). . . . . . . . . . . . . . 284MASKRULE(SCRAMBLE) . . . . . . . . 284MASKRULE(CURRENT DATE)MASKRULE(CURRENT TIME)MASKRULE(CURRENT TIMESTAMP,"timezone") . . . . . . . . . . . . . 285MASKRULE(CURRENT USER) . . . . . . 285

Target job changes. . . . . . . . . . . . 286Examples of masking jobs . . . . . . . . . 287

Chapter 18. Using image copies toclone table spaces and index spaces . 295Steps for cloning from image copies (includingindex rebuilds) . . . . . . . . . . . . . 296Selecting a specific image copy to use as thecloning source . . . . . . . . . . . . . 297Selecting the last image copy to use as the cloningsource . . . . . . . . . . . . . . . . 298Source job changes for cloning from image copies 298

Chapter 19. Using LOG-APPLY tomake consistent copies of tablespaces and index spaces . . . . . . 301Source job changes . . . . . . . . . . . 302Using LOG-APPLY across multiple LPARs. . . . 303Target job changes. . . . . . . . . . . . 303

Chapter 20. Options for rebuildingindexes . . . . . . . . . . . . . . 305Recommendations when rebuilding indexes . . . 306Method 1: Intelligent rebuild . . . . . . . . 307Method 2: Using job templates in the source job 308Method 3: Using job templates in the target job . . 308

Chapter 21. Using job templates . . . 311Predefined processing variables . . . . . . . 312Data set processing variables . . . . . . . . 313Block processing variables . . . . . . . . . 314Job templates for utilities . . . . . . . . . 314Job templates for cloning consistent FlashCopydata sets to Db2 data sets using IBM SterlingConnect:Direct . . . . . . . . . . . . . 316

Using the ISPF interface and job templates toclone with IBM Sterling Connect:Direct . . . . 318Cloning source VSAM files using SterlingConnect:Direct . . . . . . . . . . . . 319

Chapter 22. Using the ISPF interface 321The Db2 Cloning Tool ISPF interface . . . . . 321Configuring Db2 subsystems . . . . . . . . 322

Configuring a subsystem . . . . . . . . 323Configuring user settings . . . . . . . . . 324

Setting job card defaults . . . . . . . . . 324Setting subsystem cloning defaults . . . . . 325Setting table space cloning defaults . . . . . 335

Creating cloning jobs using the interface . . . . 370Creating a profile . . . . . . . . . . . 370

Subsystem cloning. . . . . . . . . . . . 371Subsystem cloning steps summary . . . . . 371Step summary for subsystem cloning from asystem-level backup . . . . . . . . . . 371Select source and target subsystems . . . . . 372Add or verify high level qualifiers . . . . . 374Specify source and target volume pairings. . . 374Specify source and target ICF catalogs . . . . 375Specify rename masks for source and target datasets. . . . . . . . . . . . . . . . 375Build the cloning jobs from a profile. . . . . 376Submit the jobs. . . . . . . . . . . . 385

Table space cloning . . . . . . . . . . . 386Table space cloning steps summary . . . . . 386Select the source and target Db2 subsystems . . 387Edit the source job . . . . . . . . . . 387Verify the target job settings . . . . . . . 388Verify the report job settings . . . . . . . 389Verify the TCP/IP server job settings . . . . 389Verify the source TCP/IP server job settings . . 389Build the table space cloning jobs from a profile 390Submit the jobs. . . . . . . . . . . . 391

vi Db2 Cloning Tool User's Guide

Table space cloning across multiple profiles . . 391

Chapter 23. Table spacing cloningusing z/OSMF REST services . . . . 395Sample members and descriptions . . . . . . 395Variable input file parameters . . . . . . . . 396

Considerations for multi-line variable values 401Considerations for multi-line variable valuesin a JSON request body . . . . . . . . 402

Configuring and running the workflow . . . . 403Running the workflow via REST services . . . 404Running the workflow via the z/OSMF webbrowser-based interface . . . . . . . . . 406

Chapter 24. Cloning table spaces fromDb2 Administration Tool. . . . . . . 409

Chapter 25. Db2 Cloning ToolSubsystem Cloning commands. . . . 411BACKINFO-REFORMAT . . . . . . . . . 412

BACKINFO-REFORMAT command syntax . . 413BACKINFO-REFORMAT command andkeyword definitions . . . . . . . . . . 415BACKINFO-REFORMAT step JCL examples . . 417

BCSCLEAN . . . . . . . . . . . . . . 420BCSCLEAN command syntax . . . . . . . 420BCSCLEAN command and keyword definitions 421BCSCLEAN step JCL examples . . . . . . 423

COPY . . . . . . . . . . . . . . . . 425COPY command syntax . . . . . . . . . 429COPY command and keyword definitions . . . 430COPY step JCL example . . . . . . . . . 448

COPY-BY-DS . . . . . . . . . . . . . 451Planning for subsystem cloning by data set . . 451COPY-BY-DS command syntax . . . . . . 452COPY-BY-DS command and keyworddefinitions . . . . . . . . . . . . . 453COPY-BY-DS step JCL example . . . . . . 456

COPYCHECK . . . . . . . . . . . . . 457COPYCHECK command syntax . . . . . . 458COPYCHECK command and keyworddefinitions . . . . . . . . . . . . . 458COPYCHECK step JCL example . . . . . . 459

DB2ALTERBSDS . . . . . . . . . . . . 460DB2ALTERBSDS command syntax . . . . . 461DB2ALTERBSDS command and keyworddefinitions . . . . . . . . . . . . . 461DB2ALTERBSDS step JCL example . . . . . 463

DB2FIX . . . . . . . . . . . . . . . 466DB2FIX command syntax . . . . . . . . 467DB2FIX command and keyword definitions . . 468DB2FIX step JCL example . . . . . . . . 470

DB2GETBACKINFO . . . . . . . . . . . 471DB2GETBACKINFO command syntax . . . . 472DB2GETBACKINFO command and keyworddefinitions . . . . . . . . . . . . . 472DB2GETBACKINFO step JCL examples . . . 475

DB2LGRNXCLEAN . . . . . . . . . . . 477DB2LGRNXCLEAN command syntax . . . . 478

DB2LGRNXCLEAN command and keyworddefinitions . . . . . . . . . . . . . 478DB2LGRNXCLEAN step JCL example . . . . 479

DB2RBLDBSDS. . . . . . . . . . . . . 480DB2RBLDBSDS command syntax. . . . . . 480DB2RBLDBSDS command and keyworddefinitions . . . . . . . . . . . . . 480DB2RBLDBSDS step JCL example . . . . . 482

DB2SCHEMA-UPDATE . . . . . . . . . . 483DB2SCHEMA-UPDATE command syntax . . . 484DB2SCHEMA-UPDATE command and keyworddefinitions . . . . . . . . . . . . . 485DB2SCHEMA-UPDATE step JCL example . . . 488

DB2SETLOG . . . . . . . . . . . . . 488DB2SETLOG command syntax . . . . . . 489DB2SETLOG command and keyword definitions 489DB2SETLOG step JCL example . . . . . . 490

DB2SQL . . . . . . . . . . . . . . . 491DB2SQL command syntax . . . . . . . . 492DB2SQL command and keyword definitions . . 493DB2SQL step JCL example . . . . . . . . 496

DB2START . . . . . . . . . . . . . . 497DB2START command syntax . . . . . . . 498DB2START command and keyword definitions 499DB2START step JCL example . . . . . . . 501

DB2STOP. . . . . . . . . . . . . . . 502DB2STOP command syntax. . . . . . . . 502DB2STOP command and keyword definitions 503DB2STOP step JCL example . . . . . . . 504

DB2UPDATE . . . . . . . . . . . . . 504DB2UPDATE command syntax . . . . . . 506DB2UPDATE command and keyworddefinitions . . . . . . . . . . . . . 507DB2UPDATE step JCL example . . . . . . 511

DB2UTILXCLEAN . . . . . . . . . . . 515DB2UTILXCLEAN command syntax . . . . 515DB2UTILXCLEAN command and keyworddefinitions . . . . . . . . . . . . . 516DB2UTILXCLEAN step JCL example . . . . 517Step JCL example to identify objects with UTstatus . . . . . . . . . . . . . . . 517

DB2XCFCLEAN . . . . . . . . . . . . 518DB2XCFCLEAN command syntax . . . . . 519DB2XCFCLEAN command and keyworddefinitions . . . . . . . . . . . . . 519DB2XCFCLEAN step JCL example . . . . . 520

FINDUCATS . . . . . . . . . . . . . 520FINDUCATS command syntax . . . . . . 521FINDUCATS command and keyworddefinitions . . . . . . . . . . . . . 521FINDUCATS step JCL example . . . . . . 522

JRNLUPGRADE . . . . . . . . . . . . 522JRNLUPGRADE command syntax . . . . . 524JRNLUPGRADE command and keyworddefinitions . . . . . . . . . . . . . 524JRNLUPGRADE step JCL example . . . . . 524

ONLINECLIP . . . . . . . . . . . . . 525ONLINECLIP command syntax . . . . . . 526ONLINECLIP command and keyworddefinitions . . . . . . . . . . . . . 526ONLINECLIP step JCL example . . . . . . 526

Contents vii

RENAME . . . . . . . . . . . . . . 527RENAME command syntax . . . . . . . 527RENAME command and keyword definitions 530RENAME step JCL example . . . . . . . 543

RESTORE-FROM-DUMPTAPES . . . . . . . 544RESTORE-FROM-DUMPTAPES commandsyntax . . . . . . . . . . . . . . . 546RESTORE-FROM-DUMPTAPES command andkeyword definitions . . . . . . . . . . 546RESTORE-FROM-DUMPTAPES step JCLexample . . . . . . . . . . . . . . 550

UCATOPTIONS . . . . . . . . . . . . 552UCATOPTIONS command syntax . . . . . 553UCATOPTIONS command and keyworddefinitions . . . . . . . . . . . . . 553UCATOPTIONS step JCL example . . . . . 554

VARYOFF . . . . . . . . . . . . . . 555VARYOFF command syntax . . . . . . . 556VARYOFF command and keyword definitions 556VARYOFF step JCL example . . . . . . . 558

VARYON. . . . . . . . . . . . . . . 560VARYON command syntax. . . . . . . . 560VARYON command and keyword definitions 560VARYON step JCL example . . . . . . . 562

VOLOPTIONS . . . . . . . . . . . . . 564VOLOPTIONS command syntax . . . . . . 565VOLOPTIONS command and keyworddefinitions . . . . . . . . . . . . . 566VOLOPTIONS step JCL example . . . . . . 568

Chapter 26. Db2 Cloning Tool TableSpace Cloning commands . . . . . . 569COPY . . . . . . . . . . . . . . . . 569

COPY command syntax . . . . . . . . . 570COPY command and keyword definitions . . . 573OBJECT-TRANSLATE considerations . . . . 613DDL-ATTRIBUTE-CHANGE parameter values 614GLOBAL command values for EMCTimeFinder/Clone Mainframe Snap Facility dataset level support . . . . . . . . . . . 617

DATASUBTYPE . . . . . . . . . . . . 619DATASUBTYPE command syntax . . . . . 620DATASUBTYPE command & keyworddefinitions . . . . . . . . . . . . . 620

HLQDDDF . . . . . . . . . . . . . . 620HLQDDDF command syntax . . . . . . . 620HLQDDDF command and keyword definitions 621

LISTDEF . . . . . . . . . . . . . . . 621LISTDEF command syntax . . . . . . . . 624LISTDEF command and keyword definitions 624

SET. . . . . . . . . . . . . . . . . 627SET command syntax . . . . . . . . . 627SET command and keyword definitions . . . 628

Chapter 27. Troubleshooting . . . . . 643Messages . . . . . . . . . . . . . . . 643

Messages and descriptions . . . . . . . . 643How to look up message explanations . . . 1044

Gathering diagnostic information . . . . . . 1045Gathering maintenance level information with theDISPLAY MEPL command . . . . . . . . 1046Validating load module contents withMODLEVEL . . . . . . . . . . . . . 1046Tools Customizer troubleshooting . . . . . . 1047

Gathering diagnostic information . . . . . 1048Determining the trace data set name . . . . 1048

Chapter 28. Tools Customizerreference. . . . . . . . . . . . . 1049Tools Customizer terminology and data sets. . . 1049

Tools Customizer terminology . . . . . . 1049Data sets that Tools Customizer uses duringcustomization . . . . . . . . . . . . 1052

Chapter 29. Reference . . . . . . . 1055Cloning scenarios . . . . . . . . . . . 1055

Volume cloning using an interim set ofvolumes . . . . . . . . . . . . . . 1055Volume cloning using multiple interim sets ofvolumes . . . . . . . . . . . . . . 1061Db2 subsystem cloning using data set copy 1070Db2 subsystem cloning from a Db2 BACKUPSYSTEM backup . . . . . . . . . . . 1072Db2 subsystem cloning to a specific point intime from a Db2 BACKUP SYSTEM backup . . 1083Db2 subsystem cloning from Db2 BACKUPSYSTEM dump tapes . . . . . . . . . 1099Db2 subsystem cloning from other system levelbackups when backup volumes are online . . 1106Db2 subsystem cloning from other system levelbackups when backup volumes are offline . . 1112

CKZINI customization values . . . . . . . 1119Structure of the CKZINI member . . . . . 1119Syntax rules . . . . . . . . . . . . 1119About Db2 Cloning Tool Table Space Cloningtoken errors . . . . . . . . . . . . 1120CKZINI keyword syntax and descriptions . . 1121

Deallocating target Db2 coupling facilitystructures . . . . . . . . . . . . . . 1136Previous changes to Db2 Cloning Tool. . . . . 1137

Notices . . . . . . . . . . . . . 1153

Index . . . . . . . . . . . . . . 1157

viii Db2 Cloning Tool User's Guide

About this information

Db2® Cloning Tool for z/OS® (also referred to as Db2 Cloning Tool) makes it easyto quickly clone a Db2 subsystem or a Db2 table space. Db2 Cloning Tool can alsobe used to clone non-Db2 volumes.

These topics provide instructions for installing, configuring, and using Db2Cloning Tool.

These topics are designed to help database administrators, system programmers,application programmers, and system operators perform these tasks:v Plan for the installation of Db2 Cloning Toolv Install and operate Db2 Cloning Toolv Customize your Db2 Cloning Tool environmentv Diagnose and recover from Db2 Cloning Tool problemsv Design and write applications for Db2 Cloning Toolv Use Db2 Cloning Tool with other Db2 products

Tip: To find the most current version of this information, always use IBM®

Knowledge Center, which is updated more frequently than PDF books.

ix

https://www.ibm.com/support/knowledgecenter/https://www.ibm.com/support/knowledgecenter/

x Db2 Cloning Tool User's Guide

Chapter 1. Db2 Cloning Tool overview

Db2 Cloning Tool for z/OS (also referred to as Db2 Cloning Tool) makes it easy toquickly clone a Db2 subsystem or a Db2 table space.

Db2 Cloning Tool can also be used to clone non-Db2 volumes.

What's new in Db2 Cloning ToolThis section describes recent technical changes to Db2 Cloning Tool.

New and changed information is marked like this paragraph, with a vertical bar tothe left of a change. Editorial changes that have no technical significance are notmarked.

Older changes and enhancements are described in “Previous changes to Db2Cloning Tool” on page 1137.

New and changed functionsThis topic summarizes the recent enhancements and changes in Db2 Cloning Tool.

March 29, 2019

Description Related APARs

The USE-RUNTIME-REPOSITORY functionality was enhanced andthe documentation updated to describe restartability of the tablespace cloning target job. The following topics were added orupdated, and messages were updated and added for thisenhancement:

v “Target job overview” on page 203v “Report job details (optional)” on page 210v “Runtime repository functionality overview” on page 213v Chapter 18, “Using image copies to clone table spaces and index

spaces,” on page 295

v ISPF interface topics “Table space cloning DD descriptions” onpage 338, “SET command defaults” on page 341, and “COPYcommand defaults” on page 347

v “COPY command and keyword definitions” on page 573v “SET command and keyword definitions” on page 628

PH09043

The topic “DB2SCHEMA-UPDATE” on page 483 was updated toadd details about how the command works.

None

1

|||


Updates to the scenario topics provide additional details forsubsystem cloning when ICF catalogs may already reside on thetarget volumes. The following topics were updated:

v “Volume cloning using an interim set of volumes” on page 1055v “Volume cloning using multiple interim sets of volumes” on page

1061

v “Db2 subsystem cloning from a Db2 BACKUP SYSTEM backup”on page 1072

v “Db2 subsystem cloning to a specific point in time from a Db2BACKUP SYSTEM backup” on page 1083

v “Db2 subsystem cloning from other system level backups whenbackup volumes are online” on page 1106

v “Db2 subsystem cloning from other system level backups whenbackup volumes are offline” on page 1112

None

Access to the BPX.FILEATTR.APF FACILITY class profile is nolonger required to use log apply functionality with Db2 CloningTool Table Space Cloning. The topic “Function authorizationrequirements” on page 17 was updated.

PH05570

Information was added to “Set up your environment prior tocustomization” on page 14 to include the requirement for all cloningjobs to be at the same maintenance level.

None

The default for TCPIP_ENCRYPTION_ENABLE was changed to Nin “CKZINI keyword syntax and descriptions” on page 1121 andtext was added stating that this parameter must be set to the samevalue on the source and the target systems.

None

January 25, 2019


Support was added for subsystem and table space cloning whenpervasive data encryption in DFSMS and Db2 V12 with functionlevel 502 is implemented. The following topics were updated oradded:

v Information was added to the Db2 Cloning Tool SubsystemCloning topic “Considerations for DFSMS pervasive encryption”on page 98.

v The ENCRYPTION-MISMATCH-RC parameter was added to theISPF interface topic “COPY command defaults” on page 347 andthe Db2 Cloning Tool Table Space Cloning topics “COPYcommand syntax” on page 570 and “COPY command andkeyword definitions” on page 573.

v The KEYLABEL parameter was added to the Db2 Cloning ToolTable Space Cloning topic “DDL-ATTRIBUTE-CHANGEparameter values” on page 614.

v The TCPIP_ENCRYPTION_ENABLE and TCPIP_KEY_LABELparameters were added to the CKZINI PARMLIB member asdescribed in “CKZINI keyword syntax and descriptions” on page1121.

v The topic “Db2 subsystem cloning using data set copy” on page1070 was updated.

PH05821

2 Db2 Cloning Tool User's Guide


Support was added to allow you to specify DDF dynamic locationaliases for the subsystem cloning DB2UPATE command. Thefollowing topics were modified and messages were updated:

v Stored procedure topic “Parameter files and parameterdescriptions” on page 150.

v ISPF interface topic “Specifying information for subsystemcloning” on page 323.

v Subsystem cloning command topics “DB2UPDATE commandsyntax” on page 506 and “DB2UPDATE command and keyworddefinitions” on page 507.

PH05491

Doc clarifications were made to describe the behavior of the tablespace cloning COPY parameter COPY-IJ-TO-NONEXISTENT-TARGET. The following topics were updated:

v “Considerations for target objects created using DEFINE NO” onpage 188.

v ISPF interface topic “COPY command defaults” on page 347.v Table space cloning topic “COPY command and keyword

definitions” on page 573.

None

Documentation updates include the following:

v The job names that are generated by Tools Customizer wereupdated and a section was added that describes the job namingconventions. The topic “Worksheets: Gathering parameter valuesfor Tools Customizer” on page 25 was updated.

v The ISSUE-UCAT-UNALLOCATE keyword was missing from theDb2 Cloning Tool Subsystem Cloning RENAME command. Thekeyword and its parameters were added to “RENAME commandsyntax” on page 527 and “RENAME command and keyworddefinitions” on page 530.

v Db2 Cloning Tool removes the SLB information from the BSDS aspart of Db2 conditioning; the topic “DB2UPDATE” on page 504was updated with this information.

v Information about cloning a mixture of explicitly and implicitlycreated objects was added to “Implicitly created objects” on page182.

v Many messages were renumbered and updated in the “Db2Cloning Tool messages” on page 704 reference.

PH06199

The KEEP-VOLUMES-SEQUENCE keyword was incorrect in sometopics and has been corrected. The topics “Parameter files andparameter descriptions” on page 150, “Db2 subsystem cloning froma Db2 BACKUP SYSTEM backup” on page 1072, and “Db2subsystem cloning from Db2 BACKUP SYSTEM dump tapes” onpage 1099 were updated.

None

Chapter 1. Db2 Cloning Tool overview 3

2018-11-15


Job templates were added that can be used to clone consistentFlashCopy® data sets from the source system to Db2 data sets onthe target system using Sterling Connect:Direct®. The followingtopic were added:

v “Job templates for cloning consistent FlashCopy data sets to Db2data sets using IBM Sterling Connect:Direct” on page 316

v “Using the ISPF interface and job templates to clone with IBMSterling Connect:Direct” on page 318

v “Cloning source VSAM files using Sterling Connect:Direct” onpage 319

PI87947

An Installation Verification Process (IVP) was added for Db2Cloning Tool Table Space Cloning. The topic “Using the InstallationVerification Process” on page 86 was added and the topics“Worksheets: Gathering parameter values for Tools Customizer” onpage 25 and “Verifying successful customization” on page 86 weremodified.

PH03430

Tools Customizer parameters were added to add additional indexeson the Db2 catalog tables and to provide a buffer pool name forthose additional indexes to help improve the performance of theDB2SCHEMA-UPDATE command. The topic “Worksheets:Gathering parameter values for Tools Customizer” on page 25 wasupdated.

PH04472

The SOURCE-TCPIP-STC-NAME and TCPIP-STC-NAMEparameters were clarified in the topic “SET command and keyworddefinitions” on page 628.

None

The LISTDEF command description was enhanced to describe howCOPY command keywords can impact the construction of theLISTDEF command. The topics “LISTDEF” on page 621, “LISTDEFcommand and keyword definitions” on page 624, and “COPYcommand and keyword definitions” on page 573 were updated.

PI99297

The topic “Object compatibility checking” on page 186 was addedto clarify how Db2 Cloning Tool Table Space Cloning processesobject checking for mismatches.

None

2018-10-09


The KEEP-VOLUMES-SEQUENCE keyword was added tosubsystem cloning so that source volumes can be paired withspecific target volumes. The following topics were modified andmessage were added and removed for this feature:

v “Parameter files and parameter descriptions” on page 150v “COPY” on page 425, “COPY command syntax” on page 429, and

“COPY command and keyword definitions” on page 430

v “RESTORE-FROM-DUMPTAPES command syntax” on page 546and “RESTORE-FROM-DUMPTAPES command and keyworddefinitions” on page 546

PH02084



Subsystem cloning has been enhanced so that you can clone sourcevolumes to target volumes that have ICF catalogs on them, withouthaving to move the target catalogs off the volumes before thecloning and moving them back afterwards. TheTARGET-UCATS-ON-TARGET-VOLUME keyword was added tothe COPY and RESTORE-FROM-DUMPTAPES commands, and thestored procedure and cloning scenarios were updated for the newkeyword. The following topics were added or changed:

v Chapter 9, “Cloning Db2 subsystems,” on page 115v “Location of the source and target ICF catalogs” on page 97v “Parameter files and parameter descriptions” on page 150v “COPY” on page 425, “COPY command syntax” on page 429, and

“COPY command and keyword definitions” on page 430

v “RESTORE-FROM-DUMPTAPES” on page 544,“RESTORE-FROM-DUMPTAPES command syntax” on page 546,and “RESTORE-FROM-DUMPTAPES command and keyworddefinitions” on page 546

v Cloning scenarios “Db2 subsystem cloning from a Db2 BACKUPSYSTEM backup” on page 1072 and “Db2 subsystem cloningfrom Db2 BACKUP SYSTEM dump tapes” on page 1099

v Messages were modified and added.

PH01928

The EXECUTE-CREATE-DDL parameter was added to the Db2Cloning Tool Subsystem Cloning DB2SCHEMA-UPDATE commandso that you specify whether to run the DDL as part of the job. Thetopics “DB2SCHEMA-UPDATE command syntax” on page 484 and“DB2SCHEMA-UPDATE command and keyword definitions” onpage 485 were updated.

PH01085

A clarification about using data masking for columns withreferential integrity was added to Chapter 17, “Using data maskingwith table space cloning,” on page 275.

None

Additional job templates CKZJOBT6, CKZJOBT7, and CKZJOBT8were provided for use when you want to clone table spaces usingFUZZY-COPY(Y). The topics Chapter 21, “Using job templates,” onpage 311, “Specifying job template data set and member namedefaults” on page 356, and “GLOBAL command values for EMCTimeFinder/Clone Mainframe Snap Facility data set level support”on page 617 were modified.

PH01998

For Db2 subsystem cloning, the following command names wererenamed to clarify which volumes are being clipped:

v CLIP was changed to SOURCECLIPv UNCLIP was changed to TARGETUNCLIPv OFFLINECLIP was changed to TARGETOFFLINECLIP

Updates were made throughout the documentation to reflect thecommand name changes.

None

PGM(EMCSNAP) and PGM(SRCVSCPY) were added to somecommands and keyword descriptions. The topics “Volume copyproducts supported by Db2 Cloning Tool” on page 9, subsystemcloning “COPY command and keyword definitions” on page 430,and table space cloning “COPY command and keyword definitions”on page 573 were updated.

None

The DATA-SHARING keyword of the DB2RBLDBSDS commandwas clarified in “DB2RBLDBSDS command and keyworddefinitions” on page 480.

None



The topic “Cloning a Db2 subsystem” on page 99 was updated toadd an important note about Db2 address spaces.

None

Information was added to the topic “DB2UTILXCLEAN” on page515 about when to run the command.

None

A note was added to BCSCLEAN and COPY-BY-DS to explain howto clean up the target catalog after cloning with COPY-BY-DS. Thetopics “BCSCLEAN” on page 420 and “Planning for subsystemcloning by data set” on page 451 were updated.

None

The BIND-ON-TARGET parameter in the Db2 Cloning ToolSubsystem Cloning stored procedure was updated to describe fromwhere the DB2PLAN value is retrieved. The topic “Parameter filesand parameter descriptions” on page 150 was updated.

None

The work member name that is updated as part of the DB2SQLcommand was added to clarify the documentation. The followingtopics were updated:

v “Steps for Db2 offline cloning” on page 117v “Steps for Db2 offline cloning with removal of data sharing

members” on page 120

v “Steps for Db2 offline cloning with target becoming non-datasharing” on page 123

v “Steps for Db2 online cloning” on page 128v “Steps for Db2 online cloning with removal of data sharing

members” on page 134

v “Steps for Db2 online cloning with target becoming non-datasharing” on page 140

v “DB2SQL” on page 491

None

Additional information was provided about the minilog table that isrequired for log apply processing. The topics “Worksheets:Gathering parameter values for Tools Customizer” on page 25 andChapter 19, “Using LOG-APPLY to make consistent copies of tablespaces and index spaces,” on page 301 were updated.

None

The topics “Method 3: Using job templates in the target job” onpage 308, “COPY command and keyword definitions” on page 573,and “Report job details (optional)” on page 210 were updated toprovide information about several DDs that previously were notdescribed.

None

Warning message CKZ23526W was changed to an error message(CKZ23526E); documentation was updated throughout.

None

Message “CKZ57508I” on page 943 was added. PH02002

Message “CKZ11157E” on page 792 was modified. None

Deprecated functionsThis topic summarizes the Db2 Cloning Tool functions that were recentlydeprecated.


Deprecated parameters


For Db2 Cloning Tool Table Space Cloning, the EXTEND-TARGET-PBG-TABLESPACE command has been removed. When a targetpartition-by-growth (PGB) table space has less partitions that thesource PBG table space, ALTER ADD PARTITION syntax isautomatically generated. If your existing JCL contains theseparameters, you should remove them from the JCL.

PI92866

The following Db2 Cloning Tool Table Space Cloning parametersare obsolete. If your existing JCL contains these parameters, youshould remove them from the JCL.

v COPY command V7-MIGRATED-OBJECTS-PRESENT parameterv COPY command parameter SOURCE-PREFETCH-DATABASE-

LIST in the CATALOG-PREFETCH parameter

PI92862

What does Db2 Cloning Tool do?Db2 Cloning Tool has two components: Db2 subsystem cloning and Db2 tablespace cloning.

Db2 subsystem cloning:

v Clones automatically by using IBM FlashCopy, STK SnapShot, or EMCTimeFinder/Clone Mainframe Snap Facility's volume level support

v Uses any volume fast replication or onsite mirror tool

The cloned Db2 subsystem can be accessed from the same z/OS system. Thisincreases productivity in several ways:v Significantly reduces production online downtime and the costs associated with

cloning a Db2 subsystem with traditional tools.v Provides more availability and services to customers because Db2 no longer

needs to be shut down or conditioned the long traditional way.v Uses less personnel time to clone a Db2 subsystem – what used to take hours or

days now takes just minutes.v Allows management of larger storage environments with the same staff.v Provides quicker throughput and faster turnaround time.v Provides virtually 24x7 access to data.v Creates fast quality assurance and/or test environments.

Volume fast replication tools allow a group of data to be replicated within minutesto provide duplicate environments. However, these clones have an inherentproblem: the internal volume name, volume internals, and all data set namesreflect the source volume name.

Db2 Cloning Tool quickly solves this problem. Once the data is cloned orreplicated, Db2 Cloning Tool renames and catalogs the data sets on the clonedvolumes, fixes the volume internals, and updates the Db2 internals so the clonedDb2 subsystem can be accessed from the same MVS™ system. Db2 Cloning Toolprovides a vast improvement over existing methods. It supports entire Db2, Db2PeopleSoft, and Db2 SAP subsystems in either online or offline mode.

Db2 table space cloning:


v Clones automatically by using IBM FlashCopy, STK SnapShot, or EMCTimeFinder/Clone Mainframe Snap Facility's data set level support

v Uses any data set copy, fast or slow

The cloned Db2 table spaces can be cloned within the same or different z/OSsystem. This increases productivity in several ways:v Uses less personnel time to copy Db2 table spaces and associated manual tasks –

what used to take hours now takes just minutes.v Provides quicker throughput and faster turnaround time.v Provides virtually 24x7 access to data.v Creates fast refreshes of quality assurance and/or test environments

The remainder of this introductory topic addresses only Db2 subsystem cloningusing volume copies. For more information about Db2 Cloning Tool table spacecloning, refer to Chapter 11, “Db2 Cloning Tool Table Space Cloning overview,” onpage 177.

Cloning definitionsA clone is an exact copy, indistinguishable from the original.

Cloning is the act of replicating data, making it accessible, and then using thereplica in lieu of the original data for other purposes. Replication tools clone thedata by volume, and Db2 Cloning Tool makes the clone accessible.

Why clone a Db2 subsystem?There are several reasons to clone a Db2 subsystem.

Clone a Db2 subsystem:v To create a production quality assurance environmentv To move a group of end users to the cloned Db2 subsystem to lessen the

performance impact on the production systemv To give end users access to an application that is updated on a continual basisv To allow developers to begin changing the application for the next phase of code

updatesv To test new functions and features of SAP, or PeopleSoftv To run an online inquiry while batch runsv For data miningv For data warehousing

Can I clone a Db2 subsystem without Db2 Cloning Tool?A Db2 subsystem can be cloned without using Db2 Cloning Tool but it is acomplicated process that can take days, and requires using target volumes on aseparate LPAR.

By using Db2 Cloning Tool, you can clone a Db2 subsystem within minutes insteadof hours or days. Also, Db2 Cloning Tool does not require a separate LPAR.

Db2 supportA Db2 subsystem can be cloned in either an offline environment (Db2 is stoppedand started) or an online environment (using Db2 SUSPEND and RESUME, or via


consistent FlashCopy, SnapShot, or TimeFinder/Clone, or via consistent split orbreak mirror). There is no requirement for a separate LPAR.

Db2 Cloning Tool updates Db2 internal control information in the BSDS, directory,and Db2 catalog to reflect the target Db2 subsystem names.

Db2 data sharing groups and non-data sharing Db2 subsystems are supported.When cloning a Db2 data sharing group, you can optionally reduce the number ofDb2 data sharing members, or go from data sharing to non-data sharing.

Volume copy products supported by Db2 Cloning ToolDb2 Cloning Tool will rename and catalog data sets on target volumes created withany type of replication mechanism, where target volumes are exact replicas ofsource volumes.

If target volumes still have the source volume serial number (VOLSER), and arevaried offline, Db2 Cloning Tool can re-label and vary the target volumes online.

Restriction: "Exact Replicas": The only exception to a target volume being an exactreplica of its source volume counterpart is the internal volume serial number.Copies already partially modified are not acceptable – such as volume snaps viaSIBBATCH where the SYS1.VVDS and SYS1.VTOCIX names may have alreadybeen modified.

Storage blades

The fast replication copy services outlined in this section can be used to create thevolume copies used for Db2 system clones, or to create the data set copies used fortable space and index space refreshes. A storage blade represents fast replicationcopy services invoked directly by Db2 Cloning Tool.

Db2 Cloning Tool executes the DFSMSdss blade to issue IBM FlashCopy or STKSnapShot copy commands either by volume or by data set. When cloning usingADRDSSU, Db2 Cloning Tool specifies the DUMPCONDITIONING keyword.When cloning Db2 systems or table spaces that reside on EMC DASD, Db2Cloning Tool uses the EMC API to invoke TimeFinder/Clone to copy the data byvolume or by data set, and specifies the COPYVOLID=N and VARY_OFFLINE=Nkeywords. When cloning Db2 subsystems that reside on EMC DASD and useTimeFinder/Mirror, or that reside on Hitachi Storage Systems, an appropriateprocess is performed before Db2 Cloning Tool cloning automation is invoked and alist of copied storage volumes are passed to Db2 Cloning Tool for use in laterprocessing steps.

IBM storage blades

v IBM DFSMSdss bladev ADRDSSU utility invokedv Fast replication (preferred)v By volume or data setv FlashCopy V2 (IBM, EMC, HDS)v SnapShot (STK, Ramac)

EMC storage blades

v EMC TimeFinder


v TimeFinder/Clone Mainframe Snap Facility's volume level supportv EMC Consistency Technologyv TimeFinder/Clone Mainframe Snap Facility's data set level support

IBM FlashCopy, STK SnapShot, and EMC TimeFinder/Clone allow the creation ofwhat appears to be a copy of a volume, in a short period of time. The targetvolume of a copy will be a mirror image of the source volume, with the exceptionof the internal 'VOLSER', which remains as is, if the COPYVOLID option is notspecified. Db2 Cloning Tool requires the target VOLSER to remain as is, whichallows the target volume to remain varied online after the copy initiation, andtherefore negates the need for a CLIP (re-label) and VARY ON.

Because the logical image of a target volume may be modified before the copy isactually complete, the Db2 Cloning Tool rename step may be executed while thebackground copy is still in progress. Likewise, should the Db2 Cloning Toolprocess complete before a volume is completely copied, the application may alsobegin using volumes before the background copy is complete.

Onsite mirror tools by volume

Other cloning mechanisms, such as IBM PPRC, Hitachi ShadowImage, EMCTimeFinder/Mirror, Softek Replicator, or Innovation Data Processing FDRPAS,allow the creation of a point-in-time image of a volume by establishing a mirror,and then splitting the mirror once the target volume is synchronized with thesource volume. At the time of this publication, establishing and splitting mirrorsmust be accomplished with user-provided steps prior to execution of Db2 CloningTool.

Db2 Cloning Tool features and benefitsDb2 Cloning Tool provides solutions to many different types of problems.

Db2 Cloning Tool offers several unique and significant features that you can use toquickly clone your Db2 data for use in testing or other requirements:v Quickly fixes volume conflicts (VTOC, VTOCIX and VVDS) and then renames

and re-catalogs the target data sets to solve the data access problemv Offers extended rename capability to support Db2 log and BSDS desired namesv Db2 online or offline cloning in minutes instead of days, without a separate

imagev Automatic updating of Db2 internals to reflect renamed data setsv Db2 data sharingv Db2 data sharing many to less membersv Db2 support for either Db2 data sharing or from data sharing to non-data

sharing for maximum flexibilityv Provides automatic pairing of volume characteristics (SMS and non-SMS, or by

device size) that DFSMSdss doesn't dov Allows FlashCopy, SnapShot, or TimeFinder/Clone by VOLSER masks or entire

storage groups or any combination to eliminate the requirement for individualvolume specification

v Provides extensive SMS options that enable you to determine how the SMS classconstructs will be applied to your cloned data sets to ensure they are managedcorrectly


v Issuance of DFSMSdss commands or EMC TimeFinder/Clone commands withinthe product for ease of use

v Source volume ICF catalog information collection concurrent with FlashCopy,SnapShot, or TimeFinder/Clone initiation for rename integrity

v Early resumption of source volume activity to reduce outagesv Enhanced data set rename masking characters for flexibilityv User options to decide disposition of 'abnormal' data sets and catalog entriesv Multivolume data set and VSAM sphere integrity checks to prevent orphaned

datav Rename into existing populated ICF catalog(s) or a specific onev Faster cataloging than conventional meansv Test for termination of FlashCopy, SnapShot, or TimeFinder/Clone relationshipsv Mechanism to remove orphaned catalog entries from previous executionsv Simulate modes for most commands

Service updates and support informationService updates and support information for this product, including software fixpacks, PTFs, frequently asked questions (FAQs), technical notes, troubleshootinginformation, and downloads, are available from the web.

To find service updates and support information, see the following website:

http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/DB2_Tools_for_z~OS

Product documentation and updatesDb2 Tools information is available at multiple places on the web. You can receiveupdates to Db2 Tools information automatically by registering with the IBM MyNotifications service.

Information on the web

The most current version of this information is available on IBM KnowledgeCenter:

http://www.ibm.com/support/knowledgecenter

A PDF version of this information is available on the Db2 Tools ProductDocumentation web page; however, IBM Knowledge Center is updated morefrequently than PDF books. The Db2 Tools Product Documentation web page islocated at:

http://www.ibm.com/support/docview.wss?uid=swg27020910

IBM Redbooks® publications that cover Db2 Tools are available from the followingweb page:

http://www.redbooks.ibm.com


http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/DB2_Tools_for_z~OShttp://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/DB2_Tools_for_z~OShttp://www.ibm.com/support/knowledgecenterhttp://www.ibm.com/support/docview.wss?uid=swg27020910http://www.redbooks.ibm.com

The IBM Information Management System website shows how IT organizationscan maximize their investment in Db2 databases while staying ahead of today's topdata management challenges:

https://www.ibm.com/analytics/us/en/db2/db2-for-zos/

Receiving documentation updates automatically

To automatically receive emails that notify you when new technote documents arereleased, when existing product documentation is updated, and when new productdocumentation is available, you can register with the IBM My Notifications service.You can customize the service so that you receive information about only thoseIBM products that you specify.

To register with the My Notifications service:1. Go to http://www.ibm.com/support/mysupport2. Enter your IBM ID and password, or create one by clicking register now.3. When the My Notifications page is displayed, click Subscribe to select those

products that you want to receive information updates about. TheDb2 Toolsoption is located under Software > Information Management.

4. Click Continue to specify the types of updates that you want to receive.5. Click Submit to save your profile.

How to send your comments

Your feedback helps IBM to provide quality information. Send any comments thatyou have about this book or other Db2 Tools documentation [email protected]. Include the name and version number of the product andthe title and number of the book. If you are commenting on specific text, providethe location of the text (for example, a chapter, topic, or section title).

Accessibility featuresAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use a software product successfully.

The major accessibility features in this product enable users to perform thefollowing activities:v Use assistive technologies such as screen readers and screen magnifier software.

Consult the assistive technology documentation for specific information whenusing it to access z/OS interfaces.

v Customize display attributes such as color, contrast, and font size.v Operate specific or equivalent features by using only the keyboard. Refer to the

following publications for information about accessing ISPF interfaces:– z/OS ISPF User's Guide, Volume 1– z/OS TSO/E Primer– z/OS TSO/E User's GuideThese guides describe how to use the ISPF interface, including the use ofkeyboard shortcuts or function keys (PF keys), include the default settings forthe PF keys, and explain how to modify their functions.


https://www.ibm.com/analytics/us/en/db2/db2-for-zos/http://www.ibm.com/support/mysupportmailto://[email protected]

Chapter 2. Preparing to customize Db2 Cloning Tool

Before you start to customize Db2 Cloning Tool for the first time, determine all ofthe customization values that you need to specify during the customizationprocess, and familiarize yourself with all of the customization tasks.

Checklist for customization tasks

The following checklist lists and describes each significant customization step. Usethis checklist to guide you through the entire customization process.

Tip: Print the following checklist and the data set names and parameter valuesworksheets. Use the worksheets to record your values, and refer to them duringthe customization process.

Task Link to detailed instructions Status

Tools Customizer basics

Before you begin the customization process,familiarize yourself with Tools Customizerterminology, data sets, and other basic informationabout Tools Customizer.

“Tools Customizer terminology” on page 1049 and“Data sets that Tools Customizer uses duringcustomization” on page 1052

Software requirements

Verify that your environment meets the minimumsoftware requirements. To install and use Db2Cloning Tool, your environment must be runninga supported version of the z/OS operating systemand of Db2 for z/OS. Additionally, certain levelsof maintenance must be applied.

“Verify that your environment meets softwarerequirements” on page 15

SMP/E installation

Verify that Db2 Cloning Tool was installedcorrectly. Db2 Cloning Tool is installed by usingstandard SMP/E processing.

“Verify that Db2 Cloning Tool has been installedsuccessfully” on page 15

Verify that Tools Customizer for z/OS wasinstalled correctly. Tools Customizer for z/OS isinstalled by using standard SMP/E processing.

“Verify that Tools Customizer for z/OS has beeninstalled successfully” on page 16

Security requirements

Confirm that you have the required authorizationsto use Db2 Cloning Tool.

“Verify that your environment meets securityrequirements” on page 16

Function authorization requirements

Review the level of authority required to performcertain Db2 Cloning Tool functions.

“Function authorization requirements” on page 17

Use of the U.S.A. EBCDIC code set

Db2 Cloning Tool uses the U.S.A. EBCDIC codeset for specification and display of EBCDICcharacters and for the extended ACS maskingcharacters used for filtering. If the code tablesused by your installation are different, then youmay need to specify characters particular to yourcode table.

“Use of the U.S.A. EBCDIC code set” on page 19

Filtering pattern masks

13

Task Link to detailed instructions Status

Many Db2 Cloning Tool commands allowspecification of powerful filtering masks. Thesefiltering pattern masks can be specified withextended ACS masking characters, as specified inthe table. Your installation may need to specifydifferent masking characters to achieve the desiredresult if your code tables are different from theU.S.A. EBCDIC code set.

“Filtering pattern masks” on page 20

Gather data set names

During the customization process, you mustspecify data set names for Tools Customizer, Db2Cloning Tool, and several other items.

“Worksheets: Gathering required data set names”on page 21

APF authorization

The SCKZLOAD library must be APF authorized. “APF authorizing load libraries” on page 24

Gather parameter values

During the customization process, you mustspecify parameter values for Db2 Cloning Tool, forDb2, and for your LPAR.

“Worksheets: Gathering parameter values for ToolsCustomizer” on page 25

Customize Db2 Cloning Tool

Start Tools Customizer by running a REXX EXECfrom the ISPF Command Shell panel.

“Starting Tools Customizer” on page 57

Set up Tools Customizer user settings. If you arerunning Tools Customizer for the first time, youmust modify several user settings for yourenvironment. Otherwise, if the user settings thatyou have already established are still appropriate,skip this step.

“Modifying Tools Customizer user settings” onpage 58

Complete the steps in the appropriate customization roadmap based on the type of customization that you areperforming.

Customizing Db2 Cloning Tool for the first time

Follow this roadmap if you do not have acustomized version of Db2 Cloning Tool, and youneed to customize it for the first time.

“Roadmap: Customizing Db2 Cloning Tool for thefirst time” on page 63

Customizing a different version of Db2 CloningTool

Follow this roadmap if you previously customizeda version of Db2 Cloning Tool and want to use thesame parameter values to customize a differentversion.

“Roadmap: Customizing a new version of Db2Cloning Tool from a previous customization” onpage 64

Recustomizing Db2 Cloning Tool

Follow this roadmap if you already customizedDb2 Cloning Tool but want to change one or moreparameter values.

“Roadmap: Recustomizing Db2 Cloning Tool” onpage 65

Set up your environment prior to customizationPrior to beginning the customization process, ensure that your environment meetsall requirements, that you have installed all prerequisite software, and that youhave considered how you want to customize optional features.


Verify that your environment meets software requirements

The operation of Db2 Cloning Tool depends on the following software levels:v z/OS 2.1 and later.

Restriction: The following restrictions apply:– A source or target ICF catalog cannot be defined with extended addressability

or EATTR(OPT).– The VVDS on the volume where a source or target ICF catalog resides cannot

be defined with EATTR(OPT).– The VVDS on a source or target volume cannot be defined with EATTR(OPT).

v Db2 11 or Db2 12, until end of support for the given Db2 version.v Any available new PTFs. The same level of Db2 Cloning Tool maintenance is

required for all cloning jobs.v One or more of the cloning tools listed in section “Volume copy products

supported by Db2 Cloning Tool” on page 9, or slow copy utilities, such asDFSMSdss copy or Innovation Data Processing products.

v If you will use Db2 Cloning Tool’s stored procedure for subsystem cloning, theDb2 administrative task scheduler must be configured and available on the Db2systems where the stored procedure will be run.

v If you will use IBM FlashCopy for Db2 Cloning Tool Table Space Cloning,FlashCopy version 2 is required.

v If you plan to use fast replication via the DFSMSdss (ADRDSSU) COPY utility,review the following references prior to performing a cloning. The informationin these links might help you avoid cases when a FlashCopy target device maybe in conflict with a copy services status:– The Combining copy services operations topic in the z/OS DFSMS Advanced

Copy Services documentation.– The Preserve Mirror FlashCopy topic in the z/OS DFSMSdss Storage

Administration documentation.v If you will use the Db2 Cloning Tool ISPF interface, a minimum region size of

20000 KB is required.v If you will use Db2 Cloning Tool Table Space Cloning, UNIX System Services

access is required. The user ID under which the source and the target jobs runmust have an OMVS segment in its RACF® profile. To check whether the userID has an OMVS segment in its profile, use the following command:LU userid OMVS

To add an OMVS segment to a user ID's RACF profile, use the followingcommand:ADDUSER ddfuid OMVS(UID(nnn))

Verify that Db2 Cloning Tool has been installed successfully

See the Program Directory for IBM Db2 Cloning Tool for z/OS, GI10-8910-00, forinstallation instructions.

Chapter 2. Preparing to customize Db2 Cloning Tool 15

||

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.antg000/gr143.htmhttps://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/flcpprmir.htm

Verify that Tools Customizer for z/OS has been installedsuccessfully

Tools Customizer for z/OS is a component of IBM Tools Base for z/OS (5655-V93),which is available free of charge. Tools Customizer for z/OS provides a standardapproach to customizing IBM Db2 for z/OS Tools.

See the Program Directory for IBM Tools Base for z/OS, GI10-8819 for installationinstructions.

Verify that your environment meets security requirements

You can prevent unauthorized personnel from executing Db2 Cloning Toolcommands. To use Db2 Cloning Tool Table Space Cloning, specific authorizationsare also required.

In addition to user authorizations, some functions require other authorizations;refer to “Function authorization requirements” on page 17.

Authorizations required for Db2 Cloning Tool are:v Db2 Cloning Tool requires ALTER authority to both the source and target user

catalogs. By protecting ALTER authority, unauthorized personnel are preventedfrom executing the COPY and RENAME commands.

v Db2 Cloning Tool requires UPDATE authority to the target data sets. Byprotecting UPDATE authority, unauthorized personnel are prevented fromexecuting the DB2UPDATE command.

v The COPY command requires authorization to ADRDSSU ADMIN. By protectingADRDSSU ADMIN, unauthorized personnel are prevented from executing theCOPY command. This only applies for FlashCopy where ADRDSSU is used.

v The COPYCHECK command could be used by an unauthorized person using anauthorized person's journal file. To prevent this, secure the journal files.

Authorizations for Db2 Cloning Tool Table Space Cloning are:v SELECT authority on the Db2 catalog tables for both source and target

subsystemsv EXECUTE authority on the CKZPLAN on both source and target subsystemsv DISPLAYDB authority on both source and target databasesv STOPDB authority on the target databasev STARTDB authority on the target databasev ALTER authority for all target tables with identity columnsv If FUZZY-COPY(Y) is used to not stop the source, and ADRDSSU is used, then

RACF authority for “TOLERATE(ENQF)” is requiredv If FUZZY-COPY(N) (the default) is used, then STOPDB and STARTDB authority

for the source database is required

If your site uses ACF2 to restrict TSO command use, you may need to add theTSO commands that Db2 Cloning Tool uses to the ACF2 Command Limiting table.The TSO commands that Db2 Cloning Tool uses are CKZARGSZ, CKZ2MAIN,CKZ00500, and CKZ00600.


Function authorization requirementsThe level of authority required to perform certain Db2 Cloning Tool SubsystemCloning and Db2 Cloning Tool Table Space Cloning is detailed in this topic.

For Db2 Cloning Tool subsystem or volume cloningv Db2 Cloning Tool COPY and RENAME commands require ALTER authority to

both the source and target user catalogs. Db2 Cloning Tool does NOT update thesource catalog but requires ALTER authority to access the catalog via directaccess.– The source ICF catalog(s) requires ALTER because an IDCAMS VERIFY and

an IDCAMS EXAMINE INDEXTEST NODATATEST is done prior to readingit to ensure the source catalog is not broken.

– The target ICF catalog(s) requires ALTER because it is opened and updatedusing a routine that manages catalog updates.

v Db2 Cloning Tool COPY command when using DATA-MOVERPGM(ADRDSSU) may require the user ID running the command to have specificaccess to STGADMIN profiles in the FACILITY class.– The ADMINISTRATOR operand is always specified when invoking

DFSMSdss. To avoid WTORs, ADRDSSU ADMINISTRATOR is used to gainpermission to overlay the target volume VTOCIX and/or VVDS during theCOPY process. Because the ADMINISTRATOR operand is generated, the userID running COPY must have READ access to FACILITY class profileSTGADMIN.ADR.STGADMIN.COPY.

– If FCSETGTOK is specified, READ access is needed to FACILITY class profileSTGADMIN.ADR.COPY.FCSETGT if it exists.

– If FCTOPPRCPRIMARY is specified, READ access is needed to FACILITYclass profile STGADMIN.ADR.COPY.FCTOPPRCP if it exists.

– If FlashCopy is being used, READ access is needed to FACILITY class profileSTGADMIN.ADR.COPY.FLASHCPY if it exists.

– If CONSISTENT(YES) is specified, READ access is needed to FACILITY classprofiles STGADMIN.ADR.COPY.FCFREEZE andSTGADMIN.ADR.CGCREATE if they exist.

– If the CONCURRENT option is being used, READ access is needed toFACILITY class profile STGADMIN.ADR.COPY.CNCURRENT if it exists.

v If Db2 Cloning Tool is going to relabel the target volumes, ICKDSF REFORMATrequires RACF volume access of ALTER to RACF class DASDVOL or READaccess to FACILITY class profile STGADMIN.ICK.REFORMAT. Db2 Cloning Toolwill relabel the target volumes as part of COPY when VOLPAIRSDEVN orVOLPAIRSDEVN-DDN is used, or as part of VOLOPTIONS whenSOURCECLIP, TARGETOFFLINECLIP, or TARGETUNCLIP are used.

v Db2 Cloning Tool RENAME command invokes ICKDSF to rebuild the VTOCIX,if VTOCIX_REBUILDER = IBM is specified in CKZINI or the volume is an ExtendedAddress Volume. ICKDSF requires RACF volume access of ALTER to RACFclass DASDVOL or READ access to FACILITY class profileSTGADMIN.ICK.BUILDIX. If the default, VTOCIX_REBUILDER = MSC, is specifiedin CKZINI, ICKDSF is not used, unless the volume is an Extended AddressVolume for which ICKDSF will always be used to rebuild the VTOCIX.

v Db2 Cloning Tool COPY-BY-DS command requires READ authority to the sourcedata sets and ALTER authority to the target data sets.

v If Db2 Cloning Tool RENAME has NOTRENAMED(DELETE) in effect, READ access toFACILITY class profile STGADMIN.IGG.DLVVRNVR.NOCAT is required.


v Db2 Cloning Tool DB2UPDATE command requires authority to the target datasets.

v Db2 Cloning Tool COPYCHECK command requires UPDATE to the journal file.v Db2 Cloning Tool FINDUCATS command invokes DCOLLECT to identify

ALIAS names of the source volume data sets in order to identify the correctsource user catalogs. DCOLLECT controls access to the DCOLLECT function, byissuing a security (RACF) check for a facility class profile ofSTGADMIN.IDC.DCOLLECT. If this profile exists, then Read authority isnecessary.

v Db2 Cloning Tool DB2FIX command requires either Db2 install SYSADM orSYSADM2 authority.

v Db2 Cloning Tool DB2SQL command requires either Db2 install SYSADM orSYSADM2 authority.

v Db2 Cloning Tool DB2SETLOG command requires authorization to connect tothe Db2 subsystem and to issue Db2 SET LOG commands.

v Db2 Cloning Tool DB2START command requires authorization to issue z/OSSTART Db2 commands and to connect to the Db2 subsystem. When theSPECIAL or MAINT keyword is used, it requires either Db2 install SYSADM orSYSADM2.

v Db2 Cloning Tool DB2STOP command requires authorization to connect to theDb2 subsystem and issue the Db2 STOP DB2 command. When the Db2subsystem is running in maintenance mode, it requires either Db2 installSYSADM or SYSADM2.

v Db2 Cloning Tool RENAME command requires authorization to create an EMCSconsole and issue z/OS MODIFY CATALOG commands. Update authorizationto the VVDS data sets on the target volumes is also required.

v Db2 Cloning Tool DB2UPDATE command (if DB2XCFCLEAN(Y) is specified)requires authority to clean up XCF structures. The ability to clean up XCFstructures is controlled with profiles in the FACILITY class with names ofIXLSTR.structurename. If profiles exist that cover the target Db2 structures, thenUPDATE access is necessary.

v Db2 Cloning Tool DB2XCFCLEAN command requires authority to clean up XCFstructures. The ability to clean up XCF structures is controlled with profiles inthe FACILITY class with names of IXLSTR.structurename. If profiles exist thatcover the target Db2 structures, then UPDATE access is necessary.

v Db2 Cloning Tool DB2GETBACKINFO command requires authority to issueHSM LIST COPYPOOL commands. The ability to issue HSM LIST COPYPOOLcommands is controlled with profiles in the FACILITY class with names ofSTGADMIN.ARC.LC.copypoolname. If profiles exist that cover thecopypoolname being used, then READ access is necessary.

v Db2 Cloning Tool RESTORE-FROM-DUMPTAPES command requires thefollowing:– READ access to HSM dump tapes (for example, TAPEVOL profile HSMHSM,

or READ access by data set name).– RACF volume access of ALTER to RACF class DASDVOL.– READ access to FACILITY class profile STGADMIN.ICK.REFORMAT.– READ access to STGADMIN.ADR.STGADMIN.RESTORE for the target

volumes.v Db2 Cloning Tool BCSCLEAN command requires READ authority to profiles in

the FACILITY class with names of STGADMIN.IGG.DIRCAT andSTGADMIN.IGG.DELETE.NOSCRTCH.


For Db2 Cloning Tool Table Space Cloningv SELECT authority on the Db2 catalog tables is required for both source and

target subsystems.v EXECUTE authority on the CKZ plan is required on both source and target

subsystems.v DISPLAYDB authority is required on both source and target databases.v STOPDB authority is required on the target database.v STARTDB authority is required on the target database.v ALTER authority is required for all target tables with identity columns.v If FUZZY-COPY(Y) is used to not stop the source, and ADRDSSU is used, then

RACF authority for “TOLERATE(ENQF)” is required.v If FUZZY-COPY(N) (the default) is used, then STOPDB and STARTDB authority

for the source database is required.v If the TCP/IP server job is run as a started task, SYSCTL authority must be

granted to the started task's user ID on the target Db2 subsystem.

Use of the U.S.A. EBCDIC code setDb2 Cloning Tool uses the U.S.A. EBCDIC code set for specification and display ofEBCDIC characters and for the extended ACS masking characters used for filtering.

If the code tables used by your installation are different, then you need to enter theEBCDIC character peculiar to your code tables that results in the binary value forthe EBCDIC character specified in the product manuals.v Data supplied as input to batch programs or input to ISPF panels:

For product code shipped in binary, when specifying input where the producttakes special action based on specific characters, you must enter the EBCDICcharacter peculiar to your code tables that results in the binary value for theEBCDIC character specified in the product manuals, according to the U.S.A.EBCDIC code set.For example, if an exclamation mark ( ! ) is called for, and your code tables donot translate the ! character to a hexadecimal 5A, you must enter the characterthat your code table will translate to a 5A.

v Distributed ISPF panels:Do not change distributed ISPF panels. Program code may reference ISPF panelattribute bytes. A panel change that affects an attribute byte may cause aprogram error.

v Product output:Depictions of product output shown in the product manuals are based on theU.S.A. EBCDIC code set. Actual output may vary if your EBCDIC code tablesare different.

v Extended ACS masking characters:Your installation may need to specify different masking characters to achieve thedesired result if your code tables are different from the U.S.A. EBCDIC code set.For more information about extended ACS masking characters, see “Filteringpattern masks” on page 20.


Filtering pattern masksMany commands allow specification of powerful filtering masks. These filteringpattern masks can be specified with extended ACS masking characters, as specifiedin the table.

Note: Your installation may need to specify different masking characters to achievethe desired result if your code tables are different from the U.S.A. EBCDIC codeset.

Table 1. Filtering pattern masks

Mask Hex Description

* 5C A single asterisk (*) represents 0–ncharacters. It can be used before and/orafter an item to designate a wildcardcharacter position. You cannot use anasterisk in the middle portion of a singleitem (except for data set names). Use thepercent sign (%) character for that purpose.

Example:*PROD

In this example, an item is selected if thelast four characters are PROD regardless ofthe starting characters. Using a singleasterisk character before and after an item(i.e. *ZREM*) means that item is to beselected if any character string matchesZREM in its name.

% 6C A percent sign (%) denotes asingle-character placeholder value, whichcan be alpha-numeric or any specialcharacter. The percent sign can be used inany position order.

Example:CRM%%ER6

In this example, an item is selected if it iseight characters in length, the first threecharacters are CRM, and the last threecharacters are ER6. The two middleplaceholder values (%%) can be anycharacters.

< 4C Similar to the percent sign (%) value, the"less than" character (

Table 1. Filtering pattern masks (continued)

Mask Hex Description

> 6E Similar to the percent sign (%) value, the"greater than" character (>) denotes aplaceholder value for only numeric characters.The > character can be used in any positionorder.

Example:CR>>ER*

In this example, an item is selected if thefirst two characters are CR, the third andfourth characters are numeric, and the fifthand sixth characters are ER. Any remainingcharacters are also allowed.

** 5C5C Using two asterisks (**) allows compatibilitywith standard ACS and DFSMSdss filteringmasks. Only used for partially qualified dataset names. The * or ** characters can beused in any qualifier position to denote awildcard node.

Example:CRFM*.*VER.**

In this example, a data set entry is selectedif it has at least two qualifiers, the firstqualifier starts with CRFM, and the secondqualifier ends with VER. Any remainingqualifiers are also allowed.Note: As with common data set namemasking, any combination of *, **, %, <and/or > characters can be used for theitem mask value.

! 5A Similar to the percent sign (%) value, theexclamation point character (!) denotes aplaceholder value for only national characters,based on the U.S.A. EBCDIC code set. Referto the topic “Use of the U.S.A. EBCDICcode set” on page 19 for more information.The exclamation point (!) can be used inany position order.

National characters (based on the U.S.A.EBCDIC code set) are: @ # $

Worksheets: Gathering required data set namesIdentify and record the data set names that will be used during the customizationprocess and make sure that requirements for certain data sets are met.

Data set names for Tools Customizer

Identify and record the following Tools Customizer data set names:

Data set name Description Special requirements Your data set name

SCCQDENU Metadata library for ToolsCustomizer



SCCQLOAD Executable load modulelibrary for ToolsCustomizer

SCCQMENU ISPF messages for ToolsCustomizer

SCCQPENU ISPF panels for ToolsCustomizer

SCCQSAMP Sample members for ToolsCustomizer

SCCQTENU Table library for ToolsCustomizer

You must have write accessto this data set.

Data set names of Db2 Cloning Tool

Identify and record the following Db2 Cloning Tool data set names. During thecustomization process, you will enter the following values on panel CCQPPRD.


Installation high-levelqualifier

The high level qualifier ofthe Db2 Cloning Toolinstalled libraries.

Installation high-levelqualifier of previous releaseof Db2 Cloning Tool

The high level qualifier ofthe previous release of Db2Cloning Tool installedlibraries.

Only needed if upgradingfrom a previous release.

SCKZDBRM DBRM library for Db2Cloning Tool

SCKZDENU Metadata library for Db2Cloning Tool

SCKZJCL Sample members for Db2Cloning Tool

SCKZLOAD Executable load modulelibrary for Db2 CloningTool

You must APF authorizethis data set.

SCKZMENU ISPF messages for Db2Cloning Tool

SCKZPARM Parameter library for Db2Cloning Tool

SCKZPENU ISPF panels for Db2Cloning Tool

SCKZSLIB Skeleton library for Db2Cloning Tool

Data set names of other libraries

Identify and record the following data set names. During the customizationprocess, you will enter the following values on the Setup panel.



Discover output data set Contains the output that isgenerated when you runthe Db2 Cloning ToolDiscover EXEC.

The Db2 CloningToolDiscover EXECretrieves the metadata andvalues for the parametersfrom a previouscustomization of Db2Cloning Tool.

The default name of thedata set isDB2TOOL.CCQ110.DISCOVER. You canchange the default value onthe Tools CustomizerSettings panel or theDiscover CustomizedProduct Information panel.


Data store data set Contains product, LPAR,and Db2 parameter values,and Db2 entry associations.Tools Customizer uses thisdata set to permanentlystore all information that isacquired about the product,Db2 subsystems, and LPARwhen you customizeproducts on the local LPAR.

The default name of thedata set isDB2TOOL.CCQ110.DATASTOR. You canchange the default value onthe Tool CustomizerSettings panel.




Product customizationLibrary

Contains the customizationjobs that Tools Customizergenerates for Db2 CloningTool.

To customize Db2 CloningTool, submit the membersof the data set in the orderin which they are displayedon the Finish ProductCustomization panel. Thedata set naming conventionis:

hlq.$LPAR-name$.xyzvrm

where:

v hlq is the value of theCustomization libraryqualifier field on theTools CustomizerSettings panel(CCQPSET)

v LPAR-name is thefour-character LPARname

v xyzvrm is the three-letterproduct identifier withthe version, release, andmodification level

For example, the data setname might beDB2TOOL.PRODUCT.CUST.$MVS1$.XYZ410.


APF authorizing load librariesSome of the programs in Db2 Cloning Tool load libraries must be APF-authorizedto run.

About this task

The SCKZLOAD library for Db2 Cloning Tool must have APF authorization.Consult your Systems Programmer to have this library added into the APF list andensure appropriate access controls have been established

Procedure

db2 cloning tool user's guide - ibm.com · v ersion 3 release 2 ibm db2 cloning t ool for z/os...

Documents