Your SlideShare is downloading. ×
0
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
IMS Cloning Tool - IMS RUG March 2013 Southfield
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

IMS Cloning Tool - IMS RUG March 2013 Southfield

59

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
59
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The underlying theme of today’s topics is enlightening you to understand a couple of IMS software solutions from IBM that are not only unique when compared to the other vendors in the IMS Tools market space … they are solutions that I think can lead to significant time and cost savings … which when you add that up means to you ….the caretakers of your company’s data … it means being more productive and showing a savings to your business in terms of major CPU reduction.
  • When we talk about what I call the traditional means of copying DASD volumes and datasets from one point to another that are still used today, the names that stand out as the solution of choice is IBM and FDR. There are other vendors, but these what you see here are what we see being used the most …. Seeing these solutions in use sort of remind us what software of this type was in the past … but needs to be looked at more closely because of short comings in that they are the most expensive to use in terms of processing power … which is a quantifiable cost to an organization.
  • This slide we use to set the ground work of common understanding .. Some basic 101 stuff . You all know and understand the terms storage and processor … but when you talk about modern disk storage subsystems, the term Storage Processor comes into play. These disk storage subsystems come with their own processor .. Or I should say processors because they are multiprocessors to add a level of redundancy and protection .. Processors that do things like the caching, I/O functions, and copying data …. Which takes us to the next side.
  • Storage aware database tools provide facilities to link and coordinate application and data management organizations with storage and business continuity administrators. The use of storage-based fast-replication to perform traditional data management copy functions allows us to implement new backup and recovery methods, simplify business continuity monitoring, perform automated cloning operations and to transform tedious disaster recovery processes into efficient disaster restart procedures. A DB2 and / or IMS system level backup (SLB) methodology simplifies backup, recovery, and disaster recovery procedures. Implementing a storage-based system level backup methodology or system cloning solution are new concepts to many database administrators because we have not had the tools that could coordinate the database meta-data and schema definitions with corresponding storage processor commands to facilitate non-intrusive backup or cloning processes. Storage-aware database tools provide the necessary integration and coordination to implement fast and effective storage-based system backup and system cloning methodology.
  • Here’s some more basic terminology
  • Let’s look at how users are cloning IMS subsystems today. This process may be thought of as copying an IMS subsystem. One way of doing this is to do full volume dumps of the volumes where the production, or source IMS subsystem resides, and then to restore these volume dumps on a different, or test, LPAR. The reason these volume dumps must be restored on a separate LPAR is that they would not be accessible on the same LPAR without restoring to different volume serials, renaming and recataloging the data sets, and then updating internal IMS information with the new data set names. This process copies the data twice which results in a time consuming process and high host CPU and I/O costs. It is possible to reduce some of the costs of copying an entire IMS subsystem from one LPAR to another by just copying certain ‘sets of data’ that make up an IMS subsystem: such as just the volumes that contain the data base data sets. But, if the entire IMS subsystem is not copied, or cloned, to the test LPAR, then there are some additional steps that must be done to make sure the production and test LPARs are in sync in order to make the copied data sets usable. For instance, say you already have an IMS system installed and available on your test LPAR and the only data that you need to clone, or copy, to the test LPAR are the databases. In this scenario, you would then have to make sure that when maintenance was applied to your production environment that it was also applied to test. This is especially true when upgrading to a new IMS version. There is also the additional work of keeping all of the application libraries, ACBLIBs, PGMLIBs, etc.. in sync between the production and test environments. When a change is introduced to the production environment, that same change also needs to be made to the test system. Finding the cause of problems seen with ACBs and programs, or DMBs and actual database structure differ can often be difficult and time consuming. In addition, with current options, you are still limited to one copied subsystem per LPAR and if you want to create an additional IMS subsystem, you must go through a full SYSGEN and configuration.
  • Now lets look at how users are refreshing IMS databases today. Typically there are two methods that can be used to copy databases between production and test IMS environments. One is to take an image copy from a production database and then use a recovery utility to restore it in a test environment. You might need to rebuild indexes if they weren’t copy. Again, the problem is that the data is copied twice, once for the image copy and once for the restore, plus any rebuilding of indexes so this solution can be costly in time and resources. A second option is to unload the production data and then reload the data into the test environment. Typically the indexes are rebuilt as part of the reload process. An unload/reload process is typically used when only a subset of the data is needed in the test environment or when there needs to be some masking of the data. Masking can usually be performed with unload or reload user exits. The Unload/Load method is much slower than an image copy followed by a recovery because the data is accessed hierarchically where the image copy/recovery method processes the data sequentially. Again however, the data is copied twice. The difficulty with either one of these methods is that changes to any application libraries, ACBLIBs, DBDLIBs, PSBLIBS, PGMLIBS, etc., must be kept in sync between Production and Test IMS environments and sometimes these differences are difficult to detect rendering the copy invalid. For HALDBs, since they require DBRC registration, there are some additional considerations, such as restoring an image copy that is not registered. In this case, prior to restoring the image copy, the image copy would have to be manually registered to DBRC in the test environment. If you choose to use image copies to copy HALDB databases you must somehow guarantee that the partition numbers are the same in both the production and test RECONs. This is because the partition number is maintained in the partition data sets as well as the RECONs
  • 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. So lets get into the details.
  • 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. So lets get into the details.
  • 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. So lets get into the details.
  • IMS Cloning Tool performs automated IMS database refreshes. ________________________________________________________ It verifies that the source and target IMS databases are compatible before copying the data _______________________________________________________ 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 next step is to update the IMS meta-data
  • Transcript

    1. 1 © 2013 IBM CorporationIMS Cloning ToolIMS Regional User GroupColumbus and DetroitMarch 2013Raquel CarvalloIMS Tools – Technical Sales Supportcarvallo@us.ibm.com
    2. 2 © 2013 IBM CorporationTopics for Today’s MeetingIMS Cloning Tool– How Does It Work?– How Do I Use It?
    3. 3 © 2013 IBM CorporationHost-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 replicationHost-basedCopy ProcessAn “expensive” use of processingpower
    4. 4 © 2013 IBM CorporationStorage Processor = Storage + Processor• Storage– Non-volatile– Computer components and recording media thatretain digital data• Processor– Computing system that executes softwareprograms• Storage Processors– Enable data movement through host-based API– Allows CPU reduction from host-based systemsHostbasedAPIs
    5. 5 © 2013 IBM CorporationApplication and DatabaseStorage IntegrationMainframeApplication andDatabaseSystemsStorage-AwareDataManagementToolsApplication andDatabase ManagementDomainStorage AdministrationandBusiness ContinuityDomain“Having storage-aware tools”provide for:• Organizational Integration• New Backup Methods• New Recovery Strategies• Business Recovery Monitoring• Disaster Restart Solutions• Cloning AutomationSourceDataBackup,Clone,DR
    6. 6 © 2013 IBM CorporationCloning – 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 thenusing 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 repeatthe entire installation and system generation processes– Less than 30 minutes (average when using Fast Replication)• IMS database refresh automation– Refreshes specific databases
    7. 7 © 2013 IBM CorporationIMS ‘System’ Cloning - TodayProduction LPARUserCatalogsIMS001IMS SystemData SetsIMS002ApplicationLibrariesIMS003RECONData SetsIMS004Data BaseData SetsIMS005Test LPARUserCatalogsIMS001IMS SystemData SetsIMS002ApplicationLibrariesIMS003RECONData SetsIMS004Data BaseData SetsIMS005Two reads of the data
    8. 8 © 2013 IBM CorporationIMS ‘Database’ Cloning – How you do it ?Production IMSApplicationLibrariesRECONData SetsData BaseData SetsIMS SystemData SetsTest IMSApplicationLibrariesRECONData SetsData BaseData SetsIMS SystemData SetsUnload LoadImageCopyRecoveryIndex Rebuild???z/OS
    9. 9 © 2013 IBM CorporationProductionDatabaseIMSCloneIMSCloning ToolCloningAutomationSourceDatabaseVolumesCloneDatabaseVolumes• Performs IMS system cloning automation• Takes an existing IMS system (complete installationand system generation process completed) and createsa new(“cloned”) IMS system from it without having torepeat the entire installation and system generationprocesses• You benefit by: Simplfying IMS cloning processes Reducing cloning time and administration costs• Performs rapid volume reconditioning anddataset renaming on cloned volumes to solvethe data access challenges• Target volumes have different volser label than thesource volume• Renames the VTOC, VTOCIX, and VVDS to match thetarget volume• Renames and catalogs all data sets to a new HLQ• Adjusts target IMS to accommodate andaccept the cloned data• IMS RECONs, PROCLIB, JOBS, JCL, MDA membersCreate IMS Systems Using IMS Cloning Tool Automation
    10. 10 © 2013 IBM CorporationProductionDatabaseIMSCloneIMSCloning ToolCloningAutomationSourceDatabaseVolumesCloneDatabaseVolumes• Updates done in IMS cloned system• RECONs data sets Data set names, IMS subsystem IDs, and VOLSERs are updated in the followingRECON records:→ header record, database data set records, online log records, and back-outrecords Optionally, the following RECON records are updated if they were on volumesthat 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 memberswithin these libraries• MDA (MVS Dynamic Allocation) members for databasesor system data sets, are updated to reflect the new dataset 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 datasharing member is updated• Leverages fast replication facilities to clonedata• Data can be cloned while online or offlineCreate IMS Systems Using IMS Cloning Tool Automation
    11. 11 © 2013 IBM CorporationWhat makes IMS Cloning Tool so “fast”?• Host-based CopyOptions– Data copy processes use hostbased CPU and I/O facilities– Slower than storage-based fastreplication– Volume copy options for IMSsystem cloning TDMF (IBM), FDRPAS (Innovation DataProcessing) DFSMSdss (IBM) FDR (Innovation DataProcessing)– Data set copy options for IMSdatabase refresh Any traditional data setcopy processes• Fast Replication Data CopyOptions– Fast copy processes offloaded to thestorage processor– No host CPU or I/O resources• Data set based fast replicationoptions for IMS database refresh– Data Set FlashCopy (IBM,EMC,HDS)• Volume based fast replicationoptions for IMS system cloning– FlashCopy (IBM,EMC,HDS)– SnapShot (IBM,STK)– TimeFinder/Clone Volume Snap orSnap (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-basedCopy ProcessFastReplicationCommandsfrom z/OS
    12. 12 © 2013 IBM CorporationIMS 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 systemwithout 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 systemwithout 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. 13 © 2013 IBM CorporationProductionDatabaseIMSCloneIMSIMS Cloning ToolCloningAutomationSourceSystemVolumesCloneSystemVolumes• Performs IMS system “skeleton” cloning automation– System, no databases– Takes an existing IMS system and creates a new, or cloned, IMSsystem from it– Do not need to repeat the entire installation and system generationprocesses– 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 renamingon cloned system volumes to solve the data accesschallenges– Target volumes retain their target volume label– Renames the VTOC, VTOCIX, and VVDS to match the targetvolume– Renames and catalogs all data sets to a new HLQ• Adjusts target IMS to accommodate and accept the cloneddata– IMS RECONs, PROCLIB, JOBS, JCL, MDA membersUsing IMS Cloning Tool -IMS System Skeleton
    14. 14 © 2013 IBM CorporationIMSSystemVolumesIMSTargetIMSCloneVolumesIMSSourceIMS Cloning ToolDatabase RefreshAutomation• Performs automated IMS database refreshoperations– Fast refresh of IMS databases– IMS DB support (FF, HALDB, DEDB)• Verifies source and target databasecompatibility• IMS data copied using storage-based data setfast-replication– Target takes up the same amount of space as the source• Performs target system meta-datamanagement– 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 eliminaterebuild time– Manages partition number and gap sequencingUsing IMS Cloning Tool -IMS Database RefreshProductionDatabase
    15. 15 © 2013 IBM CorporationIMS Database Refresh -What it can deliver to you• Quickly copies a specific database or set of databases for targetedtesting.– Flexibility to select exactly what database you need thus saving space andtime• 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 testingcycle Test an application in conjunction with systemparameter tweaking• Database Testing HALDB conversions can be complex and affect databaseavailability Run performance and integrity utilities
    16. 16 © 2013 IBM CorporationRaquel CarvalloIBM IMS ToolsTechnical Sales Supportcarvallo@us.ibm.comDemo

    ×