Data integrity for variable tables

This topic explains how data integrity is guaranteed using variable tables.

In the same way as for other objects, HCL Workload Automation maintains variable table data integrity whenever you run commands that create, modify, rename, or delete the definition of a variable table.

When referencing a variable table from any run cycle, job stream, or workstation HCL Workload Automation checks that the variable table exists and preserves the link between it and the run cycle, job stream, and workstation. This means that you cannot delete a variable table definition while a reference from a run cycle, a job stream, or a workstation still exists.

Referential integrity is guaranteed at variable table level and not at variable level, that is, when a run cycle, a job stream, and a workstation references a variable table, HCL Workload Automation checks that the variable table exists, not that the referenced variable exists.