Error 1335 vmware workstation

error 1335 vmware workstation

Installing or upgrading the vCenter Single Sign-On component of vCenter Server 5.1 on Windows fails with the error: Error 1335 with ssoser~1.cab (2057691). System error messages sorted by error number. -1335. A report is accepting output or being finished before it has been Cannot create java VM. 01 I was receiving the following message: ERROR 1335. The cabinet file 'openoffice1. cab' required for this installation is corrupt and cannot.

Error 1335 vmware workstation - well understand

flm].server in the $FGLDIR/etc/fglprofile file.

Check the fglprofile file for the entry point [fgllic


© April 2004 Lytle David Smith

Install SCO OpenServer under VMware Workstation


4/7/04

I have been a SCO reseller since 1988, and I still have several clients running SCO OpenServer. I don't have a computer dedicated to running OpenServer, but it can frequently be very convenient to have access to an OpenServer system for testing. And it is not always acceptable to remotely access a client's system, because the desired testing may require rebooting or other actions that would prove disruptive to users of the system.

I have been using VMware Workstation version 4 for running Windows 98 and various distributions of Linux, so it was natural to want to do the same with OpenServer. However, I soon realized that VMware does not support OpenServer. The reason apparently has to do with how OpenServer interfaces with the hardware.

I did manage to find a brief outline of a procedure for installing OpenServer under VMware. As I am writing this, it is still available at https://www.chinaunix.net/bbsjh/4/11249.html (if you can read Chinese).

After several failed attempts, I managed to get OpenServer installed and running quite successfully under VMware. I have been using it for some time. It is very stable, and has proven very useful to me.

I wanted to fully document the procedure for installing OpenServer under VMware, for myself and for the public at large, so I went through the entire procedure and documented every step along the way. Here is the product of that process.

  • Start VMware.
  • Create a new virtual machine by selecting "File / New / New Virtual Machine...".
  • Skip through intro to "New Virtual Machine Wizard" by clicking "Next".
  • Specify a "Virtual machine configuration" of "Custom", and click "Next".
  • Specify a "Guest operation system" of "Other", and click "Next".
  • Specify a "Virtual machine name" that suits your taste, accept the default "Location", and click "Next".
  • Specify a "Memory: Guest size (MB)" of at least "48", and click "Next".
    (I tried 32MB and the installation failed with the error "".)
  • Specify a "Network connection" that suits your requirements, and click "Next".
    (I prefer "Bridged networking", which makes your virtual machine appear as if it is just another system on your existing network.)
  • Specify to "Create a new virtual disk", and click "Next".
  • Specify a "Disk size (GB)" of at least "1", specify "Allocate all disk space now" and "Split disk into 2 GB files" as appropriate for your requirements, and click "Next".
  • Specify a unique "Disk file" name, click "Advanced >>", specify a "Virtual device node" of "SCSI 0:0", and click "Finish".
  • Click "Edit virtual machine settings".
  • Click the "Audio" device, and click "Remove".
  • Click the "CD-ROM 1 (IDE 1:0)" device, specify a "Connection" that points to the CD-ROM drive from which you will be installing, and specify a "Virtual device node" of "IDE 0:1".
  • Start adding a device by clicking "Add...".
  • Skip through intro to "Add Hardware Wizard" by clicking "Next".
  • Specify a "Hardware type" of "Hard Disk", and click "Next".
  • Specify to "Create a new virtual disk", and click "Next".
  • Specify a "Disk size (GB)" of only "0.1", leave "Allocate all disk space now" and "Split disk into 2 GB files" unchecked, and click "Next".
  • Specify a unique "Disk file" name, click "Advanced >>", specify a "Virtual device node" of "IDE 0:0", and click "Finish".


Note regarding driver for BusLogic MultiMaster BT-958 SCSI host adapter:
VMware virtual machines emulate the BusLogic MultiMaster BT-958 SCSI host adapter. OpenServer includes drivers for this host adapter, but for some reason installing OpenServer under VMware without using the BusLogic MultiMaster BT-958 BTLD (which is becoming increasingly difficult to find on the Internet) will eventually result in a "" error.

  • Download the BusLogic MultiMaster BT-958 BTLD diskette creator.
  • Start a command-line session by clicking "Start / Run...", typing "cmd", and pressing [Enter].
  • Make the drive where "mmunix.exe" resides the current drive by typing "" (where {drive} is the drive letter for the drive where mmunix.exe resides) and pressing [Enter].
  • Make the directory where "mmunix.exe" resides the current directory by typing "" (where {path} is the path where mmunix.exe resides) and pressing [Enter].
  • Extract the "BusLogic Multimaster BT-958 BTLD" diskette creator by typing and pressing [Enter].
  • Create the "BusLogic Multimaster BT-958 BTLD" diskette by typing "", pressing [Enter], and confirming that you do wish to continue.
  • Close the command-line session by typing "" and pressing [Enter].
  • Insert the "SCO OpenServer CD-ROM" into the CD-ROM drive, and insert the "BusLogic Multimaster BT-958 BTLD" diskette into the diskette drive.
  • Return to VMware and start the new virtual machine by selecting "Power / Power On" (or by pressing [Ctrl-B]).
  • Enter the virtual machine's BIOS setup utility by quickly clicking inside the virtual machine window and pressing [F2].
  • Select the "" settings page by pressing [Right] three times.
  • Use [Up], [Down], [+] and [-] to rearrange the boot order so that "" is first and "" is second.
  • Use [Up] or [Down] to select the "" and press [Enter] to expand the selection.
  • Use [Up] or [Down] to select the "", then use [-] to rearrange the boot order so that it is last in the boot order.
  • Save the BIOS settings and exit the BIOS setup utility by pressing [F10] and confirming that you wish to "".


Note regarding floppy drives and VMware:
For some unknown reason, VMware seems to have frequent problems connecting to the diskette drive when booting a virtual machine. If you receive a warning stating that VMware could not connect to the floppy drive, click "OK" to dispense with the warning(s). Then, click the "Reset" toolbar icon (or press [Ctrl-R]) to recycle power to the virtual machine. After a few tries, you should eventually be able to start the virtual machine with the floppy drive connected.

  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, press [Enter] (and then be patient).
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, press [Enter].
  • At the "" prompt, press [Enter].
  • At the "" prompt, press [Enter] to "" and press [Enter] again to "".
  • At the "" prompt, specify "".
  • At the "" prompt, specify "".
  • At the "" prompt, specify "".
  • Press [Enter] until you confirm the "" prompt.
  • At the "" prompt, press [Enter].
  • At the "" prompt, specify "" (or whatever is appropriate for your circumstances), and press [Enter] until you confirm the "" prompt.
  • At the "" prompt, enter a valid license number and press [Enter].
  • At the "" prompt, enter a valid license code and press [Enter].
  • Press [Enter] until you confirm the "" prompt.
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • On the "" screen, complete the choices as appropriate and press [Enter] until you confirm the "" prompt.
  • On the "" screen, complete the choices as appropriate and press [Enter] until you confirm the "" prompt.
  • On the "" screen, specify a "" of "".
  • At the "" prompt, specify whatever optional software is appropriate for your circumstances and press [Enter] until you confirm the "" prompt.
  • On the "" screen, specify a "" of "", which should result in "" being detected.
  • Still on the "" screen, "" should already specify "".
  • Still on the "" screen, specify whatever remaining settings are appropriate for your circumstances and press [Enter] until you confirm the "" prompt.
  • On the "" screen, specify and confirm your root password and press [Enter] until you confirm the "" prompt.
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "".
    (I know this is the wrong floppy device, but there is a method to the madness, so stick with me here. We already loaded the blc driver when we booted, so the installation can complete without reloading it. After the installation, at boot-time, we will load the driver once again, and then manually install the blc driver to the root filesystem using btldinstall.)
  • At the "" prompt, press [Enter].
  • At the "" prompt, choose "".
  • At this point, the installation will continue unattended. (Be patient.)
  • At the "" prompt, press [Enter].
  • At the "" prompt, press [Enter].
  • At the "" prompt, press any key.
  • Leave the "SCO OpenServer CD-ROM" and the "BusLogic MultiMaster BT-958 BTLD" diskette in place.
  • See note above about floppy drives and VMware, and ensure that the diskette drive is connected.
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, press [Enter] (and then be patient).
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, enter your chosen root password and press [Enter].
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, type "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, choose "" and press [Enter].
  • At the "" prompt, type "" and press [Enter].


Note regarding running the SCO GUI under VMware:
The SCO GUI does not appear to work well (if at all) with VMware. This is probably largely because, since VMware does not support OpenServer, (unlike Linux and Windows) there is no accelerated video driver provide for it. If you require the GUI, then consider using VNC to access the GUI remotely from your host operating system. I have complete instructions and installation scripts for use installing TightVNC onto OpenServer at David.ComputerLandInc.com (link dead, sorry)




Got something to add? Send me email.


56 comments


Inexpensive and informative Apple related e-books:

El Capitan: A Take Control Crash Course

Take Control of iCloud, Fifth Edition

Digital Sharing Crash Course

Take Control of the Mac Command Line with Terminal, Second Edition

Take Control of Upgrading to El Capitan




More Articles by Lytle David Smith © 2015-03-05 Lytle David Smith



Update-Tools

will update only the tools on customers whose name starts with SRV.

See the cmdlet Get - VM for more details.

You can also set it update tools should immediately reboot if necessary.

What you can do with the NoReboot parameter on the cmdlet Update-Tools .

Get-VM-name Srv *

Genero BDL errors

-201

This general SQL error message indicates mistakes in the syntax 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.

-204

A numeric constant that is punctuated like a floating-point number (with a decimal point and/or an exponent starting with e) is unacceptable. Possibly the exponent is larger than can be processed.

-206

The database server cannot find a table or view specified in the statement. The table or view might have been renamed or dropped from the database.

-213

The database server received an interrupt signal from the user. The statement ended early. A program should roll back the current transaction and terminate gracefully.

-217

The column specified does not exist in the database tables used in this SQL statement.

-235

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.

-236

Each column that is named or implied in an INSERT statement must have a separate value expression. If the statement does not list specific columns, review the definition of the table for the number of columns and their data types. Also check that the list of expressions in the VALUES clause has no extra or missing comma that might result in an incorrect number of values. Be especially careful of long character strings and expressions with parentheses.

-239

The row that is being inserted (or being updated to have a new primary key) contains a duplicate value of some row that already exists, in a column or columns that are constrained to have unique values.

-244

The database server cannot read the data block for this SQL client program. The database server returns this error when a record is locked by another process, and the lock timeout defined by the current program has expired.

Consider using the instruction to define a lock timeout. By default, with most databases, this timeout is zero and error -244 is returned immediately when a lock conflict occurs. If all programs do short transactions (holding locks for a short period of time), it is usually safe to define a lock timeout of 5 to 10 seconds to avoid this SQL error.

-250

The database server cannot get a row of a table prior to update.

-251

The ORDER BY or GROUP BY clause uses column-sequence numbers, and at least one of them is larger than the count of columns in the select list.

-253

The database server cannot get a row of a table prior to update.

-254

The number of host variables that you named in the INTO clause of this statement does not match the number of columns that you referenced in the SQL statement.

-255

The database server cannot execute this COMMIT WORK or ROLLBACK WORK statement because no BEGIN WORK was executed to start a transaction. Because no transaction was started, you cannot end one.

-256

The database server does not support transactions.

-257

The database server can handle only a fixed number of prepared SQL statements for each user. This limit includes statements that were prepared with the PREPARE statement and cursors that were declared with the DECLARE statement.

-259

The current statement refers to a cursor that has not been opened. Review the logic of the program to see how it failed to execute the OPEN statement before it reached this point.

-263

This statement, probably a FETCH statement that names a cursor declared FOR UPDATE, failed because the row it should have fetched could not be locked.

-266

The current statement uses the WHERE CURRENT OF cursor-name clause, but that cursor has not yet been associated with a current row. Either no FETCH statement has been executed since it was opened, or the most recent fetch resulted in an error so that no row was returned. Revise the logic of the program so that it always successfully fetches a row before it executes this statement.

-268

The current statement uses the WHERE CURRENT OF cursor-name clause, but that cursor has not yet been associated with a current row. Either no FETCH statement has been executed since it was opened, or the most recent fetch resulted in an error so that no row was returned. Revise the logic of the program so that it always successfully fetches a row before it executes this statement.

-272

The person who created this table has not granted SELECT privilege to your account name or to the public for the table or the column. The owner of the table or the DBA must grant this privilege before you can select data from the table or column.

-273

The person who created this table has not granted UPDATE privilege to your account name or to the public for the table or the column. The owner of the table or the DBA must grant this privilege before you can update a row in this table or update the column.

-274

The person who created this table has not granted DELETE privilege to your account name or to the public. The owner of the table or the DBA must grant this privilege before you can delete a row in this table.

-275

The Insert access privilege on this table or column is not currently held by your account name, nor by the PUBLIC group, nor by your current role. The owner of the table or the DBA must grant the Insert privilege before you can insert a row into this table.

-280

A character literal in this statement exceeds the maximum length. Check the punctuation and length of all quoted strings in the statement. Possibly two missing quotes make a long string out of two short ones. You must revise the statement to use a shorter character string.

-282

Inspect the current statement, examining the punctuation of all quoted strings.

-284

A subquery that is used in an expression in the place of a literal value must return only a single row and a single column. In this statement, a subquery has returned more than one row, and the database server cannot choose which returned value to use in the expression. You can ensure that a subquery will always return a single row. Use a WHERE clause that tests for equality on a column that has a unique index. Or select only an aggregate function. Review the subqueries, and check that they can return only a single row.

This error can also occur when you use a singleton SELECT statement to retrieve multiple rows. You must use the DECLARE/OPEN/FETCH series of statements or the EXECUTE INTO statement to retrieve multiple rows.

-285

The cursor that this statement uses has not been properly declared or prepared, or the FREE statement has released it, or an automatic re-prepare has been attempted while opening the cursor but that operation failed, leaving the cursor unavailable. Review the program logic to ensure that the cursor has been declared. If it has, and if the DECLARE statement refers to a statement identifier, check that the referenced statement has been prepared.

-290

This statement attempts to update with a cursor that was not declared for update. To use a cursor with the UPDATE or DELETE statements, you must declare it FOR UPDATE. Review the program logic to make sure that this statement uses the intended cursor.

-294

In a grouping SELECT, you must list every nonaggregate column in the GROUP BY clause to ensure that a well-defined value exists for each selected column in each grouped row. A column contains either a single aggregate value or a value unique to that group. If a selected column were neither an aggregate nor in the list, two or more values for that column might possibly exist in some group, and the database server could not choose which value to display. Revise the query to include either the column name or its positional number in the clause.

-307

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.

-309

An expression or column name is in the ORDER BY clause of this SELECT statement, but the expression or column name is not in the select list (the list of values that follows the word SELECT). This action is not supported when a UNIQUE or DISTINCT operator is being used in a query.

-316

This statement tries to create an index with the name shown, but an index of that name already exists. Only one index of a given name can exist in a single database.

-324

The column name appears in more than one of the tables that are listed in the FROM clause of this query. The database server needs to know which columns to use. Revise the statement so that this name is prefixed by the name of its table (table-name.column) wherever it appears in the query.

-329

The database you tried to connect to is not known by the db server.

Check database client configuration settings and make sure that there is no spelling error in the name of the database

-330

Possibly you tried to create a database with the same name as one that already exists or rename a database to a name that already exists; if so, choose a different name.

-349

The SQL statement cannot be executed because no current database exists. You must issue a DATABASE or CONNECT TO instruction before executing other SQL statements.

-350

This CREATE INDEX statement cannot be executed because an index on the same column or combination of columns already exists. For a given collation order, at most two indexes can exist on any combination of columns, one ascending and one descending.

-354

This statement contains the name of a database or a cursor in some invalid format. If the statement is part of a program, the name might have been passed in a host variable.

-360

The UPDATE, INSERT, or DELETE statement uses data taken from the same table in a subquery. Because of the danger of entering an endless loop, this action is not allowed, except in the case of an uncorrelated subquery in the WHERE clause of the DELETE or UPDATE statement.

-363

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.

-366

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].

