Error messages

A syntax error has occurred.

This general error message indicates mistakes in the form of an SQL statement.

Look for missing or extra punctuation; keywords misspelled, misused, or out of sequence, or a reserved word used as an identifier.

Statement interrupted by user.

Character column size is too big.

The SQL statement specifies a width for a character data type that is greater than 65,534 bytes.

If you need a column of this size, use the TEXT data type, which allows unlimited lengths. Otherwise, inspect the statement for typographical errors.

Too many or too few host variables given.

Illegal subscript.

The substring values (two numbers in square brackets) of a character variable are incorrect. The first is less than zero or greater than the length of the column, or the second is less than the first.

Review all uses of square brackets in the statement to find the error. Possibly the size of a column has been altered and makes a substring fail that used to work.

CURSOR not on SELECT statement.

The cursor named in this statement (probably an OPEN) has been associated with a prepared statement that is not a SELECT statement.

Review the program logic, especially the DECLARE for the cursor, the statement id specified in it, and the PREPARE that set up that statement. If you intended to use a cursor with an INSERT statement, you can only do that when the INSERT statement is written as part of the DECLARE statement. If you intended to execute an SQL statement, do that directly with the EXECUTE statement, not indirectly through a cursor.

The scale exceeds the maximum precision specified.

A problem exists with the precision or scale of a DECIMAL or a MONEY data type usage, for example in a DEFINE statement. The first should be declared as DECIMAL(p) or DECIMAL(p,s) where p, the precision (total number of digits) is between 1 and 32, and s, the scale (number of digits to the right of the decimal point) is greater or equal to zero and not greater than p. The MONEY type follows the same rules.

Review the DECIMAL or MONEY type definition, and make sure that the precision is in the range [1,32] and that the scale is in the range [0,precision].

Illegal ESQL locator, or uninitialized blob variable in 4gl.

An SQL statement is using a TEXT or BYTE variable that was not initialized with LOCATE IN FILE or MEMORY.

LOCATE the TEXT or BYTE variable before using it in SQL statements.

Statement not available with this database server.

The SQL statement used by the program is not valid for the target database server.

Review the code, the SQL instruction cannot be used.

Cannot open file for load.

The input file that is specified in this LOAD statement could not be opened.

Check the statement. Possibly a more complete pathname is needed, the file does not exist, or your account does not have read permission for the file or a directory in which it resides.

Cannot open file for unload.

The output file that is specified in this UNLOAD statement could not be opened.

Check the statement. Possibly a more complete pathname is needed; the file exists, but your account does not have write permission for it; or the disk is full.

SQL Syntax error has occurred.

The INSERT statement in this LOAD/UNLOAD statement has invalid syntax.

Review it for punctuation and use of keywords.

Number of values in load file is not equal to number of columns.

The LOAD processor counts the delimiters in the first line of the file to determine the number of values in the load file. One delimiter must exist for each column in the table, or for each column in the list of columns if one is specified.

Check that you specified the file that you intended and that it uses the correct delimiter character. An empty line in the text can also cause this error. If the LOAD statement does not specify a delimiter, verify that the default delimiter matches the delimiter that is used in the file. If you are in doubt about the default delimiter, specify the delimiter in the LOAD statement.

Field name not found in form.

A field name listed in an INPUT, INPUT ARRAY, CONSTRUCT, SCROLL or DISPLAY statement does not appear in the form specification of the screen form that is currently displayed.

Review the program logic to ensure that the intended window is current, the intended form is displayed in it, and all the field names in the statement are spelled correctly.

Field subscript out of bounds.

The subscript of a screen array in an INPUT, DISPLAY, or CONSTRUCT statement is either less than 1 or greater than the number of fields in the array.

Review the program source in conjunction with the form specification to see where the error lies.

Record name not in form.

The screen record that is named in an INPUT ARRAY or DISPLAY ARRAY statement does not appear in the screen form that is now displayed.

Review the program source in conjunction with the form specification to see if the screen record names match.

List and record field counts differ.

The number of program variables does not agree with the number of screen fields in a CONSTRUCT, INPUT, INPUT ARRAY, DISPLAY, or DISPLAY ARRAY statement.

Review the statement in conjunction with the form specification to see where the error lies. Common problems include a change in the definition of a screen record that is not reflected in every statement that uses the record, and a change in a program record that is not reflected in the form design.

Form file (file-name) not found.

The form file that is specified in an OPEN FORM or OPEN WINDOW WITH FORM statement was not found.

Inspect the form name used in the statement. It should not include the form file suffix. If the form is not in the current directory, verify that FGLRESOURCEPATH / DBPATH environment variables contain the path to the form file.

A form is incompatible with the current BDL version. Rebuild your form.

The form file that is specified in an OPEN FORM statement is not acceptable. Possibly it was corrupted in some way, or it was compiled with a version of the Form Compiler that is not compatible with the version of the BDL compiler that compiled this program.

Use a current version of the Form Compiler to recompile the form specification.

No form has been displayed.

The current statement requires the use of a screen form. For example, DISPLAY...TO or an INPUT statement must use the fields of a form. However, the DISPLAY FORM statement has not been executed since the current window was opened.

Review the program logic to ensure that it opens and displays a form before it tries to use a form.

NEXT FIELD name not found in form.

This statement (INPUT or INPUT ARRAY) contains a NEXT FIELD clause that names a field that is not defined in the form.

Review the form and program logic. Perhaps the form has been changed, but the program has not.

Field ( field-name ) in BEFORE/AFTER clause not found in form.

This statement includes a BEFORE FIELD clause or an AFTER FIELD clause that names a field that is not defined in the form that is currently displayed.

Review the program to ensure that the intended form was displayed, and review this statement against the form specification to ensure that existing fields are named.

The NEXT OPTION name is not in the menu.

This MENU statement contains a NEXT OPTION clause that names a menu-option that is not defined in the statement.

The string that follows NEXT OPTION must be identical to one that follows a COMMAND clause in the same MENU statement. Review the statement to ensure that these clauses agree with each other.

NEXT OPTION is a hidden option.

The option that is named in this NEXT OPTION statement has previously been hidden with the HIDE OPTION statement. Because it is not visible to the user, it cannot be highlighted as the next choice.

Use the SHOW OPTION statement to unhide the menu option.

Cannot close window with active INPUT, DISPLAY ARRAY, or MENU statement.

This CLOSE WINDOW statement cannot be executed because an input operation is still active in that window. The CLOSE WINDOW statement must have been contained in, or called from within, the input statement itself.

Review the program logic, and revise it so that the statement completes before the window is closed.

Window is already open.

This OPEN WINDOW statement names a window that is already open.

Review the program logic, and see whether it should contain a CLOSE WINDOW statement, or whether it should simply use a CURRENT WINDOW statement to bring the open window to the top.

PROMPT message is too long to fit in the window.

Although BDL truncates the output of MESSAGE and COMMENT to fit the window dimensions, it does not do so for PROMPT and the user's response.

Reduce the length of the prompt string, or make the window larger. You could display most of the prompting text with DISPLAY and then prompt with a single space or colon.

Window is too small to display this menu.

The window must be at least two rows tall, and it must be wide enough to display the menu title, the longest option name, two sets of three-dot ellipses, and six spaces. Revise the program to make the window larger or to give the menu a shorter name and shorter options.

Review the OPEN WINDOW statement for the current window in conjunction with this MENU statement.

Command does not appear in the menu.

The SHOW OPTION, HIDE OPTION, or NEXT OPTION statement cannot refer to an option (command) that does not exist.

Check the spelling of the name of the option.

The type of your terminal is unknown to the system.

Check the setting of your TERM environment variable and the setting of your TERMCAP or TERMINFO environment variable.

Check with your system administrator if you need help with this action.

An attempt was made to divide by zero.

Zero cannot be a divisor.

Check that the divisor is not zero. In some cases, this error arises because the divisor is a character value that does not convert properly to numeric.

Invalid year in date.

The year in a DATE value or literal is invalid. For example, the number 0000 is not acceptable as the year.

Check the value of year.

Invalid month in date.

The month in a DATE value or literal must be a one- or two-digit number from 1 to 12.

Check the value of month.

Invalid day in date.

The day number in a DATE value or literal must a one- or two-digit number from 1 to 28 (or 29 in a leap year), 30, or 31, depending on the month that accompanies it.

Check the value of day.

Date could not be converted to month/day/year format.

The DATE type is compatible with the INTEGER type, but not all integer values are valid dates. The range of valid integer values for dates is from -693,594 to +2,958,464. Numbers that are outside this range have no representation as dates.

Check the value of the number used to assign the date variable.

Date conversion format must contain a month, day, and year component.

When a date value is converted between internal binary format and display or entry format, a pattern directs the conversion. When conversion is done automatically, the pattern comes from the environment variable DBDATE. When it is done with an explicit call to the rfmtdate(), rdefmtdate(), or USING functions, a pattern string is passed as a parameter. In any case, the pattern string (the format of the message) must include letters that show the location of the three parts of the date: 2 or 3 letters d; 2 or 3 letters m; and either 2 or 4 letters y.

Check the pattern string and the value of DBDATE.

A character to numeric conversion process failed.

A character value is being converted to numeric form for storage in a numeric column or variable. However, the character string cannot be interpreted as a number.

Check the character string. It must not contain characters other than white space, digits, a sign, a decimal, or the letter e. Verify the parts are in the right order. If you are using NLS, the decimal character or thousands separator might be wrong for your locale.

Value too large to fit in a SMALLINT.

The SMALLINT data type can accept numbers with a value range from -32,767 to +32,767.

To store numbers that are outside this range, redefine the column or variable to use INTEGER or DECIMAL type.

Value too large to fit in an INTEGER.

The INTEGER data type can accept numbers with a value range from -2,147,483,647 to +2,147,483,647.

Check the other data types available, such as DECIMAL.

String to date conversion error.

The data value does not properly represent a date: either it has non-digits where digits are expected, an unexpected delimiter, or numbers that are too large or are inconsistent.

Check the value being converted.

Value will not fit in a SMALLFLOAT.

A statement tries to assign a value that exceeds the limits of the SMALLFLOAT data type.

Review the code and consider using a FLOAT or DECIMAL type.

Value will not fit in a FLOAT.

A statement tries to assign a value that exceeds the limits of the FLOAT data type.

Review the code and consider using a DECIMAL type.

Decimal or money value exceeds maximum precision.

The data value has more digits to the left of the decimal point than the declaration of the variable allows.

Revise the program to define the variable with an appropriate precision.

It is not possible to convert between the specified types.

Data conversion does not make sense, or is not supported.

Possibly you referenced the wrong variable or column. Check that you have specified the data types that you intended and that literal representations of data values are correctly formatted.

Too many digits in the first field of datetime or interval.

The first field of a DATETIME literal must contain 1 or 2 digits (if it is not a YEAR) or else 2 or 4 digits (if it is a YEAR). The first field of an INTERVAL literal represents a count of units and can have up to 9 digits, depending on the precision that is specified in its qualifier.

Review the DATETIME and INTERVAL literals in this statement, and correct them.

Non-numeric character in datetime or interval.

A DATETIME or INTERVAL literal can contain only decimal digits and the allowed delimiters: the hyphen between year, month, and day numbers; the space between day and hour; the colon between hour, minute, and second; and the decimal point between second and fraction. Any other characters, or these characters in the wrong order, produce an error.

Check the value of the literal.

A field in a datetime or interval is out of range.

At least one of the fields in a datetime or interval is incorrect.

Inspect the DATE, DATETIME, and INTERVAL literals in this statement. In a DATE or DATETIME literal, the year might be zero, the month might be other than 1 to 12, or the day might be other than 1 to 31 or inappropriate for the month. Also in a DATETIME literal, the hour might be other than 0 to 23, the minute or second might be other than 0 to 59, or the fraction might have too many digits for the specified precision.

Extra characters at the end of a datetime or interval.

Only spaces can follow a DATETIME or INTERVAL literal.

Inspect this statement for missing or incorrect punctuation.

Overflow occurred on a datetime or interval operation.

An arithmetic operation involving a DATETIME and/or INTERVAL produced a result that cannot fit in the target variable.

Check if the data type can hold the result of the operation. For example, extend the INTERVAL precision by using YEAR(9) or DAY(9).

Intervals or datetimes are incompatible for the operation.

An arithmetic operation mixes DATETIME and/or INTERVAL values that do not match.

Check the data types of the variable used in the operation.

The result of a datetime computation is out of range.

In this statement, a DATETIME computation produced a value that cannot be stored. This situation can occur, for example, if a large interval is added to a DATETIME value. This error can also occur if the resultant date does not exist, such as Feb 29, 1999.

Review the expressions in the statement and see if you can change the sequence of operations to avoid the overflow.

Invalid datetime or interval qualifier.

This statement contains a DATETIME or INTERVAL qualifier that is not acceptable. These qualifiers can contain only the words YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, FRACTION, and TO. A number from 1 to 5 in parentheses can follow FRACTION.

Inspect the statement for missing punctuation and misspelled words. A common error is adding an s, as in MINUTES.

Value will not fit in a BIGINT or INT8.

The BIGINT data type can accept numbers with a value range from -9223372036854775807 to +9223372036854775807.

To store numbers that are outside this range, redefine the column or variable to use the DECIMAL type.

This value is not among the valid possibilities.

A list or range of acceptable values has been established for this column in the form-specification file.

You must enter a value within the acceptable range.

The two entries were not the same -- please try again.

To guard against typographical errors, this field has been designated VERIFY in the form-specification file. You must enter the value in this field twice, identically.

Carefully reenter the data. Alternatively, you can cancel the form entry with the Interrupt key.

You cannot use this editing feature because a picture exists.

This field is defined in the form-specification file with a PICTURE attribute to specify its format.

You cannot use certain editing keys (for example, CTRL-A, CTRL-D, and CTRL-X) while you are editing such a field. Use only printable characters and backspace to enter the value.

Error in field.

You entered a value in this field that cannot be stored in the program variable that is meant to receive it.

Possibly you entered a decimal number when the application provided only an integer variable, or you entered a character string that is longer than the application expected.

This field requires an entered value.

The cursor is in a form field that has been designated REQUIRED.

You must enter some value before the cursor can move to another field. To enter a null value, type any printable character and then backspace. Alternatively, you can cancel the form entry with the Interrupt key.

Please type again for verification.

The cursor is in a form field that has been designated VERIFY. This procedure helps to ensure that no typographical errors occur during data entry.

You must enter the value twice, identically, before the cursor can move to another field. Alternatively, you can cancel the form entry with the Interrupt key.

Cannot insert another row - the input array is full.

You are entering data into an array of records that is represented in the program by a static array of program variables. That array is now full; no place is available to store another record.

Press the ACCEPT key to process the records that you have entered.

Cannot delete row - it has no data.

There are no more rows in the direction you are going.

You are attempting to scroll an array of records farther than it can go, either scrolling up at the top or scrolling down at the bottom of the array. Further attempts will have the same result.

FORMS statement error number error-num.

An error occurred in the form at runtime.

Edit your source file: go to the specified line, correct the error, and recompile the file.

SQL statement error number error-num.

The current SQL statement returned this error code number.

Program stopped at 'filename', line number line-number.

At runtime an error occurred in the specified file at the specified line. No .err file is generated.

Edit your source file, go to the specified line, correct the error, and recompile the file.

A parameter count mismatch has occurred between the calling function and the called function.

Either too many or too few parameters were given in the call to the function.

The call is probably in a different source module from the called functions. Inspect the definition of the function, and check all places where it is called to ensure that they use the number of parameters that it declares.

A function has not returned the correct number of values expected.

A function that returns several variables has not returned the correct number of parameters.

Check your source code and recompile.

A validation error has occurred as a result of the VALIDATE command.

The VALIDATE LIKE statement tests the current value of variables against rules that are stored in the syscolval table. It has detected a mismatch.

Ordinarily, the program would use the WHENEVER statement to trap this error and display or correct the erroneous values. Inspect the VALIDATE statement to see which variables were being tested and find out why they were wrong.

A report output file cannot be opened.

The file that the REPORT TO statement specifies cannot be opened.

Check that your account has permission to write such a file, that the disk is not full, and that you have not exceeded some limit on the number of open files.

A report output pipe cannot be opened.

The pipe that the REPORT TO PIPE statement specifies could not be started.

Check that all programs that are named in it exist and are accessible from your execution path. Also look for operating-system messages that might give more specific errors.

A report output file cannot be written to.

The file that the REPORT TO statement specifies was opened, but an error occurred while writing to it.

Possibly the disk is full. Look for operating- system messages that might give more information.

An array variable has been referenced outside of its specified dimensions.

The subscript expression for an array has produced a number that is either less than one or greater than the number of elements in the array.

Review the program logic that leads up to this statement to determine how the error was made.

An insert statement could not be prepared for inserting rows into a temporary table used for a report.

Within the report function, BDL generated an SQL statement to save rows into a temporary table. The dynamic preparation of the statement (see the reference material on the PREPARE statement) produced an error.

Probably the database tables are not defined now, at execution time, as they were when the program was compiled. Either the database has been changed, or the program has selected a different database than the one that was current during compilation. Possibly the database administrator has revoked SELECT privilege from you for one or more of the tables that the report uses. Look for other error messages that might give more details.

A temporary table needed for a report could not be created in the selected database.

Within the report definition, BDL generated an SQL statement to save rows into a temporary table, but the temporary table could not be created.

