1. Home
  2. Knowledge Base
  3. Important Steps to take after Migration to 7.4

Important Steps to take after Migration to 7.4

System Settings

Each MDCMS instance (System) now requires an ID to uniquely identify it in order to reliably converse with the other instances. The ID is saved in the Location ID in the System Settings (settings menu option 11). It can be any alphanumeric value up to 10 characters. It is recommended to avoid embedded spaces or special characters. It is essential that the ID entered is truly unique within the collection of IBMi systems/partitions.

OS/400 Locations

The connection information for DDM connections and for RFP distribution have been combined into OS/400 location settings to reduce the amount of connections necessary to be defined.
Each Location is uniquely identified by a Location ID. The Location ID for each location MUST match the system setting location ID of the target system. MDCMS initially names the Location IDs in the OS/400 locations MDRLnnnnnn. This can be easily renamed to match the correct ID by using option 7.
Each location should be carefully reviewed to ensure that the migrated data match the settings required for DDM connectivity and RFP distribution connectivity. It is possible to have a location only for DDM, only for distribution or both. See the MDCMS User Manual for more information about the individual parameters.
For each location that MDWorkflow uses as the connection repository (typically only one location is used for the repository), use option S to sync all information from the local location to that location. This is should include *LOCAL, when the local location is the repository.

Distribution Levels

The Distribution Queues menu option has been replaced by Distribution Levels. This allows for the simple reuse of a connection definition for many applications, levels and target levels.
The migrated data should be carefully reviewed, particularly the Target Level definition. MDCMS had previously allowed a Target Level of 0, but from MDCMS 7.4, the target level must be defined to ensure proper tracking of installations on the target systems. If a definition is incorrect, it can be deleted and then re-added with the correct target.


The various batch services that may be used by MDCMS are now listed/managed from new setting Services. The service list should be reviewed to determine the correct setting for auto-start (where applicable), job queue and end time. Any services already set up as scheduled jobs can continue to be so, though the parameters have been enhanced, so it is recommended to re-prompt the commands for the scheduled jobs to change the commands where necessary. Any jobs that shouldn’t auto-start should be set to N in the service list. The prior versions of MDCMS used data areas to contain the default job queue – those data areas no longer exist, but the values are carried across to the services table during the upgrade.


The MDMAIL service, along with the MDMAIL and MDMAILF commands have been moved from library MDCMS to library MDSEC. If you have qualified the library for commands MDSTRMAIL, MDENDMAIL, MDMAIL or MDMAILF anywhere, you’ll need to update those programs, exit points or scheduled jobs to use library MDSEC instead. Because of the move of these objects to MDSEC, you no longer require MDXREF or MDCMS in the library list to export and email reports.