You are on page 1of 20


Migrating Off the Mainframe
The Approaches, Techniques, and Tools Organizations Need to Successfully Migrate Data to Open Standard Relational Database Management Systems

This document contains Confidential, Proprietary and Trade Secret Information (“Confidential Information”) of Informatica Corporation and may not be copied, distributed, duplicated, or otherwise reproduced in any manner without the prior written consent of Informatica. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Informatica does not accept responsibility for any kind of loss resulting from the use of information contained in this document. The information contained in this document is subject to change without notice. The incorporation of the product attributes discussed in these materials into any release or upgrade of any Informatica software product—as well as the timing of any such release or upgrade—is at the sole discretion of Informatica. Protected by one or more of the following U.S. Patents: 6,032,158; 5,794,246; 6,014,670; 6,339,775; 6,044,374; 6,208,990; 6,208,990; 6,850,947; 6,895,471; or by the following pending U.S. Patents: 09/644,280; 10/966,046; 10/727,700. This edition published July 2006

. . . . . . . . .4 Data Migration Project Challenges. . . . . . . . . . . . and Tools . . . . . . . . . . . . Unified Enterprise Data Integration Platform . . . . . . . . . Metadata-Based Data Integration Platform to Support the Data Migration Lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unified. . . . . . . . . . . . . . . . . . . . . .6 Mainframe Data Migration Project Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 The Business Challenges of Mainframe Migration . . . . . . . . . . . . . . . . . . . .3 The Technical Challenges of Mainframe Migration . . . . . . .9 Universal Data Access Capabilities for Accessing Source Data . . . . . . . . . . . . . . . . . . . . . . . . . .White Paper Table of Contents Executive Summary . . . . . . . . . .4 The Seven Approaches to Mainframe Migration . . . . . . . . . . .14 Conclusion and Next Steps . . . . .16 Migrating Off the Mainframe 1 . . . . . . . Methodologies.8 The Solution: Single. .11 Built-In Data Transformation and Correction Capabilities to Address Data Quality in Legacy Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Data Migration Methodologies and Tools . . . . . . .14 Single. . . . . . . . .9 Data Profiling Capabilities for Identifying and Analyzing Source Data . . . . . . . . . . . . . . . . . .

“The useful life of pre-relational mainframe database management system engines is coming to an end because of a diminishing application and skills base. the installed base for pre-relational database management systems has been declining. 1 Mattern. This white paper examines both the business and technical challenges of migrating off the mainframe. once the decision has been made. It explores common data migration project methodologies and tools. this paper focuses specifically on migrations to Oracle environments. This is due primarily to increased prices from the vendors. iterative process. This is where this white paper can help. your IT organization needs to know about the approaches. Although the installed base for pre-relational DBMSs is shrinking. While most of the practices discussed in this paper apply to migrations from mainframe-based legacy applications to any relational database management system. In real numbers. It outlines the seven mainframe migration approaches that IT organizations can use to develop their migration strategies. according to Gartner. Regardless of the reasons why your business has elected to move off mainframe. this white paper describes how IT organizations can use Informatica enterprise data integration software to effectively migrate off the mainframe to more modernized systems. and increasing costs. for example. and suggests ways to convert a serial approach to migration into a more effective. 2 . Finally. Thomas and Matthias Haendly.Executive Summary For more than 40 years companies have deployed mission-critical business applications on the mainframe. 2005. Many of these applications have been built for both non-relational database management systems (DBMSs)." Integration Developer News. such as DB2. as well as for relational sources of data on the mainframe. Yet recently. the revenue is dropping as the number of customers and licenses decreases. and tools to successfully migrate to a more modern application landscape or open standard RDBMS like Oracle. the market share numbers from Gartner Dataquest…show that the revenue is increasing. "ESA: A 2005 'Business-Savvy' Take on SOAs. currency conversions and mainframe CPU replacement.”1 Many companies have migrated mission-critical applications off the mainframe onto open standard relational database management systems (RDBMS) like Oracle for a variety reasons— limited application support from independent software vendors (ISVs) and a shrinking resource base. techniques. February 9.