You must have permission to create tables in the selected database, and there must be sufficient disk space left in the database. You may already have a table in your current database with the same name as the temporary table that the report definition is attempting to create as a sorting table; the sorting table is named "t_ reportname ". Another possible cause with some database servers is that you have exceeded an operating-system limit on open files.

A database index could not be created for a temporary database table needed for a report.

Within the report definition, BDL generated SQL statements to save rows into a temporary table. However, an index could not be created on the temporary table.

Probably an index with the same name already exists in the database. (The sorting index is named "i_reportname"; for example, "i_order_rpt".) Possibly no disk space is available in the file system or dbspace. Another possibility with some database servers is that you have exceeded an operating-system limit on open files.

A row could not be inserted into a temporary report table.

Within the report definition, BDL generated SQL statements that would save rows into a temporary table. However, an error occurred while rows were being inserted.

Probably no disk space is left in the database. Look for other error messages that might give more details.

A row could not be fetched from a temporary report table.

Within the report definition, BDL generated SQL statements to select rows from a temporary table. The table was built successfully but now an error occurred while rows were being retrieved from it.

Almost the only possible cause is a hardware failure or an error in the database server. Check for operating-system messages that might give more details.

A character variable has referenced subscripts that are out of range.

In the current statement, a variable that is used in taking a substring of a character value contains a number less than one or a number greater than the size of the variable, or the first substring expression is larger than the second.

Review the program logic that leads up to this statement to find the cause of the error.

A report is accepting output or being finished before it has been started.

The program executed an OUTPUT TO REPORT or FINISH REPORT statement before it executed a START REPORT.

Review the program logic that leads up to this statement to find the cause of the error.

The variable variable-name has been redefined with a different type or length, definition in module-name-1.4gl, redefinition in module-name-2.4gl.

The variable that is shown is defined in the GLOBALS section of two or more modules, but it is defined differently in some modules than in others.

Possibly modules were compiled at different times, with some change to the common GLOBALS file between. Possibly the variable is declared as a module variable in some module that does not include the GLOBALS file.

The function 'function-name' has not been defined in any module in the program.

The named function is called from at least one module of the program, but it is defined in none.

Verify that the module containing the function is a part of the program, and that the function name is correctly spelled.

The error log has not been started.

The program called the errorlog() function without first calling the startlog() function.

Review the program logic to find out the cause of this error.

Use '!' to edit TEXT and BYTE fields.

This is a normal message text used outside an error context.

Cannot build temporary file.

A TEXT or BYTE variable has been located in a temporary file using the LOCATE statement. The current statement assigns a value into that variable, so BDL attempted to create the temporary file, but an error occurred.

Possibly no disk space is available, or your account does not have permission to create a temporary file. Look for operating-system error messages that might give more information.

Read error on blob file 'file-name'.

The operating system signaled an error during output to a temporary file in which a TEXT or BYTE variable was being saved.

Possibly the disk is full, or a hardware failure occurred. For more information, look for operating-system messages.

No PROGRAM= clause for this field.

No external program has been designated for this field using the PROGRAM attribute in the form-specification file (For Text User Interface mode on ASCII terminals only)

The field 'field-name' is not in the list of fields in the CONSTRUCT/INPUT statement.

The built-in function get_fldbuf() or field_touched() has been called with the field name shown. However, input from that field was not requested in this CONSTRUCT or INPUT statement. As a result, the function cannot return any useful value.

Review all uses of these functions, and compare them to the list of fields at the beginning of the statement.

SQL character truncation or transaction warning.

The program set WHENEVER WARNING STOP, and a warning condition arose. If the statement involved is a DATABASE statement, the condition is that the database that was just opened uses a transaction log. On any other statement, the condition is that a character value from the database had to be truncated to fit in its destination.

SQL NULL value in aggregate or mode ANSI database warning.

The program set WHENEVER WARNING STOP, and a warning condition arose. If the statement that is involved is a DATABASE statement, the condition is that the database that was just opened is ANSI compliant. On any other statement, the condition is that a null value has been used in the computation of an aggregate value.

SQL, database server, or program variable mismatch warning.

The program set WHENEVER WARNING STOP, and a warning condition arose. If the statement that is involved is a DATABASE or CREATE DATABASE statement, the condition is that the database server opened the database. On any other statement, the condition is that a SELECT statement returned more values than there were program variables to contain them.

SQL float-to-decimal conversion warning.

The program set WHENEVER WARNING STOP, and a warning condition arose. The condition is that in the database that was just opened, the database server will use the DECIMAL data type for FLOAT values.

SQL non-ANSI extension warning.

A database operation was performed that is not part of ANSI SQL, although the current database is ANSI compliant. This message is informational only.

A report PRINT FILE source file cannot be opened for reading.

The file that is named in a PRINT FILE statement cannot be opened.

Review the file name. If it is not in the current directory, you must specify the full path. If the file exists, make sure your account has permissions to read it.

The character data value does not convert correctly to the field type.

You have entered a character value (a quoted string) into a field that has a different data type (for example INTEGER). However, the characters that you entered cannot be converted to the type of the field.

Re-enter the data.

There is already a record 'record-name' specified.

A screen record is automatically defined for each table that is used in the ATTRIBUTES section to define a field. If you define a record with the name of a table, it is seen as a duplicate.

Check that the record-name of every screen record and screen array is unique in the form specification.

The symbol 'symbol-name' does not represent a table prefix used in this form.

In a SCREEN RECORD statement, each component must be introduced by the name of the table as defined in the TABLES section or by the word FORMONLY.

Review the spelling of the indicated name against the TABLES section, and check the punctuation of the rest of the statement.

Screen record array 'record-name' has different component sizes.

The screen record array name has component sizes which either differ from the specified dimension of the array or differ among themselves. This error message appears when one or more of the columns appear a different number of times.

The dimension of the screen array is written in square brackets that follow its name. Verify that the dimensions of the screen array match the screen fields.

The attributes AUTONEXT, DEFAULT, INCLUDE, VERIFY, RIGHT and ZEROFILL are not supported for BLOB fields.

Columns of the data type specified cannot be used in the ways that these attributes imply.

Check that the table and column names are as you intended, and verify the current definition of the table in the database that the DATABASE statement names.

The form 'form-name' cannot be opened.

The form filename cannot be opened. This is probably because it does not exist, or the user does not have read permission.

Check the spelling of filename. Check that the form file exists in your current directory. If it is in another directory, check that the correct pathname has been provided. On a UNIX™ system, if these things are correct, verify that your account has read permission on the file.

The conditional attributes of a field cannot depend on the values of other fields.

The boolean expression in a WHERE clause of a COLOR attribute can use only the name of that field and constants.

Revise this attribute, and recompile the form.

Field 'field-name' has validation string error, String = string.

One of the formatting or validation strings that is stored in the syscolval or syscolatt tables is improperly coded. The string is shown as is the field to which it applies.

Update the string in the tables.

The name 'database-name' is not an existing database name.

This name, which was found in the DATABASE statement at the start of the form specification, is not a database that can be found.

Check the spelling of the database name and the database entries in the fglprofile file.

The label name between brackets is incorrectly given or the label is missing.

In the layout section of a form specification, the brackets should contain a simple name. Instead, they contain spaces or an invalid name.

Check the layout section of the form for invalid form item labels.

A left square bracket has been found on this line, with no right square bracket to match it.

Every left square bracket field delimiter must have a right square bracket delimiter on the same line.

Review the form definition file to make sure all fields are properly marked.

The field label 'label-name' was not defined in the form.

The indicated name appears at the left of this ATTRIBUTES statement, but it does not appear within brackets in the SCREEN section.

Review the field tags that have been defined to see why this one was omitted.

The column 'column-name' does not appear in the form specification.

A name in this ATTRIBUTES statement should have been defined previously in the form specification.

Check that all names in the statement are spelled correctly and defined properly.

The field 'field-name' is not a member of the table 'table-name'.

Something in this statement suggests that the name shown is part of this table, but that is not true in the current database.

Review the spelling of the two names. If they are as you intended, check that the correct database is in use and that the table has not been altered.

The column 'column-name' is a member of more then one table -- you must specify the table name.

Two or more tables that are named in the TABLES section have columns with the name shown.

You must make clear which table you mean. To do this, write the table name as a prefix of the column name, as table.column, wherever this name is used in the form specification.

There is a column/value type mismatch for 'column-name'.

This statement assigns a value to the field with the DEFAULT clause or uses its value with the INCLUDE clause, but it does so with data that does not agree with the data type of the field.

Review the data type of the field (which comes from the column with which it is associated), and make sure that only compatible values are assigned.

The table 'table-name' cannot be found in the database.

The indicated table does not exist in the database that is named in the form.

Check the spelling of the table name and database name. If they are as you intended, either you are not using the version of the database that you expected, or the database has been changed.

The column 'column-name' does not exist among the specified tables.

The tables that are specified in the TABLES section of the form exist, but column-name, which is named in the ATTRIBUTES section, does not.

Check its spelling against the actual table. Possibly the table was altered, or the column was renamed.

The table 'table-name' is not among the specified tables.

The indicated table is used in this statement but is not defined in the TABLES section of the form specification.

Check its spelling; if it is as you intended, add the table in the TABLES section.

The column 'column-name' does not exist in the table 'table-name'.

Something in this statement implies that the column shown is part of the indicated table (most likely the statement refers to table-name.column-name). However, it is not defined in that table.

Check the spelling of both names. If they are as you intended, then make sure that the database schema (.sch) is up to date; possibly the table has been altered or the column renamed, and thus needs a new db schema extraction with the fgldbsch tool.

The column 'column-name' appears more then once. If you wish a column to be duplicated in a form, use the same display field label.

The same column name is listed in the ATTRIBUTES section more than once.

The expected way to display the same column in two or more places is to put two or more fields in the screen layout, each with the same tag-name. Then put a single statement in the ATTRIBUTES section to associate that tag-name with the column name. The current column value will be duplicated in all fields. If you intended to display different columns that happen to have the same column-names, prefix each column with its table-name.

The display field label 'label-name' appears more than once in this form, but the lengths are different.

You can put multiple copies of a field in the screen layout (all will display the same column), but all copies must be the same length.

Review the form definition to make sure that, if you intended to have multiple copies of one field, all copies are the same.

The display field label 'label-name' has not been used.

A field tag has been declared in the screen section of the form- specification file but is not defined in the attributes section.

Check your form-specification file.

The display label 'label-name' has already been used.

The forms compiler indicates that name has been defined twice. These names must be defined uniquely in the form specification.

Review all uses of the name to see if one of them is incorrect.

See error number error-num.

The database server returned an error that is shown.

Look up the shown error in the database server documentation.

A blob variable or cursor name expected .

The argument to the FREE statement must be the name of a cursor or prepared statement or, in 4GL, the name of a variable with the BYTE or TEXT data type.

Check the name used after the FREE keyword.

The number of variables and/or constants in the display list does not match the number of form fields in the display destination.

There must be exactly as many items in the list of values to display as there are fields listed following the TO keyword in this statement.

Review the statement.

The number of input variables does not match the number of form fields in the screen input list.

Your INPUT statement must specify the same number of variables as it does fields.

When checking this, keep in mind that when you refer to a record using an asterisk or THRU, it is the same as listing each record component individually.

Printing cannot be done within a loop or CASE statement contained in report headers or trailers.

BDL needs to know how many lines of space will be devoted to page headers and trailers; otherwise, it does not know how many detail rows to allow on a page. Since it cannot predict how many times a loop will be executed, or which branch of a CASE will be execute, it forbids the use of PRINT in these contexts within FIRST PAGE HEADER, PAGE HEADER, and PAGE TRAILER sections.

Re-arrange the code to place the PRINT statement where it will always be executed.

The symbol 'symbol-name' has been defined more than once.

The variable that is shown has appeared in at least one other DEFINE statement before this one.

Review your code. If this DEFINE is within a function or the MAIN section, the prior one is also. If this DEFINE is outside any function, the prior one is also outside any function; however, it might be within the file included by the GLOBALS statement.

The symbol 'symbol-name' is not the name of a table in the specified database.

The named table does not appear in the database.

Review the statement. The table name may be spelled wrong in the program, or the table might have been dropped or renamed since the last time the program was compiled.

The symbol 'symbol-name' is not the name of a column in the specified database.

The preceding statement suggests that the named column is part of a certain table in the specified database. The table exists, but the column does not appear in it.

Check the spelling of the column name. If it is spelled as you intended, then either the table has been altered, or the column renamed, or you are not accessing the database you expected.

The variable 'variable-name' is too complex to be used in an assignment statement.

The named variable is a complex variable like a record or an array, which cannot be used in a LET statement.

You must assign groups of components to groups of components using asterisk notation.

The variable 'variable-name' is not a character type, and cannot be used to contain the result of concatenation.

This statement attempts to concatenate two or more character strings (using the comma as the concatenation operator) and assign the result to the named variable. Unfortunately, it is not a character variable, and automatic conversion from characters cannot be performed in this case.

Assign the concatenated string to a character variable; then, if you want to treat the result as numeric, assign the string as a whole to a numeric variable.

The source and destination records in this record assignment statement are not compatible in types and/or length.

This statement uses asterisk notation to assign all components of one record to the corresponding components of another. However, the components do not correspond. Note that BDL matches record components strictly by position, the first to the first, second to second, and so on; it does not match them by name.

If the source and destination records do not have the same number and type of components, you will have to write a simple assignment statement for each component.

The variable 'variable-name' is too complex to be used as the destination of a return from a function.

The named variable is too complex to be assigned directly in a RETURNING clause.

Individual members of the complex variable must be returned separately.

The function 'function-name' has already been called with a different number of parameters.

Earlier in the program, there is a call to this same function or event with a different number of parameters in the parameter list. At least one of these calls must be in error.

Examine the FUNCTION statement for the named function to find out the correct number of parameters. Then examine all calls to it, and make sure that they are written correctly.

The variable 'variable-name' in its current form is too complex to be used in this statement.

The variable has too many component parts. Only simple variables (those that have a single component) can be used in this statement.

If variable-name is an array, you must provide a subscript to select just one element. If it is a record, you must choose just one of its components. (However, if this statement permits a list of variables, as in the INITIALIZE statement, you can use asterisk or THRU notation to convert a record name into a list of components)

The symbol 'field-name' is not an element of the record 'record-name'.

The field name used in a record.field expression is not identified as a member of the record variable.

Find the definition of the record (it may be in the GLOBALS file), verify the names of its fields, and correct the spelling of field-name .

The parameter 'param-name' has not been defined within the function or report.

The name variable-name appears in the parameter list of the FUNCTION statement for this function. However, it does not appear in a DEFINE statement within the function. All parameters must be defined in their function before use.

Review your code. Possibly you wrote a DEFINE statement but did not spell variable-name the same way in both places.

The symbol 'symbol-name' has already been defined once as a parameter.

The name that is shown appears in the parameter list of the FUNCTION statement and in at least two DEFINE statements within the function body.

Review your code. Only one appearance in a DEFINE statement is permitted.

The variable 'variable-name' is too complex a type to be used in an expression.

In an expression, only simple variables (those that have a single component) can be used.

If the variable indicated is an array, you must provide a subscript to select just one element. If it is a record or object, you must choose just one of its components.

Aggregate functions are only allowed in reports and SELECT statements.

Aggregate functions such as SUM, AVG, and MAX can only appear in SQL statements and within certain statements that you use in the context of a report body. They are not supported in ordinary expressions in program statements.

Review the code and check that the aggregate functions are in an SQL statement or in the correct blocks of the REPORT routine.

Subscripting cannot be applied to the variable 'variable-name'.

You tried to use a [x,y] subscript expression with a variable that is neither a character data type or an array type.

Check the variable data type and make sure it can be used with a subscript expression.

The variable 'variable-name' is not a record. It cannot reference record elements.

In this statement variable-name appears followed by a dot, followed by another name. This is the way you would refer to a component of a record variable; however, variable-name is not defined as a record.

Either you have written the name of the wrong variable, or else variable-name is not defined the way you intended.

The type of this ORDER BY or GROUP item specified for the report is not valid for sorting.

A REPORT routine defines an ORDER BY or GROUP clause using a variable defined with a type such as TEXT and BYTE, that is too complex to be used in comparisons. As result, columns with such types cannot be used to sort or group rows.

Review the report and sort or group rows by using items defined with simple data types.

A PAGE HEADER has already been specified within this report.

Only one PAGE HEADER control block is allowed in a REPORT.

Search for other PAGE HEADER sections and combine all statements in a unique control block.

A PAGE TRAILER has already been specified within this report.

Only one PAGE TRAILER control block is allowed in a REPORT.

Search for other PAGE TRAILER sections and combine all statements in a unique control block.

A FIRST PAGE HEADER has already been specified within this report.

Only one FIRST PAGE TRAILER control block is allowed in a REPORT.

Search for other FIRST PAGE TRAILER sections and combine all statements in a unique control block.

An ON EVERY ROW clause has already been specified within this report.

Only one ON EVERY ROW control block is allowed in a REPORT.

Search for other ON EVERY ROW sections and combine all statements in a unique control block.

An ON LAST ROW clause has already been specified within this report.

Only one ON LAST ROW control block is allowed in a REPORT.

Search for other ON LAST ROW sections and combine all statements in a unique control block.

Group aggregates can occur only in AFTER GROUP clauses.

The aggregate functions that apply to a group of rows (GROUP COUNT/PERCENT/SUM/AVG/MIN/MAX) can only be used at the point in the report when a complete group has been processed, namely, in the AFTER GROUP control block.

