1. Home
  2. Knowledge Base
  3. MDRapid Enhancements in 8.2

MDRapid Enhancements in 8.2

This document briefly describes the enhancements provided with version 8.2.x of the MDTransform product.
See the build log for fixes made to 8.2.x after the initial release occurs.

From Build Date

February 4, 2020 When an SQL error occurs during the MDRapid data copy or sync process, it is logged and the table is flagged with a warning state, but the MDRapid process continues. Depending on the error, further syncing will often auto-clean the error. If not, the authorized user can specify to allow the installation in spite of the error and can copy all records in error to a separate file for manual review/cleanup.
March 22, 2020 MDSTRRAP and MDENDRAP commands to systematically start and stop some or all MDRapid Jobs for an RFP
new filter fields and F13=Repeat Opt key in the green screen console for MDRapid
April 2, 2020 The MDRapid console view in MDOpen has now been enhanced with:

  • Filter by active or inactive jobs
  • Multi-Select jobs to end, hold or restart
  • View the job log for an ended MDRapid job that encountered an error
  • Additional columns of information
June 10, 2020 The job queue to apply to a MDRapid template can now be browsed/created/managed by pressing F4 on the job queue name.
September 25, 2020 The MDRapid copy/sync jobs will have the library list of the job description for the target promotion level in case the copy will involve custom user defined functions.
October 15, 2020 MDRapid now starts a separate job to build logical files per target replication library to speed up the MDRapid prep process when many logicals and/or libraries are involved. Additionally, a new flag has been added to the MDRapid template to allow standalone logical changes to be handled by MDRapid to limit deployment downtime when physical files they are based on aren’t included in the RFP.
October 30, 2020 The maximum number of concurrent MDRapid copy jobs can now be defined for MDRapid templates to limit the impact to system resources during the replication of data to the new version of tables. Additionally, the sync and monitor jobs require a lot less resources than they did before to impact the system less.