Some of these variables must be set and exported before any of the ecflow_client commands are executed. Since the script/job can call ecflow_client, then typically they are all set in an include file in the header of the task so that all tasks would have them correctly set. Table 4 3 shows environment variables used by the ecFlow client.
Table 4 3 Environment variables for the ECFLOW client
Variablename |
Explanation |
Compulsory? |
Example |
---|---|---|---|
ECF_NODE |
Name of the host running ECF |
Yes |
hostname[.domain.name]nickname |
ECF_NAME |
Full name of the task |
Yes |
/suite/family/task |
ECF_PASS |
Jobs password |
Yes |
(generated) |
ECF_PORT |
port number |
No |
3141, This must match server port number |
ECF_TRYNO |
Task try number |
No |
(generated) |
ECF_HOSTFILE |
File to list possible alternate ECFs |
No |
/home/user/avi/.ecfhostfile |
ECF_TIMEOUT |
Maximum time in second for the client to try to deliver the message |
No |
1 - 86400 |
ECF_DENIED |
If set to 1 and ecFlow denies access, the client will exit with failure |
No |
1 |