m-Power Documentation
How to Convert Previously Created mrc-Productivity Series Applications to m-Power
We realize that many of our customers who are converting from mrc-Productivity Series to m-Power have already customized and deployed many applications. However, in the process to convert to m-Power, all mrc-Productivity Series Data Dictionaries must be converted to m-Power. (More information about this process can be found here ).
While we will copy all of your tables and application specifics (via the MRC2MPOWER command), we do not copy over any HTML changes made. This document will serve as a reference as a “how-to” manually convert all previously created applications to your new m-Power Data Dictionary. For the purposes of the document, your old Data Dictionary, will be titled DDOLD and your new m-Power Data Dictionary will be titled DDNEW. Additionally, this document assumes you are installing m-Power on a Windows server. If not, please modify the paths accordingly. The document also assumes you have already installed m-Power.
After creating DDNEW via the m-Power interface and running the MRC2MPOWER command we are ready to begin.
1. On your mrc-Productivity Series server copy all objects located in c:\m-power\mrcjava\WEB-INF\classes\DDOLD. Place them on the m-Power server in c:\m-power\mrcjava\WEB-INF\classes\DDNEW.
2. Within Windows Explorer & your favorite test editor, edit each .HTML file and do a Find & Replace, Finding DDOLD and replacing it with DDNEW.
3. mrc Menu (If you are not utilizing mrc Menuing, please move on to Step 4)
a. Assuming you have done work with the menuing system, please copy the following tables from DDOLD to DDNEW: MRCSEC1, MRCSEC2, MRCSEC3, MRCSEC4.
b. Within m-Power, click the “Application Menu & Security,” then click on the “Manage Menu Options,” and change each option to point from DDOLD to DDNEW.
4. External Objects (If you are not using any mrc Java External Objects [Dropdown lists or Security] please skip to Step 5)
a. Under the Data Dictionary tab, click Manage External Objects and change the Class Name to point from DDOLD to DDNEW.
5. We are now ready to recompile all applications in the DDNEW. Within the m-Power interface, click the “Edit” button for each application, then click the “Build/Compile”. Be sure to specify “No” to overwriting the HTML and the XML . Note: You have already handled the HTML and XML in Step 2 above.
6. Be sure to modify the Header (Accessed by clicking the Data Dictionary tab, then clicking the “Edit Data Dictionary Files” link. From here click the Header link.
a. Change all instances of DDOLD to DDNEW.
Congratulations – your DDNEW instance should now mirror your DDOLD instance. Be sure to now point your end users to DDNEW.
Note: DDNEW cannot be accessed via the 5250 interface. Similarly, you will not be able to modify application within DDOLD via the Web interface.
Common Question:
We still run a lot of applications from the 5250 interface. Namely, green screen summaries [MRCSUM] & scheduled reports [MRCRPTSND] . What am I supposed to do with these applications?
mrc recommends you continue to utilize these applications in their DDOLD instance. To minimize confusion, we recommend:
1. On your Windows server, delete the DDOLD folder from c:\m-power\mrcjava\WEB-INF\classes\DDOLD (always take a backup, just in case).
2. Since almost all of your applications in DDOLD are now being used in DDNEW, lets clean up DDOLD
a. Delete all Retrievals from DDOLD.
b. Delete all Reports from DDOLD that are not being used in conjunction with MRCRPTSND.
c. Keep the summaries you want, however delete the ones that are no longer being used.
d. Remove maintainers that are no longer being used. If you have active maintainers, you may wish to leave them as they will allow you to alter the existing table if necessary.
3. Remove unnecessary applications from DDNEW
a. Since your existing summaries exist in DDOLD, there is no need to have a duplicate in DDNEW. Remove the appropriate summaries from DDNEW.
b. Similarly, remove Reports that are only being used for MRCRPTSND from DDNEW.
4. Move necessary data files from DDOLD to DDNEW
a. From the 5250 interface, modify each summary in DDOLD to point to DDNEW
b. Copy all physical files from DDOLD to DDNEW
c. From the Data Dictionary tab, click the “Manage Data Dictionary Tables” and change the “Schema” option from DDOLD to DDNEW
d. Recompile all applications that reference these physical tables. Be sure to specify “No” to overwriting the HTML and the XML .
5. User Created CL/RPG External Objects
a. Move objects from DDOLD to DDNEW (or if you store all programs in one Dictionary, please move them there).
b. Make sure that any references within RPG/CL pointing to DDOLD now points to DDNEW.
c. Under Data Dictionary, Click the “Manage External Objects” link and modify any references to DDOLD to DDNEW for existing RPG/CL programs.
d. Be sure to click the “Create Stored Procedure” for each changes object.
e. Be sure to recompile any application that uses these external objects. Be sure to specify “No” to overwriting the HTML and the XML .
Want to receive weekly insight, tips, viewpoints, and news from a 28-year industry veteran? Enter your email below to subscribe!
Customers