Data is the foundation of the modernization process. Assembler. The mainframe migration strategy should ensure the continuity of the new application and. The application.White Paper The Business Challenges of Mainframe Migration Mainframes typically run mission-critical applications that have been in production for two to three decades. Many analysts argue that introducing new business processes into an organization is much more costly than the migration of the technology itself. Businesses find it challenging to prioritize the order in which these applications are to be moved off the mainframe and ensure that the order meets both business needs and minimizes risk in the migration process.” and some will need to be changed to accommodate the new application. many companies take the opportunity to examine the business processes they have followed for many years and modernize them to support their current and future business requirements. Mitigation of this risk is an essential component of any migration plan. but without a clean migration of the data. Once a specific mainframe application is being migrated. rollback to the mainframe application. business logic. the next challenge is deciding which business processes will be migrated. During a mainframe migration. businesses often move applications one at a time to mitigate risk. or Natural programs. Many of these applications often include hundreds. for instance. A technology migration provides organizations with the opportunity to reevaluate. streamline. legacy processes linger because of technology limitations that. A clean data migration involves data that is: • Organized in a usable format by all modern tools • Optimized for an Oracle database • Easy to maintain Migrating Off the Mainframe 3 . are no longer relevant. many business processes do not need to be migrated. some will need to be moved “as is. and update these business processes. in the event of failure. Even among the business processes that need to be migrated. PL/1. Complicating mainframe migration is the fact that while mainframe applications tend to be interdependent. When migrating an application off the mainframe. Many companies have business processes that reflect the way their systems work. and work flow can all be migrated. maintaining this continuity is one of the primary business challenges to address. Once the decision has been made to migrate off the mainframe. In many cases. This approach requires data in the mainframe application to be synchronized with data in the new application. of homegrown COBOL. companies will not meet their business requirements. while valid a decade ago. even thousands.

Most applications that maintain mainframe data (e. The Seven Approaches to Mainframe Migration Since migrating off the mainframe is not an easy process. Mainframe data may be organized in an order of key value that makes sense for that particular mainframe system. In addition. networked structures. as well as extensive expertise in both the legacy and relational environments. Correlating these unique formats and vastly different structures to a relational model is typically a tedious process that often requires significant labor.The Technical Challenges of Mainframe Migration The technical challenges of migrating an application off the mainframe reflect both the vast differences in programmatic and data formats. it is still possible to reconcile them during migration. which includes mapping mainframe keys to Oracle primary and secondary keys. While incompatible file formats and structures complicate the migration effort. organizations should employ multiple approaches. such as multiple record types in one file. Organizations need a way to transparently extract both legacy and relational data and to present this data consistently across the enterprise. as well as the sheer complexity of systems that have been continually evolving in-house for decades. IT organizations need to create an Oracle schema. They are not split out into related normalized tables. In many cases. on the mainframe multiple iterations of related repeating fields are denormalized and housed in one record. but would not make sense in the Oracle target system. This section presents seven different approaches that organizations can use to develop their mainframe migration strategy. • Performance. 4 . as they would be housed in Oracle. or a combination of any of these structures. and maintain these non-relational links to their relational equivalents—thereby dramatically simplifying the procedure and ensuring data integrity across the move. When organizations migrate off the mainframe. etc. IDMS. It should be noted that these approaches are not mutually exclusive. IMS. Maintaining referential integrity when moving from a nonrelational to relational model presents considerable challenges.) typically do so in non-relational formats. The complexity and variety of non-relational database management systems represent a daunting challenge for organizations attempting to correlate their format and structure to a relational system. IT organizations face a variety of technical challenges in migrating off the mainframe. hierarchical structures. flexible file definitions that facilitate data files with multi-record formats and multi-record types in same data set—compound this problem. including: • Incompatible file formats and structures. ADABAS. correlate. organizations need a comprehensive mainframe migration strategy to address all the variables. Every mainframe migration project is unique and will involve some subset or hybrid of these seven approaches. VSAM. They also need to define how looping data structures and substructures are mapped to relational tables. they need to map mainframe keys to Oracle’s concept of primary and secondary keys. They need a way to extract non-relational data in tact and present it in a graphical design environment so that developers can easily identify.. • Data and referential integrity.g. Regardless of the approach or combination of approaches used. IT organizations need both a robust data migration methodology and data migration toolset to migrate off the mainframe onto the Oracle system. Organizations need to ensure that all of the parent-child relationships across mainframe files and records are appropriately mapped to RDBMS tables. to maximize performance. Both these scenarios could negatively impact performance on an Oracle RDBMS. Architectural elements unique to the mainframe—for example.

