Adding a variable

This procedure describes how to add a variable parameter to jobs. You can define variables in a job definition to enable sharing data between multiple jobs.

To add a variable:

1. From the Properties pane, in the General tab, click More.
2. In the Variables area, click .
3. In the Variable Name field, type a variable name.
4. From the Variable Type drop-down list, select one of the following:
   • Local: Defines variables that can be used by other post-processing actions of the job, such as messages, do-action arguments, or the script itself in the next run.

     EXAMPLE: %%<variable_name>

   • Global: Enables you to access the variables by its name at the Control-M/Server level, which can be used by any job.

     EXAMPLE: %%\<variable_name>

   • Named Pool: Organizes variables into groups in a hierarchy. The variable is referenced by the pool name.

     EXAMPLE: %%\\<named_pool>\<variable_name>

   • Smart Folder: Enables other jobs in the folder to access the specified variable either in the script during the job run, or in post-processing.

     EXAMPLE: %%\\<variable_name>

   NOTE: The SMART folder option in the Variable Type drop-down list appears when the job is included in the SMART folder.

   For more information on variables, see User-defined variables.

   If Named Pool is selected, the Pool Name field appears. In the Pool Name field, type the name of the pool.

5. In the Variable Value field, type the value of the variable.

   A variable is added to the job definition.

   EXAMPLE: A user-defined variable for the day before yesterday is needed in the job script. Do the following:

   In the Variable Name field type, TwoDaysAgo.

   In the Variable Type field, select Local.

   In the variable value field, type %%DAY %%MINUS 2.

   NOTE: %%DAY is a system variable. %%MINUS is an operator.

6. If you want to view the resolved value of the variable, click .

   The Variables Simulation window appears.

   For information about Variables Simulation, see Variable Simulation.

   NOTE: The resolved value is a reflection of the data that is available at the time of running the Variable Simulation. For example, %%ODATE is the current Control-M/Server date.