next up previous 63
Next: Killing Tasks
Up: ADAM as a Data Acquisition Environment
Previous: D-tasks and C-tasks


Task Loading

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.

ALOAD
-- Loads a task into a subprocess without waiting for completion.

LOADW
-- Loads a task into a subprocess and waits for completion.

LOADD
-- Loads a task into a detached process and waits for completion.



next up previous 63
Next: Killing Tasks
Up: ADAM as a Data Acquisition Environment
Previous: D-tasks and C-tasks

ICL The Interactive Command Language for ADAM
Starlink Guide 5
J A Bailey
A J Chipperfield

9th June 1998
E-mail:ussc@star.rl.ac.uk

Copyright © 2009 Science and Technology Facilities Council