Deploy IBM i database changes in minutes

How MDRapid Works

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.

  1. MDCMS creates a new version of the DB2 file or SQL table in a temporary library.
  2. MDCMS checks to see if the current version contains sufficient records to require use of MDRapid based on application preferences.
  3. User or system approves the launch of MDRapid.
  4. MDRapid creates empty members in the new format of the staged files.
  5. 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.
  6. MDRapid copies all records from the current version to the new version. You can specify custom data conversion and mapping parameters.
  7. MDRapid builds any logical files including views and indexes once the initial copy is complete.
  8. MDRapid simultaneously migrates any transactions performed in the live application until such time that the deployment of the changes should occur.
  9. 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.