Skip to main content Skip to complementary content

Set the components

About this task

In this example, the value set in the parent Job is transferred to the child Job. There, it is modified and adopts the value of the child Job, and then transferred to the parent Job again.

Procedure

  1. In parentJob, select the tSetEnv component and click the Component tab. Add a variable row by clicking the [+] button to set the initial value of the variable. Type Variable_1 in the Name field, and Parent Job value in the Value field.
  2. Select the first tMsgBox component, and click the Component tab. In the Message field, type the message displayed in the info-box which confirms that your variable has properly been taken into account. For example: "Parent:"+System.getProperty("Variable_1") displays the variable set in the tSetEnv component (here Parent Job value).
  3. Select the second tMsgBox component, and click the Component tab. In the Message field, type the "Parent:"+System.getProperty("Variable_1") line again. It makes the variable set in the child Job appear.
  4. Select the tRunJob component and click the Component tab. In the Job field, type the name of your child Job, here ChildJob. This will run the child Job when you run the parent Job.
  5. Now double-click the tRunJob component to open the child Job ChildJob.
  6. Select the tSetEnv component, and click the Component tab. Add a variable row by clicking the [+] button to set the initial value of the variable. Type Variable_1 in the Name field, and Child Job value in the Value field.
  7. Select the tMsgBox component and click the Component tab. In the Message field, type the message displayed in the info-box which confirms that your variable has properly been taken into account. For example: "Son:"+System.getProperty("Variable_1") displays the variable set in the tSetEnv component (here Child Job value).
  8. Save your Job, go back to parentJob, then run the Job by pressing F6.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here