Reduce Application Downtime and Risk

MDRapid and Midrange Dynamics change management (MDCMS) work together to substantially reduce business application downtime and risk as you deploy database changes across your enterprise. Ultimately, your IT team can respond with more agility to business needs and enhancement requests. A move to modern and efficient database architecture becomes easier to plan and achieve.

MDRapid employs high availability technology in conjunction with change management techniques to convert IBM i database files with minimal interruption. This strategy allows your business applications to continue to access databases as usual while upgrades are taking place.

MDRapid uses MDTransform to convert and migrate data to new file formats while the application is in use. Any changes made to the current version of the files are journaled and synced with the new version held in the staged library. Thanks to a low performance footprint, users are not impacted during this process.

Since MDRapid deploys database changes quickly, even for multi-million- and multi-billion record files that have an extensive amount of update activity, it’s easy to integrate MDRapid into day-to-day operations.

For example, consider a table with 388 million records. There are 101 logical files over the table, 30 of which are join files to additional tables:

  • Time to transform data into new version of table, including the build of the 101 logicals, using MDRapid while application still active: 90 minutes*
  • Time for MDCMS to need application in lock state to move in new version of all files: 17 seconds
  • Time a change management product not using MDTransform/MDRapid would need to have application in lock state while performing a CPYF on same machine: 15 hours

How MDRapid Works

How MDRapid Works

Click to view a larger image

Taking full advantage of control and auditing functionality inherent with change management, MDCMS and MDRapid work in concert to manage database updates and implementation of all associated application objects.

  • MDCMS creates a new version of the DB2 file or SQL table in a temporary library.
  • MDCMS checks to see if the current version contains sufficient records to require use of MDRapid based on application preferences.
  • User or system approves the launch of MDRapid.
  • MDRapid creates empty members in the new format of the staged files.
  • MDRapid ensures that the limits for record count and member count are high enough to accommodate all records and members in the current version of your production DB2 file or SQL table. MDRapid also provides for replicating a multimember DB2 file to several SQL tables.
  • MDRapid copies all records from the current version to the new version. You can specify custom data conversion and mapping parameters.
  • MDRapid builds any logical files including views and indexes once the initial copy is complete.
  • MDRapid simultaneously migrates any transactions performed in the live application until such time that the deployment of the changes should occur.
  • MDCMS moves all impacted objects to a backup library and moves the new files and related objects into the application. If an exception occurs, MDCMS automatically rolls back. Since all copying and building were done beforehand, this final step is performed very quickly.

Relax! It’s Under Control

One of the big benefits of using MDRapid is that your business is protected from risk. MDRapid maintains all changes in a safe staging environment. If there is any kind of interruption (e.g., a hardware problem, power outage, or subsystem termination), you can easily re-start the conversion process. Your applications and data remain unaffected until you are ready to move the new files into production. If anything goes wrong, MDCMS’s robust installation and rollback capabilities protect your production environment, and you can roll back to your old production data.

MD Extras

Helpful job monitor — Display job status, total number of members and records, percent complete, time estimated to complete, and elapsed time.
Status Updates — Convenient email notifications and status exit points keep you informed.
Automatic installation — Specify a time window for installation of database changes.
Continue where you left off — Hold or end any MDRapid job during the copy or sync phase, and MDRapid will pick up where it left off when restarted, even after an IPL.


*Due in part to SQL Engine enhancements included in IBM i OS V7R2. On an older version of the OS, this would take approximately 3 hours. The 17 second application lock time would still apply.