... Bailey¹

Anglo-Australian Observatory

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... simple.^2.1

The disadvantage is that ICL cannot usually spot cases where we accidentally mistype the name of a variable, as can languages which enforce declaration of variables (such as FORTRAN with the IMPLICIT NONE directive). This is not thought to be a serious problem for the relatively simple programs for which ICL is intended.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... FORTRAN^2.2

But different from those in Pascal

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... message.^4.1

A tidier exit can be arranged by using an exception handler for the EOF exception.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... commands^9.1

In fact, any ICL command may be specified in place of KAPPA in the ADAM command.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... message^9.2

These loading messages can be turned off by the SET NOMESSAGES command, if desired

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... 0591KAPPA^9.3

The name is prefixed with a number (e.g. 0591) to make a unique process name, so that there is no conflict between your version of KAPPA, and another version run at the same time by another user

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... NDF^9.4

`NDF' stands for Extensible N-Dimensional Data Format. For more information see Section .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... implementor^9.5

For a detailed description of the parameter help system, see SUN/115.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... names^9.6

Note that for reasons explained in Section , strings defining names to be used as ADAM task parameters are generally prefixed with @.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... programs^10.1

The alternative way is by using the DEFUSER command

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.