1. 1 Source cartography & modeling Source technical objcts (DDL, programs, jcl,..) DATA MIGRATION general method Models compatibility & migration rules definition Data migration Data migration validation Source base model Migrated data Data migrated & validated Target technical objects (DDL, programs, jcl,..) modèle base cible Target cartography & modeling

2. 2 CARTOGRAPHY & MODELING cartography – Galois connections

3. 3 CARTOGRAPHY & MODELING modeling – logical model

4. 4 CARTOGRAPHY & MODELING modeling – semantic model

5. 5 121015091249# attributes 11012873# relations 105112 # entity types Semantic model Logical model Physical model MODELING synthesis

6. 6 Source cartography & modeling Source technical objcts (DDL, programs, jcl,..) DATA MIGRATION general method Models compatibility & migration rules definition Data migration Data migration validation Source base model Migrated data Data migrated & validated Target technical objects (DDL, programs, jcl,..) modèle base cible Target cartography & modeling

7. 7 Target model Source model IS COMPATIBILITY Semantic level Logical level Physical level ? ? ? Sematic model Logical model Physical model Sematic model Logical model Physical model

8. 8 Enrichment ? SEMANTIC DIFFERENCES EXAMPLES contracts damages addendum sourcetarget exemple 2 : relations differences example 1 : concepts differences contracts damages addendum contracts : A contract might exist for a person or a group of person contracts : A contract is linked to one and only one person Impoverishment ?

9. 9 sourcetarget example 1 : transformations differences A multivaluated field : PHONE (5) Is transformed in 5 colums PHONE1, …PHONE5 Is transformed in a table with a foreign key PHONENBR, FK example 2 : implementation differences A relation between 2 entities Is implemented as a set in a CODASYL DBMS  the records are accessible only through the record owner ( the father) Is implemented as a table with a foreign key in relational  the records are directly accesible LOGICAL DIFFERENCES EXAMPLES

10. 10 sourcetarget example 1 : format differences the field « DATE »is defined in 6 figures is defined as a field « DATE » example 2 : coding differences codingdata are in EBCDICdata are in ASCII PHYSICAL DIFFERENCES EXAMPLES

11. 11 MAPPING TOOLS

12. 12 Source cartography & modeling Source technical objcts (DDL, programs, jcl,..) DATA MIGRATION general method Models compatibility & migration rules definition Data migration Data migration validation Source base model Migrated data Data migrated & validated Target technical objects (DDL, programs, jcl,..) modèle base cible Target cartography & modeling

13. 13 TRANSFORMATION RULES CODING

14. 14 SOURCE CODE GENERATION FOR THE UNLOAD The tools generate the unload program source code for the source persistent objects  Depending on the source technological environment  Programming language  Type of persistent objects  By integrating the transformation rules  In function of the target persistent objects The programs generate « source data files » ready to be loaded.

15. 15 UNLOAD generation program JCL

16. 16 Source data validtion VS Target model Synthesis

17. 17 Source data validtion VS Target model Details

18. 18 Source cartography & modeling Source technical objcts (DDL, programs, jcl,..) DATA MIGRATION general method Models compatibility & migration rules definition Data migration Data migration validation Source base model Migrated data Data migrated & validated Target technical objects (DDL, programs, jcl,..) modèle base cible Target cartography & modeling

19. 19 Data migration validation  3 methods to validate a data migration 1.Technical counters 2.Functional counters 3.Content comparison

20. 20 Functional counters

21. 21 CONTENT COMPARISON process

22. 22 CONTENT COMPARISON common model

23. 23 CONTENT COMPARISON extraction programs generation

24. 24 CONTENT COMPARISON comparison

25. 25 CONTENT COMPRISON comparison – Keys interrupt

26. 26 CONTENT COMPARISON comparison– value differences

27. 27 Programs classification according to the DB risks they might have  A weight is given to each entity type, according to the number of parents and child they have  To each DB access verb, a weight is given according to the type of action ( read, write, delete…)  In a module  The weight of an access is a function of the weight of the verb and the entity  A module weight is the sum of the weight of each accesses in the module  The program weight is the sum of the weight of the modules PROGRAM WEIGHT CALCULATION

28. 28 PROGRAM WEIGHT CALCULATION

29. 29 ic62blad icada Low risks ic5623b ic62ur01 icaccdo ic62btot ic5623 ic62i ic180 ic56conv ic679 ic242 ic180dch icaanwb icaanw ic180sp ic18i ic62b250 ic62bfsa ic180ap ICAFL1 ic003 ic180st2 ic62bvgl ic2tgvja High risks IDENTIFICATION of the « RISKY » programs