General Information

By default, Database variables modified by a rule (using statement DO SET or DO EXTRACT) are not immediately written to (stored in) the Control-M/Analyzer Database. Instead, Database variables are committed at rule termination if the rule does not abend.

• If the rule was called by a job step, commitment occurs when the rule terminates.
• If the rule was called by another rule through statement DO RULE, commitment occurs when the called rule terminates.

DO COMMIT statements specified by a rule may override this default and force immediate commitment of Database variables.

Note: Subsequent settings of a variable (before commitment occurs) change the current value of the variable. Only the current value of the variable is written to the Database.

The DO COMMIT statement enables a rule to:

• Mark or unmark all modified Database variables for commitment.
• Selectively mark or unmark specific Database variables for commitment.
• Force immediate commitment of specific Database variables.
• Delete specific Database variables from the memory of the rule as if these variables were never set.

The DO COMMIT options described above are useful when various rule results and decisions affect how variables should be committed.

If a rule ends OK, all Database variables are committed. However, if the rule ends NOTOK, it may be preferred that no variables be committed. In this latter case, DO COMMIT=NONE could be specified before rule termination to achieve the desired effect.

Instead of issuing a "global" COMMIT (for example, the default COMMIT method), it is possible to commit certain variables, but not others. This can be achieved by using the DO COMMIT options INCLUDE or EXCLUDE and specifying the desired variables in the VAR parameter.

The NOW option forces immediate commitment of specified variables. This option enables the creation of several generations of the same variable during the same rule execution.

The DELETE option reverses variable settings and modifications (provided that the variable was not already committed). The result is that the variable is undefined as if it had not been previously set or modified.

Note: The DELETE option frees (unlocks) the Database variable so it can be accessed by other rules executing concurrently. The EXCLUDE option unmarks the variable for commitment but does not free the variable until rule termination.

Control-M/Analyzer AutoEdit variables and Local variables (preceded by the %% operator) can be embedded in the VAR parameter. These variables are resolved (replaced) at time of rule execution. For additional information on AutoEdit processing, see Control-M/Analyzer Variables.

For additional information on committing Database variables, see Committing Database Variables.