IMS Cloning Tool Migrate to New Releases of IMS - IMS UG May 2012 DFW
Upcoming SlideShare
Loading in...5
×
 

IMS Cloning Tool Migrate to New Releases of IMS - IMS UG May 2012 DFW

on

  • 575 views

 

Statistics

Views

Total Views
575
Views on SlideShare
575
Embed Views
0

Actions

Likes
0
Downloads
11
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Now we’ll get into IMS Cloning Tool subsystem cloning. IMS Cloning Tool takes an existing IMS system and its databases and creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes __________________________________________________________ It leverages volume-based fast replication facilities to copy the data quickly, speed up the cloning process, and save host CPU and I/O resources __________________________________ After the volumes have been copied, IMS Cloning Tool performs volume reconditioning on the copied volumes so they can be brought on-line to the same or different z/OS LPAR solving the challenges discussed in the previous slides. Data set names are changed on the copied volumes so they can be accessed from the cloned IMS system without z/OS ICF catalog conflicts. The volume reconditioning and data set renaming processes are performed fast and efficiently to reduce overall IMS system cloning time. __________________________________ After the volumes are copied, reconditioned, and data sets renamed, then the cloned IMS meta-data must be adjusted to accommodate the copied data. The IMS RECONS, IMS PROCLIB and JOBS libraries, MDA, members, etc. must be updated to reflect the new data set names in the cloned IMS system. Saves system IO and resources!!!
  • 05/23/12 Steps IMS cloning tool will perform
  • 05/23/12 IMS Cloning Tool requires the target database definitions be set up in advance if they don’t exist. One way to accomplish this is to create an IMS system skeleton. A cloned IMS system skeleton can be created such that the cloned IMS system contains all database definitions. The database data is not initially copied, it is copied when a database refresh operation is performed after the cloned IMS skeleton is created.
  • IMS Cloning Tool leverages fast replication data set facilities to copy the data quickly, speed up the refresh process, and save host CPU and I/O resources. Data can be copied while the source database is running or stopped. Slow copy mechanisms can also be used to copy the data but it negates the benefits of high availability
  • The left side of the slide represents the source IMS, in this case, a Production IMS system. The right side of the slide represents the target IMS system – where you want to refresh the IMS data to. Step 1 – is on the target side. The definitions need to exist in advance Step 2 - The source databases to be refreshed are selected by database name. IMS Cloning Tool finds the IMS subsystem name and determines if it is active, then it finds the source and target databases and indexes (if the targets already exist), determines the data set names for each database and index and then verifies their existence Step 3 - Checks are performed to ensure the characteristics of the source and target IMS databases are compatible. IMS Cloning Tool gets the attributes of the IMS databases and indexes from the source and target IMS RECON, ACBLIB, and MDALIB data sets. Some characteristics that are checked include: Type, Access Method, Number of segments, data set groups, Blocksize, Randomizer Parameters, etc. Step 4 - The source and target databases are stopped (DBR commands automated). Optionally, the source databases can be copied while they are running to create a fuzzy copy. However, the fuzzy copy option does not guarantee transactional integrity on the refreshed copy. Step 5 – Data sets are copied. For sites using FlashCopy or SnapShot, IMS Cloning Tool will invoke these copy facilities. For sites using EMC TimeFinder or Hitachi ShadowImage, IMS Cloning Tool will produce the output files describing source and target data set information so users can create their own data set fast-replication job streams. Step 6 - The source IMS databases are started unless a fuzzy copy was specified in step four. The following steps will be performed on the target IMS system. Step 7 - If the target databases are registered to DBRC, IMS Cloning Tool updates the target IMS RECONS Step 8 – Start target databases Step 9 - The refreshed IMS databases are now available for application or offload work. Step 7 - Detail LIST.DB – extract information (on both source and target) DELETE.DB - to remove recovery history (on target) to prevent invalid recovery processes INIT.DB, INIT.DBDS, INIT.PART, and INIT.AREA to redefine target databases and data sets CHANGE.DB to: a. sets IC RECOMMENDED flag on for target databases and indexes / b. HALDB (copy and shadow) make sure target is on same sets
  • IMS Cloning Tool takes an existing IMS system and its databases and creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes __________________________________________________________ It leverages volume-based fast replication facilities to copy the data quickly, speed up the cloning process, and save host CPU and I/O resources __________________________________ After the volumes have been copied, IMS Cloning Tool performs volume reconditioning on the copied volumes so they can be brought on-line to the same or different z/OS LPAR solving the challenges discussed in the previous slides. Data set names are changed on the copied volumes so they can be accessed from the cloned IMS system without z/OS ICF catalog conflicts. The volume reconditioning and data set renaming processes are performed fast and efficiently to reduce overall IMS system cloning time. __________________________________ After the volumes are copied, reconditioned, and data sets renamed, then the cloned IMS meta-data must be adjusted to accommodate the copied data. The IMS RECONS, IMS PROCLIB and JOBS libraries, MDA, members, etc. must be updated to reflect the new data set names in the cloned IMS system.
  • The left side of the slide represents the source IMS, in this case, a Production IMS system. The right side of the slide represents the target or cloned IMS system. On the source, Step 1 --- The disk volumes that make up the production IMS system are identified by using specific VOLSER IDs, VOLSER mask, or SMS storage group. Step 2-4 ---To gain a static copy of your data and the source ICF catalog entries, there are several options: a. IMS is up and the IMS log is suspended (this is proprietary code in IMS Cloning Tool and it works similar to DB2’s log suspend.) b. IMS is up and can use either IBM FlashCopy, FlashCopy Manager, or EMC consistency group support ----With either of these techniques, IMS Cloning Tool immediately invokes a DFSMSdss Copy to issue IBM FlashCopy or SnapShot commands to copy the data instantly and backs up the ICF catalogs that point to the data sets being copied. ----When cloning IMS systems that reside on EMC or Hitachi Storage Systems, an appropriate storage-based fast-replication process is performed before the IMS Cloning Tool cloning automation is invoked and a list of copied storage volumes is passed to IMS Cloning Tool for use in later processing steps. ----Once the copy is complete which is in seconds, IMS Cloning Tool can resume the source log. At this point, we are done using the production IMS system. The following steps will be performed on the target or cloned IMS system shown on the right side of the slide Step 5 - The data sets on the target volumes are renamed and cataloged to a new high level qualifier. Data sets are renamed to eliminate duplicate data set names from a z/OS ICF catalog perspective and to allow the new data set names to be integrated into the cloned IMS system. The cloned IMS data sets can then be used on the same LPAR but integrated into a different IMS system using different data set names. Step 6 – The next step is to update the cloned IMS system data sets with the new names and volsers. I’ll show you what is updated in the cloned IMS when we get to the next slide. Step 7 - The cloned IMS system is then started and can be used to run offload or application work.
  • IMS Cloning Tool simplifies and automate database administration tasks so DBA’s can concentrate on business-critical work. They integrate and coordinate the database and storage activities so fast replication can be executed in a safe and transparent manner ________________________________________________________ So DBA’s can provide the high availability solutions their companies require. IMS Cloning Tool clones IMS systems fast and refreshes databases quickly so that clones can be available in significantly less time. ________________________________________________________ IMS Cloning Tool integrates storage-based fast replication to provide fast and non-intrusive cloning and refresh operation while saving valuable host CPU and I/O utilization costs.

