...
When a job sends an event, it is saying that part of its task has been carried out and that any task waiting for that part can now start, unless it also needs other conditions to be met. If the job then aborts and the task is resubmitted, the restarted job should be able to carry on from where it previously left off. Otherwise, there is the possibility of destroying information needed by the task triggered by the event.
In order to use events you have to first define the event in the suite definition file, e.g.
| Code Block |
|---|
suite x |
...
family |
...
f task t event foo |
Where 'foo' is the name of the event. The default value for event is "clear" or false (the value shown when the suite begins). After (command begin) it looks like: 
Then you can modify your task to change this event while the job is running, e.g.
| Code Block |
|---|
ecflow_client --init $$ |
...
ecflow_client --event foo |
...
ecflow_client --complete |
After the job has modified the event it looks like: 
Now the value of the event is "set" or true.