Running the batch processor

Starting a batch job with a single input file
Batch jobs that use a single input file are initiated by running runbatch.sh with arguments to define the input file and options.

Starting a batch job with multiple input files
Batch jobs that use a multiple input files are initiated by running runbatch.sh.

Starting a batch job based on a job definition file
To explicitly create a batch job based on one or more job definition files, run runbatch.sh with job definition file names as arguments.

Starting a batch job that is scheduled or part of a job chain
Run runbatch.sh with arguments to initiate a check by the batch processor to see if a job or job chain is due to be processed.

Stopping a batch job using the runbatch script
You can use the runbatch.sh script to stop batch jobs from processing.

Stopping a batch job using a transaction
You can use the InfoSphere MDM updateTask transaction to stop batch jobs from processing.

Restarting a stopped batch job using the runbatch script
You can directly restart a stopped batch job through the command line interface using the runbatch script.

Restarting a stopped batch job using a transaction
You can use the InfoSphere MDM updateTask transaction to restart stopped batch jobs.

Running the batch processor in the background
The batch processor can be run in the background so that the batch job or chain can run while still allowing you to interact and run other commands.

Scheduling a batch job
To schedule batch jobs, you must use a third party scheduler such as CRON jobs on UNIX systems.