The Ftscript is checked when it is read.
If errors are identified then the Ftscript is not run. When the Ftscript is started, you see a corresponding error message and a return code, see description of the ftscript command in manual "openFT (Unix and Windows systems) - Command Interface".
If the check is completed successfully then the Ftscript is executed asynchronously. If an error occurs during execution then the cause of the error is logged.
Every error message has a unique internal code and is assigned to a specific error code. The errors are assigned to one of the following two categories on the basis of the error codes:
"normal" Ftscript error codes
"severe" Ftscript error codes
The table listing all these error messages can be found in chapter “Error messages”.
The error codes assigned by openFT-Script always start with "ft_".
You can also use the fault activity (see section “fault”) to assign any other error codes. However, these may not begin with "ft_". These are always considered to be "normal" error codes.
The cause of the error can be displayed with ftshwact.
If no faulthandler exists for an error then ftscript is terminated with an error (status F). The status and cause of termination can be displayed using ftshws.