Variable lists

The %%LIBMEMSYM variable can be used in the Variable Assignment or Do Variable parameters to indicate a text file containing a list of Variable assignments. This variable enables you to create a central file containing Variable assignment statements that can be read by many job processing definitions.

You can also use the %%POOLSYM variable to call variables from a pool. %%POOLSYM is relevant only to a Control-M distributed system.

NOTE: Multiple LIBMEMSYM statements can be included in a single job processing definition. In this way you can maintain groups of local or global variables that are relevant to certain jobs, and allow more than one such group to be applied to a job. However, if a variable is defined in more than one list, the last list defined overrides previous lists.

The format for the %%LIBMEMSYM variable:

%%LIBMEMSYM=path_name

path_name is the full (case sensitive) path name of a text file containing Variable assignment statements. This file must be accessible to Control‑M. The file must contain a single assignment on each line.

• For the Variable Assignment parameter, the specified file is accessed at the time the job is submitted for execution by Control‑M.
• If a %%LIBMEMSYM statement is specified using the Do Variable parameter, local variables defined in the specified file are relevant only during a rerun of the job if and when the On Statement/Code conditions are satisfied.

  NOTE: For z/OS jobs, a variable list can be specified using the %%LIBSYM and %%MEMSYM variables. If a %%LIBMEMSYM variable is specified for an z/OS job, it is treated as a user-defined variable, and does not reference a variable list.

EXAMPLE: If a job processing definition contains the following specifications for the Variable Assignment parameter:

• %%a=5
• %%LIBMEMSYM=/controlm/ctm/variable.common1
• %%PARM1=%%c

  And the file /controlm/ctm/variable.common1 contains the following entries:

• %%b=%%CALCDATE %%DATE -%%a
• %%yy=%%SUBSTR %%b 1 2
• %%mm=%%SUBSTR %%b 3 2
• %%dd=%%SUBSTR %%b 5 2
• %%c=%%dd/%%mm/%%yy

  When the job is submitted for execution by Control‑M, variables are resolved as if the Variable Assignment parameter contained the following entries:

• %%a=5
• %%b=%%CALCDATE %%DATE -%%a
• %%yy=%%SUBSTR %%b 1 2
• %%mm=%%SUBSTR %%b 3 2
• %%dd=%%SUBSTR %%b 5 2
• %%c=%%dd/%%mm/%%yy
• %%PARM1=%%c

The format for the %%POOLSYM variable:

%%POOLSYM=<poolname>

poolname is the name of the pool containing the pool variable.

EXAMPLE: If a job processing definition contains the following specifications for the Variable Assignment parameter:

• %%a=5
• %%POOLSYM=<poolname>
• %%PARM1=%%c

  Variables in <poolname> include the following entries:

• %%b=%%CALCDATE %%DATE -%%a
• %%yy=%%SUBSTR %%b 1 2
• %%mm=%%SUBSTR %%b 3 2
• %%dd=%%SUBSTR %%b 5 2
• %%c=%%dd/%%mm/%%yy

  When the job is submitted for execution by Control‑M, variables are resolved as if the Variable Assignment parameter contained the following entries:

• %%a=5
• %%b=%%CALCDATE %%DATE -%%a
• %%yy=%%SUBSTR %%b 1 2
• %%mm=%%SUBSTR %%b 3 2
• %%dd=%%SUBSTR %%b 5 2
• %%c=%%dd/%%mm/%%yy
• %%PARM1=%%c