In a data acquisition situation the task caching scheme described in the previous section is usually inappropriate. We don't want tasks to be killed when the caching limit is exceeded, and we may not want a task to be killed when ICL exits (as happens with cached tasks). Also the unique process names created for cached tasks are undesirable as many different tasks may want to communicate with a given task, and therefore need to know its name.
Therefore I-tasks are normally loaded as uncached tasks, and this is achieved by explicitly loading them using one of the three ICL load commands.
ICL The Interactive Command Language for ADAM