Commands

call processor
call processor(arg1,arg2,...)
goto label
continue
quit_event
quit_job

call processor - A processor call where processor is the short name of the software unit (MCO, FTT, ANL etc). Some processors support a list of arguments (see section 9.2.3 for a full list). Eg,

call out(1,2,3) * Output on streams 1, 2 & 3

Note that:-

1. Arguments should appear in parentheses with no space between processor name and the opening bracket.

2. Only integer arguments are recognized. All others are errors. By default integers are assumed to have decimal radix. You can specify binary, octal or hexadecimal by appending the letters b, o, and h repectively e.g. 11001b, 777o, 0ffh. Note that for hexadecimal the first character must be numeric, so add a leading 0 if the first digit would otherwise be greater than 9.

3. Arguments can be separated by commas and/or spaces.

The standard course of action after a processor call is to quit the event if an error occurred, unless the processor was a fitter, classifier or filter. In such cases, an error is not considered fatal. This default behaviour can be overidden if the call is followed immediately by a conditional command, thus allowing the user to gain full control:-

  call mco
  if_not_ok continue     * Don't quit if MC error 
                         *      (a strange request!)
  call ftt
  if_not_ok quit_event   * Fit failed

goto label - This causes execution to jump to the command associated with label.

continue - This command has no action. It could be used with a condition to force execution to continue after a processor failure (see above).

quit_event - Stops processing of the current event and skips to the next cycle of the event loop.

quit_job - Terminates SNOMAN.