IMS Cloning Tool Migrate to New Releases of IMS - IMS UG May 2012 DFW IMS Cloning Tool Migrate to New Releases of IMS - IMS UG May 2012 DFW Presentation Transcript

  • Data Management ToolsIMS Cloning ToolSmooths the IMS migration path! Rosemary Shay Quality Assurance and Product Specialist for IMS Tools, Rocket Software Email: rshay@rocketsoftware.com Ron Bisceglia Development for Database Tools: Backup & Recovery for z/OS, Rocket Software Email: rbisceglia@rocketsoftware.com © 2012 IBM Corporation M
  • Data Management Tools – IMS ToolsMigrating to IMS 12? Do you want to avoid surprises and delays in the upgrade process? IBM’s IMS Cloning tool can help by offering multiple levels of testing environments that can be created with minimum skilled resources, minimum time and no interruption to your production systems. Creating exact copies of production quickly for high quality testing reduces the risk of impacting critical applications during the migration process.2 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsAgenda Problems and Concerns Test environments needed for success Test environments created with IMS Cloning Tool IMS Cloning Tool Step by Step test environment creations3 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsProblems and Concerns Migrating to a new version of IMS  Upgrading to a new IMS version is a high impact effort. – An issue could be visible system wide or company wide  It is difficult to measure the impact or savings that implementing new features of the new IMS without a production like environment.  There is only one Sandbox but many production IMS configurations.  Sandbox environments used to initially test IMS version release software is rarely kept in sync with production – This is due to resources issues of time, money, space, manpower, and availability of required skills.4 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsProblems and Concerns Creating and Maintaining Test Environments  Creating test environments requires a lot of host CPU and I/O – Running Volume copies – Running the UNLOAD/RELOAD or IMAGE/RECOVERY or dataset copies  Cloning is a complicated process – Putting up a brand new IMS system environment • New PROCLIBs and JOBs with all new names • All new sysgens, RECONS, MDA (MVS Dynamic Allocation) members • Constantly comparing libraries to insure a quality copy process – Copying databases • UNLOAD/RELOAD jobs possible outage for source databases • IMAGE/RECOVERY jobs possible pointer error on target or source outage – Maintaining the cloned environment5 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsProblems and Concerns IMS Cloning Tool Delivers Solutions  Leverages Storage-based fast replication – Very fast -13TB in .4 seconds - no outage of source system – Large systems cloned in less then 30 minutes – Saves hours over traditional cloning – Saves CPU and I/O processing  Automation – We condition the copied volumes for usability – We condition the cloned IMS’s RECON, PROCLIB,JOBS, MDA members – everything you need to bring up your cloned IMS – Databases are copied, underlying data sets renamed, DBRC updated – Repeatable process With IMS Cloning Tool it is now easy and inexpensive to create cloned environments for testing , offloading reporting, moving data or aiding in problem determinations.6 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsWe Need an Exact Copy of Each Environment to Test  The Apply Process – Applying the new release of IMS – Applying Vendor and Home Grown software upgrades needed to support the new release – Activating new functionality  Application and Database testing – Systems with a history of having issues during an upgrade – Business critical systems – Testing new functionality  New functionality – Load level testing – Performance statistics to push out new functionality7 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsTest Environments Created with IMS Cloning Tool  IMS System Skeleton clone – Clones an IMS system without cloning any data – Without requiring a system generation  IMS Database Refresh clone – Refreshes specific databases  IMS Full System clone – Clones a complete IMS system including all its databases – Less than 30 minutes average when using Fast Replication8 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone  IMS System Skeleton clone – Clones an IMS system without cloning any data – The replicated system is accessible and is usable in lieu of the original system without requiring a system generation – Contains all of the database and application definitions – Creates an IMS system to test the apply process9 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone  The Apply Process – Install prerequisite software and maintenance • Check your tools • Related products – Apply coexistence Maintenance to other IMS systems – Evaluate IMS Exit Routines • RECON I/O • Reassemble all exit routines which use IMS Macros (recommended) – Install IMS 12 • SMPE, CBPDO, ServerPac, or a Home Grown process10 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone  The Apply Process cont. – System Definition • Copy the GENDECKS for use with the cloned system • Edit your Stage 1 GENDECKS – Upgrade your RECONS – Run ACBGEN – Review the cloned PROCLIB – Can you bring your newly versioned IMS UP? • Are you missing any modules or exits? • Did your RECON upgrade correctly? • Did the Vendor and Home Grown software generate any errors? • Did you skip something?11 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone  Activating New Functionality – Dynamic Buffer Pools – Dynamic Resource Definitions (DRD) • IMPORT..OPTION UPDATE • IMS Repository – Member Online Change NAMEONLY Option – Migration to Striping and Buffers in 64-bit Storage – Extended Address Volume (EAV) for Non-VSAM Data Sets – RECON - changing the MINVERS – IMS 11 SPE User Exit Enhancements (APAR PM04456/PTF UK67199) • Now included in IMS 1212 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone  Want to try something different? – Change your apply process? – Test an existing configuration that is different? – Try a brand new configuration? – What is the impact of not upgrading a Vendor’s software? – Need to manually clean up a RECON?  Just Re-Clone the System Skeleton and start over. – No back out needed – One job – Repeatable – Automation cleans up between cloning cycles13 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone Plus IMS Database Refresh Clone  IMS Database Refresh clone – Refreshes specific databases – The act of replicating the data, making the replica accessible, and then using the replica in lieu of the original data – Copies by data set – If you refresh into a System Skeleton Clone • All the database and application definitions will exist • All the ACB’s, PSBs, and DBDs will exist • MDA and RECON will be conditioned14 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone Plus IMS Database Refresh Clone  Application and Database Testing – Run the IVP validation steps – Test IMS Exit Routines – Test Home Grown Exit Routines – Test Security – Test Systems that are vital to multiple applications • Common Table systems – Test Systems with a history of having issues during past upgrades – Test Business Critical systems15 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Skeleton Clone Plus IMS Database Refresh Clone  Test new functionality – Full Function Databases • Dynamic Database Buffering • Extended Address Volume (EAV) for Non-VSAM Data Sets – Fast Path (DEDB) Databases • Buffer Manager 64 bit Enhancements • Secondary Index Processing – Further test your TM enhancements – Test your system enhancements • Log Archiving for Non-Recoverable Databases • IMS 11 SPE User Exit Enhancements (APAR PM04456/PTF UK67199) * Now included in IMS 1216 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsFull System Clone  IMS Full System clone – Clones a complete IMS system including all its databases – The act of replicating the data, making the replica accessible, and then using the replica in lieu of the original data without requiring a system generation – Less than 30 minutes average when using Fast Replication17 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsFull System Clone  Provides Exact Copy of a Production Environment – Performance testing before and after upgrade – A complete dry run of the installation Process – All Vendor Software – All Home Grown Custom Software – Complete Application testing – Complete new function tests – This may be your only option to fix some bugs18 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsFull System Clone  Load testing and performance testing – zAAP/zIIP Accounting Log Records • Distinguish between CP (Central Processor) and zAAP/zIIP times – Logging Enhancements • Striping – improved logging throughput • Moved above 2 GB boundaries – ECSA saves – Fast Path (DEBD) databases • 64 Bit manager enhancements • Dynamic Pool compression • Use of secondary Indexes for processing – CPU usage and through put improvements • QCF (Queue Control Facility) • IMS Performance Analyzer19 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsAdvantages of Cloning Tool Created Environments  It creates an Exact Copy – Avoid surprises  Fast – No interruptions to your production – Less than 30 minutes average for a full clone when using Fast Replication  Easily Repeatable – One Batch Job – Automation includes clean up features between cloning cycles  Flexible – Easily controlled - parameter and command driven  Disposable – If anything fails or you want to try something different just re-clone the environment20 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning Tool  Unique Features of IMS Cloning Tool – Leverages Storage-based Fast Replication facilities to clone data – Performs rapid volume reconditioning and data set renaming on cloned system volumes to solve the data access challenges – Adjusts target IMS to accommodate and accept the cloned data21 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning ToolWhat is Storage-based Fast Replication?  An instant copy of a volume/data set at a specific point in time – Builds a bitmap to describe the source volume Storage Processor- – After the bitmap has been created, the source based Copy Process and target volume data can be used immediately  Data movement (CPU and I/O) offloaded to storage processor – Frees up resources on host processor – No host CPU or I/O costs  Consistency Groups – Group of volumes copied at exactly the same point in time while maintaining the order of dependent writes22 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning ToolFast Replication Data Copy Options  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 based fast replication options for IMS database refresh – Data Set FlashCopy (IBM,EMC,HDS) – Data set SnapShot (IBM,STK) – TimeFinder/Clone Data set Snap (EMC)23 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning ToolDo I have to Use Storage-based Fast Replication?  IMS Cloning Tool works with Host- Host-based Copy Process based copy options - Consider the availability requirements of the source system - Consider the amount of data being copied  All the same test environments can be created  Rapid volume reconditioning will be performed to make the copied volumes accessible  The target IMS datasets will be conditioned24 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning Tool - Challenges to Data Access on theSame or Shared LPAR  IMS system cloning is best done using volume replication  Volume data is replicated fast and easy but… – How do you access the cloned data?  Inherent Problems: – VOLSERs may have the same volume names as the source – Volume VTOC, VTOCIX and VVDS would reference the source VOLSERs – Data set names are the same on source and target volumes25 © 2012 IBM Corporation
  • Data Management Tools – IMS Tools IMS Cloning Tool - Challenges to Data Access Data Set Name and Cataloging Issues SourceP Target A1.CAT IMS01 TIMS01 ICF User VTOC VVDS VTOC VVDS Catalog VTOCIX VTOCIX A.DSN3 A.DSN3 A.DSN2 A.DSN2 A.DSN1 A.DSN11. Data sets on the volume are copied, but keep their original name2. Only the source data sets are cataloged; even if the catalog is on the cloned volumes, it isn’t connected to the system’s master catalog24 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning Tool - Provides Data Access On the Same or Shared LPAR  Solution – IMS Cloning Tool performs rapid volume reconditioning and data set renaming on cloned system volumes to solve the data access challenges – Provides access to data sets on target volumes • Renames the VTOC, VTOCIX, and VVDS to match the target volume • Renames and catalogs all data sets to a new HLQ • Adjusts target IMS system to accommodate and accept the cloned data – Solution to enable the use of the data sets on the target volumes on the same image • No more complicated cloning • No more requirement for a separate image27 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsAdjusts Target IMSTo Accommodate and Accept the Cloned Data  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  IMS PROCLIB and 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 updated28 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsStep by Step Creation of TestEnvironments Using IMS Cloning Tool29 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsCloning IMS System Skeleton Test New Releases of IMS  Quickly create an IMS Skeleton (system only, no data) for sandbox testing – IMS Cloning Tool for fast creation of IMS system skeleton – Apply IMS 12 – Start your newly upgraded IMS  Copy applications that were problematic in the past into the skeleton environment and test  Copy critical applications into the skeleton environment and test  Test IMS 12 new features – example the new Fast Path Secondary index functions  Load vendor products / home grown software and test  Exact copy of production testing  Load testing and performance testing  Easily and quickly repeat clone of skeleton as you roll out the new version of software to environments with different configurations – Prevents environmental issues not found in the original testing.30 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsClone IMS Systems Using IMS Cloning Tool IMS System Skeleton Cloning (Databases not included) Performs IMS system skeleton cloning automation – System, no databases Production – Takes an existing IMS system (complete installation and system Database generation process completed) and creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes – Simplifies IMS cloning processes IMS IMS Clone – Reduces cloning time and administration costs IMS Cloning Tool Leverages fast replication facilities to clone data Cloning – Host-based copy can also be used Automation 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 Source Clone System System – Renames and catalogs all data sets to a new HLQ Volumes Volumes Adjusts target IMS to accommodate and accept the cloned data – IMS RECONs, PROCLIB, JOBS, JCL, MDA members 31 © 2012 IBM Corporation
  • Data Management Tools – IMS Tools Create an IMS Cloned System Skeleton Production IMS Target IMS ‘Source’ Test new releases of IMS 3 Create Cloned IMS System Without IMS IMS Cloned Database Clone Data IMS System Volumes ONLY IMS System IMS IMS 4 Install new 1 IMS release Volume Selection System Data Skeleton System Sets 2 Perform IMS 5 Start Your IMS System Cloning Skeleton Data- Automation base Using System Data Sets Volumes Only32 32 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsCloning IMS System Skeleton Test New Releases of IMS  Quickly create an IMS Skeleton (system only, no data) for sandbox testing – IMS Cloning Tool fast creation of IMS system skeleton – Apply IMS 12 – Start your newly upgraded IMS  Copy applications that were problematic in the past into the skeleton environment and test  Copy critical applications into the skeleton environment and test  Test IMS 12 new features – example the new Fast Path Secondary index functions  Load vendor products / home grown software and test  Exact copy of production testing  Load testing and performance testing  Easily and quickly repeat clone of skeleton as you roll out the new version of software to environments with different configurations – Prevents environmental issues not found in the original testing.33 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloned System Skeleton Copy Databases for Application Testing Production IMS Target IMS ‘Source’ 3 Create Cloned IMS System Without IMS IMS Cloned Database Clone Data IMS Database Refresh Environment IMS System and Database Volumes Refresh IMS Databases IMS System IMS IMS 4 Refresh IMS 1 Database A Volume System Selection Data Skeleton Refresh IMS Sets System 5 2 Perform IMS System Database B Cloning Automation Using System Data 6 Test Set Volumes Only A A B B34 34 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsRefresh IMS Databases Using IMS Cloning Tool Database Refresh Automation Performs automated IMS database refresh Production operations Database – Fast refresh of IMS databases – IMS DB support (FF, HALDB, DEDB) IMS IMS Verifies source and target database compatibility Source Target IMS Cloning Tool IMS data copied using storage-based data set fast- Database Refresh replication Automation – Target takes up the same amount of space as the source – Host-based copy can also be used Performs target system meta-data management – Updates DBRC information for target databases – Supports HALDB special requirements • Primary and secondary indexes and ILDS can be copied to eliminate index and ILDS rebuild time • Partition and reorg numbers will reflect the source RECON IMS IMS System Clone Volumes Volumes 35 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsRefresh IMS Databases Using IMS Cloning Tool Production IMS Target IMS ‘Source’ 1 Create target IMS databases IMS IMS if they do not exist TargetSource Job Target Job 2 7 Update DBRC Database Selection for Target Databases 3 Compatibility Check 8 Start Target Databases Stop Source and 4 Target IMS databases 5 Data Set Copy Process Start Source 6 IMS databases36 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsCloning IMS System Skeleton Test New Releases of IMS  Quickly create an IMS Skeleton (system only, no data) for sandbox testing – IMS Cloning Tool fast creation of IMS system skeleton – Install IMS V12 – Run IVP testing  Copy applications that were problematic in the past into the skeleton environment and test  Copy critical applications into the skeleton environment and test  Test IMS 12 new features – example the new Fast Path Secondary index functions  Load vendor products / home grown software and test  Exact copy of production testing  Load testing and performance testing  Easily and quickly repeat clone of skeleton as you roll out the new version of software to environments with different configurations – Prevents environmental issues not found in the original testing.37 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Cloning Automation When a Full System Clone is Needed (Databases Included) Performs IMS system cloning automation – Takes an existing IMS system (complete installation and Production system generation process completed) and creates a new, Database or cloned, IMS system from it without having to repeat the entire installation and system generation processes – Simplifies IMS cloning processes IMS – Reduces cloning time and administration costs IMS Clone Leverages fast replication facilities to clone data IMS Cloning Tool – Host-based copy can also be used Cloning Automation Performs rapid volume reconditioning and data set renaming on cloned 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 Source Clone Database Database – Renames and catalogs all data sets to a new HLQ Volumes Volumes Adjusts target IMS to accommodate and accept the cloned data – IMS RECONs, PROCLIB, JOBS, JCL, MDA members38 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS System Cloning Steps Production IMS Target IMS ‘Source’ IMS IMS Clone 1 IMS volume 5 Volume Recondition selection 2 A. Log Suspend 6 Data set rename B. Consistency Group 7 Update cloned IMS systems data 3 Volume copy 8 Start cloned IMS 4 Log Resume if 2A Source Clone Database Database Volumes Volumes 9 Upgrade IMS39 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning Tool Benefits Significantly reduced administrator time when migrating to new versions of IMS – IBM IMS Cloning Tool does the administrative work for you – It takes 30 minutes vs. 4 days on average Significantly faster migrations are possible – Migrations go faster resulting in quicker time to realize the benefits of the new version – Freeing up people and systems for other requirements Significantly lower CPU when cloning multiple systems and databases verses traditional methods – Unload/Load Utilities – Image Copy Recoveries40 © 2012 IBM Corporation
  • Data Management Tools – IMS ToolsIMS Cloning Tool Smooths Your Migration Path Create exact copies of production environments for the highest quality testing IMS System Skeleton clone – Test your apply process – Test activating new functionality IMS Database Refresh clone – Buffering and Logging enhancements – Focused testing on problematic or critical business applications IMS Full System clone – Gather performance metrics and load testing Less than 30 minutes average when using Fast Replication The process will be easy, flexible and repeatable!41 © 2012 IBM Corporation
  • Data Management Tools – IMS Tools © 2012 IBM Corporation