Page History

...

• Job and order Parameters are exposed to shell scripts as environment variables to shell scripts.
• Environment variables are named using a predefined prefix and the name of the original parameter: 
  • The default value for the environment variable prefix is SCHEDULER_PARAM_ . 
  • Environment variable names are provided with uppercase letters.
  • For example, a parameter param1 can be accessed by the SCHEDULER_PARAM_PARAM1 environment variable. This syntax applies for both job and order parameters.
    

  • For details see Which environment variables are provided by JobScheduler?

...

The following two examples show a job parameter defined in a job <param> tag can be used in a shell script. Note that the parameter could have been equally well have been defined in the order.

 <job>
    <params>
        <param name="param1"  value="Test"/>
    </params>
    <script language="shell">
        <![CDATA[
 rem This is an example shell script to show the use of parameters
 echo Param1 has the value %SCHEDULER_PARAM_PARAM1%
        ]]>
    </script>
    <run_time/>
 </job>

...

 <start_job job="my_job">
    <params>
        <param name="param1"  value="Test"/>
    </params>
 </start_job>

• A parameterized parametrized job start can be used programmatically, e.g. by use of the JobScheduler start script.
• Such parameterized parametrized job starts can be effected by JOC.

...