Make sure that the AFTER GROUP block exists and was recognized. If you need the value of a group aggregate at another time (for instance, in a PAGE TRAILER control block), you can save it in a module variable with a LET statement in the AFTER GROUP block.

The report cannot skip lines while in a loop within a header or trailer.

BDL needs to know how many lines of space will be devoted to the page header and trailer (otherwise it does not know how many detail rows to allow on the page). It cannot predict how many times a loop will be executed, so it has to forbid the use of SKIP statements in loops in the PAGE HEADER, PAGE TRAILER, and FIRST PAGE HEADER sections.

Review the report header or trailer to avoid SKIP in loops.

The symbol 'symbol-name' does not represent a defined variable.

The name shown appears where a variable would be expected, but it does not match any variable name in a DEFINE statement that applies to this context.

Check the spelling of the name. If it is the name you intended, look back and find out why it has not yet been defined. Possibly the GLOBALS statement has been omitted from this source module, or it names an incorrect file. Possibly this code has been copied from another module or another function, but the DEFINE statement was not copied also.

Cursors must be uniquely declared within one program module.

In the statement DECLARE cursor-name CURSOR, the identifier cursor-name can be used in only one DECLARE statement in the source file. This is true even when the DECLARE statement appears inside a function. Although a program variable made with the DEFINE statement is local to the function, a cursor within a function is still global to the whole module

Search for duplicated cursor names and change the name to have unique identifiers.

The cursor 'cursor-name' has not yet been declared in this program.

The name shown appears where the name of a declared cursor or a prepared statement is expected; however, no cursor (or statement) of that name has been declared (or prepared) up to this point in the program.

Check the spelling of the name. If it is the name you intended, look back in the program to see why it has not been declared. Possibly the DECLARE statement appears in a GLOBALS file that was not included.

This type of statement can only be used within a MENU statement.

This statement only makes sense within the context of a MENU statement.

Review the program in this vicinity to see if an END MENU statement has been misplaced. If you intended to set up the appearance of a menu before displaying it, use a BEFORE MENU block within the scope of the MENU.

The page length is too short to cover the specified page header and trailer lengths.

A REPORT defines page header and trailer sections with a total number of lines that is not sufficiently less than the specified page length in order to print some detail lines.

Review the [FIRST] PAGE HEADER and PAGE TRAILER blocks to use less lines or increase the page length.

The input file 'file-name' cannot be opened.

Either the file does not exist, or, on UNIX, your account does not have permission to read it.

Possibly the filename is misspelled, or the directory path leading to the file was specified incorrectly.

The listing file 'file-name' cannot be created.

The file cannot be created.

Check that the directory path leading to the file is specified correctly and, on UNIX systems, that your account has permission to create a file in that directory. Look for other, more explicit, error messages from the operating system. Possibly the disk is full, or you have reached a limit on the number of open files.

Record variables that contain array type elements may not be referenced by the ".*" or THROUGH shorthand, or used as a function parameter .

The .* and THROUGH/THRU notation is used to expand a record with an array member.

It is allowed to define a record with an array member, but this element must always be used with its full designation of record.array[n]. The .* or THROUGH/THRU notation only expands simple members of the record.

The elements 'name-1' and 'name-2' do not belong to the same record.

The two names shown are used where two components of one record are required; however, they are not components of the same record.

Check the spelling of both names. If they are spelled as you intended, go back to the definition of the record and see why it does not include both names as component fields.

In this type of statement, subscripting may be applied only to array.

The statement contains a name followed by square brackets, but the name is not that of an array variable.

Check the punctuation of the statement and the spelling of all names. Names that are subscripted must be arrays. If you intended to use a character substring in this statement, you will have to revise the program.

The number of dimensions for the variable 'variable-name' does not match the number of subscripts.

In this statement, the array whose name is shown is subscripted by a different number of dimensions than it was defined to have.

Check the punctuation of the subscript. If it is as you intended, then review the DEFINE statement where variable-name is defined.

There is a numeric constant in the previous line that is too large or too small.

The compiler could not process a numeric constant because it is too big or too small to represent a valid SMALLINT, INTEGER, BIGINT or DECIMAL constant.

Check the number of digits and the punctuation of the numeric constant. Make sure you have not typed a letter for a digit for example.

The label 'label-name' has been used but has never been defined within the above main program or function.

A GOTO or WHENEVER statement refers to the label shown, but there is no corresponding LABEL statement in the current function or main program.

Check the spelling of the label. If it is as you intended it, find and inspect the LABEL statement that should define it. You cannot transfer out of a program block with GOTO; labels must be defined in the same function body where they are used.

An ORDER BY or GROUP item specified within a report must be one of the report parameters.

The names used in a ORDER BY, AFTER GROUP OF, or BEFORE GROUP OF statement must also appear in the parameter list of the REPORT statement. It is not possible to order or group based on a global variable or other expression.

Check the spelling of the names in the statement and compare them to the REPORT statement.

There is an error in the validation string: 'validation-string'.

The validation string in the syscolval table is not correct.

Change the appropriate DEFAULT or INCLUDE value in the syscolval table.

This type of statement can be used only in a report.

Statements such as PRINT, SKIP, or NEED are meaningful only within the body of a report function, where there is an implicit report listing to receive output.

Remove the report specific statement from the code which is not in a report body.

The variable used in the INPUT ARRAY or DISPLAY ARRAY statement must be an array.

The name following the words DISPLAY ARRAY or INPUT ARRAY must be that of an array of records.

Check the spelling of the name. If it is as you intended, find and inspect the DEFINE statement to see why it is not an array. (If you want to display or input a simple variable or a single element of an array, use the DISPLAY or INPUT statement.)

The number of lines printed in the IF part of an IF-THEN-ELSE statement of a header or trailer clause must equal the number of lines printed in the ELSE part.

The runtime system needs to know how many lines will be filled in header and trailer sections (otherwise it could not know how many detail rows to put on the page). Because it cannot tell which part of an IF statement will be executed, it requires that both produce the same number of lines of output.

Use the same number of occurrences of PRINT statements in each block of the IF statement.

The variable 'variable-name' has not been defined like the table 'table-name'.

The named variable has been used in the SET clause of an UPDATE statement or in the VALUES clause of an INSERT statement, but it was not define LIKE the table being modified. As a result, then runtime system cannot associate record components with table columns.

Make sure the schema file is up to date and check that the variable was defined like the table. You can also rewrite the UPDATE or INSERT statement with a different syntax to show the explicit relationship between column names and record components.

The field 'field-name-1' precedes 'field-name-2' in the record 'record-name' and must also precede it when used with the THROUGH shorthand.

The THROUGH or THRU shorthand requires you to give the starting and ending fields as they appear in physical sequence in the record.

Check the spelling of the names; if they are as you intended, then refer to the VARIABLE statement where the record was defined to see why they are not in the sequence you expected.

'key-name' is not a recognized key value.

The key name used in an ON KEY clause is not known by the compiler.

Search the documentation for possible key names (F1-F255, Control-?).

Cannot open the file 'file-name' for reading or writing.

The file cannot be opened.

Verify that the filename is correctly spelled and that your account has permission to read or write to it.

The function (or report) 'function-name' has already been defined.

Each function (or report, which is similar to a function) must have a unique name within the program.

Change the function or report name.

You may have at most 4 keys in the list.

An interactive instruction defines a ON KEY() clause with more that 4 keys.

Remove keys from the list.

One dimension of this array has exceeded the limit of 65535.

The program is using a static array with a dimension that exceeds the limit.

Use a dimension below the 65535 limit.

The NEXT FIELD statement can only be used within an INPUT or CONSTRUCT statement.

The NEXT FIELD statement is used outside an INPUT, INPUT ARRAY or CONSTRUCT statement.

Remove the NEXT FIELD statement from that part of the code.

The number of columns must match the number of values in the SET clause of an UPDATE statement.

In an UPDATE statement, the number of values used does not match the number of columns.

Check for the table definition, then either add or remove values or columns from the UPDATE statement.

Record members may not be used with database column substring.

This statement has a reference of the form name1.name2[...]. This is the form in which you would refer to a substring of a column: table.column[...]. However, the names are not a table and column in the database, so BDL presumes they refer to a field of a record.

Inspect the statement and determine what was intended: a reference to a column or to a record. If it is a column reference, verify the names of the table and column in the database. If it is a record reference, verify that the record and component are properly defined.

The variable 'variable-name' is an array. You must specify one of its elements in this statement.

You tried to use an array without element specification in a SQL statement.

Use one of the members of the array.

Only blob variables of type BYTE or TEXT may be used in a LOCATE statement.

The LOCATE statement is using a variable defined with a data type different from BYTE or TEXT.

Make sure the variables used with LOCATE are defined as BYTE or TEXT.

The program cannot CONTINUE or EXIT statement-type at this point because it is not immediately within statement-type statement.

This CONTINUE or EXIT statement is not appropriate in its context.

Review your code. Possibly the statement is misplaced, or the statement type was specified incorrectly.

A variable used in the above statement must be a global variable.

A REPORT routine is defining an OUTPUT REPORT TO using a local function variable or report parameter.

Review the report clause to use a global or module variable instead.

You cannot have multiple BEFORE clauses for the same field.

You cannot specify more than one BEFORE FIELD clause for the same field.

Review your code to eliminate multiple BEFORE FIELD clauses.

You cannot have multiple AFTER clauses for the same field.

You cannot specify more than one AFTER FIELD clause for the same field.

Review your code to eliminate multiple AFTER FIELD clauses.

Wordwrap may not be used within report headers or trailers.

The report routine uses the WORDWRAP clause in the FIRST PAGE HEADER, PAGE HEADER or PAGE TRAILER sections.

Remove the WORDWRAP clause from the expression.

Startfield of DATETIME or INTERVAL qualifiers must come earlier in the time-list than its endfield.

The qualifier for a DATETIME or INTERVAL consists of start TO end, where the start and end are chosen from this list: YEAR MONTH DAY HOUR MINUTE SECOND FRACTION.

The keyword for the start field must come earlier in the list than, or be the same as, the keyword for the end field.

Check the order of the startfield and endfield qualifiers. For example, qualifiers of DAY TO FRACTION and MONTH TO MONTH are valid but one of MINUTE TO HOUR is not.

Parenthetical precision of FRACTION must be between 1 and 5. No precision can be specified for other time units.

In a DATETIME qualifier only the FRACTION field may have a precision in parentheses, and it must be a single digit from 1 to 5.

Check the DATETIME qualifiers in the current statement; one of them violates these rules. The first field of an INTERVAL qualifier may also have a parenthesized precision from 1 to 5.

The function 'function-name' can only be used within an INPUT or CONSTRUCT statement.

The function shown is being used outside of an INPUT or CONSTRUCT statement. However, it returns a result that is only meaningful in the context of INPUT or CONSTRUCT.

Review the code to make sure that an END INPUT or END CONSTRUCT statement has not been misplaced. Review the operation and use of the function to make sure you understand it.

No more than one BEFORE or AFTER INPUT/CONSTRUCT clause can appear in an INPUT/CONSTRUCT statement.

There may be only one BEFORE block of statements to initialize each of these statement types.

Make sure that the scope of all your INPUT, CONSTRUCT and MENU statements is correctly marked with END statements. Then combine all the preparation code into a single BEFORE block for each one.

CANCEL INSERT can only be used in the BEFORE INSERT clause of an INPUT ARRAY statement.

The CANCEL INSERT statement is being used outside of the BEFORE INSERT clause of an INPUT ARRAY.

Review the code to make sure that CANCEL INSERT has not been used anywhere except in the BEFORE INSERT clause.

CANCEL DELETE can only be used in the BEFORE DELETE clause of an INPUT ARRAY statement.

The CANCEL DELETE statement is being used outside of BEFORE DELETE clause of an INPUT ARRAY.

Review the code to make sure that CANCEL DELETE has not been used anywhere except in the BEFORE DELETE clause.

The report output, specified by a START REPORT statement, is not any of file, pipe, screen, printer, pipe in line mode, or pipe in form mode.

The output of a report can be sent only to any of file, pipe (in form or line modes), screen, or printer.

Check the START REPORT instruction and make sure that the OUTPUT clause specifies one of the supported values.

This syntax is not supported here. Use [screenrecordname.]screenfieldname.

The field name specification in a BEFORE FIELD or AFTER FIELD is not valid.

Check for the field name and use [screenrecordname.]screenfieldname syntax.

Fatal internal error: description ( line-number ).

This generic error occurs when the fglcomp compiler cannot identify the problem and must stop processing the source.

Check the code near the line displayed in the error message.

The license manager daemon cannot be started.

This error occurs when a process creation fails during the start of the license manager.

Increase the maximum number of processes allowed (ulimit)

Cannot get license information. Check your environment and the license (run 'fglWrt -a info').

See error -6015.

Time limited version: time has expired.

The license installed is a license with time limit and time has expired. The program can not start.

Contact your distributor or support center.

Your serial number is not valid for this version.

The license serial number is invalid for this version of the software.

Contact your distributor or support center.

Cannot get license information. Check your environment and the license (run 'fglWrt -a info').

It is not possible for the application to check the license validity.

• License manager:

  • The license may not have been installed

  • The license controller can not communicate with the license manager. Check that the license manager is started and check that the fglprofile entries flm.server and flm.service contain valid information.

  • The directory $FLMDIR/lock and all the files below must have read/write permission.

• License controller:

  • The license may not have been installed.

  • The directory $FGLDIR/lock and all the files below must have read/write permission.

Cannot get information for license (Error error-num). Check your environment and the license (run 'fglWrt -a info').

The application is unable to check the license validity.

See error -6015.

User limit exceeded. Cannot run this program.

The maximum number of users allowed by the license has been reached. The program can not start.

Contact your distributor or support center.

Cannot access internal data file. Cannot continue this program. Please, check your environment(variable-name).

When a client computer starts an application on the server, the application stores data in the $FGLDIR/lock directory. The client must have permission to create and delete files in this directory.

This demonstration version allows one user only.

The demonstration version is designed to run with only one user. Another user or another graphical daemon is currently active.

Wait until the user stops the current program, or use the same graphical daemon.

Installation: Cannot open 'file-name'.

A file is missing or the permissions are not set for the current user.

Check that the file permissions are correct for the user trying to execute the application. If the file is missing, re-install the compiler package.

Demonstration time has expired. Please, run this program again.

The runtime demonstration version is valid only for a few minutes after you have started a program.

Restart the program.

Demonstration time has expired. Please, contact your vendor.

The demonstration version of the product has a time limit of 30 days.

Either reinstall a new demonstration version, or call your software vendor to purchase a permanent license.

Bad link for runner demonstration. Please, retry or rebuild your runner.

The runner is corrupted.

Cannot access license server. Please check the following:

- the license server entry in your resource file. (service port)

- the license server host.

- the license server program.

You have not specified a value for the environment variable [fgllic|fls|flm].server in the $FGLDIR/etc/fglprofile file.

Check the fglprofile file for the entry point [fgllic|fls|flm].server and specify the name of the computer that runs the License Manager.

Unknown parameter 'param-name' for checking.

The command line of the fglWrt or flmprg tool contains an unknown parameter.

Check your command-line parameters and retry the command.

Temporary license license-number has expired.

Your temporary runtime license has expired.

Call your software vendor to get a new license.

command-name: illegal option: 'option-name'.

You are not using a valid option for the specified command.

Check your command line syntax and try again.

command-name: 'option-name' option requires an argument.

You cannot use this option of the tool without a parameter.

Check your command line and try again.

Warning! This is a temporary license, installation number is 'installation-number'.

You have installed a temporary license of 30 days. You will have to enter an installation key before the end of this period if you want to keep on running the program.

This is only a warning message.

Cannot read in directory

The compiler cannot access the $FGLDIR/lock directory. The current user must have read and write permissions in this directory.

Give the current user read and write permissions to the $FGLDIR/lock directory.

Can not retrieve network interface information.

An error occurred while retrieving network interface information.

Restart your program. If this does not solve your problem, contact your distributor.

MAC Address has changed.

The MAC address of the host has changed since the license was first installed.

The license must be reinstalled, or restore the old MAC address.

The testing period is finished. You must install a new license.

The test time license of has expired.

Call your software vendor to purchase a new license.

IP Address has changed.

The IP Address of the host has changed.

Restore the IP address of the host, or reinstall the license. This is no longer checked by the latest versions of the license controller.

Host name has changed.

The host name has changed.

Restore the host name or reinstall the license. This is no longer checked by the latest versions of the license controller.

Could not get file reference number information.

The license could not get information about the license file.

Reinstall the license. Contact your distributor.

The device number of the license file has changed.

The license file has been touched. The license is no longer valid.

Reinstall the license. Contact your distributor.

The file reference number of the license file has changed.

The license file has been touched. The license is no longer valid.

Reinstall the license. Contact your distributor.

This product is licensed for runtime only. No compilation is allowed.

You have a runtime license installed with this package. You cannot compile BDL source code modules with this license.

If you want to compile 4GL source code, you must purchase and install a development license. Contact your distributor.

Temporary license license-number expired. Please contact your vendor.

A license with a time limit has been installed and the license has expired.

Install a new license to activate the product. Contact your distributor.

Temporary license license-number expired. Please contact your vendor.

A license with a time limit has been installed and the license has expired.

Install a new license to activate the product. Contact your distributor.

Temporary license license-number expired. Please contact your vendor.

A license with a time limit has been installed and the license has expired.

