5. Embedded SQL for Ada : Preprocessor Error Messages
 
Share this page                  
Preprocessor Error Messages
The following is a list of error messages specific to Ada.
E_DC000A
"Table 'employee' contains column(s) of unlimited length."
Reason:
Character string(s) of zero length have been generated. This causes a compile-time error.
Action:
Modify the output file to specify an appropriate length.
E_E60001
"The Ada variable '%0c' is an array and must be subscripted."
Reason:
A variable declared as an array must be subscripted when referenced. The preprocessor does not confirm that you use the correct number of subscripts. A variable declared as a 1-dimensional array of characters must not be subscripted as it refers to a character string.
E_E60002
"The Ada variable '%0c' is not an array and must not be subscripted."
Reason:
A variable not declared as an array cannot be subscripted. You cannot subscript string variables in order to refer to a single character or a slice of a string (sub-string).
E_E60003
"The Ada identifier '%0c' is not a declared type."
Reason:
The identifier was used as an Ada type name in an object or type declaration. This identifier has not yet been declared to the preprocessor and is not a preprocessor-predefined type name.
E_E60004
"The Ada CHARACTER variable '%0c' must be a 1-dimensional array."
Reason:
Variables of type CHARACTER can only be declared as 1-dimensional arrays. You cannot use a single character or a multi-dimensional array of characters as an Ingres string. Note that you can use a multidimensional array of type STRING.
E_E60005
"The Ada DIGITS clause '%0c' is out of the range 1..16."
Reason:
Embedded Ada supports D_FLOAT floating-point variables. Consequently, all DIGITS specifications must be in the specified range.
E_E60006
"Statement '%0c' is embedded in INCLUDE file package specification."
Reason:
Preprocessor INCLUDE files may only be used for Ada package specifications. The preprocessor generates an Ada WITH clause for the package. No executable statements may be included in the file because the code generated will not be accepted by the Ada compiler in a package specification.
E_E60007
"Too many names (%0c) in Ada identifier list. Maximum is %1c."
Reason:
Ada identifier lists cannot have too many names in the comma-separated name list. The name specified in the error message caused the overflow, and the remainder of the list is ignored.
Action:
Rewrite the declaration so that there are fewer names in the list.
E_E60008
"The Ada identifier list has come up short."
Reason:
The stack used to store comma separated names in Ada declarations has been corrupted.
Action:
Try rearranging the list of names in the declaration.
E_E60009
"The Ada CONSTANT declaration of '%0c' must be initialized."
Reason:
CONSTANT declarations must include an initialization clause.
E_E6000A
"The Ada identifier '%0c' is either a constant or an enumerated literal."
Reason:
The named identifier was used to retrieve data from Ingres. A constant, an enumerated literal and a formal parameter with the IN mode are all considered illegal for the purpose of retrieval.
E_E6000B
"The Ada variable '%0c' with '.ALL' clause is illegal."
Reason:
The ADA .ALL clause, as specified with access objects, can be used only if the variable is an access object pointing at a single scalar-valued type. If the type is not scalar valued, or if the access object is pointing at a record or array, then the use of .ALL is illegal.
E_E6000C
"The Ada variable '%0c' with '.ALL' clause is not a scalar type."
Reason:
The ADA .ALL clause, as specified with access objects, can be used only if the variable is an access object pointing at a single scalar-valued type. If the type is not scalar valued, or if the access object is pointing at a record or array, then the use of .ALL is illegal.
E_E6000D
"Last component in Ada record qualification '%0c' is illegal."
Reason:
The last component referenced in a record qualification is not a member of the record. If this component was supposed to be declared as a record, the following components will cause preprocessor syntax errors.
E_E6000E
"In ADA RENAMES statement, '%0c' must be a constant or a variable."
Reason:
The target object of a RENAMES statement must be a constant or a variable, and the item being declared is used a synonym for the target object.
E_E6000F
"In ADA RENAMES statement, object is incompatible with type."
Reason:
The type of the target object in the RENAMES statement must be compatible in base type, size and array dimensions with the type name specified in the declaration.
E_E60010
"Only one name may be declared in an ADA RENAMES statement."
Reason:
One object can rename only one other object.
E_E60012
"The Ada variable '%0c' has not been declared."
Reason:
The named identifier was used where a variable must be used to set or retrieve Ingres data. The variable has not yet been declared.
E_E60013
"The ADA type %0c is not supported."
Reason:
Some Ada types are not supported because they are not compatible with the Ingres runtime system.
E_E60014
"The ADA variable '%0c' is a record, not a scalar value."
Reason:
The named variable qualification refers to a record. It was used where a variable must be used to set or retrieve Ingres data. This error may also cause syntax errors on record component references.
E_E60016
"The ADA statement %0c is not supported."
Reason:
Statements that modify the internal representation of variables that interact with Ingres are not supported.