-371

This CREATE UNIQUE INDEX statement cannot be completed because the column (or columns) contains one or more duplicate rows.

-387

You cannot access the database that this statement requests because you have not been granted CONNECT privilege to it. Contact a person who has Database Administrator privilege to that database and ask to be granted CONNECT privileges to it.

-388

If you issued a CREATE TABLE, CREATE INDEX, or CREATE PROCEDURE statement, you cannot execute this statement because your account has not been granted the RESOURCE privilege for this database. You need the RESOURCE privilege to create permanent tables, indexes on permanent tables, and procedures.

-389

This statement cannot be executed because you have not been granted DBA privilege for this database. Contact a person who has DBA privilege for the database and ask to be granted DBA privilege (or simply ask to have this statement executed for you).

-391

This statement tries to put a null value in the noted column. However, that column has been defined as NOT NULL. Roll back the current transaction. If this is a program, review the definition of the table, and change the program logic to not use null values for columns that cannot accept them.

-400

This FETCH statement names a cursor that has never been opened or has been closed. Review the program logic, and check that it will open the cursor before this point and not accidentally close it. Unless a cursor is declared WITH HOLD, it is automatically closed by a COMMIT WORK or ROLLBACK WORK statement.

-404

You used a statement that names a cursor that is was destroyed. Review the program logic and check that the cursor specified is declared and opened, but not freed, prior to reaching this statement.

