When moving MDCMS from one partition to another partition or physical system, the following steps will make the transition easy. The assumptions outlined in this document are based on moving to another system. If you adding a new system/partition; there is a separate Quick Tip document for that process. The term “system” is used here for simplicity sake, but the process is the same if you are moving to another partition.
Prior to Hardware Change
Request new license keys for the system here: https://support.mdcms.ch/plugins/servlet/desk.
- Be sure and provide the old serial number and partition along with the new serial number and partition.
- When you receive your keys, you have completed the Initial portion of the process.
Making a Smooth Transition with MDCMS.
Product Check
If you are doing an image of your old system to your new system, you may not need the following step, but because of the different ways people move to a new box, we recommend that you run the MDINSTSAVF command with your existing MDCMS installation save files or from a new build of MDCMS downloaded from the website. This makes sure all the commands are in QGPL, the MDOWNER profile exists, and the correct directory entries are established. The process usually takes less than 20 minutes. Complete instructions can be found in the MDCMS Installation Guide.
Caution: Be sure to select the same MDCMS release.
Completing the steps above will make the ‘go-live’ transition smoother. The libraries and IFS folder that you will need to make sure are moved to the new system are identified below.
MDCMS
MDXREF
MDSEC
MDREP (optional library may or may not be on your system)
IFS Folder
MDCMS/
If you have stored your job descriptions or special MDCMS programs in a separate library, then you will want to make sure it goes along with your MDCMS libraries.
Connectivity Check
If you have defined your OS locations with a same DNS name, you shouldn’t have to change any location information. However, you will want to do a sync to make sure the connections are re-established and the appropriate connections are in place behind the scenes.
To test your DDM connection to each system:
- MDCMS
- Select option 1 – MDCMS Setup Menu
- Select option 6 – OS/400 Locations
- Select option S – Next to the production system on development
Repeat this on the production system for the development location.
To verify your FTP connection (from the Development System):
- MDCMS
- Select option 1 – MDCMS Setup Menu
- Select option 7 – Distribution Locations
- Select option T – Test Connection
Differences to Watch for
Changed the DB name.
Confirm the DB name is the same.
STRSQL and it will show you the database you connected to.
Verify it matches the location record on the development partition.
- MDCMS
- Option 1 MDCMS Setup Menu
- Option 6 OS/400 Locations
- Option S Next to the production system on development
Changed the location id or IP address
On the development system
Update the Location Information
- MDCMS
- Option 1 MDCMS Setup Menu
- Option 6 OS/400 Locations
- Option 3 Next to the old location
Update with the new location information.
Any existing distribution levels need to be copied to the new location name before you delete the location.
Location id changes requires an update the Distribution Levels
- MDCMS
- Option 1 MDCMS Setup Menu
- Option 7 Distribution Levels
- Option 3 Next to the old location records
Update with the new location information.
On the new system
Location id changes require an update the System Settings to reflect the new location id
- MDCMS
- Option 1 MDCMS Setup Menu
- Option 11 System Settings
Update the location id to match the MDCMS
If you make any of these changes be sure and perform the Connectivity Check after you have made the changes.
If you make any location/distribution level changes you will want to make MDPUSH is stopped and restarted to pick up these changes.
On the new System
- MDCMS
- Option 1 MDCMS Setup Menu
- Option 13 Services
- Option E End MDPUSH
Watch the number of jobs go to 0.
- Option S Start the MDPUSH job again.