Example

A rule contains a DO SHOUT statement with the message:

VOLSER %%VOL001 WAS CHECKED-IN

When the DO SHOUT is performed, AutoEdit variable %%VOL001 is analyzed and resolved.

If the actual volser of the checked-in volume is 111222, the shouted message automatically appears as:

VOLSER 111222 WAS CHECKED-IN

AutoEdit variables are divided into two types:

• System Variables

  AutoEdit system variables are predefined variables, provided with the product, that are replaced by values taken from the Control-M/Tape environment.

  For example, AutoEdit system variable %%TDATE is replaced by the date a specified event occurred.

• User-Defined Variables

  In contrast to system variables, user-defined variables are variables that are created by the user. The user must therefore provide the value (or the tools to derive the value) that replace the variable. Values for user-defined variables are provided by DO SET statements. These values can be used as input for other INCONTROL products (for example, Control-M).

  For example, the user can define a variable %%TAPELOG whose value is supplied by System variable %%JCLVOL:

  DO SET=%%TAPELOG = %%JCLVOL

  User-defined variables can be any non-reserved alphanumeric string starting with %%. Characters @, #, $, and – are also valid. Lowercase characters are not translated to uppercase characters upon resolution.