IMS to SQL migration : Part 4 of 4

Last article in a four-part series.

Read the previous parts ->

Program adaptation

The first three parts of this article described the design of the new database and the migration of data. This last part describes how the applications will be modified to allow them to access the new database instead of the old IMS database.

This program adaptation must meet two constraints :


IMS to SQL migration : part 2 of 4

Second article in a four-part series

Read the first part ->

In our previous article, we had briefly described the principles of migrating an IMS database towards a relational database (SQL). In this new article, we are going to describe how the structure of the legacy database can be reverse engineered and how the new database can be designed.

The data migration is broken down into three phases :


IMS to SQL migration : Principles (part 1 of 4)

First article in a four-part series.

The IMS to SQL migration is broken down into two phases :

  • the first phase is the creation of the new database (OracleDB2...) that offers the advantages of the SQL language and the migration of the data.
  • the second phase is the transformation of the application programs in order for them to use the new database, without changing the functionalities. 

Subscribe to RSS - database migration