|
|
|
|
|
When a rule processes data, the rule can save values in the Control-M/Analyzer Database for future use. These values can be accessed by both the original rule that created the variable and other Control-M/Analyzer rules. All Control-M/Analyzer rules can share information by accessing the Database.
Database variables must be created (defined) before they can be used. The definition consists of parameters that contain basic information about the variable (such as its group and name). These parameters also determine the number of values a variable can have. Each variable value represents a generation: a historical occurrence of a variable and its value at that time.
Once a Database variable definition is created, rules can refer to and add generations to that variable. Attributes can be specified to identify (to refer to) a specific variable generation from within a balancing rule definition. The attributes are described briefly in Table 130.
Table 130 Control-M/Analyzer Database Variables
Attribute |
Description |
|---|---|
Database prefix |
Name prefix DB_, which identifies the variable as a Database variable. |
Group name |
Name of the group to which the Database variable belongs. |
Variable name |
Name of the Database variable. |
Generation |
Reference to the current or any previous value of the Database variable. |
Date |
Date of Database variable creation. |
User key |
User-defined Database variable identifier. |
Run ID |
User-defined run identifier. For example, Daily, Monthly) during which the Database variable was created. |
Example
Distinguish between accounting and marketing departments’ total expense figures by referring to the group name when accessing the variables:
DB_ACCOUNTING.TOTALEXP and DB_MARKETING.TOTALEXP
For additional information about referring to Database variables, see "Variable Generation Attributes" below.
For further information, see Automatic Database Variable Creation.
Parent Topic |