-410

This EXECUTE statement refers to a statement id that has not been prepared. Either no PREPARE statement was done, or one was done but returned an error code. Review the program logic to ensure that a statement is prepared and the PREPARE return code is checked. A negative error code from PREPARE usually reflects an error in the statement being prepared.

-412

This statement (probably an EXECUTE or DECLARE) refers to a dynamic SQL statement that has never been prepared or that has been freed. Review the program logic to ensure that the statement has been prepared, the PREPARE did not return an error code, and the FREE statement has not been used to release the statement before this point.

-413

This INSERT statement names a cursor that has never been opened or that has been closed. Review the program logic, and check that it will open the cursor before this point and not accidentally close it. An insert cursor is automatically closed by a COMMIT WORK or ROLLBACK WORK statement.

-422

This FLUSH statement names a cursor that has never been opened or has been closed. Review the program logic to ensure that it will open the cursor before this point and not accidentally close it. An insert cursor is automatically closed by a COMMIT WORK or ROLLBACK WORK.

-450

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.

-458

The database server ran out of log space in which to record this transaction. A transaction that is not fully recorded cannot be rolled back. To preserve database integrity, the operating system ended the transaction and rolled it back automatically. All changes made since the start of the transaction have been removed. Terminate the application, and replan it so that it modifies fewer rows per transaction. Alternatively, contact the database server administrator to discuss increasing the number or the size of the logical logs. Be prepared to talk about the number of rows being updated or inserted and the size of each row.

