...
The <control> section contains parameters that control the batch job, including the number of events to run and whether various debugging output should be printed.
dryRun
Setting <dryRun> to true means that the job manager will create the drivers but will not run the job. This can be used to check that your driver setup and arguments are correct. No events will be processed when this argument is set to true.
logFile
The <logFile> element is used to specify a log file location. If no log file is specified, the job output goes to the terminal screen. The text needs to point to a valid path on the local file system.
cacheDirectory
The <cacheDirectory> specifies the root directory to be used for caching remote data files.
numberOfEvents
The <numberOfEvents> is the total number of events that will be run before the job ends. All events will be processed if this argument is left blank or if it is set to a negative number.
skipEvents
The <skipEvents> argument tells the job manager to skip a number of events up-front before processing the rest.
The "print" These tags can also be set to true to print out additional information about the job: <printDriverStatistics>, <printSystemProperties>, <printUserClassPath>, and <printDriversDetailed>. The meaning of each should be self-explanatory.
verbose
The <verbose> tag should be set to true for to enable verbose debugging output when the XML input file is processed. This turns on all of the "print" elements described above, which can still be turned off individually by setting them to false after verbose has been turned on.
...