...
EcFlow allows access to be restricted to one ecFlow server, using ecf.list file in $ECF_HOME. We recommend that you set up and use this file, mainly to allow ECMWF staff to monitor your suite and to prevent unintentional access by other users. A sample suite file is available in ~usx/time_critical/sample_suite.defecf.list.
2.4.5 EcFlow suite design recommendations
...
One key point in the successful communication between the jobs running on the HPCFs systems or ecgate and your ecFlow server is the error handling. We recommend the use of a trap, as illustrated in the sample suite in ~usx/time_critical/include/head.h. The shell script run by your batch job should also use the ”set -ue” options.
...
We recommend the use of the ectrans command to send data to remote sites. The command has recently been enhanced to include a retrial of transfers from the spool.
...
The UIDs authorised to run ”option 2” work will be given higher batch job scheduling priority than normal Member State work. All ”option 2” UIDs will be given the same priority. The Centre’s core operational activities will always be given higher priority than MS time-critical activities. If problems affecting the core activity suites arise or long system sessions are needed, the Member State suites and jobs may be delayed or possibly abandoned. Member State users may need to consider the possibility of setting up suitable backup procedures for such eventualities.
...