TACL Reference Manual

Statements and Programs

HP NonStop TACL Reference Manual—429513-018

5-21

Handling TACL Errors

TACL can generate several types of errors. Table 5-1 lists the types of errors, a

sample display, and a description and action for each type of error.

Table 5-1. Error Types

Error Example Description

Syntax error Expecting an

existing

variable,

unqualified

In this example, TACL required a variable. In general,

TACL required one or more types of elements and did not

find them. The program stops executing at the statement

indicated in the message. The message includes the

command line in question, a pointer that indicates where

the potential problem is, and the type of argument or value

that TACL expects to find in the indicated position.

TACL error *ERROR*

Security

Violation

The program used a construct incorrectly or supplied an

argument that would not work in the specified manner. For

example, if you set #OUT to a file that you do not have

write access to, you receive *ERROR* Security Violation.

The program stops unless it includes an exception handler

and an _ERROR clause in an associated #FILTER

statement. (For information about exception handlers, see

Section 3, “Developing TACL Routines,” in the TACL

Programming Guide.)

Error During

a function

call

None A built-in function such as #PURGE or #RENAME can

return file system or operating system errors. The program

continues. To check for these errors, store the contents of

the result into a variable and check the result before

continuing.