MDMIGMD - Merge MDCMS Configuration and Activity Data
The MDCMS Merge Data (MDMIGMD) command copies configuration and activity data from one instance of MDCMS to another instance. This provides a quick way to merge work that was previously done across several instances into one instance.
MDCMS ensures that RFP numbers are unique. If the RFP number already exists in the target instance, a new number will be applied to the RFP details and objects in the RFP.
If active checkouts are to be copied, MDCMS verifies for locked modifications or deletes that the object isn't already locked in the target instance. If already locked, the object request is omitted.
The command should be run from a command line within the instance that is the target for the data to be copied to.
If configuration data will be copied, the application group must already be defined in the target and the level(s) to copy must NOT already be defined. Additionally, distribution levels will only be copied for OS/400 locations that are already defined in the target instance.
During the Merge process, configuration data is copied first, followed by activity data. Activity will only be copied if the level exists in the target instance, which occurs during the copy of the configuration data or if the level was already there.
It is recommended to back up the target MDCMS and MDXREF libraries prior to running this command, in case you aren't happy with the results.
Restrictions:
- You must have MDSEC authority for Application Group maintenance (md/3)
- The version of the from instance and target instance must be the same
MDMIGMD Parameter Table
| Column 1 | Column 2 | Column 3 |
|---|---|---|
| Title | Type | Description |
| From Product Instance | CHAR | the suffix of the MDCMS and MDXREF libraries containing the data to be copied from |
| Application | CHAR | the application to be included in the copy *ALL - all applications that are defined in both the from instance and the target instance. |
| Minimum Level | DEC | The lower limit of the range of levels to be copied |
| Maximum Level | DEC | The upper limit of the range of levels to be copied |
| Migrate Configuration | CHAR | *YES - for each qualifying APP that already exists in the target and each qualifying level that doesn't already exist, the following information will be copied: Levels, Attributes, Commands, Scripts, Templates used by copied attributes (if not already defined), Distribution Levels (for pre-defined OS/400 locations), Workflow Acceptance settings, MDXREF library list. *NO - Configuration Data isn't copied |
| Migrate Active Checkouts | CHAR | *YES - For each Application and Level in the range that exists in the from and to instances, the active checkouts will be copied. If an object is already locked on the target, it won't be copied for modifications and deletions. The copied information includes: RFP (will get a new number if prior RFP number already exists in target instance), Object information, commands for RFP or Object, scripts for RFP or Object, Project information (if doesn't already exist). *NO - Active Checkouts aren't copied |
| Migrate Install History | CHAR | *YES - For each Application and Level in the range that exists in the from and to instances, the installation history will be copied. This includes: RFP (will get a new number if prior RFP number already exists in target instance), Object information, commands for RFP or Object, scripts for RFP or Object, archived source, Project information (if doesn't already exist), Deployment log. Archived Objects, which are zipped and stored in the IFS, aren't migrated to the target instance. Refer to the original instance if an archived object needs to be restored. *NO - Installation History isn't copied |
| Migrate Active Send Info | CHAR | *YES - For each Application and Level in the range that exists in the from and to instances, the open RFPs to be sent will be copied. The copied information includes: RFP (will get a new number if prior RFP number already exists in target instance), Object information, commands for RFP or Object, scripts for RFP or Object, Project information (if doesn't already exist), Send History for targets attempted by open RFP. *NO - Open RFPs to Send aren't copied |
| Migrate Send History | CHAR | *YES - For each Application and Level in the range that exists in the from and to instances, the RFP Send History will be copied. The copied information includes: RFP (will get a new number if prior RFP number already exists in target instance), Object information, commands for RFP or Object, scripts for RFP or Object, Project information (if doesn't already exist), Send Log and Problem list. *NO - Send History isn't copied |