or both.g. Physical Federation. Companies keep their mainframe systems.White Paper 1. weekly.g. especially since the entire bulk data load has to be moved within a short window of time. In this approach. which must be read and joined to produce a single view of the data inside an Oracle RDBMS. Typically. ADABAS. 2. but by pulling the data into an Oracle system. or when parts of the mainframe system are so complicated that they cannot be replaced for years to come. unpredictable updating could occur to either the source or target system. this approach is used for the initial data load for testing the migration.. daily. DB2. Bi-directional Replication Synchonization. Incremental Delta Offload. since in many cases. This approach requires considerable advance planning. After the initial data movement. and after all the testing has been done and before moving the system to production. they put in place a service-oriented architecture (SOA) for integration with the rest of the enterprise. This approach is typically used for testing and staging environments. business decisions would have to be made well in advance of implementing this replication scenario to determine the master/slave relationship in this bi-directional transaction. but the Oracle system becomes the “single version of the truth. IMS. Data is migrated off the mainframe as a one-time data movement event.. One-Time “Bulk” Offload. often completed during a lean period like a weekend or the early morning hours. The challenge of this approach is to identify the changes made on the mainframe and selectively extract just the changes. both systems will be running for years before the mainframe is shut down. Datacom. This approach facilitates phased migration of mission-critical infrastructure.” This is a popular approach when the packaged application replacing the mainframe may not have all the functionality of the mainframe. 4. Migrating Off the Mainframe 5 .). Data is still stored in the respective mainframe data stores. Otherwise. In this approach. The challenge of this approach is to support both batch and realtime bi-directional integration. data is migrated off the mainframe in batches. two production systems – the mainframe system and the Oracle system – run in parallel with data on each system and replicate data on the other. monthly). VSAM. 3. This approach involves multiple data sources (e. It’s important to note that in this scenario. etc. the goal is to bring over changes made to the mainframe system data on a periodic basis (e.

6. formerly known as IMS/Data Communications (IMS/DC). This means that the data in the Oracle application must be accurate and trustworthy for business users to readily transition from their legacy mainframe applications to adopt an Oracle system. Mainframe Transactions on Oracle. Oracle Transactions on Mainframe. or that data migration is something a consulting partner will handle. but the mainframe still remains the primary system of record for business process execution. and/or batch mainframe transactions that need to access data in the Oracle database. the data from all the mainframe sources is joined virtually to provide a “just in time” single view to the consuming applications or users. and Tools While data migration is essential to the success of an Oracle RDBMS implementation. there are still CICS. but some critical business functionality still resides on the mainframe. The common assumption is that tools exist to extract the data from the mainframe and move the data into Oracle. Since functionality and data have been moved to the Oracle system. Research has shown that software implementations are put at risk when data migration is not thoroughly considered and planned. 7. Methodologies. but instead of loading all the data into an Oracle RDBMS. more than 80 percent of 6 . IMS. and then related mainframe system updates are executed by initiating batch jobs.5. it’s about making the data work once within Oracle. the role of data migration in the project often overlooked and underestimated. Virtual Federation. functionality moves slowly to the Oracle system. New transactions are first processed on the Oracle system. This approach is sometimes called Enterprise Information Integration (EII). But data migration is not just about moving the data into Oracle. Often project teams tasked with data migration focus solely on the timely conversion and movement of data between systems. the Oracle system becomes the primary system of record for business process execution. According to recent research. or by such on-line transaction systems as Customer Information Control Systems (CICS) or Information Management System/Transaction Manager (IMS/TM). This approach is identical to the physical federation model. Data Migration Project Challenges. In this approach. In this approach.

or Natural programs. Legacy mainframe systems are usually kept alive after new systems launch. half exceed timescales by 75 percent and two-thirds exceed the overall project budgets. cannot be made in a vacuum—these changes have an impact on the people in your organization. or sometimes missing altogether. maintained. the typical organization relies on more than 50 core business applications.e. or 500 source systems to migrate. partners. and customers are prone to failure. Identifying and analyzing source data. constraints. Migration projects that don’t accommodate for associated adjustments in the behavior of the employees. and/or stored. PL/1. as well as the quality and the format of the data. Complicated target data validations. Simple extraction and upload often proves to be unrealistic due to the volume of source systems and the availability of legacy application resources. Accessing source data. synchronization) so that the most appropriate behavioral practices can be developed. According to a recent survey of more than 350 firms. and quality of data to be loaded. Data migration is not a one-time effort. Of the projects that are overrun. not in the right format. timeliness.e. Migration teams can accommodate behavioral changes by either ensuring a high degree of user transparency (i. user-transparent integration) or by providing for the concurrent synchronization and operation of both legacy and new systems over a period of time (i. To address data quality issues when migrating off the mainframe. validity. Addressing data quality in legacy applications. long after the migration is completed. Data quality can be compromised as a result of how the data has been entered. Data migration teams need to understand and accept that there may be “dirty” data in the mainframe system. 2. Identifying and analyzing source data in mainframes is even more complicated since mainframes house custom applications developed over decades that often incorporate hundreds—sometimes thousands—of individual COBOL. data migration teams should consider the data’s existence. only accessible through little-understood interfaces.. 3. of poor quality. 4. and the requirements often change during the project.White Paper software implementation projects fail or overrun their budgets and schedules. The target system is often under development at the time of data migration. Also. integrity. burdened by superfluous logic. one-time event during the overall implementation. The required data is spread across multiple source systems. For example. processed. Many target systems have restrictions. and companies with more than $1 billion annual revenue have as many as 500 systems. “relevance” may mean that data that is relevant in the mainframe system will not be needed on the target Oracle-based system. especially to systems that have been in production for two to three decades. missing source code. Regardless of whether there are five. consistency. accuracy. Accommodating behavioral changes. companies often have to prove the migration was complete and accurate in order to comply with regulations like Sarbanes-Oxley and Basel II. Often there is insufficient understanding of data and source systems. Organizations need to determine how mainframe source data will be accessed before it is migrated. 6. poorly documented. Synchronization is required between the old and new systems during this hand-off period. 50.. and thresholds on the validity. nor have most companies built up any internal competency from which to draw. Preparing and loading data into the target system. and relevance. Assembler. for instance. Migration is not an industry-recognized area of expertise with an established body of knowledge and practices. 5. Organizations need to understand the unique challenges of migration projects and adopt an appropriate migration methodology to address and overcome these challenges Mainframe Data Migration Project Challenges The top six challenges associated with mainframe data migration projects are: 1. Technical changes. the question needs to be answered as to how this will be accomplished. A major reason why these failure rates are so high is because data migration is considered a minor. Supporting the data migration lifecycle. Migrating Off the Mainframe 7 .

and a quality assurance (QA) testing tool to test and load the data. Since sufficient time is rarely planned or allocated for analysis.In summary. Data Migration Methodologies and Tools Migration projects are commonly and mistakenly thought of as a serial. Validating the data according to various integrity and quality constraints also typically poses a challenge. most importantly. If the validation fails. This agile methodology uses the same four stages—analyze. the problem of this serial project methodology is that it does not support the iterative nature of migrations. Cobol code for extraction of mainframe data to flat files. extract/transform. The ideal approach for successfully managing a data migration project is cyclical. designs to be refined. validate. It allows IT organizations to analyze the data. Based on the initial mapping specification. and best practices to be applied as the project progresses. and then. unexpected data scenarios often break the loading process and send the project back for more analysis. For example. These disconnected or siloed tools only serve to exacerbate an already inappropriate project methodology. four-stage process: 1. This cyclical methodology enables target-driven analysis. any mapping specification from the mainframe to Oracle is hardly more than an intelligent guess. most of the assumptions about the data are proved wrong. repeat the process until the migration is successfully completed. Often technology used for data migration consists of general-purpose tools repurposed for each of the four stages. the validation of assumptions. Figure 1 illustrates how migration can be converted from a serial process into an iterative process. Analyze the source data 2. extract and transform the data. Load the data into the target However. Further complicating the issue is inadequate technology. and load—but the four stages are but also interconnected with one another. Extract/transform the data into the target formats 3. more extractions and transformations. extractions and transformations run into changing target data requirements. requiring additional analysis and changes to the mapping specification. and more validations. during the upfront analysis of the source mainframe data. Validate/cleanse the data 4. spreadsheets or SQL scripts are used for data analysis. the project goes back to further analysis and then additional rounds of extractions and transformations. When the data is finally ready to be loaded into the Oracle system. validate the data. transformation or application integration tools to convert the data. load it into targets. Analyze Extract/ Transform Validate/ Cleanse Load Analyze Extract/Transform Load Validate/Cleanse Figure 1: The Data Migration Methodology Should Be Converted from a Serial Process into an Iterative Proces 8 .

and file-based systems. unified enterprise data integration platform that enables companies and government organizations of all sizes to access and integrate data from virtually any business system. The Solution: Single. incremental updates. and deliver that data throughout the enterprise at any speed. midrange. Data profiling is the analysis of data to understand its content. In an iterative process. and the context and relationship of the data may not meet or match Oracle requirements.White Paper This iterative approach to data migration is best achieved by using a single. including mainframe. or in real time. and methodology challenges associated with migrating off the mainframe and onto an Oracle system? The answer is by using a single. During Oracle implementations. These capabilities include: • Data profiling capabilities for identifying and analyzing source data • Universal data access capabilities for accessing source data • Built-in transformation and correction capabilities for addressing the quality of data in legacy applications • Single. A single platform not only unifies the development team across the project phases. but also unifies the separate teams that may be handling each different source system in a multi-source migration project. Both Informatica products provide powerful capabilities to help overcome the challenges associated with migrating data off the mainframe and into an Oracle DBMS. Unified Enterprise Data Integration Platform So how do organizations address the business. more frequent and ultimately fewer iterations—a key to success in a migration project. the results of one stage can be easily carried into the next. unified enterprise data integration platform for data migration. technical. structure. Informatica® PowerCenter® is a single. Available with PowerCenter. unified data integration platform to support the data migration lifecycle Data Profiling Capabilities for Identifying and Analyzing Source Data While the objective of moving data from the mainframe to an Oracle system seems straightforward. When IT organizations use one unified toolset. Informatica PowerExchange® provides on-demand access to data in all critical enterprise data systems. Data migration teams can realize significant benefits from using PowerExchange to access mainframe and legacy data and make it available in when they need it—batch. and dependencies. Manual data profiling ranges from spot inspections of actual legacy Migrating Off the Mainframe 9 . PowerExchange helps organizations leverage mission-critical operational data by making it available to people and processes without requiring manual coding of data extraction programs. complications arise when “legacy” migration translates to n number of distinct business applications running on different platforms and data stores. there is a big difference between using four different tools for each stage and one unified toolset across all four stages. in any format. data migration teams typically try to profile legacy data manually. enabling faster. Informatica provides a single. quality. unified toolset or platform that leverages automation and provides functionality that spans all four stages. unified enterprise data integration platform that is ideal for migrating data off the mainframe into Oracle systems.

Figure 3: PowerCenter Profiling Report Infers Primary Key and Foreign Key Relationships between Multiple Legacy Application Tables 10 . analysis. PowerCenter: • Reduces data quality assessment time with easy-to-use wizards and pre-built metric-driven reports that comprise a single interface for the entire profiling process • Addresses ongoing data quality in legacy applications with Web-based dashboards and reports that illustrate changes in data content. but the results are often inaccurate and incomplete. and resources required to properly analyze source data systems.applications or sample data extracts.. build. schedule. Figure 2 shows how a much more even distribution of project resources over the key project phases (e. to analysis via custom-coded reports or elaborate and intertwined spreadsheets. Relying on the build or development phase to identify and fix data issues can increase the cost by ten times. and values over time • Ensures end user data confidence by automatically and accurately profiling any data accessible to PowerCenter—virtually any and all enterprise data formats Figure 3 shows an example of a PowerCenter data profiling report. and structure of data in virtually any operational system. Typical Project Effort Ideal Project Effort Analysis 10% Test 30% Analysis Build Test Analysis 40% Build 30% Test 30% Build 60% Figure 2: Proactive Analysis of Source Data Saves Both Time and Money PowerCenter’s data profiling capabilities provide comprehensive. quality. The report shows how PowerCenter automatically infers the primary and foreign key relationships across three tables in a legacy application. and test) can promote savings. accurate information about the content. Organizations can automatically assess the initial and ongoing quality of data regardless of its location or type. structure. An inadequate toolset and manual approach to profiling often leads to a data migration project which underestimates the scope. including mainframe tables. It’s important to note that PowerCenter data profiling can profile any data source that PowerCenter can natively access. PowerCenter’s data profiling reports help migration teams determine if the legacy data has quality issues and how to properly address them.g. With its comprehensive data profiling capabilities. quality. These data profiling methods typically sample data in a few key fields to get a sense of what the data is like in these columns.

a complex. The ability to readily access all enterprise data—structured. but the fact that much of the mainframe data is not stored in a relational format leaves the migration teams relying exclusively on mainframe developers to extract and replicate data. Universal Data Access Capabilities for Accessing Source Data Analysis of legacy data is essential for creating accurate data migration mapping specifications with relevant data conversion requirements.e. These reports help the migration teams help migration teams determine if the legacy data has quality issues and how to properly address them. on average. and semi-structured—is vital to successful data migration. A significant percentage of data for a mainframe migration will need to be extracted from these systems.. The platform provides the tools to automatically scan all records across all columns and tables in a source system and dynamically generate reports that make it easy to understand the true state of the data. a multitude of other data formats are also prevalent and considered to be of enterprise access significance. PowerCenter’s capabilities enable the profiling of data pre. However. as shown in Figure 4. This average will inexorably increase over time as organizations expand their enterprise application landscape to support more subject areas and groups in the organization. payloads from message queues. inefficient migration process still lies ahead if the data migration team relies exclusively on manually extracting data from each legacy data source. Based on a 2003 TDWI survey of the types of data sources that ETL programs process. Many mature and established applications are still maintained on mainframe platforms. organizations extract data from at least 12 distinct data sources. upfront source system profiling) and after (profiling the converted data for the Oracle application environment) migration. as well as unstructured data formats such as Microsoft Excel and Adobe .White Paper PowerCenter’s data profiling capabilities help migration teams to do much more thorough analysis than manual profiling of the legacy systems.pdf files . enterprise data may reside in XML files. validating the readiness of the mainframe data for Oracle. Data Sources Relational databases Flat files Mainframe/legacy systems Packaged application Replication or change data capture utilities EAI/messaging software Web XML Other 4% 15% 12% 15% 15% 39% 65% 81% 89% 0 20 40 60 80 100 Figure 4: Enterprise Data Resides in a Variety of Sources and Formats Migrating Off the Mainframe 11 . In addition to mainframe data formats. Web-based data sources. According to a report from The Data Warehousing Institute (TDWI).and post-migration. Data profiling is important both before (i. unstructured.

ACORD) Print Stream BLOBs Any proprietary data format/standard Informatica PowerCenter Across the Firewall/WAN Open and Relational Data Sources Oracle IBM Microsoft Sybase Informatix Teradata Flat Files XML Web Logs Remote Data Access Remote or Outsourced Business Applications Figure 5: PowerCenter Provides Universal Data Access The flexibility to access all types of enterprise data in a single data integration platform offers significant advantages over hand-coded data migration approaches.g. Sources of data for Oracle DBMS implementations tend to be dynamic. DB2. ACORD.) • Semi-structured data (e.g.. 12 . PowerCenter’s data access capabilities offer migration teams the flexibility to source these “softer” forms of data which traditionally would be left up to manually interpretation and processing—or worse. left unaccounted for in the migration process. PeopleSoft. MS MQ. Oracle. having to migrate over mainframe and mid-range applications from applications resulting from a corporate merger or acquisition.. data migration teams can source directly from a mainframe non-relational data source (in addition to getting to DB2 mainframe data) as if it were a relational database. PowerCenter frees data migration teams from having to maintain and be dependent on a cumbersome. PowerCenter reduces the risk of both current and future data migration efforts by providing access to a broad range of enterprise data formats. With the ability to centralize data access and management. SAP. Extracting data from a client/server-based legacy application today does not insulate the team from future requirements—for example.g.) Figure 5 shows the breadth of PowerCenter’s data access capabilities. etc.) • ERP (e. IBM MQ Series. etc.) • Relational data (e. • Reduced risk. industry-specific formats such as HL7. . etc.g. SWIFT. time-consuming process where programs are developed to extract and stage data for each source of legacy data. PowerCenter provides universal data access. Microsoft Word documents and Excel spreadsheets. including: • Increased productivity. HL7.. JMS.g. Microsoft SQL Server. binary files. etc. etc. SWIFT. FIXML. Real-Time Data Sources TIBCO IBM WebSphere MQ JMS SAP MSMQ WEBM Web Services Enterprise Software Sources Mainframe AS/400 JDE PeopleSoft Siebel SAP SAS Essbase Lotus Notes Unstructured Data PDF Word Excel Vertical Standards (e. email. allowing the data migration team to source virtually any and all enterprise data formats.g. TIBCO...) and file data • Message queues (e. including: • Mainframe data • Structured data • Unstructured data (e. Siebel.Source Virtually Any and All Data Formats With PowerCenter..pdf files.

This interface is both codeless and universal. PowerExchange provides the data in batch for initial load.g. Once the data has been identified and its relationship interpreted. Migrating Off the Mainframe 13 . thereby eliminating the need for lengthy training and implementation. instead of interpreting the meaning of their old one. Figure 6 shows how PowerExchange can move data in real-time.White Paper Unlock Complex Non-relational Data without Coding PowerExchange provides both the interface and engine to ensure successful migration from mainframe data to newer relational systems. COBOL or PL/1 copybooks. This functionality includes the ability to import existing metadata (e.. Legacy PowerExchange Real Time Target Mainframe Oracle Change DB2. change for incremental updates. This is critical for developers migrating from non-relational to newer relation systems. and better integrate complex nonrelational data residing on the mainframe. while maintaining their associated structures. install gateways or implement new communications protocols. or Natural DDMs) directly from the source to be leveraged in the migration strategy. where the tedious translation of these formats and structures is often cited as the most problematic aspect of the migration project. PowerExchange provides direct access to some or all of the data in the source system without requiring IT staff to manage multiple interfaces. regardless of the source platform. This means that developers can spend time designing form and function of their new environment. IDMS Batch Figure 6: PowerExchange Accesses Mainframe and Provides a Choice of Latency to Deliver Data When Needed Simplify Management of Disparate File Formats and Structures PowerExchange simplifies the management and organization of disparate file formats and data structures by providing a single platform with a ubiquitous and transparent access to numerous newer and legacy systems. manipulate. PowerExchange’s navigator console performs seamless extraction of all major mainframe file formats. IMS. this console represents mainframe file formats in a consistent manner. Regardless of the source type. write scripts. install special drivers. or real-time for environments where migration will occur while both systems are in production for months or years. PowerExchange provides an intuitive graphical user interface that allows developers to access. or bulk modes. change data capture.

a common outcome is the “code. PowerCenter provides all the capabilities that are essential to support the data migration lifecycle from a single. This ugly scenario repeats itself until the project deadlines and budgets become imperiled and angry business sponsors halt the project. integration. PowerExchange ensures that even novice developers can maintain data integrity across the migration. Unified. not in the end-to-end data migration process. By leveraging PowerCenter’s codeless and wizard-driven approach for Oracle data conversion. Ensure Data and Referential Integrity Mainframe migration projects are often stalled at the interpretation and translation of data and referential integrity.Built-In Data Transformation and Correction Capabilities to Address Data Quality in Legacy Applications The Informatica product suite helps data migration teams by enabling the team to focus on the data and not code. Once issues like the mapping of mainframe keys to Oracle primary and secondary keys has been resolved. Single. developers can spend time focusing on the most efficient schema. load. Metadata-Based Data Integration Platform to Support the Data Migration Lifecycle When data migrations projects are driven by teams that are focused exclusively on the target system. and explode” phenomenon. only to find more errors. This occurs when developers code the extraction and conversion logic thought to be required for migration. unified. PowerCenter provides a single. By automatically identifying the relationships of non-relational mainframe data and intuitively representing them to developers. PowerExchange automatically identifies all relevant referential relationships in the mainframe data files and represents them in a manner that can be easily understood and maintained across the migration. They fix the errors and rerun the conversion process. instead of trying to ensure basic operation. then attempt to load it to the target business application. and so on. for example. teams can focus more on the business rules and data. scalable enterprise data integration platform with a robust library of transformation and data services capable of handling all data conversion on any mainframe data migration project. and explode” cycle. Understanding the referential “child and parent” relationships of a mainframe file or set of files is often a tedious and complex undertaking for development teams that may be more familiar with relational tables. extraction. and less on the code. PowerExchange allows developers to spend their time focusing on improving overall performance of the new system instead of having to ensure the accuracy of data—a tedious process. or. Focus on New System Performance By simplifying the identification. only to discover an unacceptably large number of errors due to unanticipated values in the source data files. PowerCenter breaks this “code. load. perhaps not well-versed in either approach. and manipulation of disparate sources with an intuitive and universal interface. unified 14 .

With its metadata-driven architecture.White Paper platform based on a metadata-driven architecture. data access. Figure 7: PowerCenter Lineage Diagram Demonstrates the Flow and Transformation of Data From the Mainframe to Oracle RDBMS The foundation for all of PowerCenter’s data integration components is the shared metadata. PowerCenter promotes faster and more flexible iterations in the data migration lifecycle. PowerCenter enables immediate visibility into those changes. to preparing it in the format required for upload into an Oracle DBMS. data conversion. PowerCenter enables data lineage problems to be traced at a metadata level. from the mainframe to an Oracle system. and Web Services 2 3 FIREWALL Reusability/Team Productivity 4 Analyze/ Profile Extract/ Transform 6 Validate/ Lead Packaged Applications Iterate 1 7 8 Relational and Flat Files Access source systems/data Access target/data Execute Migration Target Application 9 Synchronize Mainframe and Midrange 10 Audit/Lineage Informatica Data Integration Platform Figure 8: PowerCenter Is the Ideal Platform for Migrating Data PowerCenter’s metadata management capabilities provide visibility across the entire data migration process—from sourcing legacy applications and cleansing the legacy data. using PowerCenter. 5 XML. When changes are made anywhere in the profiling. Figure 8 shows how PowerCenter is used for migrating data. or loading process. Migrating Off the Mainframe 15 . Figure 7 shows the flow and transformation of data. Messaging.

Furthermore. instilling new Oracle application users with confidence that legacy application data has in fact been converted and moved from the mainframe. Accessing source data 3. Preparing and loading data into the target system 5. unified data integration platform.PowerCenter helps data migration teams trace and prove how data has been converted and moved. The top six challenges associated with migrating data off the mainframe are: 1. please visit us at www. and reduces risk. PowerCenter and PowerExchange allow data migration teams to leverage all these capabilities from a single. ensures scalability. Identifying and analyzing source data 2. Conclusion and Next Steps Mainframe data migrations are complex. To find out more. unified data integration platform. what is your next step? Contact Informatica to find out how our enterprise data integration software can help your next mainframe migration project. Now that you have a solid understanding of the challenges around mainframe data migration and how Informatica enterprise data integration software can help you overcome them. Supporting the data migration lifecycle 6. The capabilities include: • Data profiling capabilities for identifying and analyzing source data • Universal data access capabilities for accessing source data • Built-in transformation and correction capabilities for addressing the quality of data in legacy applications • Single. They should not be approached as singular event. unified data integration platform to support the data migration lifecycle Furthermore. whether related to legacy mainframe applications or the target Oracle application. 16 . This increases or call us at (800) 653-3871. Data migration activities. and between technical and functional resources. Addressing the quality of the data within the legacy applications 4. This promotes effective and productive communication between legacy mainframe and Oracle resources. PowerCenter alleviates the politics associated with data migration projects. These capabilities also help with user adoption. Both PowerCenter and PowerExchange offer data migration teams powerful capabilities to meet each of the five data migration challenges. The enhanced data visibility and tracking helps organizations comply with reporting requirements. Accommodating behavioral changes The best way to overcome these challenges is to rely on Informatica enterprise data integration software. can be centralized within a single.

White Paper Migrating Off the Mainframe 17 .

385.Worldwide Headquarters. Printed in the U.3871 www. All other company and product names may be tradenames or trademarks of their respective owners. CA 94063.A.385. and. All rights reserved.800.informatica. Informatica Offices Around The Globe: Australia • Belgium • Canada • China • France • Germany • Japan • Korea • the Netherlands • Singapore • Switzerland • United Kingdom • USA © 2006 Informatica Corporation. USA phone: 650.5000 fax: 650.5500 toll-free in the US: 1.S. Redwood City. PowerCenter are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. 100 Cardinal Way. J50837 6691 (07/11/06) .653. the Informatica logo.