TACL Reference Manual

Statements and Programs
HP NonStop TACL Reference Manual429513-018
5-22
Handling TACL Errors
TACL programs can check for function call errors immediately after a function call. To
handle other types of errors, see the discussion about exception handlers in the TACL
Programming Guide.
TACL can generate one type of EMS error: Error 66, an I/O error.
Error defined
by program
None The program detected a condition defined as an error in
the local TACL environment; this error could be a volume
name that should not be accessed by a particular user.
Action depends on the code. The program can exit or raise
a user-defined exception, which causes TACL to invoke an
exception handler if one is defined.
Fatal error ABENDED:
$TCL2 CPU
TIME
0:00:00.013
Termination
Info 14 TACL
fatal error:
Couldn't open
TACL IN
ABENDED: $TCL2 CPU TIME 0:00:00.013 Termination
Info 14 TACL fatal error: Couldn't open TACL IN TACL
encountered a problem with an external file, memory, or
other resource, and could not continue. If, for example,
TACL cannot find its IN file at startup time, it produces this
error. Termination info reports the error that TACL
received. TACL abends or stops itself.
Internal error ABENDED:
$TCL4 CPU
TIME
0:00:00.052
Termination
Info 18 TACL
internal error:
Initialize.100
TACL encountered an internal error condition and could
not continue. TACL abends or stops itself.
Table 5-1. Error Types
Error Example Description