USoft Batch Log Files

Previous Next

See Also

When USoft Batch Runner executes a job, it produces a log file which is by default named <jobname>HHMMSSLL.LOG, where HHMMSSLL is the time at which the job was executed (hours, minutes, seconds, and milliseconds). This file is created in the central logging directory that is specified during the installation of the USoft product set. A fragment of a logfile is shown here.

Jun 23 16:07:18 2007: Information: Started batch

Jun 23 16:07:19 2007: Information: Starting job "MARTYN3".

Jun 23 16:07:21 2007: Information: Ended job "MARTYN3".

Jun 23 16:07:21 2007: Information: Batch finished normally

If you want to specify a different file name for a log file, you can either do this by setting the Logfile property for a Batch Runner item in USoft Binder, or by adding the

–logfile <file_name>

parameter to a Batch Runner command line. You can specify a full pathname, a file name, or a folder name. If you specify a folder name, the value must end with a '\' character.

By default, if the log file specified already exists, the log information will be appended to the file. You can overwrite the existing log file by checking the Logfile Overwrite check box in the Batch Runner Properties Sheet in USoft Binder, or by specifying Batch Runner command line option:


Here is an overview of what happens with specified values for the Log file and for the Logfile Overwrite settings:

Log file (example)

Logfile Overwrite




A filename is generated (<jobname>HHMMSSLL.LOG). The file is placed in the central logging directory.



A filename is generated (<jobname>HHMMSSLL.LOG). The file is placed in the c:\mylogs folder.



Logging information is appended to C:\mylogfiles\mylog.log. If the file does not exist, it will be created.



Logging information is written to C:\mylogfiles\mylog.log. Before writing, the file is emptied. If the file does not exist, it is created.


The log level of all batch jobs can be controlled using the Batch_Loglevel deployment configuration setting in the Authorizer. This setting has three possible values, Information, Error, and No Logging. Please note that RunBatch, client server and the rules service each have their own set of deployment configuration settings: these can be found on the corresponding tab in this window. Jobs running under each of these environments respond to the log level setting of the corresponding tab.


Related Topics:

Logging Jobs Started from Within a USoft Application