x

To start the migration job:

1. Click the Workspace link in the toolbar and click Configuration/Monitor.
2. Expand the Server folder, right-click Migration, and select Resource Management, as shown in the following image.

   

3. The Resource Management Migration page opens, as shown in the following image.

   

   Note: All values are required.

   The following options are available:

   Release to migrate data from

   The release number you are migrating from. Options include 53x, 710-712, 713-718, and 76x.

   Note: For Service Pack releases, 5.3x includes all 5.3 releases; 710-712 includes 7.1.0, 7.1.1, and 7.1.2; 713-718 includes 7.1.3 and later 7.1x releases, and 76x includes all 7.6 releases.

   Server name to migrate

   The server name used by Resource Management in the old release. You can find the server name in the GKESET FOCEXEC.

   EDACONF directory to migrate

   The path to the EDACONF directory of the release being migrated. Examples are C:\ibi\srv76\wfs for Windows and /home1/ibi/srv71/wfs for Unix.

   Migrate system data

   Select Yes if the previous releases system data should be migrated. If Yes is selected, SMCNTRL, SMPRMTRS, and SMPRL data will be migrated. Only custom BRL members will be migrated. The SMKNBNAME value in SMCNTRL will not be migrated and any Govern and/or Advise values will be set to OFF. Any compiled rule files must be rebuilt after the migration is completed and new Govern and/or Advise values must be set. The default value is No.

   Note: If multiple migration runs are being made, only migrate the system data once.

   Create 7.6 compatibility masters

   Select Yes if you want to have 7.6 style masters created that will allow existing custom reports to run. Some modifications to your custom reports may be required.

   Start Date

   The earliest date of the data to be migrated. The format is MM/DD/YYYY. The default value is 1/1/1995.

   End Date

   The latest date of the data to be migrated. The format is MM/DD/YYYY. The default value is the current date.

4. Click Next. The Deferred Execution page opens, as shown in the following image.

   

5. Accept the default date and time, or enter the specific date and time that you want the migration to run. Click Continue to submit the Deferred request. Confirmation of the request appears, as shown in the following image.

   

   To view the progress of the Deferred request, expand the Special Services and Listeners folder to see a list of the various special services and listeners.

6. Right-click on the DFM item to display the context menu for the Deferred Manager.

   

7. Select Deferred List to display the list of deferred requests and to view the request name that was displayed when the deferred migration job was scheduled. Examples of request names are listed in the Deferred ID column, as seen in the following image.

   

The Status column shows the state of the deferred request, which can be Queued, In-progress, or Ready. To see if the status has changed to Ready, either keep refreshing the page using the refresh options located at the top of the page, or redisplay the page at a later time. Once the status is Ready, right-click the request line and select Get to review the job output.

x

1. To start the migration process, click the Resource Management link on the toolbar in the Web Console. A warning message is displayed, as shown in the following image.

   

   This warning message indicates that the structure of the Resource Management repository has changed. A migration process is required in order to update the existing repository so that new data columns can be archived to the repository. If the migration process is not run, monitor data will still be collected and archived but without the new data columns.

   You can:

   • Ignore the message contents by closing the message window. The repository will still have the old structure and the warning message will continue to be shown.
   • Start the migration process by closing the message window and right-clicking the warning link in the statistics table. Select Migrate Configuration, as shown in the following image.

     

   The Resource Management Configuration Migration pane opens.

2. Select Phase 1 actions from the drop-down menu (for Relational repository only).

   DDL Only

   Select this option if you do not have DBA authority over the existing Resource Management repository tables. This option creates a file, rmldb.sql, which contains RDBMS specific DDL.

   Click Next to display the instructions for the location of the rmldb.sql file. Give this file to the DBA for processing.

   Note: Your DBA must create the new Repository tables in the same location as the original 7.7 tables and both sets of tables have to be accessible on the same Adapter connection on the server. The new tables will have the release number appended to the name. The format will be tablename_release.

   Once the repository tables have been created, return to the Web Console and click Resource Management. The warning message opens again. Close the window and right-click on the warning link in the Statistics table and then click on the Migrate Configuration entry to continue the Configuration Migration process. The process will resume at phase 2, as shown in the following image.

   

   Yes

   Select this option if you have DBA authority over the existing Resource Management repository tables. New repository tables will be created with the _7703 suffix, and the process will continue at Phase 2.

   Note: If migrating a FOCUS repository, there will be no Phase 1 drop-down menu.

3. Select Phase 2 options from the drop-down menu.

   No

   Select this option if you do not want data to be copied from the old repository to the new one.

   To run the migration process at a later date, right-click Resource Management in the navigation pane and select Configuration, Migrate 7700-7702 data.

   Yes

   Select this option to copy data from the old repository to the new one.

   1. Click Next to schedule the migration procedure.

      The Deferred Execution pane opens, as shown in the following image.

      

   2. Select the date and time for the execution to take place. Click Continue.
   3. To view the List Configuration Migration Job Output, right-click Resource Management in the navigation pane and select Configuration, List Configuration Migration job output, as shown in the following image.

      

   4. A list of jobs opens. Right-click on the job and select Get to see if there are any focus errors, as shown in the following image.

      

4. In the Remove old configuration and data files step (Phase 3), you can choose whether to remove the old configuration files or perform this action in the future. To perform this step, right-click Resource Management in the navigation pane and select Configuration, Remove old Configuration files.

   Note: Once you choose to remove the old configuration files, the option to migrate data will no longer be available.

x

To start the migration job:

1. Click the Workspace link in the toolbar and click Configuration/Monitor.
2. Expand the Server folder, right-click Migration, and select Resource Management, as shown in the following image.

   

3. The Resource Management Migration page opens, as shown in the following image.

   

   On MVS, the migration page uses data set names to locate the Resource Management files to be migrated instead of an ECADONF path value.

   The following options are available:

   Release to migrate data from

   The release number you are migrating from. The only previous release supported for MVS migration is 76x.

   Server name to migrate

   The server name used by Resource Management in the old release. You can find the server name in the GKESET FOCEXEC.

   MASTER files dataset name

   The dataset name that was used to save the MASTER files during configuration of the previous release.

   ACCESS files dataset name

   The dataset name that was used to save the ACCESS files during the configuration of the previous release.

   Migrate system data

   Select Yes if the previous releases system data should be migrated. If Yes is selected, SMCNTRL, SMPRMTRS and SMPRL data will be migrated. Only custom BRL members will be migrated. The SMKNBNAME value in SMCNTRL will not be migrated and any Govern and/or Advise values will be set to OFF. Any compiled rule files must be rebuilt after the migration is completed and new Govern and/or Advise values must be set. The default value is No.

   Note: If multiple migration runs are being made, only migrate the system data once.

   Create 7.6 compatibility masters

   Select Yes if you want to have 7.6 style masters created that will allow existing custom reports to run. Some modifications to your custom reports may be required.

   Start Date

   The earliest date of the data to be migrated. The format is MM/DD/YYYY. The default value is 1/1/1995.

   End Date

   The latest date of the data to be migrated. The format is MM/DD/YYYY. The default value is the current date.