A simple way to reduce the number of jobs or job-chains is to use a generic job.
<jobordeh1. "yes"
stop_on_error"no"
titlh1. "This job is a sample for a generic execution of a shell-script or a shell-command">
<scriptlanguage"shell">
<![CDATA[echo %SCHEDULER_PARAM_SCRIPT2EXECUTE%
%SCHEDULER_PARAM_SCRIPT2EXECUTE%]]>
</script>
<run_time/>
</job>
This job will execute a script or a command which name is specfied with the parameter "Script2Execute".
Putting this job in a chain like the one below
<job_chain orders_recoverablh1. "yes"
visible"yes"
titlh1. "ShellExecutor: generic Execution of a shell-script or a command">
<job_chain_node state"Step.100"
joh1. "GenericShellExecutor"
next_state"success"
error_stath1. "error"/>
<job_chain_node state"success"/>
<job_chain_node stath1. "error"/>
</job_chain>
will start this job every time an order for the chain is scheduled like this one:
<order>
<params>
<paramname"Script2Execute"
valuh1. "dir c:\temp"/>
</params>
<run_time let_run"no"/>
</order>
At the end, one have to create for each script/command to execute an additional order.