<div  id="file-location">
<span id="index-0"></span><span id="id1"></span>
<div >
<div >We have seen so far that <a  href="/wiki/display/ECFLOW/Glossary#term-ecflow-server"><em >ecflow_server</em></a> is looking for the files it needs in specific locations.</div>
<div >You can control the location of your files by using the following <a  href="/wiki/display/ECFLOW/Glossary#term-variable"><em >variable</em></a>&#8216;s</div>
</div>
<div ><pre>ECF_INCLUDE  Is where ECF will look for include files.
ECF_FILES    Is where ECF will look for the '.ecf' scripts if they are not at their default location.
ECF_OUT      Is where the job output files will go.</pre>
</div>
<div >
<div >If two tasks use the same <a  href="/wiki/display/ECFLOW/Glossary#term-ecf-script"><em >ecf script</em></a>, and are simply using different values of the same <a  href="/wiki/display/ECFLOW/Glossary#term-variable"><em >variable</em></a>&#8216;s,</div>
<div >you do not want to maintain several copies of the same file.</div>
<div >You can use the same script in multiple places within your <a  href="/wiki/display/ECFLOW/Glossary#term-suite"><em >suite</em></a> and using the same name</div>
<div >by keeping the script into a common directory and pointing to this location using the <a  href="/wiki/display/ECFLOW/Glossary#term-variable"><em >variable</em></a> ECF_FILES.</div>
<div >Many users use just one directory for their scripts and point to this directory with ECF_FILES.</div>
</div>
<p>If the tasks have different names, you can use the unix command <strong >ln -s</strong> to create several names for the same file.</p>
<p>What to do:</p>
<ol >
<li>Try to imagine how we could use ECF_FILES and ln to reduce the number of scripts in our example suite</li>
</ol>
</div>