...
- Environment variables are used to make job (i.e. task) and order parameters accessible to shell scripts in subsequent jobs.
- Environment variables are named using a predefined prefix and the name of the original parameter:
- Environment variable names are written with uppercase letters.
- The default value for the environment variable prefix is SCHEDULER_PARAM_ .
- For example, a task parameter param1 can be accessed by the SCHEDULER_PARAM_PARAM1 environment variable name.
If the SCHEDULER_PARAM_ prefix is not to be used for the environment variables and instead the parameter names themselves then the following setting can be added to the
./config/scheduler.xmlfile:Code Block language xml <params> <param name="scheduler.variable_name_prefix" value="*NONE"/> ... </param>
Note that: there is a risk of JobScheduler overwriting already existing environment variables with new ones of the same name that have been derived from job or order parameters if a prefix such as SCHEDULER_PARAM_ is not used.
...
The example behavior described above will be visible in the order log file.
Further References
Job and Order Parameters
- How to set and read job and order parameters
- How to access order parameters and job parameters
- How to pass parameters to subsequent shell jobs in a job chain
- How to dynamically use node parameters and internal parameter substitution
- How to clone parameters from a persistent order
Environment Variables