The end point for the batch suite, containing a lightweight single-stream process that completes the currently-submitted batch precedent change set.
CAUTION:
To run this batch process, execute the following command (on one line):
build runbatch -Dbatch.program=
curam.dependency.intf.CompletePrecedentChangeSet.process
-Dbatch.username=SYSTEM
If this batch process completes successfully, it will output a simple message confirming that the submitted batch precedent change set has been completed.
Tip: A common error is to attempt to run this batch process before the Submit Precedent Change Set has been run.
This process will output a simple error message if there is no batch precedent change set in the "submitted" state.
After the batch precedent change set has been completed, the processing checks to see if any new precedent changes were queued for further batch processing since the batch suite began. This situation can occur if
- the recalculation of any dependent during the batch run gave rise to changes in data which is also used as precedent; and/or
- the online system has been running concurrently with the batch suite and a user has made changes which resulted in precedent change items being queued for batch processing.
The processing will output a simple message reporting that either:
- there are no further precedent change items queued for batch processing (and thus the system is up-to-date with respect to batch precedent change items); or
- further precedent change items have been queued for batch processing, and another run of the Dependency Manager batch suite is required to process these further items. In this situation, you will need to decide whether to execute the additional run immediately or wait until a later time (perhaps when even more batch precedent change items have been queued for batch).