Install a new license to activate the product. Contact your distributor.

Installation path has changed. It must hold the original installation path.

The value of FGLDIR or the location of FGLDIR has been changed.

Ask the person who installed the product for the location of the original installation directory and then set the FGLDIR environment variable.

Cannot read a license file. Check installation path and your environment. Verify if a license is installed.

The file that contains the license is not readable by the current user.

Cannot update a license file. Check installation path and your environment. Verify if a license is installed.

The file that contains the license cannot be overwritten by the current user.

Cannot write into a license file. Please check your rights.

The file that contains the license cannot be overwritten by the current user.

Cannot read a license file. Check installation path and your environment. Verify if a license is installed.

The file that contains the license cannot be read by the current user.

Check that the current user can read the file $FGLDIR/etc/f4gl.sn. Also check that the FGLDIR environment variable is set correctly.

Incorrect license file format. Verify if a license is installed.

The file that contains the license has been corrupted.

Reinstall the license. If you have a backup of the current installation of Genero Business Development Language, restore the files located in the $FGLDIR/etc directory.

Incorrect license file format. Verify if a license is installed.

The file that contains the license has been corrupted.

Reinstall the license. If you have a backup of the current installation of Genero Business Development Language, restore the files located in the $FGLDIR/etc directory.

License 'license-number' not installed.

The license shown is not installed.

Reinstall the license.

No installed license has been found for 'license-number'.

The add-user license can not be installed. No main license found to add users.

Contact your distributor.

License 'license-number' is already installed.

The license shown is already installed.

No particular action to be taken.

The resource 'flm.license.number' is required to use the license manager.

The resource 'flm.license.key' is required to use the license manager.

License 'license-number' cannot be installed over 'license-number'.

The add-user license does not match the main license. The add-user license can not be installed.

Contact your distributor.

You need a installed license if you want to add users.

The add-user license must be installed after the main license.

Install the main license before the add-user license. If this does not solve your problem, contact your distributor.

No license installed.

There is no license installed for Genero Business Development Language.

Install a license. If a license is already installed, check that the $FGLDIR environment variable is set correctly.

Cannot uninstall the license.

There was a problem during the uninstall of the Genero Business Development Language license.

Check whether the FGLDIR environment variable is correctly set in your environment and the current user has permission to delete files in the $FGLDIR/etc directory.

The license server entry must be set in your resource file in order to reach the license server.

You are using the remote license process and you have set the value of fgllic.server, in $FGLDIR/etc/fglprofile, to localhost or to the 127.0.0.1 address.

You must use the real IP address of the computer even if it is the local computer.

Cannot use directory 'directory-name'. Check installation path and verify if access rights are 'drwxrwxrwx'.

The compiler needs to operate in the specified directory.

Change the permission of this directory.

Cannot create file in 'file-name'. Check installation path and verify if access rights are 'drwxrwxrwx'.

The compiler needs to operate in the specified directory.

Change the permission of this directory to 777 mode.

Cannot change mode of a file in 'file-name'. Verify if access rights are 'drwxrwxrwx'.

The compiler needs to operate in the specified directory.

Change the permission of this directory to 777 mode.

'file-name' does not have 'rwxrwxrwx' rights or isn't a directory. Check access rights with 'ls -ld <installation-path>/lock' or execute 'rm -r <installation-path>/lock' if no users are connected.

The compiler needs to operate in the specified directory.

Change the permission of this directory. The $FGLDIR/lock directory contains only data needed at runtime by BDL applications. When the application is finished, you can remove this directory. If you delete this directory while BDL applications are running, the applications will be stopped immediately.

Cannot read from directory 'directory-name'. Check installation path and verify if access rights are 'drwxrwxrwx'.

The compiler needs to operate in the specified directory.

Change the permission of this directory.

Bad lock tree. Please check your environment.

There is a problem accessing the $FGLDIR/lock directory.

Check if the current user has sufficient permission to read and write to the $FGLDIR/lock directory. Check also if the FGLDIR environment variable is correctly set.

Bad lock tree. Please check your environment.

There is a problem accessing the $FGLDIR/lock directory.

Check if the current user has sufficient permission to read and write to the $FGLDIR/lock directory. Check also if the FGLDIR environment variable is correctly set.

Cannot get machine name or network IP address. Each graphical client must have an IP address when using a license server. FGLSERVER must hold the IP address or the host name of the client.

You are using the remote license process and you have set the value of fgllic.server, in $FGLDIR/etc/fglprofile, to localhost or to the 127.0.0.1 address.

You must use the real IP address of the computer even if it is the local computer. This is also true for the value used with the FGLSERVER environment variable.

Cannot get IP address from 'host-name' host. Check the 'flm.server' resource.

The system cannot find the IP address of the specified host.

This is a configuration issue regarding your system. The command ping should not reply as well. Correct your system configuration and then try to execute your program.

Cannot reach host 'host-name' with ping. Check license server entry in your resource file. Check your network configuration or increase 'flm.ping' value.

The license server cannot ping the client computer, or it does not get the response in the time limit specified by the fgllic.ping entry in the $FGLDIR/etc/fglprofile file.

Try to manually ping the specified computer. If this works, try to increase the value of the fgllic.ping entry in fglprofile. If the ping does not respond, fix the system configuration problem and then try the program again.

SYSERROR(error-num) description: Cannot set option TCP_NODELAY on socket. Check the system error message and retry.

There is a problem with the socket of the Windows™ computer.

Check that the system is correctly configured and retry the program.

SYSERROR(error-num) description: Cannot connect to the license server on host 'host-name'. Check following things: - license server entry. - the license server machine. - the license server TCP port.

The application cannot check the license validity. To do so, it tries to communicate with the Genero Business Development Language license service running on the computer where the product is installed.

Check that the Genero Business Development Language License Server is running on the computer where the product is installed.

SYSERROR(error-num) description: Cannot send data to the license server. Check the system error message and retry.

Theres a problem with the socket of the Windows computer.

Check that the system is correctly configured and retry the program.

SYSERROR(error-num) description: Cannot receive data from license server. Check the system error message and retry.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and retry the program.

You are not allowed to be connected for the following reason: description

The program cannot connect to the license server because of the specified reason.

Try to fix the problem described and rerun your application.

Each graphical client must have an IP address when using a license server. FGLSERVER must hold the IP address or the host name of the client (localhost or 127.0.0.1 are not allowed).

Use the real IP address or hostname of the client.

SYSERROR(error-num) description: Cannot create a socket to start the license server. Check the system error message and retry.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and rerun the program.

SYSERROR(error-num) description: Cannot bind socket for the license server. Check the system error message and retry.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and rerun the program.

SYSERROR(error-num) description: Cannot listen socket for the license server.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and rerun the program.

SYSERROR(error-num) description: Cannot create a socket to search an active client.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and rerun the program.

SYSERROR(error-num) description: This is a WSAStartup error. Check the system error message and retry.

There is a problem with the socket of the Windows computer.

Check that the system is correctly configured and rerun the program.

License problem: description

License type incompatible. You are installing an earlier version, which was not designated for use with the current license server.

Reinstall and then contact your vendor.

Connection refused by the license server.

There is problem connecting the client computer to the Windows license server.

There is a configuration problem with the license server computer. Check the configuration of the computers and of the products.

Bad format of line sent by the license requester.

The license request sent by the license controller is not understood by the license manager.

Upgrade your license software to the latest version available. If the issue is not solved, contact your support center.

License number 'license-number' does not correspond to license key 'license-key'.

Either the license number or the license key is invalid.

Check the license number and keys entered and try again. If that does not solve the issue, upgrade your license software to the latest version available. If the issue is not solved, contact your support center.

Verify if resource 'flm.license.number' and 'flm.license.key' correspond to a valid license.

Either the flm.license.number or flm.license.key entry in fglprofile is incorrectly filled. Ensure these fglprofile entries contain valid license numbers.

License 'license-number' is no longer available from the license server.

The license has been uninstalled from the license server. It may still appear as some sessions are active, but the license can not be used to start a new session.

Reinstall the license, or contact your support center.

User limit exceeded. Please retry later.

The maximum number of clients that can be run has been reached (due to the license installed).

Retry later (when the number of current users has decreased) or install a new license that allows more users.

Environment is incorrect.

There is no local license, or the environment is not set correctly.

Check your environment and your FGLDIR environment variable.

Cannot add session #session-number.

You do not have the permissions to create the new session (the directory representing the new client).

Check the permissions of the dedicated directories.

Cannot add program 'program-name' (pid=processid).

You do not have the permissions to create the new application (the file representing the new application) for the current user .

Check the permissions of the dedicated directories.

Compilation is not allowed: This product is licensed for runtime only.

Buy and install a development license.

Compilation is not allowed: Invalid license.

Buy and install a development license.

Cannot start program 'program-name' or result of process number is 0.

When fglWrt -u is executed to find the number of users allowed on this installation, the command "ps" may be launched (only on UNIX).

Check the permissions for ps.

Wrong number of characters.

The license number, license key, installation number, installation key or maintenance key provided is incomplete.

Ensure that provided license numbers are correct and try again.

The entry must be 12 characters long.

The license number, license key, installation number, installation key or maintenance key provided is incomplete.

Ensure that provided license numbers are correct and try again.

Wrong checksum result for this entry.

When entering license numbers, the checksum is verified if it is provided. This error occurs if the checksum computed does not match the provided checksum. Either the checksum or the license number is wrong.

Ensure that checksum and license numbers are correct and try again.

You must specify entry 'flm.server' in the resource file.

The fglprofile entry flm.server is missing. This entry should contain the host name or IP address of the host running the license manager.

Add and configure the fglprofile entry flm.server.

SYSERROR(error-num) description: Cannot open socket. Check the system error message and retry.

The license controller can not connect to the license manager.

Check the error message and fix the issue. Ensure that fglprofile entries flm.server and flm.service are correctly filled. Check your network configuration.

License uninstalled.

This is an information message.

This license requires a full installation.

The installed license has not be activated, but can not be used in temporary installation mode.

Contact your vendor to obtain the activation key.

This license number is no more valid. Please, contact your vendor.

The license number is no longer accepted.

Contact your vendor to obtain a new license number.

Incompatible License Controller (fglWrt/greWrt) version. The minimum version required is min-version.

Upgrade your license controller version to the specified version or higher.

This product requires a BDL license. The license number should start with the letter F.

A BDL license is required for this product.

Call you support center to get a BDL license.

This product requires a Genero license. The license number should start with the letter T.

A Genero license is required for this product.

Call you support center to get a Genero license.

Invalid license key.

The license key does not correspond to the license number.

Call you support center to check the license key.

The date-limited license has expired.

The time limited license has expired, the product is blocked.

Call you support center to get a new license.

This product requires a GRW license .

A GRW license is required for this product.

Call you support center to get a GRW license.

GRW licenses are not accepted by this product .

This product does not accept GRW licenses.

Call you support center to check if the license corresponds to the product.

Version version-number

This is an information message.

Try and buy demonstration time expired. Please, restart your application.

Applications started with a Try and Buy version will stop after few minutes of execution.

Restart your application.

This license requires a valid maintenance key. Check your environment (run 'fglWrt/greWrt -a info')

Genero 2.20 and higher require a valid maintenance key.

Update your maintenance key.

The DVM build date is greater than the maintenance key expiration date. Contact your nearest FourJ's sales representative to update the maintenance key.

Update your maintenance key or downgrade your Genero installation to an older version.

This product requires a Genero Time-Limited Evaluation license.

You have installed a trial version of the Genero product, but the installed license is not a trial license.

Install a trial license for this product. Contact your support to get a trial license.

This product requires a GRE Time-Limited Evaluation license.

You have installed a trial version of the GRE product, but the installed license is not a trial license.

Install a trial license for this product. Contact your support to get a trial license.

Installation path is not known.

You are handling licenses but the FGLDIR environment variable is not set.

Set the FGLDIR environment variable and retry.

Problem while installing license 'license-number'.

A problem occurred while licensing.

Note the system-specific error number and contact your Technical Support.

Temporary license not found for this version.

While adding a definitive license key, the temporary license has not been found.

Re-install the license.

Wrong installation key.

While adding a definitive license key, the installation key was not valid.

Re-install the license.

Problem during license installation.

A problem occurred while installing the license. Could not write information to the disk (either own files or system files).

Check the FGLDIR environment variable and the rights of the license files (must be able to change them).

License installation failed.

License information could not be written to files.

Check the system error message if provided, check the file permissions for the current user.

License installation successful.

This is an information message.

Too many temporary licenses. You must reinstall a license.

You installed a temporary license too many times.

Contact technical support to get a valid license.

Cannot store temporary information.

A problem occurred while installing the license. Could not write information to the disk (either own files or system files).

Check the FGLDIR environment variable and the rights of the license files (you must be able to change them).

This kind of license is not permitted.

The license numbers can not be installed.

Contact your support center.

You do not have the permissions to be connected.

The host running the license controller (where the DVM is running) is not allowed to connect to this license manager. There is likely a configuration issue.

Check your license manager configuration.

You do not have the permissions to compile.

Contact your support center.

Cannot reach the license server. Please check if 'flm.server' is correctly initialized. ('flmprg -a info up' command should answer 'ok'). The license server is running but no autocheck will be done.

While this error is no longer used, it can be raised by older versions of Genero. The license controller can not connect to the license manager.

Ensure that fglprofile entries flm.server and flm.service are filled correctly. Ensure that the license manager is running on the specified host and port.

Cannot get information from directory ' directory-name '.

Failed to read directory information.

Ensure that the user installing a license is the user that installed the product. Ensure that the user installing a license has read/write permissions on the 'etc' directory of the product.

SYSERROR(error-num) description: Cannot set option O_NONBLOCK on socket. Check the system error message and retry.

Failed to configure the socket in non-blocking mode.

Check the system error message. Contact your support center.

Old request format to license server detected. You must install a license program version 2.99 or higher.

The license controller version is too old for the current license manager version. Requests sent by the license controller are no longer supported by the current license manager.

Upgrade the license controller to the latest version available.

A license has been installed temporarily. Only the installation key is required. You must run 'fglWrt -k <installation-key>' to install it.

The installed license is temporarily installed, yet it is missing the installation key.

Obtain your installation key and install it.

Bad parameter: 'parameter' hasn't the right format.

Invalid license number or invalid license key.

During the license installation, the license number / license key couple does not match.

Ensure that the license numbers are correct. Upgrade the license software to the latest version available and retry.

This option is only available for a local license. And resource 'flm.server' was found in your configuration.

A license server is configured and the user tries to install or uninstall a license using fglWrt.

Install the license on the license manager (flmprg) Or remove the license manager configuration from fglprofile and install the license locally.

License number 'license-number' is invalid.

The license number is not valid.

Ensure that the license number provided is correct. Upgrade the license software to the latest version available.

In license server, following problem occurs with license number 'license-number': problem-description

This is a generic error containing the text of another error.

Check the error. Contact your support center.

Following problem occurs with license number 'license-number': problem-description

This is a generic error containing the text of another error.

Check the error. Contact your support center.

Your machine is not allowed to be connected on any of your authorized licenses.

The CPU license rejects the connection of a new host. All CPU licenses are consumed.

Contact your support center.

License validity time is reached. The users control is reactivated.

The CPU license is time limit is reached. The CPU license is degraded and user control is reactivated.

Contact your support center.

CPU limit exceeded. The users control is reactivated.

The CPU license has less CPUs available than the number of CPUs on the connected host, resulting in one or more hosts running in degraded mode. When running in degraded mode, the number of users allowed is the number of available CPUs in the license * 100 users. User control is activated for license request coming from that host.

In the case of a single host, user control applies to local licenses as well. If Host A has 6 CPUs, yet has a 5 CPU license, it consumes all of the CPUs for the license and run in degraded mode. That means 5 * 100 users are allowed.

Contact your support center.

Cannot get license extension information. Check your environment, the license (run 'fglWrt -a info') and the fglWrt version ('fglWrt -V' should give version-number or higher).

Contact your support center.

Your license has 'restriction-name' restriction. You are not allowed to run another mode.

The license has restrictions, and the requested use of the license is not compatible with these restrictions. For example, the license may have a text-only restriction, where GUI front-ends are not allowed.

Contact your support center to obtain a license matching your needs.

Local license controller (fglWrt) may not be compatible with this runner. Check its version ('fglWrt -V' should give version-number or higher).

The license controller is incompatible.

Update the license controller to the latest version available.

You are not authorized to run this version of runner.

Older licenses do not use the maintenance key. The DVM version that can be used is limited. The DVM version is higher that the allowed DVM version.

Contact your support center. Re-licensing is required.

Protection file is not compatible with this version of the runner. You must reinstall your license.

This error is no longer used by the current licensing software, however it may occur with older versions.

Contact your support center.

Demo version initialization.

This is an information message.

Your evaluation license period has expired. Contact your support center.

The software you are using has been installed with a demo license that has expired.

Contact your software vendor to extend the evaluation period or purchase a permanent license.

You are not authorized to delete sessions from the license server 'server-name'.

The command fglWrt -i can only be used with local licenses. If a license server is configured, this error is raised.

Use the command flmprg instead.

'extension-name' extension is not allowed with this license type.

Generic error indicating that an extension check is rejected. For example, if you are using a non-Informix database, this error will raise if the ODI extension is not set in the license.

Product identifier does not correspond to the license number.

