evaluateArrVar

Purpose:

Process user-defined expressions

Enter:

evaluateArrVar <registered_name> < path> [+c] &

Where:

registered_name

Specify the registered name.

path

Specify the specification path name.

+c

Optional. Specify this flag to indicate a critical task.

Example:

evaluateArrVar registered_task_name /specs/my_expr.1000

Notes:

The spec file has the format:

# event_name expression_file tmr-100 /specs/my_expr.100 tmr-1000 /specs/my_expr.1000

This process is normally started from the ‘go.scp’ startup script and is usually run as a critical task which will cause a watchdog shutdown if it fails.

Multiple instances of “evaluateArrVar” may be started to handle multiple spec files. Normally, there is a 1-to-1 pairing of an instance of “evaluate” with a spec file. The pairing is accomplished through the “registered name”. The “registered name” is a spawning argument for “evaluateArrVar” and is placed in the corresponding spec file following the macro “@REG_NAME”.

See Also: