Table of Contents |
---|
| outlinh1. true |
---|
| outlinh1. true |
---|
1 | printablefalse |
---|
2 | stylh1. none |
---|
3 | indent20px |
---|
|
You can use locks to prevent a job start, while another job is running. You can find some information about looks at http://www.sos-berlin.com/doc/en/scheduler.doc/lock.xml
Locks are defined in files in the hotfolder (live). The name of the file is the name of the lock followed by .lock.xml. E.g. lockSample.lock.xml
Using locks, you have to
- declare a lock
- assign the lock to the involved jobs
Example
the lock
Code Block |
---|
<locks>
<lock name="lockSample"/>
</locks>
|
two jobs, assigned to the lock
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<job order="yes"
stop_on_error="no">
<lock.use lock="lockSample"
exclusive="yes"/>
<script language="shell">
<![CDATA[
echo here is the job jobsSample_1
echo I'm not running in parallel with job jobsSample_2
ping -n 60 localhost
]]>
</script>
</job>
|
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<job order="yes"
stop_on_error="no">
<lock.use lock="lockSample" exclusive="yes"/>
<script language="shell">
<![CDATA[
echo here is the job jobsSample_2
echo I'm not running in parallel with job jobsSample_1
ping -n 60 localhost
]]>
</script>
</job>
|
Two job chains using the jobs
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain>
<job_chain_node state="100"
job="jobsSample_1"
next_state="success"
error_state="error"/>
<job_chain_node state="success"/>
<job_chain_node state="error"/>
</job_chain>
|
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain>
<job_chain_node state="100"
job="jobsSample_2"
next_state="success"
error_state="error"/>
<job_chain_node state="success"/>
<job_chain_node state="error"/>
</job_chain>
|
Two orders assigned to the job chain
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<order job_chain="job_chain1"</order>
|
Code Block |
---|
<?xml version="1.0" encoding="ISO-8859-1"?>
<order job_chain="job_chain2" </order>
|