-481

The statement has not been prepared, or the format of the statement name is not valid. A valid statement name does not exceed the maximum length, begins with a letter or underscore, does not contain any blanks or nonalphanumeric characters except underscores.

-482

You cannot issue a FETCH PRIOR, FETCH FIRST, FETCH LAST, FETCH CURRENT, FETCH RELATIVE n, or FETCH ABSOLUTE n statement with a non-scroll cursor. To do so, you must first declare the cursor as a scroll cursor.

-507

The cursor that is named in the WHERE CURRENT OF clause in this UPDATE or DELETE statement does not exist. Review the spelling of the name. If it is as you intended, check the DECLARE statement to ensure that it has been executed. Also make sure that the cursor has not been freed with the FREE statement or during a failed automatic re-prepare attempt.

-513

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

Review the code, the SQL instruction cannot be used.

-517

All database servers have limits on the number of columns that can be included in an index and on the total number of bytes in a key (the sum of the widths of the columns). This CREATE INDEX statement would exceed that limit for this database server.

-522

The table name used in an expression (for example, in the WHERE clause) has not been listed in the clause definining the tables to be used in the query (typically the FROM clause in SELECT statements).

-526

For a DECLARE statement, the clause FOR UPDATE is not allowed in conjunction with the SCROLL keyword.

