This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Creating a continuous reconciliation job


To run a continuous reconciliation job that you created, you must first manually start that job on the Reconciliation console. If the AR System server is restarted, it is recommended that you check whether the continuous reconciliation jobs have started.

You can configure reconciliation jobs to execute after a specified interval. If you specify the interval as 5 minutes, the job executes after 5 minutes. If a job takes 8 minutes to finish, then the next job starts immediately after the preceding job ends.

For more information about setting the interval, see Configuring Reconciliation Engine system parameters.

You can set any job as continuous and multiple jobs can be in the continuous mode at a given time. If the continuous jobs are running in parallel on the same production dataset, you must configure the continuous jobs to run the identify activity on all the source datasets in addition to the production dataset. For more information, see Configuring Reconciliation Engine system parameters.


  • When reconciling a large amount of data, create a job schedule to run outside of heavy use hours to minimize the impact on users. You can use the continuous mode for dataset updates.
  • In a standard reconciliation job, the identify and merge activities are run sequentially. Because of this, the instances start being merged into the target dataset only after all instances are identified. For a large amount of data, you can create separate identify and merge jobs and configure the merge job to run in a continuous mode. When the continuous merge job runs at the specified interval, all identified instances with the ReconciliationMergeStatus attribute set to Ready to Merge are merged into the target dataset.

To create a continuous reconciliation job

  1. In the Reconciliation console, select a job and click Edit Job.
  2. In the Schedule area of the Job Editor, click Continuous
  3. In the Job Editor, click Save, and then click Close.

BMC Default Continuous reconciliation job

Included with the Reconciliation Engine installation, the BMC Default Continuous job executes other reconciliation jobs and allows data providers to create reconciliation jobs.

It also adds activities to execute them in the BMC Default Continuous job. By default, the BMC Default Continuous job has no activities.

For example, when you install BMC Atrium Discovery and Dependency Mapping, the installer adds jobs with Identify and Merge activities for each BMC ADDM server and adds an Execute activity for each job in the BMC Default Continuous job.

You can also execute custom or standard reconciliation jobs from this default job.


Do not delete this job because other BMC applications that add reconciliation jobs during installation use the BMC Default Continuous job.

The purpose of the BMC Default Continuous job is to reconcile a small but critical set of data that needs to be updated frequently. For large updates or initial loads, create a scheduled job to minimize the impact on users.

The activities in the BMC Default Continuous job do not run in parallel or simultaneously but run sequentially.

Configuring a continuous single reconciliation job

In earlier versions, the Reconciliation Engine system parameters were global--your settings affected the entire server. You could not configure the Continuous Job Interval at an individual job level. You can now set this for individual jobs. In the ContinuousJobInterval field on the Job Information window, you can configure a single reconciliation job to execute after a specified interval.

You can expect the following behavior:

  • If you configure a continuous job interval as 300 seconds, only that job executes after 300 seconds.
  • If the job is continuous but there is no particular setting or if the setting is 0 seconds, then the job interval reverts to the global setting.
  • If you try to set the field to some lower number less than 120 seconds (for example, 60 seconds), the system defaults to 120 seconds.

For example, three reconciliation jobs are set as follows:

  • The first continuous job has the ContinuousJob set to Yes and the ContinuousJobInterval field set to 300 seconds.
  • The second continuous job is not set at the individual job level, but the global interval for the server is set to 600 seconds.
  • The third continuous job has the ContinuousJob set to Yes and the ContinuousJobInterval field set to 900 seconds.

As a result, the first job executes every 5 minutes, the second job executes every 10 minutes, and the third job executes every 15 minutes.

Before you begin

This feature applies only when the ContinuousJob field is set to Yes.

To configure a continuous single reconciliation job

  1. Open the RE:Jobs form using the direct URL:
  2. Enter the name of the job, and optionally select the Job Status.
  3. Click Search.
  4. Set ContinuousJob to Yes.
  5. In the ContinuousJobInterval field, enter an interval number equal to or greater than 120 (seconds).
  6. Click Save.


 If your continuous job is running and you need to do any configuration changes to the job, make sure that you first manually stop that job. For more information on stopping reconciliation jobs, see Manually stopping a batch or continuous reconciliation job.

Was this page helpful? Yes No Submitting... Thank you