You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Setting Parameter in Shell-Scripts and put them to the next node(s) in job chains.


At every change of status in job chains Job Scheduler parses a temporary file for "namh1. value" pairs. The "namevalue" pairs will be set as order params. The name of the temporary file is availabe with the environment variable SCHEDULER_RETURN_VALUES.

The sample below describes a job chain with two steps. Both are running the generic job PowerShellExecutor to run a powershell script within a JobScheduler job.

First Step: set a parameter for the next step in the job chain

 $A="myParam=PowerShellParam"
 $A | out-file -encoding ASCII $env:scheduler_return_values
 get-content $env:scheduler_return_values
 exit $lastexitcode
 # to change the policy for using powershell you can use this .adm file:
 #    http://www.microsoft.com/download/en/confirmation.aspx?id=25119

Second Step: get the parameter sets in the first step

 "the parameter from the previous job chain node is '$env:SCHEDULER_PARAM_myParam'"
 exit $lastexitcode
 # to change the policy for using powershell you can use this .adm file:
 #    http://www.microsoft.com/download/en/confirmation.aspx?id=25119

Job Chain

 <job_chain>
    <job_chain_node state="100" job="PowerShellExecutor" next_state="150" error_state="error"/>
    <job_chain_node state="150" job="PowerShellExecutor" next_state="200" error_state="error"/>
    <job_chain_node state="success"/>
    <job_chain_node state="error"/>
 </job_chain>

related downloads:

see also:

  • No labels