Configuration Language

The 3L configuration language defines how you write configuration files for the various 3L configuration utilities. It is designed to allow easy description both of physical processor networks and of user applications built from tasks, without your being concerned with the details of how the tasks are actually loaded into the processor network.

Each of the configuration utilities will, in general, accept a subset of the language described here, according to its needs. In addition, implementations for different processors will differ semantically to some extent. You should refer to the sections describing the processor in question.

Use of Files

The default extension for the filenames of task image files is .tsk. This means that each of the following results in file abc.tsk being opened:

task abc

task xxx file=abc

task yyy file="abc.tsk"