This error indicates that a wrong license is installed in the product, such as when you attempt to use a Genero Report Writer (GRW) license when installing the Genero Business Development Language (BDL). This error should not be raised, as fglWrt will reject the installation of a Genero Report Engine (GRE) license when installing Genero BDL, and conversely greWrt will not allow the installation of a Genero BDL license.

That being said, the installation checks to ensure the license is valid for the product, and raises this error it if is not.

Ensure the proper license is used with the proper package.

Cannot create directory 'directory-name'. Check installation path and verify your access rights.

The specified directory can not be created or modified.

Module 'module-name': The function function-signature-1 will be called as function-signature-2 .

An incorrect number of parameters are used to call a BDL function.

Check your source code and recompile your application.

Module 'module-name': Bad version: Recompile your sources.

You have compiled your program with an old version. The newly compiled version of your program is not supported.

Compile all source files and form files again.

filename 'file-name': Bad magic: Code can't run with this p code machine.

You have compiled your program with an old version. The new compiled version of your program is not supported. You might also have a file with the same name as the .42r. You used the fglrun 42r-Name without specifying the extension.

To resolve this problem, call fglrun with the .42r extension or recompile your application.

Module 'module-name-1': The function 'function-name' has already been defined in module 'module-name-2'.

The specified function is defined for the second time in the application. The second occurrence of the function is in the specified module.

Eliminate one of the two function definitions from your source code.

Module 'module-name': Unknown op-code.

An unknown instruction was found in the compiled BDL application.

Check that the version of the Genero Business Development Language package executing the compiled application is the same as the one that compiled the application. It is also possible that the compiled module has been corrupted. If so, you will need to recompile your application.

INTERNAL ERROR: Alignment.

This error is internal, which should not normally occur.

Contact your Technical Support.

The 42m module 'module-name' could not be loaded, check FGLLDPATH environment variable.

The 42m module is not in the current directory or in one of the directories specified by the FGLLDPATH environment variable.

Set the environment variable FGLLDPATH with the path to the 42m modules to be loaded.

The dynamic loaded module 'module-name' does not contain the function 'function-name'.

A BDL module has been changed and recompiled, but the different modules of the application have not been linked afterward.

Link the new modules together before you execute your application.

Module 'module-name' already loaded.

A module was loaded twice at runtime. This can occur because one module has been concatenated with another.

Recompile and re-link your BDL modules.

INTERNAL ERROR: exception 2 raised before invoking the exception handler for exception 1.

A module was loaded twice at runtime. This can occur because one module has been concatenated with another.

Check for function names, recompile and re-link your BDL modules.

Link has failed.

A problem occurred while linking the BDL program.

Check for function names, recompile and re-link your BDL modules.

Function function-name : local variables size is too large - Allocation failed.

A local function variable is too large and runtime could not allocate memory.

Review the variable data types in the function.

Module module-name : Module's variable size is too large - Allocation failed.

A module variable is too large and runtime could not allocate memory.

Review the variable data types in the module.

Global variable variable-name size is too large - Allocation failed.

A global variable is too large and runtime could not allocate memory.

Review the variable data types in the globals.

Memory allocation failed. Ending program.

Runtime could not allocate memory.

Check for system resources and verify if the OS user is allowed to allocate as much memory as the program needs (check for ulimits on UNIX systems).

The global 'constant-name' has been redefined with a different constant-value.

A global constant has been defined twice with a different value.

A global constant may have only one value. Review your code.

The global 'variable-name' has been defined as a constant and a variable.

The same symbol was used to define a constant and a variable.

Use a different name for the constant and the variable. Review your code.

No runtime. You must call fgl_start() before calling fgl_call().

This error occurs when a C extension has redefined the main() routine, but then does not call fgl_start() to initialize the BDL runtime environment.

Check the C extension and call fgl_start() before any other operation.

WHENEVER ERROR CALL: The error-handler recursively calls itself.

The function specified with the WHENEVER ERROR CALL instruction raises an error that would call itself recursively.

Review the function called by the WHENEVER ERROR CALL and make sure it does not produce a runtime error.

Could not load C extension library ' library-name'. Reason: reason

Runtime system could not find the shared library for the reason given.

Check if the C extension library exists in one of the directories defined by FGLLDPATH. If the C extension module depends from other shared libraries, make sure that these libraries can be found by the library loader of the operating system (check the LD_LIBRARY_PATH environment variable on UNIX or the PATH environment variable on Windows).

C extension initialization failed with status number.

C extension failed to initialize and returned the status shown in the error message.

Check the C extension source or documentation.

class-name class not found.

The program was compiled with the built-in class class-name but at execution time the class is not found.

Check you installation, it is possible that you are executing program that was compiled with a younger version as the version used in the execution context, which certainly is missing that class in the runtime library.

Can not connect to GUI.

You have run a GUI application but the environment variable FGLSERVER is not set correctly, or the Genero client (graphical front-end) is not running.

The FGLSERVER environment variable should be set to the hostname and port of the graphical front end used by the runtime system to display the application windows. Check that the network connection is still available, make sure no firewall denies access to the workstation, and see whether the front-end is still running.

Can not write to GUI: reason

You are running a GUI application but for an unknown reason the front-end no longer responds and the runtime system could not write to the GUI socket.

Check that the network connection is still available, make sure no firewall denies access to the workstation, and see whether the front-end is still running.

Can not read from GUI: reason

You are running a GUI application but for an unknown reason the front-end no longer responds and the runtime system could not read from the GUI socket.

Check that the network connection is still available, make sure no firewall denies access to the workstation, and see whether the front-end is still running.

Invalid user interface protocol.

You are trying to execute a program with a runtime system that uses a different AUI protocol version as the front-end.

Install either a new front-end or a new runtime environment that matches (2.0x with 2.0x, 1.3x with 1.3x).

Invalid abstract user interface definition.

You are trying to execute a program with a runtime system that uses a different AUI protocol version as the front-end.

Install either a new front-end or a new runtime environment that matches (2.0x with 2.0x, 1.3x with 1.3x).

Can not open char table file. Check your fglprofile.

This error occurs if the conversion file defined by the gui.chartable entry, in the $FGLDIR/etc/fglprofile file, is not readable by the current user.

Check if the gui.chartable entry is correctly set and if the specified file is readable by the current user.

Can not open server file. Check installation.

A file on the server side cannot be sent to the graphical interface.

Check the permissions of the file located in the $FGLDIR/etc directory. These files must have at least read permission for the current user.

GUI server autostart: can not identify workstation.

GUI Server autostart configuration is wrong. Either DISPLAY, FGLSERVER or fglprofile settings are invalid.

Set the required environment variables and check for fglprofile autostart entries.

GUI server autostart: unknown workstation: check gui.server.autostart entries.

The computer described by the X11 DISPLAY environment variable is neither the local host, nor is it listed in the fglprofile entries.

Check if the X11 DISPLAY name is correctly set, or review the fglprofile entries.

Not connected. Cannot write to GUI.

For unknown reasons there was an attempt to write on the GUI socket before the connection was initiated.

Check the program for invalid GUI operations.

Not connected. Cannot read from GUI.

For unknown reasons there was an attempt to read on the GUI socket before the connection was initiated.

Check the program for invalid GUI operations.

No current window.

The program tries to issue a MENU instruction with no current window open.

Review the program logic and make sure a window is open before MENU.

The type of the user interface (FGLGUI) is invalid.

While initiating the user interface, the runtime system did not recognize the GUI type and stopped.

Make sure the FGLGUI environment variable has a correct value.

The UserInterface has been destroyed.

The error occurs when the front-end sends a DestroyEvent event, indicating some inconsistency with the starting program. This can happen, for example, when multiple StartMenus are used, or when you try to run an MDI child without a parent container, or when two MDI containers are started with the same name, etc.

Check for inconsistency and fix it.

Wrong connection string. Check client version.

While starting the program, the runtime received a wrong or incorrectly constructed answer from the front-end.

Make sure you are using a front-end that is compatible with the runtime system.

The form is too complex for the console-ui.

The program tries to display a form with a complex layout that can't be displayed in text mode.

Review the form file and use a simple grid with a SCREEN section instead of LAYOUT.

Error error-num returned from client: description

Front end returned the specified error during GUI connection initialization.

Check the front-end documentation for more details.

Invalid or unsupported client protocol feature.

The GUI protocol feature you are trying to use is not supported by the front-end. For example, you are trying to use protocol compression but the runtime is not able to compress data.

Make sure that the front-end component is compatible with the runtime system (versions must be close). Check the runtime system version for supported protocol features. If compression is enabled, check that the zlib library is installed on your system.

Choosing the DIALOG implementation by setting the environment variable FGL_USENDIALOG=0 has been desupported since version 2.20.03.

You try to use the old dialog implementation by setting FGL_USENDIALOG to zero.

The old dialog implementation has been removed, you must unset the FGL_USENDIALOG environment variable.

Internal error in the database library. Set FGLSQLDEBUG to get more details.

An unexpected internal error occurred in the database driver.

Set the FGLSQLDEBUG environment variable to level 1, 2, 3 or 4 to get detailed debug information.

Can't open file 'file-name'.

The runtime system tried to open a resource file in FGLDIR but access is denied or file no longer exists.

Check for file permissions and existence in FGLDIR.

No such interface capability: 'feature-name'.

The runtime system tried to use a front-end protocol capability, but is not able to use it.

Check if the front-end is compatible with the runtime system.

version-num-1 wrong version. Expecting version-num-2.

Some resource files of FGLDIR have been identified as too old for the current runtime system.

Re-install the runtime system environment.

Can't load factory profile 'file-name'.

The default fglprofile file located in FGLDIR/etc is missing or is unreadable.

Check the permission of the file. If the file is missing, reinstall the software.

Can't load customer profile 'file-name'.

The configuration file defined by the FGLPROFILE environment variable is missing or unreadable.

Check if the FGLPROFILE environment variable is correctly set and if the file is readable by the current user.

Can't load application resources 'file-name'.

The directory specified by the fglrun.default entry in FGLDIR/etc/fglprofile is missing or not readable for the current user.

Check if the entry fglrun.default is correctly set in FGLDIR/etc/fglprofile and if the directory specified is readable by the current user.

Internal error in the run time library file library-name.

Something unpredictable has occurred, generating an error.

Contact your Technical Support.

Bad format of resource 'entry-name' value 'entry-value': you must use the syntax: entry-name='VARNAME=envvar-value'.

The FGLPROFILE file contains an invalid environment variable definition format.

Check the content of the profile file.

All TABLE columns must be defined with the same height.

The form layout defines a TABLE with field tags using different heights.

Review all cells of the table to use the same height in all columns.

Syntax error in profile 'file-name', line number lineno , near 'token'.

The FGLPROFILE file shown in the error message contains a syntax error.

Check the content of the profile file.

Front end module could not be loaded.

A front end call failed because the module does not exist.

The front end is probably not supporting this module.

Front end function could not be found.

A front end call failed because the function does not exist.

The front end is probably not supporting this function.

Front end function call failed. Reason: description

A front end call failed for an unknown reason.

Call the support and report the problem.

Front end function call stack problem.

A front end call failed because the number of parameter or returning values does not match.

Make sure the number of parameters and return values are correct.

Can't open file.

The channel object failed to open the file specified.

Make sure the filename is correct and user has permissions to read/write to the file.

Unsupported mode for 'open file'.

You try to open a channel with an unsupported mode.

See channel documentation for supported modes.

Can't open pipe.

The channel object failed to open a pipe to execute the command.

Make sure the command you try to execute is valid.

Unsupported mode for 'open pipe'.

You try to open a channel with an unsupported mode.

See channel documentation for supported modes.

Can't write to unopened file, pipe or socket.

You try to write to a channel object which is not open.

First open the channel, then write.

Channel write error.

An unexpected error occurred while writing to the channel.

See system error message for more details.

Cannot read from unopened file, pipe or socket.

You try to read from a channel object which is not open.

First open the channel, then read.

This runner can't execute any SQL.

The runtime system is not ready for database connections.

Check the configuration of BDL.

Dynamic SQL: type unknown: type-name .

The database driver does not support this SQL data type.

You cannot use this SQL data type, review the code.

Cannot connect to sql back end.

The runtime system could not initialize the database driver to establish a database connection.

Make sure the database driver exists.

Database driver not connected yet.

There is an attempt to execute an SQL statement, but no database connect is established.

First connect, then execute SQL statements.

Could not load database driver driver-name.

The runtime system failed to load the specified database driver. The database driver shared object (.so or .DLL) or a dependent library could not be found.

Make sure that the specified driver name does not have a spelling mistake. If the driver name is correct, there is probably an environment problem. Make sure the database client software is installed. Check the UNIX LD_LIBRARY_PATH environment variable or the PATH variable on Windows. These must point to the database client libraries.

Incompatible database driver interface.

The database driver interface does not match the interface expected by the runtime system. This can occur if you copy an old database driver into a younger FGLDIR installation.

Call the support to get a valid database driver.

SQL driver initialization function failed.

The runtime system failed to initialize the database driver, program must stop because no database connection can be established.

There is probably an environment problem (for example, INFORMIXDIR or ORACLE_HOME is not set). Check your environment and try to connect with a database vendor tool (dbaccess, sqlplus) to identify the problem.

Invalid database connection mode.

You try to mix DATABASE and CONNECT statements, but this is not allowed.

Use either DATABASE or CONNECT.

Unsupported SQL feature.

This SQL command or statement is not supported with the current database driver.

Review the code and use a standard SQL feature instead.

SQL statement error number error-num (native-error).

An SQL error has occurred having the specified error number.

You can query SQLERRMESSAGE or the SQLCA record to get a description of the error.

General SQL error, check SQLCA.SQLERRD[2].

A general SQL error has occurred.

You can query SQLERRMESSAGE or the SQLCA record to get a description of the error. The native SQL error code is in SQLCA.SQLERRD[2].

Invalid database connection string.

The database connection string that you have used is not valid.

Verify the format of the connection string.

Wrong database driver context.

You try to EXECUTE, OPEN, FETCH, PUT, FLUSH, CLOSE or FREE a cursor that was declared or prepared in a different connect and driver.

Issue a SET CONNECTION before the statement to select the same connection and driver as when the cursor was created.

LOAD cannot get describe information for table columns.

The LOAD instructions needs column description to allocate the automatic fetch buffers, but the database driver is not able to describe the table columns used in the INSERT statement.

If the underlying database client API does not provide result set column description, the LOAD statement cannot be supported.

Can not open Database dictionary 'directory-name'. Run database schema extraction tool.

The schema file does not exist or cannot be found.

If the schema file exists, verify that the filename is spelled correctly, and that the file is in the current directory or the FGLDBPATH environment variable is set to the correct path. If the file does not exist, run the database schema extraction tool to create a schema file.

Can not open globals file 'file-name'.

The globals file does not exist or cannot be found.

Verify that the globals file exists. Check the spelling of the filename, and verify that the path is set correctly.

The file 'file-name' cannot be created for writing.

The compiler failed to create the file shown in the error message for writing.

Check for user permissions to make sure that the .42m file can be created.

The function 'function-name' can only be used within an INPUT [ARRAY], DISPLAY ARRAY or CONSTRUCT statement.

The language provides built-in functions that can only be used within specific interactive statements.

Review your code and make the necessary corrections.Check that the function is within the interactive statement and that appropriate END statements (END INPUT/ARRAY/DISPLAY ARRAY/CONSTRUCT) have been used.

The module 'module-name' does not contain function 'function-name'.

The module shown in the error message does not hold the function name as expected.

The specified function needs to be defined in this module.

No member function 'function-name' for class 'class-name' defined.

The function name is misspelled or is not a method of the class for which it is called.

Review your code and the documentation for the method you are attempting to use. If the function is an object method, make sure the referenced object in your code is of the correct class.

Resource error: entry-name :parameter expected

This is a generic error message for resource file problems.

A grammatical error has been found at 'seen-token' expecting: expected-token.

A general syntax error message that indicates the location of the problem code and what code was expected.

Review your code, particularly for missing END statements such as END FUNCTION or END INPUT, etc., and make the necessary corrections.

The function 'function-name' has already been called with a different number of parameters.

Earlier in the program, there is a call to this same function or event with a different number of parameters in the parameter list.

Check the correct number of parameters for the specified function. Then examine all calls to it, and make sure that they are written correctly.

Function 'function-name': unexpected number of returned values.

The function shown returned a different number of values as expected.

Check the body of the function for RETURN instructions.

Redeclaration of function 'function-name'.

The function shown was defined multiple times.

Change the name of conflicting functions.

The library function 'function-name' is not declared.

The function shown was not declared.

Change the name of the function.

The function 'function-name' may return a different number of values.

The function shown contains multiple RETURN instructions which may return different number of values.

Review the RETURN instructions to return the same number of values.

The symbol 'symbol-name' is unused.

This is a warning indicating that the shown symbol is defined but never used.

Useless definition can be removed.

The symbol 'symbol-name' does not represent a defined CONSTANT.

The shown symbol is used as a CONSTANT, but it is not a constant.

Review your code and check for this name.

The symbol 'symbol-name' is a VARIABLE.

The symbol shown is a VARIABLE which cannot be used in the current context.

Review your code and check for this name.

The symbol 'symbol-name' is a CONSTANT.

The symbol shown is a CONSTANT which cannot be used in the current context.

Review your code and check for this name.

The symbol 'symbol-name' is not an INTEGER CONSTANT.

The symbol shown is used as if it was an INTEGER constant, but it is not.

Review your code and check for this name.