-530

The check constraint placed on the table column was violated.

-535

This BEGIN WORK statement is redundant; a transaction is already in progress. If this is a program, review its logic to make sure it has not accidentally failed to end the previous transaction.

-551

The total number of columns listed in a UNIQUE, PRIMARY KEY, or FOREIGN KEY clause is limited. The limit depends on the database server in use.

-674

You called a routine that does not exist in the database, you do not have permission to execute the routine, or you called the routine with too few or too many arguments.

-681

The error occurs if the user specifies a column name more than once in the INSERT column list.

-691

A referential constraint has been violated. This condition usually occurs when you are trying to insert a value into or update the value of a column that is part of a referential constraint. The value you are trying to enter does not exist in the referenced (parent-key) column.

-743

You are trying to define an object that already exists in the database.

-768

If this internal error recurs, note all circumstances and contact your technical support.

-805

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.

-806

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.

-809

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

Review it for punctuation and use of keywords.

-846

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.

-930

The application is trying to access the database server but failed.

-942

This error can occur at transaction-commit time if the database server could not commit the transaction.

-1102

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.

-1107

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.

-1108

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.

-1109

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.

-1110

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.

-1112

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.

-1114

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.

-1119

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.

-1129

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.

-1133

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.

-1140

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.

-1141

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.

