Running the input of a DAT EXECUTE monitoring its own input.

Sometimes one may want to execute a generated script each time it changes:

DATA1 → DAT EXECUTE DATA1

Issue:

When the data is generated programmatically, the DAT Execute script may result in bugs like truncated values as it monitors its own input without any delay.

Solution:

Using an OP execute in-between with a time command

OP EXECUTE (time > table1) monitors DATA1 and outputs time value to TABLE1
DAT EXECUTE monitors TABLE1 at row change and executes DATA1.

Notice:

In simple cases, one may just use the run command (RUN DATA1) in the OP Execute with Post Cook without the need for Time Command.

Notice 2:

The OP execute with Post-Cook on won’t work properly if the data monitored (DATA1) is a Null DAT.

The following works:
DATA1 (table DAT) → Null DAT → OP Exe DAT monitoring DATA1 and executing NULL DAT.