The symbol 'symbol-name' is not a REPORT.

The symbol shown is used as a REPORT, but it is not defined as a REPORT.

Review your code and check for this name.

The symbol 'symbol-name' is not a FUNCTION.

The symbol shown is used as a FUNCTION, but it is not defined as FUNCTION.

Review your code and check for this name.

The symbol 'symbol-name' does not represent a valid variable type.

The symbol shown is not known as a valid type to define a program variable.

Review your code and check for the type name.

The method 'method-name' can't be called without an object.

The specified method is an object method of its class.

Review your code. Ensure that the required object of the class has been instantiated and still exists, and that the method is called specifying the object variable as the prefix, with the period character as a separator.

The method 'method-name' can't be called with an object.

The specified method is a class method and cannot be called using an object reference. No object has to be created.

Review your code. Ensure that the method is called using the class name as the prefix, with the period character as a separator.

The statement is not Informix compatible.

The SQL statement is not Informix^® compatible.

Change the SQL statement by using Informix SQL syntax.

The symbol 'symbol-name' is not a VARIABLE.

The symbol shown is use as a variable, but is not defined as a variable.

Review your code and check for this name.

The GLOBALS file does not contain a GLOBALS section.

The filename specified in a GLOBALS statement references a file that does not contain a GLOBALS section.

Review your code to make sure that the file specified by the filename is a valid GLOBALS file, containing the required GLOBALS section.

The type 'type-name' is too complex to be used within a C-extension.

The type of the global variable is too complex to be used in a C extension. This error can occur when the -G option of fglcomp, to generate the C sources to share global variables with C extensions, when a global variable is defined with complex data types without a C equivalent.

Review the definition of the global variables and use simple types instead, corresponding to a C data type. The BYTE, TEXT and STRING types are complex types.

Memory overflow occurred during p-code generation. Simplify the module.

A memory overflow occurred during compilation to p-code because the 4gl source module is too large.

This problem can occur with very large source files. You must split the module into multiple sources.

Incompatible types, found: source-type, required: target-type.

A LET or RETURNING tries to assign a value or an object reference to a variable defined with a data type or class that is not compatible to the value type. This occurs usually when using Java™ classes because Java is a strongly type language. For example, assigning a Java string to a Java StringBuffer raises this error.

Define the target variable with a type corresponding to the assigned value.

Cannot find symbol symbol-name, location: category type-name.

The symbol used does not exist. This occurs typically when referencing a Java class with an invalid name in the class path, or when referencing a class member that does not exist.

Check the symbol names used in the instruction.

primitive-type cannot be dereferenced.

An expression references a method or a field with a primitive Java type, but primitive types are not classes and therefore do not have methods or fields. For example, you try to call a method with a symbol defined as integer or short in Java: DISPLAY java.lang.Short.MAX_VALUE.foo

Review the code using the symbol defined with a primitive type.

Incompatible or corrupted database dictionary 'database-name'.

The .sch database schema 'database-name' contains incompatible type definitions or is corrupted.

Re-generate the .sch file with the fgldbsch tool by using the correct command line options to generate compatible types.

The license 'license-num' requires a full installation.

Licenses with 'Strict licensing' option require a complete (full) install.

The license 'license-num' is no more valid. Please contact your vendor.

The license number is no longer valid.

Contact your vendor to obtain a new license number.

Invalid license request format.

The request sent to the license manager was not recognized.

Check that the version of the license manager is compatible with the runtime system.

Incompatible License Manager (flmprg) version. The minimum version required is version-num.

The license manager is too old and is not compatible with the current runtime system.

Call the support center to get a new version of the license manager.

The license number 'license-num' is invalid. Please, contact your vendor.

The license number could not be validated by the license server.

Call the support center to get a new license number.

The license 'license-num' has expired. Please, contact your vendor.

The license is time limited and it has expired.

Call the support center to get a new license number.

CPU limit exceeded. Please, contact your vendor.

The license is CPU limited and the system has more CPUs as allowed.

Call the support center to get a new license number.

Report Writer token creation failed.

Check permissions on the lock/token directory (in FGLDIR or FLMDIR).

This GRW license requires a DVM license with a valid maintenance date.

GRW licenses with the option 'DVM under maintenance' require that the DVM maintenance key expiration date not be expired.

Update the DVM maintenance key.

Cannot get GRW report token information.

Contact your support center.

The installed license is invalid and cannot be used by this product.

The current license is not valid for the product you have installed.

Contact your support center to get a license corresponding to the current installed product.

Can not open Database dictionary 'schema-name'. Run schema extraction tool.

The schema file does not exist or cannot be found.

If the schema file exists, verify that the filename is spelled correctly, and that the file is in the current directory or the FGLDBPATH environment variable is set to the correct path. If the file does not exist, run the database schema extraction tool to create a schema file.

A grammatical error has been found at 'line-number', expecting token-name.

This is a generic message for errors.

'form-name' form compilation was successful.

This is an information message indicating that the form was compiled without problem.

Open Form 'form-name', Bad Version: version-1, expecting: version-2.

You have compiled your form with a version of the form compiler that is not compatible with that used for compiling the other source code.

Compile your form file and related source code files using the same or compatible versions of the compilers.

The label 'label-name' could not be used as column-title.

The form file defines an invalid TABLE column title.

Check for column titles which are not corresponding to column positions.

The widget 'widget-name' can not be defined as array.

The form file defines an item which is used as a matrix column.

Review your form definition.

The layout tag 'tag-name' is invalid, expecting: token-name.

The form compiler detected an invalid layout tag specification.

Review your form definition.

The attribute 'attribute-name' is invalid for item type 'type-name'.

The form compiler detected an invalid attribute definition for this item type.

Review your form definition and check for invalid attributes.

Syntax error near 'token-1', expecting token-2.

A general syntax error message that indicates the location of the problem code and what code was expected.

Review your code and make the necessary corrections.

Unterminated char constant.

The form compiler detected an unterminated character constant.

Review your form definition and check for missing quotes or double-quotes.

The element 'element-name' conflicts with group-box 'group-name'.

You have used the same name for an element and for a group-box.

Review your form definition and ensure that the names used are unique.

All members of the SCREEN RECORD 'screen-record-name' must reference the same Table or ScrollGrid.

The shown screen record references multiple tables or scrollgrids in your form file.

Review your form definition and use one unique table for a given screen record.

Invalid indentation in between braces.

The LAYOUT section of your form defines an invalid indentation.

Review your form definition and check for corresponding indentations.

TABLE container defined without a SCREEN RECORD in the INSTRUCTION section.

The minimum value of the defined attribute must be lower than the maximum value.

Review your code and make the necessary corrections.

Min value must be lower that Max value.

The minimum value of the defined attribute must be lower than the maximum value.

Review your code and make the necessary corrections.

Number of elements in the SCREEN RECORD must match the number of columns in TABLE container.

The elements defined in the screen record differs from the columns used for the TABLE container.

Review your form definition and add missing table columns to the screen record, order does not matter.

ScrollGrid and/or Group layout tags cannot be nested.

The form definition has nested ScrollGrid and/or Group layout tags. These tags cannot be nested.

Review your form definition and make the necessary corrections.

HBOX tags cannot be used for ARRAYS.

The form definition is using an HBOX tag for an array, which is not permitted.

Review your form definition and make the necessary corrections.

Escaped graphical characters are not accepted in GRID sections.

You try to use Text User Interface graphics in the new GRID container.

This is not allowed, use GROUPs instead.

Close tag does not have a matching tag above.

The form definition has a close tag without a prior matching open tag. Open tags and close tags must match.

Review your form definition file and make the necessary corrections.

The table 'table-name' is empty.

The form layout defines a table layout tag identified by tablename , but nothing was found directly under this table which could be a column or a column title.

Append columns to the table layout region.

The tag 'tag-name' overlaps with table 'table-name'.

In the form layout, tagname overlaps the layout region of tablename and makes it invalid.

Move or remove tagname , or redefine the layout region of tablename .

Checked value must be different from unchecked value for field 'field-name'.

The VALUECHECKED and VALUEUNCHECKED attributes have the same value. This makes no sense because these attributes define the values corresponding to the checked and unchecked states of a checkbox.

Use different values for these attributes.

Duplicated item key found for field 'field-name'.

The ITEMS attribute of field fieldname defines item keys with the same value.

Check ITEMS attribute and use unique key values. Note that '' and NULL are equivalent.

The attribute attribute-name must belong to a column of a TABLE.

A form item uses an attribute that references a form field which is not defined or does not belong to the TABLE.

Check the ATTRIBUTES section for invalid column references.

The column column-name referenced by the attribute-name attribute must belong to the TABLE.

A form item uses an attribute that references a form field which is not defined or does not belong to the TABLE.

Check the ATTRIBUTES section for invalid column references.

Not implemented (yet): feature-name

The feature or syntax you are using is not implemented yet.

This feature cannot be used in the Genero version you have installed.

At least one member of the SCREEN RECORD 'screen-record-name' must not be a PHANTOM field.

A screen record is defined with form fields that are all defined as PHANTOM fields.

At least on screen record field must not be a PHANTOM field.

Repeated screen tags 'tag-name' are misaligned, must align on X or Y.

The layout defines multiple tags with the same name, but these are not properly aligned in the X or Y direction.

Edit the form file and make sure that repeated tags are correctly aligned.

Invalid TREE definition: the field 'field-name' must be an EDIT or LABEL.

The form defines a TREE container with the field column defined with a wrong item type.

Replace the item type by EDIT or LABEL.

Invalid TREE definition: the field 'field-name' must be defined for the SCREEN RECORD.

The form defines a TREE container with an invalid field set.

Check that mandatory fields such as node name, parent id and node id fields are defined.

The fields specified in the THRU option appear in the reverse order.

The form defines a screen record by using the THRU or THROUGH keyword, but the first field is defined after the last field in the ATTRIBUTES section.

Exchange the field names specified in the screen record definition, or review the declaration order in ATTRIBUTES.

Invalid TREE definition: the attribute 'attribute-name' conflicts with id or parentid.

The .per form defines a TREE with invalid configuration. You have probably used the same field for the named attribute and for IDCOLUMN or PARENTIDCOLUMN.

Review the form definition and configure the TREE properly. You must use dedicated columns for the attributes mentioned.

Invalid AGGREGATE definition: must be located below a table column.

The .per form defines an AGGREGATE form item with a field tag that is not aligned under a table column field tag.

Review the table layout and make sure that all aggregate fields are properly aligned and placed below column tags.

This area is reserved for AGGREGATEs.

The .per form defines a TABLE with aggregate fields, but not all aggregate fields are declared with the AGGREGATE item type.

Review the field definitions in the ATTRIBUTES section.

The screen tag 'tag-name' can not be defined in a TABLE.

The .per form defines a TABLE with columns using different field tag names, an no AGGREGATE field is defined.

Review columns of the TABLE, each field tag of a given column must use the same tag name, except if you want to define an AGGREGATE field.

Columns with AGGREGATE must have type EDIT.

The form field table column corresponding to the aggregate field must be of type EDIT.

FORM not contain TOPMENU or TOOLBAR.

The form layout includes an external form specification file containing a TOPMENU or a TOOLBAR. Remove these sections from the included form file.

FORM is out of date.

The form layout includes an external form specification file the was compiled with a older version.

Dom: Node not found.

The node could not be found in the current document.

Review your code.

Dom: Invalid Document.

The document passed to the DOM API is not a valid document. Review your code.

Dom: Invalid usage of NULL as parameter.

NULL cannot be used at this place.

Review your code.

Dom: A node is inserted somewhere it doesn't belong.

You try to insert a node under a parent node which does not allow this type of nodes.

Check for the possible nodes and review your code.

Sax: Invalid hierarchy.

The SAX handler encountered an invalid hierarchy.

Make sure parent/child relations are respected.

Deprecated feature: feature-name

The feature you are using will be removed in a next version.

A replacement for the feature is normally available.

The string resource file 'file-name' cannot be found.

The string file shown could not be found.

Check if file exists and if path is valid.

The string resource file 'file-name' cannot be read.

The string file shown could not be read.

Check if file exists and if user has read permissions.

There is no string text defined for the 'key-name' string key.

The runtime system could not find a string resource corresponding to the shown key.

Check if the key is defined in one of the resource files.

String resource syntax error near 'token-name', expecting token.

The string file compiler detected a syntax error.

Check for invalid syntax in the .str file.

Duplicate string key 'key-name' ( file-name : line ) IGNORE LINE.

The string file compiler detected duplicated string keys.

Review the .str file and remove duplicated keys.

The string file 'file-name' can not be opened for writing.

The string file compiler could not write to the specified string file.

Make sure the user has write permissions and file name is valid.

The string file 'file-name' can not be read.

The runtime system could not read from the specified string file.

Make sure the user has read permissions.

Field ( field-name ) in ON CHANGE clause not found in form.

The field used in the ON CHANGE clauses was not found in the form specification file.

Make sure the field name of the ON CHANGE clause matches a valid form field.

You cannot have multiple ON CHANGE clauses for the same field.

It is not possible to specify multiple ON CHANGE clauses using the same field.

Remove unnecessary ON CHANGE clauses.

SFMT: Invalid % index used.

The format string is not valid.

Check for invalid % positions.

SFMT: Format error.

The format string is not valid.

Check for invalid % positions.

Multiple ON ACTION clauses with the same action name appear in the statement.

It is not possible to specify multiple ON ACTION clauses using the same action name.

Remove unnecessary ON ACTION clauses.

Multiple ON KEY clauses with the same key name appear in the statement.

It is not possible to specify multiple ON KEY clauses using the same key.

Remove unnecessary ON KEY clauses.

Dom: Cannot open xml-file.

The file could not be loaded.

Check file name and user permissions.

Dom: The attribute 'attribute-name' does not belong to node 'node-type'.

You try to set an attribute to a node which does not have such attribute.

This is not allowed, review your code.

Dom: Character data can not be created here.

You try to create a text node under a node which does not allow such nodes.

This is not allowed, review your code.

Dom: Cannot set attributes of a character node.

You try to set attributes in a text node.

This is not allowed, review your code.

Dom: The attribute 'attribute-name' can not be removed: the node 'node-type' belongs to the user-interface.

You try to remove a mandatory attribute from an AUI node.

You can only change the value of this attribute, try 'none' or an empty string.

Sax: can not write.

The SAX handlers could not write to the destination file.

Make sure the file path is correct and the user has write permissions.

Multiple inclusion of the source file 'file-name'.

The preprocessor detected that the specified file was included several times by the same source.

Remove unnecessary file inclusions.

The full path to the source file 'file-name' is too long.

The preprocessor does not support very long file names.

Rename the file.

The source file 'file-name' cannot be read.

The preprocessor could not read the file specified.

Make sure the use has read permissions.

The source file 'file-name' cannot be found.

The preprocessor could not find the file specified.

Make sure the file exists.

Extra token found after 'directive-name' directive.

The preprocessor detected an unexpected token after the shown directive.

Review your code and make the necessary corrections.

feature-name : This feature is not implemented.

This preprocessor feature is not supported.

Review your code and make the necessary corrections.

The macro 'macro-name' has already been defined.

The preprocessor found a duplicated macro definition.

Review your code and make the necessary corrections.

A &else directive found without corresponding &if,&ifdef or &ifndef directive.

The preprocessor detected an unexpected &else directive.

Review your code and make the necessary corrections.

A &endif directive found without corresponding &if,&ifdef or &ifndef directive.

The preprocessor detected an unexpected &endif directive.

Review your code and make the necessary corrections.

Invalid preprocessor directive & name found.

The preprocessor directive shown in the error message does not exist.

Review your code and check valid macros.

Invalid number of parameters for macro-name.

The number of parameters of the preprocessor macro shown in the error message does not match de number of parameters in the definition of this macro.

Review your code and check for the number of parameters.

Lexical error: Unclosed string.

The compiler detected an unclosed string and cannot continue.

Review your code and make the necessary corrections.

Unterminated condition &if or &else.

The preprocessor found an un-terminated conditional directive.

Review the definition of this directive.

The operator '##' can only be used with identifiers and numbers. token is not allowed.

The preprocessor found an invalid usage of the ## string concatenation operator.

Review the definition of this macro.

Could not run FGLPP, command used: command

The compiler could not run the preprocessor command shown in the error message.

Make sure the preprocessor command exists.

Lexical error: Unclosed comment.

The compiler detected an unclosed comment and cannot continue.

Review your code and make the necessary corrections.

This type of statement can only be used within an INPUT, INPUT ARRAY, DISPLAY ARRAY, CONSTRUCT or MENU statement.

This statement has not been used within a valid interactive statement, which must be terminated appropriately with END INPUT, END INPUT ARRAY, END DISPLAY ARRAY, END CONSTRUCT, or END MENU.

Review your code and make the necessary corrections.

This type of statement can only be used within an INPUT, INPUT ARRAY, DISPLAY ARRAY or CONSTRUCT statement.

This statement has not been used within a valid interactive statement, which must be terminated appropriately with END INPUT, END INPUT ARRAY, END DISPLAY ARRAY, or END CONSTRUCT.

Review your code and make the necessary corrections.

Invalid use of 'dialog'. Must be used within an INPUT, INPUT ARRAY, DISPLAY ARRAY or CONSTRUCT statement.

The predefined keyword DIALOG has not been used within a valid interactive statement, which must be terminated appropriately with END INPUT, END INPUT ARRAY, END DISPLAY ARRAY, or END CONSTRUCT.

