Character strings(s) of zero length have been generated. This causes a compile-time error.

Modify the output file to specify an appropriate length.

'smaller': typesmaller = [byte] 1..100;

varbigger : [word] smaller;

Both bounds of a subrange declaration must be of the same ordinal type (single character or integer). If the subrange bounds types are different or if they are not ordinal types, the preprocessor will use the type of the second bound and accept the usage of variables declared with this subrange type. This will cause an error in later PASCAL compilation.

You may have an exec sql end statement that is not balanced by a exec sql label statement. These subprogram delimiters provide scoping for PASCAL labels generated by the preprocessor.

If you had syntax errors on the exec sql label statement, then correct those errors and preprocess the file again.

A string referenced in an embedded statement must be a PACKED ARRAY OF CHAR, a VARYING OF CHAR or a single CHAR. You have used a non-packed ARRAY OF CHAR as an embedded string variable.

Convert the variable declaration to either PACKED or VARYING, or subscript the array to reference only one element.

Only one semicolon is allowed between components of a record declaration. The preprocessor ignores the extra semicolons.

Delete the extra semicolon in your source code.

This error occurs when the address or value of a variable is incorrectly expressed because of faulty indirection. For example, the name of an integer pointer has been given instead of the variable at which the pointer was pointing.

Either redeclare the variable with the intended indirection (and check any implicit indirection in the type), or change its use in the current statement.

The PASCAL preprocessor must take a second pass in order to declare implicitly generated labels. If the source file referenced embedded INCLUDE files, then the second pass needs to generate labels into those files. Consequently there is a maximum nesting limit of INCLUDE files.

Try reorganizing your files to create a flatter source file structure.

The PASCAL preprocessor must take a second pass in order to declare implicitly generated labels. Because there is a temporary file involved, and this file has a fixed name, you should avoid running the preprocessor more than once in the same directory. This error may also occur if the intermediate file disappeared, the system protections of the current directory are too restrictive or have changed, or if the original input file was moved between the first and second pass of the preprocessor.

The PASCAL preprocessor must take a second pass in order to declare implicitly generated labels. There was a difference between the number of label declaration sections the preprocessor expected to generate and the number of markers found in the intermediate file. This may be caused by an embedded INCLUDE statement that requires its own scope for label generation.

If there are nested INCLUDE statements whose files require labels, try to flatten them out into larger source files.

You did not use the specified keyword, or you did not make the word known to the preprocessor. If there are no other errors the preprocessor will generate correct PASCAL code.

You have used pointer indirection on a name that was not declared as a PASCAL variable to the preprocessor.

If this really is a variable, make its declaration known to the preprocessor.

You have used array subscription on a name that was not declared as a PASCAL variable to the preprocessor.

If this really is a variable, make its declaration known to the preprocessor.

Elements of a varying-length character string array cannot be passed to the runtime system.

If you need to pass a single element, then declare the array as a plain array (not PACKED nor VARYING).

PASCAL requires that bounds expressions of conformant arrays be of a scalar type.

Choose a scalar type, such as a single character or an integer.

You have used the specified name as an embedded variable, but you have not declared it to the preprocessor. This may also be a scope problem.

Make sure you have typed the name correctly, declared the variable to the preprocessor and have used it in its scope.

The declaration of a comma-separated list of names in a declaration is too long. For example: vara, b, ..... N : Integer;

Try breaking up the declaration into groups.

The last record member referenced is not a member of the current record.

Make sure you have spelled the member name correctly, and that it is a member of the specified record.

The end of the file was reached with some program blocks left open.

Make sure you have an END statement for each subprogram header or embedded LABEL statement.

The specified TYPE or CONST name has not yet been declared.

Make sure that all types and constants are defined before use. Forward type declarations (such as pointers to undefined types) are an exception.

The stack used to store comma-separated names in declarations has been corrupted.

Try rearranging the list of names in the declaration.

You may declare variables of type SET And QUADRUPLE, but you may not use them in embedded statements. The declarations are only allowed so that you can declare records with components of those types.

If those variables need to interact with Ingres, then declare the SET variable as an ARRAY OF BOOLEAN, and the QUADRUPLE variable as a DOUBLE.

The named variable refers to a record. It was used where a variable must be used to retrieve data from Ingres. This error may also cause a syntax error on any subsequent record components that are referenced.

The PASCAL preprocessor must take a second pass in order to declare implicitly generated labels. If labels were implicitly generated then the preprocessor needs to know where to declare them on the second pass.

Be sure to issue the embedded LABEL statement (and corresponding END statement) in each subprogram that issues an embedded block-structured statement. If you did not issue the EXEC SQL LABEL statement, the generated labels will be marked as undeclared by the PASCAL compiler.