-1143

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.

-1146

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.

-1150

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.

-1168

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.

-1170

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.

-1202

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.

-1204

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.

-1205

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.

-1206

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.

-1210

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.

-1212

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.

-1213

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.

-1214

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.

-1215

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.

-1218

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.

-1222

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.

-1223

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.

-1226

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.

-1260

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.

-1261

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.

-1262

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.

-1263

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.

-1264

Only spaces can follow a DATETIME or INTERVAL literal.

Inspect this statement for missing or incorrect punctuation.

-1265

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).

-1266

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

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

-1267

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.

-1268

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.

-1279

You attempted to insert into a CHAR, NCHAR, VARCHAR, NVARCHAR or LVARCHAR column using a string host variable, but the string is too long.

-1284

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.

-1301

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.

-1302

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.

-1303

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.

-1304

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.

-1305

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.

-1306

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.

-1307

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.

-1308 You try to delete a row in an empty row. Nothing was deleted.-1309

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.

-1312

An error occurred in the form at runtime.

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

-1313

The current SQL statement returned this error code number.

-1314

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.

-1318

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.

-1320

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

Check your source code and recompile.

-1321

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.

-1322

The file that the REPORT TO statement specifies cannot be opened. See the description for more details.

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.

-1323

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.

-1324

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.

-1326

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.

-1327

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.

-1328

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.

-1329

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.

-1330

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.

-1331

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.

-1332

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.

-1335

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.

-1337

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.

-1338

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.

-1340

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

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

-1349

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. It contains some characters other than white space, digits, a sign, a decimal, or the letter e, or else the parts are in the wrong order so that the number cannot be deciphered.

-1353

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

-1355

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.

-1359

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.

-1360

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)

-1373

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.

-1374

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.

-1375

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.

-1376

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.

-1377

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.

-1378

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

-1396

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.

-2017

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.

-2024

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.

