Upgrading 9.2 Reviewer batch jobs

The Upgrade 9.2 Reviewer Batch Jobs command allows you to update workspace references used with your existing 9.2 batch jobs and migrate them to versions that will work with the current version. The references to the data sources contain the paths to the databases that contain the feature classes and tables to be validated by checks in the batch job.

The command initially searches the specified directory and, optionally, subdirectories for batch jobs, regardless of whether they have been created using GIS Data ReViewer 9.2 or a later version. After the tool finishes searching for batch jobs, it reports the number of batch jobs that have been loaded as well as the number that had no workspace or that had errors reading the workspace information. If there are any 9.3 or later batch jobs that already exist, they are skipped, and only the 9.2 batch jobs are displayed.

For each batch job, the following properties are displayed:

• ID—A number associated with the batch job
• Batch Job—The path to the batch job
• Workspace—The path to the workspace the batch job is referencing
• Valid?—Indicates whether or not the workspace path is valid
• Version—The name of the database version, if the workspace is an enterprise database
• New Workspace—The path to the new workspace to be referenced by the batch job

If the workspace is valid, there is a check mark in the Valid? cell. If the workspace path is invalid, it appears in red text, and the Valid? cell contains a red circle with an "X" in it.

The Convert 9.2 Reviewer Batch Jobs dialog box with checks to be migrated

You can update the invalid workspace paths as needed and upgrade all the batch jobs to the current version. This process automatically updates the paths to all the feature classes and tables in the checks to reference the workspace you specify. Only checks with valid workspace paths will be upgraded from 9.2 to the current version. When the batch jobs are migrated to work with 10, _10 is appended to the end of the original batch job's name. For example, SoCal_AllChecks.rbj would become SoCal_AllChecks_10.rbj.

Note:

If you are migrating a batch job that contains checks for database validation, topology, or z-values, the new workspace must contain the appropriate tables and feature classes. For instance, if a batch job with a topology check is being migrated, the new workspace needs to have a topology defined.

Steps:

1. Start ArcMap.
2. If necessary, add the Upgrade 9.2 Reviewer Batch Job by doing the following:
   1. On the main menu, click Customize > Customize Mode.

      The Customize dialog box appears.

   2. Click the Commands tab.
   3. In the Categories list, click Data Reviewer.
   4. Click and drag the Upgrade 9.2 Reviewer Batch Job command to a toolbar.
   5. Click Close.
3. Click the Upgrade 9.2 Reviewer Batch Jobs command on the toolbar.

   The Upgrade 9.2 Reviewer Batch Jobs dialog box appears.

4. Click the ellipsis (...) next to the Search the following folder for RBJs text box.

   The Browse For Folder dialog box appears.

5. Navigate to the directory that contains the batch jobs you want to migrate.
6. Click OK.
7. To include any subdirectories in the search, check the Include Subfolders check box.
8. Click Refresh.

   Once the process is complete, the batch jobs from the directory appear in the Upgrade 9.2 Reviewer Batch Jobs dialog box. The Load Batch Job Results dialog box appears with the number of batch jobs that have been loaded from the directory.

9. Click OK.

   The Upgrade 9.2 Reviewer Batch Jobs dialog box appears with the names of the 9.2 batch job workspaces in red.

10. For the first batch job in the list, click the ellipsis (...) at the end of the row.

    This allows you to change the database that is being referenced by the batch job.

    The Select Workspace dialog box appears.

11. Navigate to the geodatabase that contains the data to be validated by the batch job.
12. Click Select.

    The name of the database appears in the New Workspace cell for the first batch job in the list.

13. To use a different database for another batch job, repeat steps 10–12.
14. Click Apply.
15. Click the Close button .