<p>We have several jobs that run concurrently that have to use the same config info for log4j.  They are all dumping the logs into one file using the same appender.  Is there a way to have each job dynamically name its log file so they stay seperate?</p>

<p>Thanks<BR>
Tom</p>

You could programmatically configure log4j when you initialize the job.
You can also set the log4j.properties file at runtime via a system property. From the
manual
:
Set the resource string variable to the value of the
log4j.configuration
system property. The preferred way to specify the default initialization file is through the log4j.configuration system property. In case the system property log4j.configuration is not defined, then set the string variable resource to its default value "log4j.properties".
Assuming you're running the jobs from different java commands, this will enable them to use different log4j.properties files and different filenames for each one.
Without specific knowledge of how your jobs are run it's difficult to say!