Executing the Migration Database Analyzer Program

To fill in the Processing Options, use these guidelines:

• Enter the target library to create the JD Edwards EnterpriseOne indexes.

  For this processing option, enter QTEMP or an empty library you have created. The program creates the JD Edwards EnterpriseOne indexes in this library. After the index is created, the index is deleted from the library. Therefore, when the program is finished the library is again empty.

• Enter the library to check for the existence of the JD Edwards World files.

  For this processing option, enter either the name of a library in the library list or leave it blank. If you enter a library name, the program checks for the existence of JD Edwards World files in that library and attempt to create the JD Edwards EnterpriseOne indexes for those files in the library name you entered for Processing Option 1.

  If you leave the processing option blank, the program uses *LIBL and searches the JD Edwards World library list to determine if the file exists. It then attempts to create indexes for those files in the library you entered for Processing Option 1. If the environment is set up so that you have both a common and a data library, leave this processing option blank.

• Enter 1 for a full report of all conditions.

  It is suggested that you enter 1 in this field to get a full report for all indexes that were created or failed. If you leave this processing option set to 0, the report only lists the indexes that failed to create.

• Clear process status flag in F98888. Enter 1 to clear the process status flags in F98888.

  The default for this option is 0. This means that the status flag in the F98888 file will not be cleared. The status flag indicates if the creation of the index was successful or not. If the status flag is not cleared then you are able to rerun this job using data selection. You can then process only those files that had issues the first time.

  For example, you could run the process again and change the Migration Status Field NE 4 on the data selection. If errors still show up, you can continue to run the program this way until you have cleaned up all errors.

  If for some reason you want to run the entire program again, you can change the processing option value to 1 instead of 0. The status field in the F98888 file would then be cleared first so all indexes would be created again.

  Enter 1 to print a duplicate record detail report for each file where duplicate records are found or enter 0 to bypass the report.

  If you leave the processing option value as 1, a separate report prints for each file that has duplicate records. This report prints all duplicate records along with the key fields associated with the index that could not be created. The relative record number of the record also prints. You can use this report to clean up the duplicate records. You should clean up records so that only one record with the same key values exists. To clean up duplicate records, you must either change a value for one of the key fields or delete one of the records.

  After you clean up duplicate records, run the Migration Database Analyzer program again to make sure all indexes can be created successfully. You can use data selection as described in step 4 above.