-2028

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.

-2029

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.

-2039

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.

-2041

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.

-2045

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.

-2100

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.

-2810

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.

-2820

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.

-2830

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.

-2840

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.

-2843

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.

-2846

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.

-2859

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.

-2860

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.

-2862

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.

-2863

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.

-2864

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.

-2865

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.

-2892

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.

-2893

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.

-2975

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.

-2992

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.

-2997

The database server returned an error that is shown.

Look up the shown error in the database server documentation.

-4303

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

Check the name used after the FREE keyword.

-4307

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.

-4308

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.

-4309

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.

-4319

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.

-4320

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.

-4322

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.

-4323

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.

-4324

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.

-4325

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.

-4328

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

Individual members of the complex variable must be returned separately.

-4333

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.

-4334

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)

-4335

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 .

-4336

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.

-4338

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.

-4340

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.

-4341

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.

-4343

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.

-4347

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.

-4353

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.

-4356

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.

-4357

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.

-4358

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.

-4359

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.

-4360

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.

-4361

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.

-4363

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.

-4369

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.

-4371

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.

-4372

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.

-4374

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.

-4375

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.

-4379

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.

-4380

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.

-4382

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.

-4383

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.

-4402

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.

-4403

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.

-4410

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.

-4414

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.

-4415

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.

-4416

The validation string in the syscolval table is not correct.

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

-4417

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.

-4418

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.)

-4420

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.

-4425

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.

-4440

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.

-4447

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-?).

-4448

The file cannot be opened.

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

-4452

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

Change the function or report name.

-4457

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

Remove keys from the list.

-4458

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

Use a dimension below the 65535 limit.

-4463

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.

-4464

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.

-4476

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.

-4477

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

Use one of the members of the array.

-4485

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.

-4488

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.

-4489

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.

-4490

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

Review your code to eliminate multiple BEFORE FIELD clauses.

-4491

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

Review your code to eliminate multiple AFTER FIELD clauses.

-4534

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.

-4631

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.

-4632

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.

-4652

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.

-4653

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.

-4656

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.

-4657

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.

-4668

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.

-4900

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

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

-4901

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.

-6001

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

Increase the maximum number of processes allowed (ulimit)

-6012

See error -6015.

-6013

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

Contact your distributor or support center.

-6014

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

Contact your distributor or support center.

-6015

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.

-6016

The application is unable to check the license validity.

See error -6015.

-6017

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

Contact your distributor or support center.

-6018

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.

  • Do not remove or modify files contained in the directory $FGLDIR/lock

  • Change the permissions of the $FGLDIR/lock directory, or connect to the server with a user name having the correct permissions.

-6019

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.

-6020

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.

-6022

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

Restart the program.

-6025

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.

-6026

The runner is corrupted.

-6027

- 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

Operating system not found on VMWare Workstation Player 16 #1335

Hardware Environment
Running an Intel NUC with Ubuntu 18.04 LTS with VMWare Workstation 16 Player

Home Assistant OS release:
Downloaded hassos_ova-5.13.vmdk direct from home assistant site

I followed the install instructions (as closely as I could, since they seem to be for Workstation 15, not 16) from the Home Assistant site: https://www.home-assistant.io/installation/linux - I always get an error as soon as it tries to boot "Operating system not found"

There is no place in the VMWare Workstation 16 settings for the VM to change the firmware type to UEFI, and as far as selecting the image, I had to do that after creating the VM (not during the setup process). When selecting the vmdk, it asks "Convert existing virtual disk to newer format?" and states that if I do so, it won't work with older VMs. I've tried converting as well as keeping the existing format, as well as setting the virtual HD to be SCSI, SATA and IDE.

None of these things result in a different outcome - in all cases, it always says "Operating system not found" on boot.

Any thoughts? I've tried to find the bundle for VMWare Workstation 15 Player but had no luck either. I've got HA Core installed on my Ubuntu machine, and really want to get the OS installed in a VM (so that I can get Supervisor).

Update-Tools