Review your code and make the necessary corrections.

An error occurred while preprocessing the file 'file-name'. Compilation ends.

The Genero BDL preprocessor could not parse the whole source file and stopped compilation.

Review the source code and check for not well formed & preprocessor macros.

The program cannot ACCEPT (INPUT|CONSTRUCT|DISPLAY) at this point because it is not immediately within (INPUT|INPUT ARRAY|CONSTRUCT|DISPLAY ARRAY) statement.

ACCEPT XXX has not been used within a valid interactive statement, which must be terminated appropriately with END INPUT, END PROMPT, or END INPUT ARRAY.

Review your code and make the necessary corrections.

Dom: Invalid XML data found in source.

ACCEPT DISPLAY has not been used within a valid DISPLAY ARRAY statement, which must be terminated with END DISPLAY ARRAY.

Review your code and make the necessary corrections.

Sax: Invalid processing instruction name.

The om.SaxDocumentHandler.processingInstruction() does not allow invalid processing instruction names such as 'xml'.

<?xml ..?> is not a processing instruction, it is reserved to define the XML file text declaration. You must use another name.

Illegal input sequence. Check LANG.

The compiler encountered an invalid character sequence. The source file uses a character sequence which does not match the locale settings (LANG). Check source file and locale settings.

Unknown preprocessor directive 'directive-name'.

The preprocessor directive shown in the error message is not a known directive.

Check for typo errors and read the documentation for valid preprocessor directives.

Unexpected preprocessor directive.

The preprocessor encountered an unexpected directive.

Remove the directive.

The resource file 'file-name' contains unexpected data.

The XML resource file shown in the error message does not contain the expected nodes. For example, you try to load a ToolBar with ui.Interface.loadActionDefaults().

Check if the XML file contains the node types expected for this type of resource.

XPath: Unclosed quote at position integer .

The XPath parser found an unexpected quote at the given position.

Review the XPath expression.

XPath: Unexpected character 'char' at position pos.

The XPath parser found an unexpected character at the given position.

Review the XPath expression.

XPath: Unexpected token/string 'token-name' at position pos.

The XPath parser found an unexpected token or string at the given position.

Review the XPath expression.

SQL statement or language instruction with vendor proprietary syntax.

The compiler found an SQL statement which is using a database specific syntax. This statement will probably not run on other database servers as the current.

Review the SQL statement and use standard/common syntax and features.

Spacer items are not allowed inside a SCREEN sections.

The form contains spacer items in a SCREEN section, while these are only allowed in LAYOUT.

Review the form specification file.

A TABLE row should not be defined on multiple lines.

All columns of a row in a TABLE container must be in a single line.

Use a SCROLLGRID if you want to show row cells on multiple lines.

DOM(ui): insert of removed node is not allowed.

It is not possible to insert a removed node in the AUI document.

Review the code.

The client connection timed out, exiting program.

The runtime system could not establish the connection with the front-end after a given time. This can for example happen during a file transfer, when the front-end takes too much time to answer to the runtime system.

Check that your network connection is working properly.

File transfer interrupted.

An interruption was caught during a file transfer.

File could not be transferred, you need to redo the operation.

Network error during file transfer.

An socket error was caught during a file transfer.

Check that your network connection is working properly.

Could not write destination file for file transfer.

The runtime system could not write the destination file for a transfer.

Make sure the file path is correct and check that user has write permissions.

Could not read source file for file transfer.

The runtime system could not read the source file to transfer.

Make sure the file path is correct and check that user has read permissions.

File transfer protocol error (invalid state).

The runtime system encountered a problem during a file transfer.

A network failure has probably raised this error.

File transfer not available.

File transfer feature is not supported.

Make sure the front-end supports file transfer.

The localized string file 'file-name' is corrupted.

The shown string resource file is invalid (probably invalid multibyte characters corrupt the file).

Check for locale settings (LANG), make sure the .str source uses valid characters and recompile it.

'symbol-name' is already defined.

The form file defines several elements of the same type with the same name.

Review the form file and use unique identifiers.

Statement must terminate with ';'.

An ESQL/C preprocessor directive is not terminated with a semicolon.

Add a semicolon to the end of the directive.

Invalid 'include' directive file name.

An include preprocessor directive is using an invalid file name.

Check the file name.

A &elif directive found without corresponding &if,&ifdef or &ifndef directive.

The preprocessor found an &elif directive with no corresponding &if .

Add the &if directive before the &elif, or remove the &elif .

The compiler plugin name could not be loaded.

fglcomp could not load the plugin because it was not found.

Make sure the plugin exists and can be loaded.

The compiler plugin name does not implement the required interface.

fglcomp could not load the plugin because the interface is invalid.

Check if the plugin corresponds to the version of the compiler.

The attribute 'attribute-name' has been defined more than once.

The variable attribute shown in the error message was defined multiple times.

Review the variable definition and remove duplicated attributes.

The attribute 'attribute-name' is not allowed.

The variable attribute shown in the error message is not allowed for this type of variable.

Review the possible variable attributes.

An error occurred while parsing the XML file.

The runtime system could not parse an XML file, which is probably not using a valid XML format.

Check for XML format typos and if possible, validate the XML file with a DTD.

Could not open xml file.

The specified XML file cannot be opened.

Make sure the file exists and has access permissions for the current user.

Invalid multibyte character has been encountered.

A compiler found an invalid multibyte character in the source and cannot compile the form or module.

Check locale settings (LANG) and verify if there are no invalid characters in your sources.

The item 'item-name' is used in an invalid layout context.

The form item name is used in a layout part which does not support this type of form item. This error occurs for example when you try to define a BUTTON as a TABLE column.

Review your form definition file and use correct item types.

NULL pointer exception.

The program is using calling a method thru an object variable which is NULL.

You must assign an object reference to the variable before calling a method.

Can't open socket.

The channel object failed to open a TCP socket.

Make sure the IP address and port are correct.

Unsupported mode for 'open socket'.

You try to open a channel with an unsupported mode.

See channel documentation for supported modes.

The socket connection timed out.

Socket connect could not be established and timeout expired.

Check all network layers and try again.

File error in BYTE or TEXT readFile or writeFile.

File I/O error occurred while reading from or writing to a file.

Verify the file name, content and access permissions.

The dialog attribute 'attribute-name' is not supported.

A dialog instruction was declared with an ATTRIBUTES clause containing an unsupported option.

Review the ATTRIBUTES clause and remove unsupported option.

Action 'action-name' not found in dialog.

You try to use and action name that does not exist in the current dialog.

Verify if name of the action is defined by an ON ACTION clause.

Field 'field-name' already used in this DIALOG.

The DIALOG instruction binds the same field-name or screen-record multiple times.

Review all sub-dialog blocks and check the field-names / screen-records.

The clause 'clause-name' appears more than once.

You have defined the same dialog control block multiple times. For example, AFTER ROW was defined twice.

Remove the un-necessary control blocks.

At least one field for this INPUT ARRAY must be editable.

An INPUT ARRAY is executed on fields that are read-only. At least one field must be editable and active.

Review the form specification file or check that at least one field is active.

Multi-range selection is not available in this context.

You try to use multi-range selection but it is not possible in the current dialog type.

Disable this feature.

Multi-range selection is not available in this context.

You try to use multi-range selection but it is not possible in the current dialog type.

Disable this feature.

Cannot change selection flag for this range of rows.

An attempt of selection flag modification with DIALOG.setSelectionRange() failed because the range is out of bounds or because there is no multi-range selection available in this context.

Make sure you can use multi-range selection, and check the start and end index of the range.

General SQL Warning, check SQLCA.SQLERRD[2] or SQLSTATE.

The last SQL statement has generated an SQL warning setting the SQLCA.SQLAWARN flags.

Program execution can continue. However, you should take care and check the native SQL code and the SQL message in SQLERRMESSAGE.

Value too large to fit in a TINYINT.

The TINYINT data type can accept numbers with a value range from -128 to +127.

To store numbers that are outside this range, redefine the column or variable to use the SMALLINT or INTEGER type.

ON FILL BUFFER conflicts with DISPLAY ARRAY as a tree.

The DISPLAY ARRAY instruction is using a treeview as decoration, but it implements also an ON FILL BUFFER trigger to do paged mode. The paged mode is not possible when using a treeview, because all rows of visible nodes are required (i.e. the dialog cannot display a tree only with a part of the dataset).

To populate dynamically the array for a treeview, use the ON EXPAND to add new nodes and ON COLLAPSE to remove nodes.

The form 'form-name' is incompatible with the current runtime version. Rebuild you forms.

The .42f form was probably compiled with an earlier version as the current runtime system.

Recompile the form with the fglform compiler corresponding to the current fglrun.

Attempt to access a closed dialog.

A call to a DIALOG class method is done with a dialog object that has terminated.

Review the program logic and call the DIALOG methods only for active running dialogs.

The TABLE column tag 'tag-name' appears multiple times in the row definition.

A TABLE column can only be used once in the row definition, you have probably repeated the same screen tag by mistake.

Modify the TABLE row definition in the layout section in order to use each column only once.

Syntax error in preprocessor directive.

The source file contains a preprocessor macro with an invalid syntax.

Check the preprocessor manual page and fix the syntax error.

The source and destination file name of a file transfer must not be NULL or empty.

The program is doing an fgl_getfile() or fgl_putfile() and the source or destination file name is NULL or empty.

Provide a valid file name for both source and destination parameters.

Cannot read from TUI: system-error .

A program running in text mode (FGLGUI=0) failed to read from console input stream.

Check the console/terminal settings.

Not found.

This message displayed by the runtime system when a record was not found. It can be displayed in different contexts, for example when searching a record in a list with the built-in search feature.

Field ( field-name ) in ON ACTION INFIELD not found in form.

The field name used in an ON ACTION INFIELD action handle could not be found in the form.

Make sure you are using the correct field name and field prefix (table name or screen record name).

FGL_LENGTH_SEMANTICS environment variable is invalid. Valid values are BYTE and CHAR

The value specified in the FGL_LENGTH_SEMANTICS environment variable must be BYTE or CHAR.

Subdialog dialog-name: already active

The sub-dialog is already in use.

JSON parse error: error-description

Verify the input string passed to the JSON parsing function.

JSON stringify error: error-description

The JSON serialization failed.

Can not happen: description

The runtime system encounters an unexpected situation. The message is displayed to the user, but the program flow will continue. This unexpected situation must be fixed by programmers.

apidoc: parameter name 'param-name' is invalid.

The compiler has detected a comment error while extracting the source documentation: The @param variable name is not in the list of parameters in the next FUNCTION definition.

Check the function parameter name.

apidoc: tag missing: @param param-name.

The compiler has detected a comment error while extracting the source documentation: There is a missing @param tag that should describe a parameter of the next FUNCTION definition.

Check the function parameter name.

apidoc: invalid tag name @ tag-name.

The compiler has detected a comment error while extracting the source documentation: The @ tag-name tag is not a known tag name.

Check for typo errors in the tag name.

Cannot load java shared library. Reason: system-error

The runtime system could not load the JVM shared library (or DLL).

Make sure that a JRE is installed on the machine and check the environment (LD_LIBRARY_PATH on UNIX or PATH on Windows).

Cannot create java VM.

The runtime system could load the JVM shared library (or DLL), but could not initialize the Java VM with a call to JNI_CreateJavaVM().

Check that the Java requirements and resources needs to create a Java VM.

Array element type is not a Java type.

The fglcomp compiler detected a Java Array definition which is not using a Java type for the elements.

Review the DEFINE statement and use a Java type.

Java is not supported.

The platform you are using does not support a recent Java version required by Genero.

You cannot use the Java interface in this operating system, you must review your source code and remove all Java related parts.

Cannot assign a value to final variable 'variable-name'.

The program tries to set a Java class variable which is not writable.

Review the program logic.

The Java variable 'variable-name' can not be used here.

The program tries to use a Java class variable in an invalid context. For example, a Java class variable is used in an INPUT instruction.

Review the program logic and use a regular Genero BDL variable.

Java exception thrown: java-exception-text.

A Java exception has been thrown while executing Java code.

Check the exception text and review the code.

module.name has private access.

An instruction references a module function or module variable which is declared as private.

Make the function or variable public in the imported module.

Reference to name is ambiguous.

A function or variable referenced without the module prefix, but exists in several imported modules. This error can also be printed by the compiler for Java calls.

Add the module prefix before the object name to remove the ambiguity.

Cyclic IMPORT FGL involving module.

Some modules are importing each other and introduce a cyclic reference which is impossible to resolve.

Extract common language elements into a new module.

Module name does not exist.

The module name to be imported could not be found.

Make sure the module name matches the file name.

Module name has not been imported.

A statement is referencing module name which has not been imported.

Import the module before usage.

category-name qualifier-name.symbol-name has not been defined.

The symbol identified by qualifier-name.symbol-name cannot be found. For example, a START REPORT or SUBDIALOG is referencing a report or sub-dialog symbol with module prefix, but the symbol is not found in the specified module.

You must import the module defining the referenced symbol.

The function 'function-name' has not been defined. This conflicts with IMPORT FGL.

The function name is referenced in the compiled module, but none of the imported modules define that function.

You must import the module containing the function.

The type of the parameter 'param-name' is not an SQL type: cannot be inserted into a temporary table used for this report.

The REPORT parameter name is defined with a BDL type that has no SQL equivalent and thus cannot be used to create the temporary table needed to sort rows for a two-pass report.

Define the parameter with an SQL-compatible type (CHAR, VARCHAR, INTEGER, DECIMAL, etc).

ON ACTION action-name conflicts with ON action-name.

The dialog block defines conflicting ON ACTION and ON triggers, defining the same actions. For example, an ON ACTION delete is defined within a dialog block that is also defining an ON DELETE trigger.

Review the dialog actions, if you want to use ON triggers defining actions.

The action action-name shadows another action with the same name.

The dialog defines ON ACTION blocks using the same action name at different levels (dialog, sub-dialog and field level).

Use different action names when a conflict occurs.

The symbol 'symbol-name' is not a DIALOG.

The symbol referenced is not defined as a DIALOG subdialog block.

Value not allowed for this XML attribute.

Remove the value for this attribute or see the "Mapping between simple 4GL and XML data types" section.

Value mandatory for this XML attribute.

Set a value to the XML attribute. See the "Mapping between simple 4GL and XML data types" section.

Cannot set the XML attribute, because only one XSD attribute is allowed per definition.

Select the unique appropriate XSD data type.

XML Attribute only allowed on a 4GL TYPE.

Remove the XML attribute or change your 4GL DEFINE instruction into a 4GL TYPE definition.

XML Attribute is not allowed on a type definition.

Remove the XML attribute or change your 4GL TYPE definition into a 4GL DEFINE instruction.

XML Attribute XSTypeNamespace cannot be set without attribute XSTypeName.

Add a XSTypeName attribute.

XML Attribute is only allowed on a simple data type definition.

Remove the XML attribute or change your RECORD or ARRAY into a simple 4GL data type.

XML Attribute is only allowed on a 4GL RECORD definition.

Change your 4GL variable definition into a RECORD.

XML Attribute is only allowed on a one dimentional array definition.

Remove the XML attribute or use a one dimentional array.

Attributes XMLAttribute, XMLElement, XMLAny and XMLBase are exclusives.

Choose only one of the above available choices.

Attributes XMLChoice, XMLAll, XMLSequence, XMLSimpleContent and XSComplexType are exclusives.

Choose only one of the above available choices.

Attribute XSTypeName has been defined twice with the same value XML attribute and the same XSTypeNamespace value, but not the same definition.

Define a unique (XSTypeName,XSTypeNamespace) couple for your program.

XMLName or XMLNamespace not allowed on nested XMLChoice variable.

Remove the XMLName and XMLNamespace attributes.

XMLName or XMLNamespace not allowed on nested XMLSequence variable.

Remove the XMLName and XMLNamespace attributes.

Unrecognized XML attribute value.

Review the available values for this XML attibute.

XML Attribute is only supported on a member of a record.

Remove the XML attribute.

XML Attribute is only supported on a record's member when XMLChoice is defined.

Remove the XML attribute.

XML Attribute is only supported on a record's member when XMLSimpleContent is defined.

Remove the XML attribute.

XML Attribute not supported on this simple type.

Remove the XML attribute or change your 4GL type definition.

Attribute XMLTypeNamespace cannot be set without attribute XMLTypeName.

Set XMLTypeName attribute.

XMLSimpleContent attribute supports only XMLAttribute and XMLAnyAttribute attributes.

Remove the unallowed XML attributes.

Attribute XMLBase has been defined more than once in the 4GL record.

Set only one XMLBase attribute.

Attribute XMLSelector has been defined more than once in the 4GL record.

Set only one XMLSelector attribute.

XML Attribute cannot be set with other attributes.

Remove all the other XML attributes.

Attribute XMLSelector is missing in the 4GL record.

Set the XMLSelector attribute on one of the record member.

Attribute XMLBase is missing in the 4GL record.

Set the XMLBase attribute on one of the record member.

Nested XML attribute cannot be defined on a 4GL TYPE.

Remove the Nested XML attribute.

Nested XML attribute cannot be defined on root variable.

Remove the Nested XML attribute.

Invalid parameter.

See the documentation about the function paramaters.

Parameters of a published RPC Web Service operation must be a Record or NULL.

Review your parameters definition.

Parameters of a published DOC Web Service operation must be a Record, an Array or NULL.

Review your parameters definition.

XML Attribute is not allowed on a 4GL record's member.

