1 © 2013 IBM Corporation
IMS Cloning Tool
IMS Regional User GroupColumbus and DetroitMarch 2013
Raquel CarvalloIMS Tools – Technical Sales [email protected]
2 © 2013 IBM Corporation
Topics for Today’s Meeting
IMS Cloning Tool– How Does It Work?
– How Do I Use It?
3 © 2013 IBM Corporation
Host-Based Data Copy Options
• Volume copy options
– DFSMSdss (IBM)
– FDR (Innovation Data Processing)
– TDMF (IBM)
– FDRPAS (Innovation Data Processing)
• Data set copy options
– DFSMSdss (IBM)
– FDR (Innovation Data Processing)
“Traditional” data copy processes use host based CPU and I/O facilitiesMore costly and slower than storage-based fast replication
Host-basedCopy Process
An “expensive” use of processing power
4 © 2013 IBM Corporation
Storage Processor = Storage + Processor
• Storage
– Non-volatile
– Computer components and recording media that retain digital data
• Processor
– Computing system that executes software programs
• Storage Processors
– Enable data movement through host-based API
– Allows CPU reduction from host-based systems
Host based APIs
5 © 2013 IBM Corporation
Application and Database Storage Integration
MainframeApplication and
Database Systems
Storage-AwareData
Management Tools
Application and Database Management
Domain
Storage Administration and
Business ContinuityDomain
“Having storage-aware tools” provide for: • Organizational Integration• New Backup Methods• New Recovery Strategies• Business Recovery Monitoring• Disaster Restart Solutions• Cloning Automation
SourceData
Backup,Clone,
DR
6 © 2013 IBM Corporation
Cloning – Some Terminology
• A clone is an exact replica
– Clone an IMS system by volume
– Clone an IMS database by data set
• IMS system cloning and database refresh
– The act of replicating the data, making the replica accessible, and then using the replica in lieu of the original data
• IMS system cloning automation
– Clones a complete IMS system including all its databases.
– Creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes
– Less than 30 minutes (average when using Fast Replication)
• IMS database refresh automation
– Refreshes specific databases
7 © 2013 IBM Corporation
IMS ‘System’ Cloning - Today
Production LPAR
User Catalogs
IMS001
IMS System Data Sets
IMS002
Application Libraries
IMS003
RECON Data Sets
IMS004
Data Base Data Sets
IMS005
Test LPAR
User Catalogs
IMS001
IMS System Data Sets
IMS002
Application Libraries
IMS003
RECON Data Sets
IMS004
Data Base Data Sets
IMS005
Two reads of the data
8 © 2013 IBM Corporation
IMS ‘Database’ Cloning – How you do it ?
Production IMS
Application Libraries
RECON Data Sets
Data Base Data Sets
IMS System Data Sets
Test IMS
Application Libraries
RECON Data Sets
Data Base Data Sets
IMS System Data Sets
Unload Load
Image Copy
Recovery
Index Rebuild
???
z/OS
9 © 2013 IBM Corporation
Production Database
IMSCloneIMS
Cloning ToolCloning
Automation
SourceDatabaseVolumes
CloneDatabaseVolumes
• Performs IMS system cloning automation• Takes an existing IMS system (complete installation
and system generation process completed) and creates a new(“cloned”) IMS system from it without having to repeat the entire installation and system generation processes
• You benefit by: Simplfying IMS cloning processes Reducing cloning time and administration costs
• Performs rapid volume reconditioning and dataset renaming on cloned volumes to solve the data access challenges
• Target volumes have different volser label than the source volume
• Renames the VTOC, VTOCIX, and VVDS to match the target volume
• Renames and catalogs all data sets to a new HLQ
• Adjusts target IMS to accommodate and accept the cloned data
• IMS RECONs, PROCLIB, JOBS, JCL, MDA members
Create IMS Systems Using IMS Cloning Tool Automation
10 © 2013 IBM Corporation
Production Database
IMSCloneIMS
Cloning ToolCloning
Automation
SourceDatabaseVolumes
CloneDatabaseVolumes
• Updates done in IMS cloned system• RECONs data sets
Data set names, IMS subsystem IDs, and VOLSERs are updated in the following RECON records:
→ header record, database data set records, online log records, and back-out records
Optionally, the following RECON records are updated if they were on volumes that were cloned:
→ image copy records, change accumulation records→ system log data set (SLDS) records→ recovery log data set (RLDS) records
• IMS PROCLIB, JOBS and user JCL libraries New values for IMSID, VOLSERS, and data set names in the JCL members
within these libraries
• MDA (MVS Dynamic Allocation) members for databases or system data sets, are updated to reflect the new data set names. Updates include:
The RECON data sets Online Log data sets (OLDS) Write-ahead data sets (WADS)
• If IMS data sharing is involved, each additional IMS data sharing member is updated
• Leverages fast replication facilities to clone data
• Data can be cloned while online or offline
Create IMS Systems Using IMS Cloning Tool Automation
11 © 2013 IBM Corporation
What makes IMS Cloning Tool so “fast”?
• Host-based Copy Options
– Data copy processes use host based CPU and I/O facilities
– Slower than storage-based fast replication
– Volume copy options for IMS system cloning
TDMF (IBM), FDRPAS (Innovation Data
Processing) DFSMSdss (IBM) FDR (Innovation Data
Processing)
– Data set copy options for IMS database refresh
Any traditional data set copy processes
• Fast Replication Data Copy Options
– Fast copy processes offloaded to the storage processor
– No host CPU or I/O resources
• Data set based fast replication options for IMS database refresh
– Data Set FlashCopy (IBM,EMC,HDS)
• Volume based fast replication options for IMS system cloning
– FlashCopy (IBM,EMC,HDS)
– SnapShot (IBM,STK)
– TimeFinder/Clone Volume Snap or Snap (EMC)
– Mirror processes PPRC (IBM,EMC,HDS) TimeFinder/Mirror, SRDF (EMC) ShadowImage HUR (HDS)
– Data set SnapShot (IBM,STK)
– TimeFinder/Clone Data set Snap (EMC)
Host-based
Copy Process
Fast ReplicationCommands from z/OS
12 © 2013 IBM Corporation
IMS Cloning - Methods
• IMS System Skeleton– Clones an IMS system without cloning any data by volume
Recommended for IMS new version migration activities
– The replicated system is accessible and is usable in lieu of the original system without requiring a system generation
• IMS Full System Clone– Copies an IMS system WITH the databases by volume
– The replicated system is accessible and is usable in lieu of the original system without requiring a system generation
– Less than 30 minutes average when using “Fast Replication”
• IMS Data Refresh– Copies individual or groups of databases by data set
13 © 2013 IBM Corporation
Production Database
IMSCloneIMS
IMS Cloning ToolCloning
Automation
SourceSystem
Volumes
CloneSystem
Volumes
• Performs IMS system “skeleton” cloning automation– System, no databases
– Takes an existing IMS system and creates a new, or cloned, IMS system from it
– Do not need to repeat the entire installation and system generation processes
– Simplifies IMS cloning processes
– Reduces cloning time and administration costs
• Leverages fast replication facilities to clone data– Can also leverage traditional Host Based copy options
• Performs rapid volume reconditioning and data set renaming on cloned system volumes to solve the data access challenges
– Target volumes retain their target volume label
– Renames the VTOC, VTOCIX, and VVDS to match the target volume
– Renames and catalogs all data sets to a new HLQ
• Adjusts target IMS to accommodate and accept the cloned data
– IMS RECONs, PROCLIB, JOBS, JCL, MDA members
Using IMS Cloning Tool - IMS System Skeleton
14 © 2013 IBM Corporation
IMSSystem Volumes
IMSTarget
IMS Clone
Volumes
IMSSource
IMS Cloning Tool Database Refresh
Automation
• Performs automated IMS database refresh operations
– Fast refresh of IMS databases– IMS DB support (FF, HALDB, DEDB)
• Verifies source and target database compatibility
• IMS data copied using storage-based data set fast-replication
– Target takes up the same amount of space as the source
• Performs target system meta-data management
– Updates DBRC information for target databases
• Performs HALDB cloning with integrity– Updates the target IMS RECON– Primary/Secondary indexes and ILDS can be copied to eliminate
rebuild time– Manages partition number and gap sequencing
Using IMS Cloning Tool - IMS Database Refresh
Production Database
15 © 2013 IBM Corporation
IMS Database Refresh - What it can deliver to you
• Quickly copies a specific database or set of databases for targeted testing. – Flexibility to select exactly what database you need thus saving space and
time
• Application Testing Before a major upgrade to the application To debug an error that only happens in production Create consistent test environments between phases of the testing
cycle Test an application in conjunction with system
parameter tweaking
• Database Testing HALDB conversions can be complex and affect database
availability Run performance and integrity utilities