will update only the tools on customers whose name starts with SRV.

See the cmdlet Get - VM for more details.

You can also set it update tools should immediately reboot if necessary.

What you can do with the NoReboot parameter on the cmdlet Update-Tools .

Get-VM-name Srv *

Why do I see "IPC flight limit exceeded" in my log files? (1335)

Answer:

IPC flight limit exceeded is a general message indicating problem with in-flight slices exceeding the limit, and it is hard to explain why the error occurs. When an image is encoded by PCoIP it is broken down into slices for transmission. There is a limit to how many slices can be transmitted and not acknowleged by the client at any one time. Many past cases have been related to the following:

  • Upstream packet loss
  • Older firmware drivers
  • Older soft client
  • Older APEX drivers
  • Operating system stalls in the client
  • Operating system stalls in the virtual machine due to the hypervisor, storage system, etc.

Some suggestions to help troubleshoot this condition are:

  • Download Teradici's Network Checklist to help identify if network issues are part of the issue.

Network checklist for PCoIP protocol LAN and WAN deployments (1033)

  • Upgrade to latest firmware on PCoIP Zero Clients.

PCoIP Zero Clients

Upgrade to latest VMware Horizon View client.

www.vmware.com

Upgrade APEX driver to latest supported version.

Teradici PCoIP Hardware Accelerator (APEX 2800)

 

For further troubleshooting, can you provide the following?

1) pcoip server logs under c:\programdata\vmware\vdm\logs on the VMs experiencing the issue.

2) vmkernel.log and vmkernel.x.gz files under /scratch/log

If you have to upgrade the APEX driver on your VM, please remove Tera2800 device from Device Manager, then install the latest APEX driver.

flm].server and specify the name of the computer that runs the License Manager.

-6029

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

Check your command-line parameters and retry the command.

-6031

Your temporary runtime license has expired.

Call your software vendor to get a new license.

-6032

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

Check your command line syntax and try again.

-6033

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

Check your command line and try again.

-6034

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

This is only a warning message.

-6035

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

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

-6041

An error occurred while retrieving network interface information.

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

-6042

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.

-6043

The test time license of has expired.

Call your software vendor to purchase a new license.

-6044

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.

-6045

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.

-6046

The license could not get information about the error 1335 vmware workstation file.

Reinstall the license. Contact your distributor.

-6047

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

Reinstall the license, error 1335 vmware workstation. Contact your distributor.

-6048

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

Reinstall the license. Contact your distributor.

-6049

You have a runtime license installed with this package, error 1335 vmware workstation. You cannot compile BDL source code modules with this license.

If you error 1335 vmware workstation to compile .4gl source code, you must purchase and install error 1335 vmware workstation development license. Contact your distributor.

-6050

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.

-6051

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

Install a new license to activate the product, error 1335 vmware workstation. Contact your distributor.

-6052

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.

-6053

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.

-6054

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

  • License controller: Check that the FGLDIR environment variable is correctly set and that the file $FGLDIR/etc/f4gl.sn is readable by the current user.

  • License manager: Check error 1335 vmware workstation the file $FLMDIR/etc/license/lic?????.dat is readable by the current user.

-6055

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

  • License controller: Check that the FGLDIR environment variable is correctly set and that the file $FGLDIR/etc/f4gl.sn is writable by the current user.

  • License manager: Check that the file $FLMDIR/etc/license/lic?????.dat is writable by the current user.

-6056

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

  • License controller: Check that the FGLDIR environment variable is correctly set and that the file $FGLDIR/etc/f4gl.sn is writable by the current user.

  • License manager: Check that the file $FLMDIR/etc/license/lic?????.dat is writable by the current user.

-6057

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.

-6058

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.

-6059

The file that contains the license has been corrupted.

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

-6061

The license shown is not installed.

Reinstall the license.

-6062

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

Contact your distributor.

-6063

The license shown is already installed.

No particular action to be taken.

-6064

In order to use a license manager, the FGLPROFILE entry described in the error message must exist and define a license number.

-6065