Remove the XML attribute or set it at the appropriate place.

XML Attribute can only be set on a ARRAY defined inside a RECORD.

Remove the XML attribute or set it at the appropriate place.

XML Attribute cannot be defined at first level of a variable.

Remove the XML attribute or set it at the appropriate place.

Attributes 'XMLAttribute' are not allowed on nested sequence or choice.

Remove the XMLAttribute attribute.

RPC Web Functions cannot have XMLList set on one of the parameters.

Put your 4GL ARRAY inside a 4GL RECORD.

Attribute XMLName is mandatory on 4GL variable when used as SOAP Header.

Add the XMLName attribute.

RPC Web Functions cannot have XMLNamespace set on one of the parameters.

Remove the XMLNamespace attribute.

XSComplexType attribute allows only attributes with one optional nested list or nested record.

Set only one XMLOptional attribute for all nested record members.

XMLName or XMLNamespace not allowed on nested XMLAll.

Remove XMLName and XMLNamespace.

Nested XML Attribute is not allowed on an array.

Remove the XML attribute

XMLBase Attribute allows only one additional XSD attribute.

Set a unique XSD attribute.

XML Attribute value is not allowed on a 4GL record's member.

Set the appropriate value to the specified XML attribute.

Unsupported facet constraint for the 4GL type.

Check the available facet constraint in "Mapping between simple 4GL and XML data types" section.

Invalid value for facet constraint 'constraint-name'.

Check the available facet constraint value. See Facet constraints between simple 4GL and XML data types.

Facet constraint attributes cannot be defined without a XSD simple type attribute.

Add the appropriate XSD attribute.

Facet XSDLength and XSDMinLength or XSDMaxLength cannot be used together.

Select only one of the above attributes.

XML Attribute not allowed on 4GL objects.

Remove the XML attribute.

Attribute XMLName cannot be set with XMLAny or XMLAnyAttribute.

Remove the XMLName attribute.

XML Attribute not allowed on members of xmlchoice='inherited' records.

Remove the XML attribute.

Parameter with public qualifier not allowed.

Remove the PUBLIC instruction.

Parameters of published Web Service operations must be variables in global or modular scope.

Move your variables to a GLOBALS instruction or to modular scope.

A published Web service header must be a variable in global or modular scope.

Move your Web service header to a GLOBALS instruction or to modular scope.

Web service function with private qualifier not allowed.

Remove the PRIVATE instruction.

Web service function must be a string literal.

You cannot use a variable for your web service function name.

XML Attribute is not allowed on an array definition.

Remove the XML attribute.

Attribute XMLAny has been defined more than once per 4GL record.

Use only one XMLAny attribute in a 4GL RECORD.

Attribute XMLAnyAttribute has been defined more than once per 4GL record.

Use only one XMLAnyAttribute attribute in a 4GL RECORD.

Attribute XMLList and XMLAnyAttribute are exclusives.

Use only one of the above XML attributes.

Element of 4GL array with XMLAnyAttribute must be a 4GL record containing three variables for the namespace, name, value of type STRING.

Example: DEFINE arr DYNAMIC ARRAY OF RECORD ns, name, value STRING END RECORD

XML Attribute is only allowed on dynamic arrays.

Change your 4GL ARRAY into a DYNAMIC ARRAY.

XML Attribute cannot be set inside a nested record.

Remove the XML attribute.

Attribute XMLAttribute is not allowed after attribute XMLAnyAttribute.

Move the record member with XMLAnyAttribute attribute to the last position.

A published Web service fault must be in global or modular scope.

Move your variables to a GLOBALS instruction or to modular scope.

Attribute XMLName is mandatory on the 4GL variable when used as Fault.

Set the XMLName attribute.

Colon not allowed for XML attribute value.

Remove the colon.

XML Attribute is only allowed on a root variable.

Remove the attribute or move it to the root variable.

Bad W3CEndPointReference definition.

RECORD ATTRIBUTE(W3CEndpointReference)
  address STRING, -- The location of the Web Service (for ex: URL)
  ref RECORD
    ... (other members defining the state)
  END RECORD
END RECORD

See com.WebService.CreateStatefulWebService.

Invalid state 4GL variable, only simple variables or W3CEndpointReference record allowed.

Check that "state" parameter TYPE of function com.WebService.CreateStatefulWebService is correct. Its type must be a simple type definition or a W3CEndPointReference RECORD.

Registered HTTP variable error.

Check that the 4GL variable match the definition set in com.WebService.registerInputHTTPVariable or com.WebService.registerOutputHTTPVariable.

Incorrectly formed hexadecimal value.

You try to load data with LOAD or locate a BYTE variable with a file contained malformed hexadecimal values.

Check the file content and fix the typos before loading again.

Invalid delimiter. Do not use '\' or hex digits (0-9, A-F, a-f).

You try to LOAD or UNLOAD data with an invalid field delimiter.

Change the field delimiter to a valid character such as | (pipe) or ^ (caret).

Internal runtime error occurred in WS server program.

Contact your support center.

Cannot create WS operation because the given function is not defined.

Verify that the name of the BDL function of fgl_ws_server_publishFunction() is correct.

Invalid WS-function declaration, no parameters allowed.

Verify that the BDL function has no input and no output parameters.

Operation name is already used in the current web service.

You must change the name of the Web-Function operation in the function fgl_ws_server_publishFunction().

WS server port already used by another application.

You must change the port number in the function Fgl_ws_server_start().

Some BDL data types are not supported by XML.

Verify that all exposed functions don't contain one of the following data types:

• DATETIME beginning with MINUTE
• DATETIME beginning with SECOND
• INTERVAL beginning with YEAR and/or MONTH

Invalid fgl_ws_set/getOption() parameter.

Verify that the option flag of the fgl_ws_setOption()/ fgl_ws_getOption() function exists.

WS input record not defined.

Verify that the name of the input record on the fgl_ws_server_publishFunction() exists.

WS output record not defined.

Verify that the name of the output record on the fgl_ws_server_publishFunction() exists.

The port value from the FGLAPPSERVER environment variable or from the parameter of the fgl_ws_server_start() function is not a numeric one.

Verify that the port value contains only digits. See fgl_ws_server_start()

No application server has been started at specified host.

Verify that FGLAPPSERVER contains the right host and port where the application server is listening.

No more licenses available.

Contact your support center.

Current runner version not compatible with the Web Services Extension.

Install the right version of the Genero BDL.

The input namespace of your Web function is missing.

Add a valid input namespace in fgl_ws_server_publishFunction().

The output namespace >namespace of your Web function is missing.

Add a valid output namespace in fgl_ws_server_publishFunction().

Cannot load a certificate or private key file.

Verify that each ws.ident.security FGLPROFILE entries contain a valid security identifier.

Cannot find a certificate in the Windows key store.

Verify that each ws.ident.security FGLPROFILE entries contain a valid Windows security identifier.

Cannot load the Certificate Authorities file.

Verify that the security.global.ca FGLPROFILE entry contains the correct Certificate Authorities filename.

Cannot create the Certificate Authorities from the Windows key store.

Verify that you have enough rights to access the Windows key store.

Cannot set the cipher list.

Verify that all ciphers in the list are valid ones and supported by openssl.

Unable to reach the HTTP proxy.

Verify that the proxy.http.location FGLPROFILE entry contains the correct HTTP proxy address.

Unable to reach the HTTPS proxy.

Verify that the proxy.https.location FGLPROFILE entry contains the correct HTTPS proxy address.

Unknown HTTP proxy authenticate identifier.

Verify that the proxy.http.authenticate FGLPROFILE entry contains a valid HTTP authenticate identifier.

Unknown HTTPS proxy authenticate identifier.

Verify that the proxy.https.authenticate FGLPROFILE entry contains a valid HTTP authenticate identifier.

Cannot create a HTTP authenticate configuration.

Verify that all authenticate logins and passwords are correctly set.

Cannot create an encrypted HTTP authenticate configuration.

Verify that all authenticate logins and encrypted passwords are correctly set.

Cannot create a server configuration.

Verify that all ws.ident.url FGLPROFILE entries are correctly set.

Unknown server configuration security identifier.

Verify that all ws.ident.security FGLPROFILE entries contain a valid Security identifier.

Unknown server configuration authenticate identifier.

Verify that all ws.ident.authenticate FGLPROFILE entries contain a valid HTTP Authenticate identifier.

Invalid self object.

Contact your support center.

Cannot perform operation due to invalid parameters.

Check all parameters against the built-in classes documentation.

Service registration failed, see SQLCA.SQLERRM for more details.

Check the following :

Cannot create web service, see SQLCA.SQLERRM for more details.

Check that the service has a valid name and namespace.

Cannot create Web operation, see SQLCA.SQLERRM for more details.

Check that operation name and namespace are valid according to the style (Document or RPC).

Cannot publish Web operation, see SQLCA.SQLERRM for more details.

Check that input or output headers have previously been created.

Published 4GL function not found, see SQLCA.SQLERRM for more details.

Check that 4GL function to be publish exists.

Published 4GL function not correctly defined, see SQLCA.SQLERRM for more details.

Check that 4GL function has no input or output parameters.

Input parameter of published operation error. See SQLCA.SQLERRM for more details.

Contact your support center.

Output parameter of published operation error. See SQLCA.SQLERRM for more details.

Contact your support center.

Web Service header configuration error, see SQLCA.SQLERRM for more details.

Verify that a one-way function do not have an output header.

Service is already registered. You cannot modify a service after it has been registered.

Check that you do not call a service modifier method on a service after registration.

Invalid option.

Check the option name according to documentation.

Unsupported web service operation.

Verify if a Document style operation does not perform SOAP Section5 encoding.

Bad URI.

Check that URI passed to a HttpRequest or TcpRequest is valid.

HTTP runtime exception, see SQLCA.SQLERRM for more details.

Contact your support center.

XML runtime exception, see SQLCA.SQLERRM for more details.

Contact your support center.

WSDL generation failed.

Contact your support center.

Charset conversion exception, see SQLCA.SQLERRM for more details.

Change server charset response via a HTTP accept header or change you application locale.

TCP runtime exception, see SQLCA.SQLERRM for more details.

If detailed message is 'The TCP connection has been interrupted', then check that your network was working properly and that the INT_FLAG was not set to TRUE.

When working with a Web Service application, this can the result of a COM error. Check in FGLWSDEBUG to see whether it was shut down on the client or server side.

WS-DEBUG (IO ERROR)
Class: TCPConnection::atomicReceive()
Msg: TCP input stream shut down.
Code: 104
WS-DEBUG END=

You can find the 104 code in /usr/include/asm-i386/errno.h (depending on your system).

In this example it correspond to: #define ECONNRESET 104 /* Connection reset by peer */

Index is out of bound.

Check your index maximum value.

Unsupported request-response feature.

Check the streaming operations order or for invalid usage. For example, in function readTextRequest(), the incoming request can be read only once, so processing the incoming message while sending the response is not allowed.

No request was sent.

Check that you called one of the doRequest(), doXmlRequest() or doTextRequest() method before to call getResponse() or getAsyncResponse().

Request was already sent.

Check that you do not call twice one of the doRequest(), doXmlRequest() or doTextRequest() method.

Waiting for a response.

Check that you do not perform a new request before reading the response of previous one.

No stream available.

Check that you do not call a method to read on a stream that has not yet been created.

Streaming is over.

Check that you do not read a streaming response that was closed.

Streaming in progress.

Check that you do not call twice beginXmlResponse() without a call to endXmlResponse().

Streaming not yet started.

Check that you do not call endXmlRequest() or endXmlResponse() without a beginXmlRequest() or beginXmlResponse().

Streaming already started.

Check that you do not call twice beginXmlRequest() or beginXmlResponse().

Unexpected peer stream was shutdown.

The peer closed connection during reading operation.

Cannot return incoming request, see SQLCA.SQLERRM for more details.

Check detailed message.

Operation failed, see SQLCA.SQLERRM for more details.

Check the parameter for invalid data.

Parameter cannot be NULL.

Check that the parameter is not NULL

4GL callback function not found, see SQLCA.SQLERRM for more details.

Check that 4GL callback function exists.

4GL callback function requires one input and one output parameter, see SQLCA.SQLERRM for more details.

Check 4GL callback parameters according to documentation.

Web Service fault error. See SQLCA.SQLERRM for more detail.

Contact your support center.

Stateful Service error. See SQLCA.SQLERRM for more detail.

Contact your support center.

Access denied lock error.

Either the file is already locked, or the application does not have the write access right to the given path.

HTTP Multipart error : desc.

One of the methods of the COM multipart API has failed. The variable desc is replaced with the error detail. Contact your support center if the error detail does not provide the information needed to fix the error.

Internal error, should not happen.

Contact your support center.

Operation failed.

Check method for invalid parameters according to documentation.

Name cannot be NULL.

Check that name parameter is not NULL.

Namespace cannot be NULL.

Check that namespace parameter is not NULL.

Prefix cannot be NULL.

Check that prefix parameter is not NULL.

Value cannot be NULL.

Check that parameter is not NULL according to documentation.

Node cannot be NULL.

Check that node parameter is not NULL.

Text cannot be NULL.

Check that text parameter is not NULL.

Target of a processing instruction cannot be NULL.

Check that target parameter is not NULL.

Name of an entity reference cannot be NULL.

Check that entity name parameter is not NULL.

XPath expression cannot be NULL.

Check that xpath parameter is not NULL.

Filename cannot be NULL.

Check that filename parameter is not NULL.

Document cannot be NULL.

Check that document parameter is not NULL.

DTD string cannot be NULL.

Check that dtd parameter is not NULL.

Stax cannot be NULL.

Check that stax parameter is not NULL.

Malformed XML name.

Check that xml name is well-formed.

Malformed XML string.

Check that xml string is well-formed.

Malformed XML prefix.

Check that xml prefix is well-formed.

Malformed XML namespace.

Check that xml namespace is well-formed.

Bad validation type.

Check validation type parameter.

No XML schema found.

Check that a valid XML schema is used for validation.

No DTD schema found.

Check that a DTD schema is present in XML document.

Feature or option cannot be NULL.

Check that parameters are not NULL.

Feature or option is unsupported.

Check option or feature name according to documentation.

Feature or option value is invalid.

Check option or feature validity according to documentation.

Node is not part of the document.

Check that node belong to the same XML document.

Node does not have the correct parent node.

Check that node to remove belongs to the right parent node.

Node is already linked to another node.

Check that node is not already attached to another node.

Cannot add a node to itself.

Check that node to add is not itself.

Index is out of bounds.

Check index maximum value.

StaxWriter runtime exception, see SQLCA.SQLERRM for mode details.

Check detailed message of stax write.

StaxReader runtime exception, see SQLCA.SQLERRM for mode details.

Check detailed message of stax reader.

Serializer runtime exception, see SQLCA.SQLERRM for mode details.

Check detailed message of xml serializer.

Document loading runtime exception, check xml.DomDocument.getErrorDescription() for more details.

Check detailed message of dom document.

Document saving runtime exception, check xml.DomDocument.getErrorDescription() for more details.

Check detailed message of dom document.

Invalid encoding.

Check encoding value.

PublicID of a DTD cannot be set with a SystemID.

Check DTD node creation

Undefined namespace prefix in the XPath expression.

Check an undeclared prefix used in XPath expression.

XPath expression error.

Check XPath expression.

A namespace in the XPath namespace list is missing.

Check for an undeclared namespace used in XPath expression

XPath function has two mandatory parameters.

Check parameters according to documentation.

Internal XPath error.

Contact your support center.

Invalid XPath namespace.

Check namespace value passed to XPath method.

Unable to load schema.

Check XML schema parameters in DomDocument.setFeature().

Schemas are malformed or inconsistent.

Check XML schema validity in DomDocument.setFeature().

URI is malformed.

Check that URI is well-formed according to documentation.

Protocol layer needs a new try to complete operation.

Sax writer close operation requires a new request to complete previous one.

Charset conversion error.

Check fglrun LANG and system locale.

Unable to load xml security library.

Contact your support center.

Xml security operation failed. See SQLCA.SQLERRM for more detail.

Check detailed message.

URL cannot be null.

Check if XML-Security URL is NULL.

CryptoX509 cannot be null.

Verify that CryptoX509 object has been correctly instantiated.

CryptoKey cannot be null.

Verify that CryptoKey object has been correctly instantiated.

Bad signature transformation.

Check transformation URL validity passed to appendReferenceTransformation()

Bad signature digest.

Check digest URL validity passed to createReference().

Bad signature node.

Check XML-Signature node passed to CreateFromNode().

Bad key type.

Check key identifier URL.

Bad key usage.

Verify usage of CryptoKey object passed to setKeyEncryptionKey() or setKey().

Bad XPathFilter2 type, only intersect, subtract or union allowed.

Verify type used in a XPathFilter2 transformation.

Bad derived key URL.

Check derived key identifier URL.

Internal error, should not happen.

Contact your support center.

Called operation failed, see SQLCA.SQLERRM for more details.

See SQLCA.SQLERRM for details on why the operation failed.

Invalid parameter.

Check that your security library function has the correct parameters.

File access denied.

Check that your security library function has the permissions to access to the file.

File does not exist.

Check that the file exist on your system for the security library function to access.

Algorithm not supported.

Check that the algorithm is in the supported list for security library function. See security.Digest.CreateDigest.

Invalid current object.

Check that the context for security library function is correctly initialized. See security.Digest.CreateDigest.

Internal security error.

Contact your support center.