IBM CD Showcase/OS2_CD_ROM.iso/smce0001/builder/tutor/ublib/uttleng.hlp

OS/2 Help File | 1993-11-01 | 202.3 KB | 8,868 lines

ΓòÉΓòÉΓòÉ 1. Unknown character found. ΓòÉΓòÉΓòÉ

ERROR: An unrecognized character was found outside of a quoted string.

CAUSE: Possible causes are:

o Quotes have been misplaced.

o The character string includes special characters that must be inside single
  or double quotes.

ACTION: Correct the instruction and run it again.


ΓòÉΓòÉΓòÉ 2. Symbol is not an acceptable name or numeric value. ΓòÉΓòÉΓòÉ

ERROR: You are using an unacceptable character in a name or number. The program
expected a name that begins with an alphabetic character (A-Z, a-z),
underscore, !, # or @. The name can include alphabetic characters, underscore,
!, and the digits 0-9 after the first character. For example, Fred_3 is an
acceptable name.

A number can begin with a digit or a decimal point and may contain digits and a
decimal point.

CAUSE: Possible causes are:

o A typographical error in a name or number.

o Quotes are missing from a name or number in a character string.

o The name or numeric value includes special characters that should be inside
  single or double quotes.

ACTION: Correct the name or number in your instruction and run it again.


ΓòÉΓòÉΓòÉ 3. Token table full ΓòÉΓòÉΓòÉ

ERROR: The number of tokens in your story exceeds the capacity of the table.

CAUSE: Your story contains more instructions and symbols than the tokenizer can
handle.

ACTION: Split the story into smaller stories in order to reduce the size of the
token table


ΓòÉΓòÉΓòÉ 4. End comment delimiter outside of comment. ΓòÉΓòÉΓòÉ

ERROR: You have an end comment delimiter (*/) outside of a comment.

CAUSE: Each comment must be a matched pair of comment delimiters. For example:

    /* this is a comment example */
Possible causes are:

o You left out the begin comment delimiter (/*).

o You accidentally made two end comment delimiters (*/).

ACTION: Check the comment delimiters in your instruction and rerun.


ΓòÉΓòÉΓòÉ 5. Missing ending quote. ΓòÉΓòÉΓòÉ

ERROR: You entered a quoted string without ending it properly.

CAUSE: A string must begin and end with the same type of quote.

Possible causes are:

o The end quote is missing or is on the next line.

  A quoted string cannot extend beyond the end of a line.

o The quote characters at the beginning and end of the string are not the same
  type.

  A quoted string must begin and end with a single or double quote. For
  example:

       "this is OK"
       'this is also OK'

o A quote within the string is the same type as your beginning and ending
  quote.

  In this situation specify the embedded quote twice. For example:

       'An embedded quote is in this string''s syntax'

ACTION: Correct the quoted string and rerun the instruction


ΓòÉΓòÉΓòÉ 6. Name expected. ΓòÉΓòÉΓòÉ

ERROR: You provided no name, or an unacceptable name.

CAUSE: The program expected a name that begins with an alphabetic character
(A-Z, a-z), underscore, !, # or @. The name can include alphabetic characters,
underscore, !, and the digits 0-9 after the first character. For example,
Fred_3 is an acceptable name.

Possible causes:

o Your instruction is missing a name
o The name specified was not accepted

ACTION: Correct the name in the instruction and rerun it.


ΓòÉΓòÉΓòÉ 7. An expression is required. ΓòÉΓòÉΓòÉ

ERROR: Your instruction is missing an expression.

CAUSE: The instruction being processed requires an expression, which consists
of terms (strings, symbols or function calls) interspersed with operators and
parentheses.

ACTION: Add the missing expression your instruction and rerun it.


ΓòÉΓòÉΓòÉ 8. Right parenthesis expected. ΓòÉΓòÉΓòÉ

ERROR: Your expression or function call is missing a right parenthesis.

CAUSE: The program looks for a right parenthesis to match the left parenthesis
in a nested expression or function call.

ACTION: Correct your expression or function call and rerun it.


ΓòÉΓòÉΓòÉ 9. A term is expected for the expression. ΓòÉΓòÉΓòÉ

ERROR: You provided an expression without a term

CAUSE: The program found an incomplete expression. An expression consists of
terms interspersed with operators and parentheses. A term is

o a literal string, such as "This is a string"

o a symbol, such as the name of a variable

o a function call, such as LENGTH("how long is a string?")
Possible cause:

o You ended an expression with a + or *

ACTION: Add the missing term to your expression and rerun it.


ΓòÉΓòÉΓòÉ 10. Keyword found in an expression. ΓòÉΓòÉΓòÉ

ERROR: You used a reserved keyword in an expression.

CAUSE: Possible causes are:

o Your expression contains a word reserved by the AVA/2 language.

o A part of your expression is missing

o Your expression is unfinished

ACTION: Correct your expression and rerun it.


ΓòÉΓòÉΓòÉ 11. Incorrect pattern in PARSE template. ΓòÉΓòÉΓòÉ

ERROR: You specified a pattern for the PARSE instruction template that was not
accepted.

CAUSE: The template does not follow the PARSE rules. A PARSE template must
indicate one of the acceptable methods of splitting strings into words or
variables.

ACTION: Correct your parse template.  Refer to the AVA/2 Language Reference for
an explanation of parse templates.


ΓòÉΓòÉΓòÉ 12. The keyword WITH is expected. ΓòÉΓòÉΓòÉ

ERROR: You used a PARSE instruction with a VALUE expression, but it was not
followed by the WITH keyword.

CAUSE: The program expects WITH to follow the VALUE expression.

   PARSE VALUE expr WITH template

ACTION: Add the WITH keyword preceding the parse template and rerun the
instruction. Refer to the AVA/2 Language Reference for a description of parse
templates.


ΓòÉΓòÉΓòÉ 13. The keyword VAR or VALUE is missing. ΓòÉΓòÉΓòÉ

ERROR: You used a PARSE instruction without the keyword VAR or VALUE.

CAUSE: The program expects either the VAR or VALUE keyword following PARSE. For
example:

   PARSE VAR name template
   PARSE VALUE expr WITH template

ACTION: Include the VAR or VALUE keyword in the PARSE instruction. Refer to the
AVA/2 Language Reference for a description of the PARSE instruction.


ΓòÉΓòÉΓòÉ 14. Duplicate TO expression. ΓòÉΓòÉΓòÉ

ERROR: You specified a TO expression more than once in the DO statement.

CAUSE: The program only allows one TO expression in a DO instruction.

Possible causes:

o A missing DO instruction
o Accidental repetition of a TO expression

ACTION: Remove the unneeded TO expression or restructure your DO instruction.


ΓòÉΓòÉΓòÉ 15. Duplicate BY expression. ΓòÉΓòÉΓòÉ

ERROR: You specified a BY expression more than once in the DO statement.

CAUSE: The program only allows one BY expression in a DO instruction.

Possible causes:

o A missing DO instruction
o Accidental repetition of a BY expression

ACTION: Remove the unneeded BY expression or restructure your DO instruction.


ΓòÉΓòÉΓòÉ 16. Duplicate FOR expression. ΓòÉΓòÉΓòÉ

ERROR: You specified a FOR expression more than once in the DO statement.

CAUSE: The program only allows one FOR expression in a DO instruction.

Possible causes:

o A missing DO instruction
o Accidental repetition of a FOR expression

ACTION: Remove the unneeded FOR expression or restructure your DO instruction.


ΓòÉΓòÉΓòÉ 17. Incorrect action value for ON. ΓòÉΓòÉΓòÉ

ERROR: You specified an incorrect action in an ON instruction.

CAUSE: The program accepts one of the following actions only:

CALL

EXIT

IGNORE

LEAVE

NOP

QUIT

RETURN

TELL
The format for the ON instruction is:

    ON event action

ACTION: Correct your ON instruction and rerun it.


ΓòÉΓòÉΓòÉ 18. Multi-column instruction not at start of line. ΓòÉΓòÉΓòÉ

ERROR: You are running a multi-column instruction such as PLAY or SHOW that is
not on the start of an instruction line.

CAUSE: All multi-column instructions must start at the beginning of the line
prior to the other columns with values. The following instructions are
multi-column instructions:

o CLEAR

o COLOR

o PASTE

o PLAY

o SHOW

o TEXTIN

o TEXTOUT

ACTION: Begin your multi-column instruction in the first column (labeled "AVA/2
Statement").


ΓòÉΓòÉΓòÉ 19. No line or blank line following continuation. ΓòÉΓòÉΓòÉ

ERROR: You ended a line with a comma without including a continuation line. The
continuation line did not exist or was blank.

CAUSE: The program looks for a continuation line when the line ends with a
comma.

Possible causes are:

o You accidentally ended the instruction with a comma.

o The continuation line is missing or is a comment.

  A line ending with a comma requires an acceptable continuation line. Comments
  that follow a line ending with a comma are ignored.

o A blank line follows the line that ends with a comma.

ACTION: Remove the comma at the end of the line or provide an acceptable
continuation line.


ΓòÉΓòÉΓòÉ 20. The label is not a name. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable value as a label.

CAUSE: Certain characters are not acceptable in a label name. A label consists
of a name followed by a colon. A name must begin with an alphabetic character
(A-Z, a-z), underscore, !, # or @. After the first character, the name can also
contain alphabetic characters, underscore, !, and the digits 0-9.

ACTION: Correct your label and rerun the story.


ΓòÉΓòÉΓòÉ 21. Incorrect font or dissolve value. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable font size or dissolve type.

CAUSE: The font size and dissolve type must be an integer from 1 to 99.

ACTION: Change the font size or dissolve type to a value from 1 to 99.


ΓòÉΓòÉΓòÉ 22. Unacceptable condition specified for an ON instruction. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable condition in an ON instruction.

CAUSE: The program did not find one of these conditions in the ON instruction:

An integer keycode value

KEY

A trigger field name

TRIGGER

A timer name (TIMER1 through TIMER10)

TIMER

ACTION: Correct the ON instruction using one of the values above and rerun it.


ΓòÉΓòÉΓòÉ 23. End of instruction expected. ΓòÉΓòÉΓòÉ

ERROR: Your instruction has no ending.

CAUSE: The program expects an end-of-line or semicolon.

Possible cause:

o Extraneous symbols at the end of the instruction
o The instruction is missing a semicolon at the end

ACTION: Remove the extra symbols or insert a semicolon to mark the end of the
instruction.


ΓòÉΓòÉΓòÉ 24. Start of instruction expected. ΓòÉΓòÉΓòÉ

ERROR: You did not provide an instruction where one was expected.

CAUSE: The program could not find a proper instruction on the indicated line.

Possible causes:

o The instruction line was left blank
o The instruction is incomplete

ACTION: Correct the indicated instruction line and rerun it.


ΓòÉΓòÉΓòÉ 25. Name or end of instruction expected. ΓòÉΓòÉΓòÉ

ERROR: Your instruction is missing an acceptable name or is missing an
end-of-instruction marker.

CAUSE: Possible causes are:

o You typed an unacceptable name in the instruction

  A name must begin with an alphabetic character (A-Z, a-z), underscore, !, #
  or @. After the first character, the name can also contain alphabetic
  characters, underscore, !, and the digits 0-9. For example, Fred_3 is an
  acceptable name.

o There are extra symbols at the end of the instruction

o The instruction is missing the end-of-line indicator or a semicolon

ACTION: Correct the name, remove the extra symbols, or put a semicolon at the
end of the instruction.


ΓòÉΓòÉΓòÉ 26. Operator, term or end of instruction expected. ΓòÉΓòÉΓòÉ

ERROR: Your instruction is missing an operator, term for an expression, or an
end-of-instruction indication.

CAUSE: Possible causes are:

o An instruction is missing an expected operator or term.

o Extra symbols at the end of the instruction

o The instruction is missing the end-of-line indicator or a semicolon

ACTION: Add the operator or term, remove the extra symbols or put a semicolon
to mark the end of the instruction.


ΓòÉΓòÉΓòÉ 27. The keyword THEN is expected. ΓòÉΓòÉΓòÉ

ERROR: Your instruction is missing a THEN keyword

CAUSE: The IF instruction and WHEN clause must have a THEN keyword following an
expression.

The correct format for an IF instruction is:

   IF expression THEN instruction
The correct format for a WHEN clause (within a SELECT instruction) is:

   SELECT
      WHEN expression1 THEN instruction1
      WHEN expression2 THEN instruction2
      OTHERWISE instruction
   END

ACTION: Add the keyword THEN at the appropriate place.


ΓòÉΓòÉΓòÉ 28. ENABLE, DISABLE, IGNORE expected. ΓòÉΓòÉΓòÉ

ERROR: You issued a LINK instruction that is missing a required keyword:
ENABLE, DISABLE, or IGNORE.

CAUSE: The keyword LINK is not followed by an acceptable keyword: ENABLE,
DISABLE or IGNORE.

ACTION: Change the keyword after LINK to ENABLE, DISABLE or IGNORE.


ΓòÉΓòÉΓòÉ 29. Keyword EXPOSE or end of instruction expected. ΓòÉΓòÉΓòÉ

ERROR: Your Procedure is missing the EXPOSE keyword or is not ended properly.

CAUSE: Possible causes:

o The EXPOSE keyword is missing
o There are extraneous symbols at the end of the instruction
o The instruction is missing a semicolon at the end
The PROCEDURE instruction should take one of the following forms:

   PROCEDURE
   PROCEDURE EXPOSE name-list

ACTION: Correct your PROCEDURE instruction and rerun it.


ΓòÉΓòÉΓòÉ 30. End of image/audio argument field expected. ΓòÉΓòÉΓòÉ

ERROR: You entered more than one value in an instruction column.

CAUSE: Each column in a multi-column instruction should contain only one value.
One of the columns contains more than one values. These are multi-column
instructions:

o CLEAR

o COLOR

o PASTE

o PLAY

o SHOW

o TEXTIN

o TEXTOUT

ACTION: Correct any column that contains more than one value.


ΓòÉΓòÉΓòÉ 31. Number not allowed as function name. ΓòÉΓòÉΓòÉ

ERROR: You used a number as part of a function name.

CAUSE: When a symbol is immediately followed by a left parenthesis the program
assumes that it is a function call. The name of the function being called must
be an acceptable name or string that does NOT contain a numeric value.

Possible causes are:

o You misspelled the name

o The statement is missing a space or an operator between the numeric value and
  the left parenthesis

ACTION: Correct the statement and rerun it.


ΓòÉΓòÉΓòÉ 32. Number not allowed on left side of an assignment. ΓòÉΓòÉΓòÉ

ERROR: You have specified a number to the left of an assignment operator. An
assignment must have an acceptable name to the left of the assignment (=)
operator.

CAUSE: An acceptable name must appear on the left side of the an assignment
operator. A name must begin with an alphabetic character (A-Z, a-z),
underscore, !, # or @. After the first character, the name can also contain
alphabetic characters, underscore, !, and the digits 0-9. For example, Fred_3
is an acceptable name.

ACTION: Correct the symbol to the left of the assignment operator and rerun the
instruction.


ΓòÉΓòÉΓòÉ 33. Unacceptable color number. ΓòÉΓòÉΓòÉ

ERROR: You specified an incorrect color number.

CAUSE: The program accepts a color number that is an integer from 0 to 255.

For AVC compatibility, the values Cnn and Ann (where nn is a value from 0 to
255) are also accepted as color numbers.

ACTION: Change the color number to a value from 0 to 255.


ΓòÉΓòÉΓòÉ 34. Unacceptable numeric value for color. ΓòÉΓòÉΓòÉ

ERROR: You specified an incorrect color number.

CAUSE: The program accepts only color numbers that are integers from 0 to 255.

ACTION: Change the color number to a value from 0 to 255.


ΓòÉΓòÉΓòÉ 35. Operator or term expected. ΓòÉΓòÉΓòÉ

ERROR: You typed an expression that is missing an operator or term.

CAUSE: An operator or term is expected within an expression.

Possible causes are:

o You made a typing error in the expression

o A term is missing (a literal string, number, identified or function call)

o An operator is missing (terms may need to be separated by operators such as +
  and *)

o A parenthesis is missing

ACTION: Correct your expression so that it consists of the proper terms,
operators, and parentheses.


ΓòÉΓòÉΓòÉ 36. Unknown method used in PLAY instruction. ΓòÉΓòÉΓòÉ

ERROR: You used an unrecognized Method for the PLAY instruction.

CAUSE: The Method value for a PLAY instruction must either be blank or one of
the following: FADE, FADEIN, or FADEOUT.

ACTION: Correct the value in the Method column of the PLAY instruction.


ΓòÉΓòÉΓòÉ 37. Only a single WHILE or UNTIL clause allowed. ΓòÉΓòÉΓòÉ

ERROR: You specified a DO instruction with more than one WHILE or UNTIL
clause.

CAUSE: The program accepts only one WHILE or UNTIL keyword in a DO instruction.

ACTION: Remove the unneeded WHILE or UNTIL keyword and restructure your DO
instruction.


ΓòÉΓòÉΓòÉ 38. TO, BY, FOR clause out of context. ΓòÉΓòÉΓòÉ

ERROR: You specified a TO, BY or FOR clause in the improper order.

CAUSE: A TO, BY, or FOR clause is out of context in the DO instruction. The
format for a DO instruction is:

   DO name=expression TO exprt BY exprb FOR exprf
The TO, BY and FOR clauses are optional and may appear in any order. If
specified, the TO, BY or FOR clause must occur AFTER 'expression' and BEFORE
any WHILE or UNTIL clause.

ACTION: Reposition the TO, BY and FOR clauses in the DO instruction.


ΓòÉΓòÉΓòÉ 39. INPUT specified on multiple wait. ΓòÉΓòÉΓòÉ

ERROR: You specified INPUT in addition to other conditions on a single WAIT
instruction.

CAUSE: The keyword INPUT is not allowed on a WAIT instruction which specifies
multiple wait conditions. If INPUT is specified, no other conditions must be
specified.

ACTION: Either remove the INPUT keyword from the WAIT instruction or remove the
other wait conditions from the instruction.


ΓòÉΓòÉΓòÉ 40. Unacceptable integer value for keycode. ΓòÉΓòÉΓòÉ

ERROR: You specified an unknown keycode value.

CAUSE: Keycode values can only be an integer from 0 to 65,535.

ACTION: Make the keycode value an integer from 0 to 65,535.


ΓòÉΓòÉΓòÉ 41. Unknown style value. ΓòÉΓòÉΓòÉ

ERROR: You specified an unknown value for the text style number on a TEXTIN or
TEXTOUT instruction.

CAUSE: The text style must be a numeric value from 1 to 20.

ACTION: Change the TEXTIN or TEXTOUT instruction to specify a text style number
between 1 and 20.


ΓòÉΓòÉΓòÉ 42. End of field expected. ΓòÉΓòÉΓòÉ

ERROR: You entered a multi-column instruction missing an end mark

CAUSE: An end of a column mark (for a multi-column instruction) is missing.
This can sometimes happen when you delete or insert characters in a
multi-column instruction, shifting the remaining characters out of their proper
columns.

ACTION: Retype the instruction, or check that the column values are under the
appropriate columns and not in the "AVA/2 Statement" field.


ΓòÉΓòÉΓòÉ 43. Unable to start program. ΓòÉΓòÉΓòÉ

ERROR: You are trying to start a program that needs more resources than is
available.

CAUSE: There is not enough memory or other system resource for the program to
start.

Possible causes are:

o You need more memory to run this program.

o Other active applications are using resources needed by this program.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the program.

o Close all applications not being used

o Close any windows that are not needed

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists

o Archive any large or infrequently used files

o Rerun the program


ΓòÉΓòÉΓòÉ 44. Too many arguments specified. ΓòÉΓòÉΓòÉ

ERROR: You provided too many arguments to TELLPM.

CAUSE: TELLPM accepts the following:

o The name of the story to run. The story name can be preceded with drive and
  path information.

o Up to 10 arguments can be passed to the specified story.

ACTION: Issue TELLPM again using fewer than 10 arguments


ΓòÉΓòÉΓòÉ 45. Unable to load file list dialog box. ΓòÉΓòÉΓòÉ

ERROR: There is insufficient memory to start the file list dialog box. The
program cannot continue.

CAUSE: Possible causes are:

o You need more installed memory

o Other active applications are using some of the resources needed

ACTION: Try the following:

o Verify that your system meets the minimum requirements for the program.

o Close all applications not being used

o Close any windows that are not needed

o Archive any large or infrequently used files

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists

o Rerun the program


ΓòÉΓòÉΓòÉ 46. Unable to load story ΓòÉΓòÉΓòÉ

ERROR: You are trying to play a story that was not found.

CAUSE: Possible causes are:

o The story file name is misspelled.

o The story file is not in a supported format.

o The story file name is not in a directory that TELLPM searches.

  TELLPM searches for the file in this sequence:

   - The current system directory
   - The directory where the TELLPM program is located
   - The directories specified by the UMPATH environment variable

ACTION: Check the spelling of the story name or move the story file to a
directory that TELLPM searches.


ΓòÉΓòÉΓòÉ 47. R00 AVA/2 general error. ΓòÉΓòÉΓòÉ

ERROR: The AVA/2 interpreter encountered an error.

CAUSE: An unexpected internal program error occurred.

ACTION: Note the circumstances and related information and report the problem
to IBM.


ΓòÉΓòÉΓòÉ 48. R01 Story stopped by ESC. ΓòÉΓòÉΓòÉ

ERROR: You pressed the escape key which stops the story.

CAUSE: The story stops when the escape key (Esc) is pressed.

ACTION: Restart the story when ready.


ΓòÉΓòÉΓòÉ 49. R02 BREAKPOINT reached. ΓòÉΓòÉΓòÉ

ERROR: Story execution has stopped because the current story line is marked as
a breakpoint.

CAUSE: When creating or editing this story, you marked this line as a
breakpoint line.

ACTION: When you no longer want the story to stop at this point, remove the
breakpoint mark and restart the story.


ΓòÉΓòÉΓòÉ 50. R03 Unsaved changes in current story. ΓòÉΓòÉΓòÉ

WARNING: You are running a recently edited story. The recent changes have not
been saved and will be lost when the story finishes.

CAUSE: When a story ends, any changes are lost (if not saved).

ACTION: To save the changes, select 'Save' or 'Save as' from the 'File' menu.


ΓòÉΓòÉΓòÉ 51. R04 Too many story control instructions. ΓòÉΓòÉΓòÉ

ERROR: You are running a story with too many nested control instructions.

CAUSE: The story can keep track of up to 200 nested control instructions.  A
control instruction is one of the following:

o a CALL instruction

o a TELL instruction

o a function call

o a DO instruction

o an IF or ELSE instruction

o a SELECT instruction

ACTION: Modify your story to reduce the number of nested control instruction.
You can:

o Return or exit from a story or routine that was started by a CALL or TELL
  instruction

o Return from a story or routine started by a function call

o End an IF, ELSE, or SELECT instruction

o Leave or end a DO block


ΓòÉΓòÉΓòÉ 52. R99 Internal Error: 4005. ΓòÉΓòÉΓòÉ

ERROR: An internal program error was detected.

CAUSE: An unexpected internal program error occurred.

ACTION: Note the circumstances and information and report the error to IBM.


ΓòÉΓòÉΓòÉ 53. R06 Intermediate buffer space exceeded. ΓòÉΓòÉΓòÉ

ERROR: The intermediate buffer for evaluating variables on the current story
line is to small.

CAUSE: The buffer can hold up to 1024 bytes of intermediate values of
expressions being evaluated, parse templates, and evaluated arguments being
passed to a called function, procedure, or story.

Possible causes are:

o The total length of all the arguments being passed is too large to handle
  (exceeds 1024 bytes).

o Too many nested stories.

  When a story line calls a function or procedure, the evaluation of that line
  remains pending while the called procedure runs (leaving less space in the
  intermediate buffer).

ACTION: Possible actions:

o Simplify the story to reduce the number of pending expressions.

o Use exposed or global variables instead of passing arguments.

o Avoid nesting too many function or procedure calls.


ΓòÉΓòÉΓòÉ 54. R07 Not enough memory -- symbol table. ΓòÉΓòÉΓòÉ

ERROR: There is not enough memory available to create the internal symbol
tables.

CAUSE: The program requires additional space for symbols (i.e., variables and
labels) and some components of the story (audio, pictures, text, and triggers).
Memory is heavily used by:

o Calls from large stories to other large stories

o Screens with a large number of triggers and text fields all shown at the same
  time

o Lengthy audio files

o Large numbers of variables with long names and lengthy values

ACTION: Possible actions to take (which also improves the story's performance):

o Restructure your story to reduce its size.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Rerun the program


ΓòÉΓòÉΓòÉ 55. R08 Not enough memory -- procedure. ΓòÉΓòÉΓòÉ

ERROR: You are trying to run a procedure or function call, but there is not
enough memory for symbols and story components.

CAUSE: The program requires additional space for symbols (i.e., variables and
labels) and some components of the story (audio, pictures, text, and triggers).
Memory is heavily used by:

o Calls from large stories to other large stories

o Screens with a large number of triggers and text fields all shown at the same
  time

o Lengthy audio files

o Large numbers of variables with long names and lengthy values

ACTION: Possible actions to take (which also improves the story's performance):

o Restructure your story to reduce its size.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Rerun the program


ΓòÉΓòÉΓòÉ 56. R09 Too many nested calls. ΓòÉΓòÉΓòÉ

ERROR: Your story has exceeded the maximum number of nested calls. You may have
up to 8 nested calls.

CAUSE: Each time a CALL instruction is used a nest level exists until the
return from the called routine. Making another CALL from within a called
routine creates another nest level.

ACTION: Change the structure of the story so that no more than 8 nested calls
(calls within calls) occur.


ΓòÉΓòÉΓòÉ 57. R10 Too many files open. ΓòÉΓòÉΓòÉ

ERROR: You trying to open more than 8 files at the same time.

CAUSE: The file you are attempting to use cannot be opened because no more than
8 files can be open at one time. When a file is accessed using a READ, WRITE or
SEEK function, the file is opened and left open.

ACTION: Use the FINISH function to close one or more of your open files.


ΓòÉΓòÉΓòÉ 58. R11 Incomplete DO or SELECT block. ΓòÉΓòÉΓòÉ

ERROR: You are using a DO or SELECT block that is missing an END instruction.

CAUSE: Each DO or SELECT instruction must have a corresponding END instruction
to mark the end of the DO or SELECT block.

ACTION: Add an END instruction at the end of the block.


ΓòÉΓòÉΓòÉ 59. R12 THEN missing. ΓòÉΓòÉΓòÉ

ERROR: Your IF instruction or WHEN clause is missing a THEN keyword. The
required THEN keyword has been omitted from an IF instruction or a WHEN clause
of a SELECT instruction.

CAUSE: IF instructions and WHEN clauses require a THEN keyword. The correct
format for an IF instruction is:

   IF expression THEN instruction
The correct format for a WHEN clause (within a SELECT instruction) is:

   SELECT
      WHEN expression1 THEN instruction1
      WHEN expression2 THEN instruction2
      OTHERWISE instruction
   END

ACTION: Include a THEN keyword in the IF instruction or WHEN clause.


ΓòÉΓòÉΓòÉ 60. R13 LEAVE or ITERATE outside loop. ΓòÉΓòÉΓòÉ

ERROR: Your LEAVE or ITERATE instruction is not within a DO/END block.

CAUSE: A LEAVE or ITERATE instructions must be inside a block of instructions
that begin with DO and end with END.

ACTION: Correct the logic of your story and rerun it.


ΓòÉΓòÉΓòÉ 61. R14 FOR variable: not a positive integer. ΓòÉΓòÉΓòÉ

ERROR: Your expression following the FOR keyword does not result in a positive
whole number.

CAUSE: The expression does not evaluate to a positive whole number acceptable
to AVA/2. The maximum numeric value used in arithmetic operations is
+9,999,999.99.

ACTION: Correct the expression following the FOR keyword and rerun it.


ΓòÉΓòÉΓòÉ 62. R15 DO variable: not a number. ΓòÉΓòÉΓòÉ

ERROR: Your expression in the DO instruction does not result in an acceptable
AVA/2 number.

CAUSE: The expression must evaluate to a number acceptable to AVA/2. The range
of numeric values used in arithmetic operations is +9,999,999.99 to
-9,999,999.99.

ACTION: Correct the DO instruction expression and rerun it.


ΓòÉΓòÉΓòÉ 63. R16 WHEN or OTHERWISE missing. ΓòÉΓòÉΓòÉ

ERROR: You are missing a WHEN keyword or OTHERWISE clause in the SELECT block.

CAUSE: The SELECT block must have at least one WHEN keyword that evaluates to a
1 or it must have an OTHERWISE clause. The correct format for a SELECT
instruction is:

   SELECT
      WHEN expression1 THEN instruction1
      WHEN expression2 THEN instruction2
      OTHERWISE instruction3
   END

ACTION: Correct the SELECT instruction and rerun it.


ΓòÉΓòÉΓòÉ 64. R17 Too many nested DO blocks. ΓòÉΓòÉΓòÉ

ERROR: Your story has more than 60 nested DO blocks.

CAUSE: AVA/2 allows up to 60 nested DO blocks. This includes DO blocks active
in other stories. A DO block is active until the END instruction is executed. A
DO block remains active when you use the LEAVE, SIGNAL, and TELL instructions
to exit.

ACTION: Use the SELECT instruction where possible or simplify the story by
using fewer nested DO constructs.


ΓòÉΓòÉΓòÉ 65. R18 TELL instruction will cause loss of story changes. ΓòÉΓòÉΓòÉ

ERROR: You have changed but not saved the current story. When the TELL
instruction runs you will lose any changes made to the story.

CAUSE: When the TELL instruction runs, the current story is discarded from
memory.

ACTION: If you want the story changes saved, save the current story.


ΓòÉΓòÉΓòÉ 66. R19 Variable name too long. ΓòÉΓòÉΓòÉ

ERROR: Your story is using a variable name that is too long.

CAUSE: A variable name can be up to 250 characters long.

Possible causes are:

o The variable name is longer than 250 characters

o The variable name, when evaluated, becomes longer than 250 characters

o You misspelled the name

ACTION: Correct the problem, or use a shorter variable name.


ΓòÉΓòÉΓòÉ 67. R20 Variable value too long. ΓòÉΓòÉΓòÉ

ERROR: The contents of the variable exceeds 1024 characters.

CAUSE: The value assigned to a variable must be no more than 1,024 characters.

ACTION: Modify the story so that the variable value does not exceed 1024.


ΓòÉΓòÉΓòÉ 68. R21 Variable name expected. ΓòÉΓòÉΓòÉ

ERROR: You are missing a variable name.

CAUSE: The instruction must have a variable name at the proper place. The name
was either missing, or in the wrong place.

DROP           Used to discard one or more variables. The variable names are
               listed after the word DROP.

PROCEDURE EXPOSE Used to share one or more specific variables, and only those,
               with the caller. The names of the shared variables are listed
               after the word EXPOSE.

UPPER          Used to convert the contents of one or more variables to upper
               case. The variable names are listed after the word UPPER.

ACTION: Put a variable name in the proper place and rerun the instruction.


ΓòÉΓòÉΓòÉ 69. R22 Comma missing from argument list. ΓòÉΓòÉΓòÉ

ERROR: You provided an argument list that is missing a comma between arguments.

CAUSE: Each argument in a function call, or call to another story, must have a
comma separating each argument. An argument list can have up to 10 arguments.

ACTION: Put a comma between each argument and rerun the instruction.


ΓòÉΓòÉΓòÉ 70. R23 Unmatched parenthesis in argument list. ΓòÉΓòÉΓòÉ

ERROR: Your expression or function call is missing a left or right parenthesis.

CAUSE: For every left parenthesis there must be a right parenthesis.

ACTION: Correct and rerun the instruction or function.


ΓòÉΓòÉΓòÉ 71. R24 Unacceptable argument or wrong number of arguments ΓòÉΓòÉΓòÉ

ERROR: You issued a function call or call to another story with an unacceptable
argument or the wrong number of arguments.

CAUSE: The arguments must be recognizable by AVA/2. A function call or call to
another story cannot have more than 10 arguments.

If the call was for an AVA/2 function, Check one of these:

o A required argument is missing or evaluates to a null string.

o There are too many arguments.

o An argument's value does not conform to the particular requirements of the
  function (such as must be a number, must be positive, or must be within a
  specific set of values).
If the problem is an AVA/2 function call, refer to the description in the AVA/2
Language Reference and correct the instruction as required.

ACTION: Correct any arguments in error and issue no more than 10 arguments.


ΓòÉΓòÉΓòÉ 72. R25 Unacceptable name or label. ΓòÉΓòÉΓòÉ

ERROR: You used a name or label that is not acceptable to AVA/2.

CAUSE: Any name followed by a colon is a label.

A name must begin with an alphabetic character (A-Z, a-z), underscore, !, # or
@. After the first character, the name can also contain alphabetic characters,
underscore, !, and the digits 0-9. For example, Fred_3 is an acceptable name.

Lowercase letters are treated as uppercase.

Although the period is not accepted in a name, it can be used to join names to
express a compound name.

ACTION: Correct the name or label and rerun the story.


ΓòÉΓòÉΓòÉ 73. R26 Unable to restore "saved state". ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to restore a previously saved story state.

CAUSE: When trying to restore the saved state, one of the following problems
was encountered:

o A story state had not been previously saved.

o Not enough memory was available to completely restore the saved state. Try
  the following:

   - Close unneeded applications or windows.

   - Archive any large or infrequently used files.

   - Delete any unnecessary files on the disk where the SWAPPER.DAT file
     exists.

ACTION: Try saving the story state again.


ΓòÉΓòÉΓòÉ 74. R27 Incorrect syntax. ΓòÉΓòÉΓòÉ

ERROR: You typed an AVA/2 instruction using unrecognized syntax

CAUSE: The instruction was not recognized because it has missing or incorrect
information.

ACTION: Check the AVA/2 Language Reference for the proper instruction syntax.
Correct it and rerun the story.


ΓòÉΓòÉΓòÉ 75. R28 Unacceptable expression. ΓòÉΓòÉΓòÉ

ERROR: Your instruction has one or more expressions that are incorrect.

CAUSE:

Possible causes are:

o An arithmetic expression is not set to a number.

  For instance, the following is incorrect if y = 'PLAN6':

       x = y + 2

o The variable was never set to a value.

  If the variable y has never set to a value, it will contain its name in
  uppercase (y = 'Y').

o

ACTION: Check the AVA/2 Language Reference for the proper expression syntax.
Correct any errors in the expressions on the specified line and rerun it.


ΓòÉΓòÉΓòÉ 76. R29 Semicolon expected after expression. ΓòÉΓòÉΓòÉ

ERROR: A semicolon or end-of-line was expected as the next value, but something
else was found.

CAUSE: Possible causes are:

o There are extra characters that should be deleted

o You are missing the open comment delimiter (/*).

o Multiple instructions on one line are not separated by a semicolon

ACTION: Start all comments with the open delimiter and end all multiple-
instruction lines with a semicolon.


ΓòÉΓòÉΓòÉ 77. R30 Unexpected keyword. ΓòÉΓòÉΓòÉ

ERROR: You used a keyword where it was not expected.

CAUSE:

Possible causes are:

o You misspelled a name

o A variable has the same name as a keyword

o More than one instruction is on the line, but they are not separated by a
  semicolon

ACTION: Correct the instruction and rerun it.


ΓòÉΓòÉΓòÉ 78. R31 Non-numeric value in expression. ΓòÉΓòÉΓòÉ

ERROR: Your expression does not result in an acceptable AVA/2 number.

CAUSE: The expression must evaluate to a number acceptable to AVA/2. The range
of numeric values used in arithmetic operations is +9,999,999.99 to
-9,999,999.99.

Possible causes are:

o You misspelled the variable name

o An arithmetic expression is not set to a number.

  For instance, the following is incorrect if y = 'PLAN6':

       x = y + 2

o The variable was never set to a value.

  If the variable y has never set to a value, it will contain its name in
  uppercase (y = 'Y').

o

ACTION: Change the expression or parts of the expression so that it will
evaluate to an acceptable numeric value and rerun it.


ΓòÉΓòÉΓòÉ 79. R32 Logical value not 0 or 1. ΓòÉΓòÉΓòÉ

ERROR: The expression in an IF instruction or WHEN clause (of a SELECT
instruction) did not evaluation to 0 or 1.

CAUSE: An IF instruction and WHEN clause must have an expression whose value is
0 or 1. The evaluation of the expression must be true (1) or false (0).

ACTION: Change the expression or parts of the expression so that the evaluated
result has a value of 0 or 1.


ΓòÉΓòÉΓòÉ 80. R33 Unable to load function. ΓòÉΓòÉΓòÉ

ERROR: You specified a linkage to an entry point (via the FUNCADD function) in
your own dynamic link library (DLL) module, and the linkage could not be
established.

CAUSE:

Possible causes are:

o You misspelled the entry point or DLL name

o There is no such entry point in the DLL

o The DLL was not found

  If you included a specific path with the DLL name, only that path is
  searched. If you did not specify a path, the system uses the LIBPATH in your
  CONFIG.SYS to determine where to look for the DLL. The current directory or
  your story directory will not be searched unless explicitly listed in
  LIBPATH.

o The DLL could not be loaded

o

ACTION: Correct any errors in the following:

o The DLL name and path specified in the FUNCADD function

o The entry point name specified in the FUNCADD function

o The location of the DLL

o Your system's LIBPATH

o The DLL


ΓòÉΓòÉΓòÉ 81. R34 File name too long. ΓòÉΓòÉΓòÉ

ERROR: You specified a file name that exceeds the AVA/2 limit.

CAUSE: The fully-qualified file name can be up to 255 characters, including
special characters such as the back slash (\) or colon. If the name is resolved
from a variable, the contents of the variable must not be longer than 255
characters.

ACTION: Correct the name so that it is 255 characters or less. If the file
extension matches the AVA/2 defaults (._AU for audio, ._IM for images) you can
omit it from the name.


ΓòÉΓòÉΓòÉ 82. R35 Too many fields/triggers. ΓòÉΓòÉΓòÉ

ERROR: You are using more update fields and triggers than AVA/2 allows.

CAUSE: The Play window can have up to 256 triggers and update fields. The INPUT
instruction lets you specify up to 20 fields.

ACTION: Reorganize your story to display fewer fields and triggers at the same
time.


ΓòÉΓòÉΓòÉ 83. R36 Incorrect PARSE template. ΓòÉΓòÉΓòÉ

ERROR: You specified a pattern for the PARSE instruction template that was not
accepted.

CAUSE: The template does not follow the PARSE rules. A PARSE template must
indicate one of the acceptable methods of splitting strings into words or
variables.

ACTION: Correct your parse template.  Refer to the AVA/2 Language Reference for
an explanation of parse templates.


ΓòÉΓòÉΓòÉ 84. R37 Called story needs to be edited and saved. ΓòÉΓòÉΓòÉ

ERROR: The format of the story is out-of-date.

CAUSE: The called story was created with an old level of the product or with
the Audio-Visual Connection (AVC). The story may not run properly.

ACTION: Edit and save the story using the Builder/2 product. This produces a
up-to-date tokens for the story.


ΓòÉΓòÉΓòÉ 85. R38 Divide by zero not possible. ΓòÉΓòÉΓòÉ

ERROR: Your calculation has an expression which tries to divide by zero.
Dividing by zero is not possible.

CAUSE: AVA/2 cannot divide by zero.

Possible causes are:

o The variable name is misspelled

o The expression is incorrect

o You are using the wrong variable to divide by

ACTION: Use logic to check for a value of zero prior to dividing. Check and
correct variables used in the expression and rerun it.


ΓòÉΓòÉΓòÉ 86. R39 Arithmetic overflow. ΓòÉΓòÉΓòÉ

ERROR: The result of your calculation exceeds the AVA/2 maximum value.

CAUSE: The range of numeric values used in arithmetic operations is
+9,999,999.99 to -9,999,999.99.

For number in the range +99,999.99 to -99,999.99, precision is zero decimal
places. Precision is less for division involving large numbers.

ACTION: Correct the expression to prevent values from exceeding the numeric
range.


ΓòÉΓòÉΓòÉ 87. R40 LABEL defined more than once. ΓòÉΓòÉΓòÉ

ERROR: You used the same label more than once.

CAUSE: AVA/2 allows you to use a label once. Each label within a story must be
unique.

ACTION: Change the duplicate label to another name.


ΓòÉΓòÉΓòÉ 88. R41 LABEL not found. ΓòÉΓòÉΓòÉ

ERROR: You used a label in a CALL, SIGNAL or TELL instruction that could not be
found in your story.

CAUSE:

Possible causes are:

o You misspelled the label name in the CALL, SIGNAL, or TELL.

o The label name is misspelled or missing the colon

o The label does not exist

ACTION: Find the error, correct it and rerun the instruction.


ΓòÉΓòÉΓòÉ 89. R42 Incorrect art color specified ΓòÉΓòÉΓòÉ

ERROR: You specified an art color (in  the color instruction) that does not
exist within the image.

CAUSE: Art colors are only accepted for AVC images. An art color has the format
Ann where nn is a value from 0 to the number of art colors in the image.

ACTION: Change the art color in error to an acceptable art color (Ann) or to
color number between 0 and 255.


ΓòÉΓòÉΓòÉ 90. R43 Program cannot display this image. ΓòÉΓòÉΓòÉ

ERROR: You are attempting to display an image in an unsupported format.

CAUSE: The image is not displayable by AVA/2 Possible causes are:

o The image is not one of the following formats:

   AVC image

   OS/2 1.3, OS/2 2.x, WIN 3.0 bitmap (BMP)

   PCX Image

   TIF image

   Targa image

o The image uses an unsupported data compression.

o The image contains an unsupported number of colors. AVA/2 supports 8 bit
  (pixel) images (256 colors).

ACTION: Use an image conversion program to convert the image to a supported
format.


ΓòÉΓòÉΓòÉ 91. R44 Incorrect ON instruction ΓòÉΓòÉΓòÉ

ERROR: Your ON instruction has a syntax or name error.

CAUSE: The ON instruction syntax is not useable.

Possible causes are:

o You misspelled the ON condition.  It must include one of the following:

   - A reserved keyword; KEY, TRIGGER, or TIMER
   - A number representing a specific keycode
   - The name of a trigger (conforming to AVA/2 naming rules)

     A name must begin with an alphabetic character (A-Z, a-z), underscore, !,
     # or @. It can include alphabetic characters, underscore, !, and the
     digits 0-9 after the first character. Lowercase letters are treated as
     uppercase.
   - The name of a timer; TIMER1 through TIMER10

ACTION: Correct the ON instruction syntax. Refer to the AVA/2 Language
Reference for the proper ON instruction syntax.


ΓòÉΓòÉΓòÉ 92. R45 Internal audio error: 4045. ΓòÉΓòÉΓòÉ

ERROR: You were playing an audio file that resulted in an internal audio error.

CAUSE: Unexpected audio status was presented.

ACTION: Note of the circumstances and related information and report the error
to IBM.


ΓòÉΓòÉΓòÉ 93. R46 No such audio label ΓòÉΓòÉΓòÉ

ERROR: You specified an audio label that cannot be found.

CAUSE: Possible causes are:

o You misspelled the name of an audio label

o You used an unassigned variable for an audio label

o The audio label in your AVC audio file has changed

ACTION: Verify that the label is correct and does exist, and rerun the
instruction.


ΓòÉΓòÉΓòÉ 94. R47 Unacceptable audio combination. ΓòÉΓòÉΓòÉ

ERROR: You are trying to play two audio files at the same time and there is a
conflict.

CAUSE: Possible causes for this conflict are:

o An audio file is recorded in stereo.

  Since stereo uses both audio channels, no other audio can be played with it.

o An audio file is a MIDI file.

  A MIDI file cannot play while another MIDI file is playing. (However, a MIDI
  file can play with a voice-quality audio file.)

o One file was recorded at a different sample rate from the other.

ACTION: To correct this problem:

o To play two sounds at once use audio recorded at voice or music quality.

o If you are playing MIDI with a voice file, start the MIDI first.

o Check the audio file sampling rates and re-record the audio so that each file
  is in the same format.

o Play the audio files individually; issue a PLAY STOP instruction before
  playing the second file.


ΓòÉΓòÉΓòÉ 95. R48 Audio start beyond end position. ΓòÉΓòÉΓòÉ

ERROR: You specified a starting position that is either beyond end position
specified or beyond the end of the entire audio segment.

CAUSE:

Possible causes are:

o You misspelled the start position

o You specified the wrong start position

o Your audio segment may be shorter than expected

ACTION: Correct the start position and rerun the instruction.


ΓòÉΓòÉΓòÉ 96. R49 FINIS not accepted as audio start. ΓòÉΓòÉΓòÉ

ERROR: You used the keyword FINIS to define where the audio should start.

CAUSE: The keyword FINIS is only used to specify playing to the end of the
audio file.

ACTION: Correct the syntax to indicate where the audio should start.


ΓòÉΓòÉΓòÉ 97. R50 BEGIN not accepted as audio end. ΓòÉΓòÉΓòÉ

ERROR: You used the keyword BEGIN for where the audio should end.

CAUSE: The keyword BEGIN is only used to specify the start of the audio file.
You specified BEGIN for where audio should end.

ACTION: Correct the syntax to indicate where the audio should end.


ΓòÉΓòÉΓòÉ 98. R51 Unresolvable WAIT value. ΓòÉΓòÉΓòÉ

ERROR: You specified a wait interval does not resolve to a time or an audio
sync point.

CAUSE: Possible causes are:

o You misspelled a keyword

o You specified a second wait value in addition to INPUT.

  If INPUT is used, it must be the only wait value.

o You specified an unacceptable channel with an audio wait value.

  A channel identifier (A or B) must be given when waiting for a specific
  amount of audio time. The channel identifier is optional when waiting for an
  audio label.

o You specified an unacceptable timer name. Timer names are: TIMER1, TIMER2,
  through TIMER10)

ACTION: Specify an acceptable WAIT value. Refer to the AVA/2 Language Reference
for possible values.


ΓòÉΓòÉΓòÉ 99. R52 Unable to run command or program. ΓòÉΓòÉΓòÉ

ERROR: There are not enough resources to run the command or program.

CAUSE: All of the current resources of the computer are being used.

ACTION:

o Verify that your system meets the minimum requirements for the program.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Rerun the program


ΓòÉΓòÉΓòÉ 100. R53 Resource table full. ΓòÉΓòÉΓòÉ

ERROR: There is no available space in the internal resource table.

CAUSE: AVA/2 maintains a table of objects (images, audio files, fonts and
dissolves) that are currently loaded. This table keeps track of up to 25
objects. When the table is full, no object can be loaded without releasing an
object. Use the RELEASE instruction to discard loaded objects.

ACTION: Use the RELEASE instruction to free objects to make room in the
internal table. You can also use the RESOURCEMAX function to increase the
amount of space available in the table.


ΓòÉΓòÉΓòÉ 101. R54 Not enough memory -- resource. ΓòÉΓòÉΓòÉ

ERROR: You are trying to run a story (or use the CLEAR or COLOR instruction)
but there is not enough available memory for it.

CAUSE: The program requires additional space for symbols (i.e., variables and
labels) and some components of the story (audio, pictures, text, and triggers).
Memory is heavily used by:

o Calls from large stories to other large stories

o Screens with a large number of triggers and text fields all shown at the same
  time

o Lengthy audio files

o Large numbers of variables with long names and lengthy values

ACTION: Possible actions to take (which also improves the story's performance):

o Restructure your story to reduce its size.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Rerun the program


ΓòÉΓòÉΓòÉ 102. R55  Unacceptable update size argument. ΓòÉΓòÉΓòÉ

ERROR: You are trying to change the size of an object by using an unacceptable
value.

CAUSE: The new size must be larger than zero. (The size must be a positive
value.)

ACTION: Correct the size for the update request.


ΓòÉΓòÉΓòÉ 103. R56  Incorrect object type. ΓòÉΓòÉΓòÉ

ERROR: You provided an incorrect object type for update.

CAUSE: The object type provided is in conflict with the requested operation.

ACTION: Correct the object type or change the request.


ΓòÉΓòÉΓòÉ 104. R57  Resource not in table. ΓòÉΓòÉΓòÉ

ERROR: You requested a resource that is not available in the internal resource
table.

CAUSE: The resource may have been released to make room in memory for other
resources.

ACTION: Load the resource again.


ΓòÉΓòÉΓòÉ 105. R58  Resource not loaded. ΓòÉΓòÉΓòÉ

ERROR: You requested a resource that is not loaded in the internal resource
table.

CAUSE: The resource may have been released to make room in memory for other
resources.

ACTION: Load the resource again.


ΓòÉΓòÉΓòÉ 106. R59  Resource create error. ΓòÉΓòÉΓòÉ

ERROR: You requested a resource that AVA/2 was unable to create.

CAUSE: Possible causes are:

o You misspelled the name of the resource

o There is already another file with the same name

o There is not enough disk space to create the resource

ACTION: Change the name, make more space available, or cancel the operation.


ΓòÉΓòÉΓòÉ 107. R60  Incorrect resource priority value. ΓòÉΓòÉΓòÉ

ERROR: You used an incorrect value for the new resource priority.

CAUSE: Priority values must match the values permitted by the programming
interface SAPI.H.

ACTION: Use a resource priority value permitted by SAPI.H.


ΓòÉΓòÉΓòÉ 108. R61 Text or font not found. ΓòÉΓòÉΓòÉ

ERROR: You either specified TEXT for a picture that has no text or indicated a
font size that does not exist.

CAUSE: Possible causes are:

o You misspelled the file name.

o You misspelled the font size

o The font resources are not in an available directory

o The font resources are missing

ACTION: Correct the request, or provide the proper resource.


ΓòÉΓòÉΓòÉ 109. R62 Cannot write to "read only" file. ΓòÉΓòÉΓòÉ

ERROR: You are trying to change the contents of a file that is either on a
read-only drive, or is currently set to read-only.

CAUSE: AVA/2 is unable to write the file.

ACTION: Change the drive or write-enable it, then save the story.


ΓòÉΓòÉΓòÉ 110. R63  AVA/2 initialization error. ΓòÉΓòÉΓòÉ

ERROR: You are trying to start AVA/2, but there is not enough memory or system
resources for it to start.

CAUSE: Possible causes are:

o Your system may not meet minimum requirements

o AVA/2 need resources being used by other running applications.

ACTION:

o Verify that your system meets the minimum requirements for the program.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Rerun the program


ΓòÉΓòÉΓòÉ 111. R64  Unacceptable beginning line. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable value for the beginning of the block of
lines.

CAUSE: The value for the beginning line in a block must be greater than 0. It
must also be less than the end-line value and less than the last line in the
story.

ACTION: Correct the beginning line value.


ΓòÉΓòÉΓòÉ 112. R65  Unacceptable ending line. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable value for the end line of a block of
lines.

CAUSE: The value for the ending line in a block must be greater than the
beginning line value, and equal to or less than the number of lines in the
story.

ACTION: Correct the ending line value.


ΓòÉΓòÉΓòÉ 113. R66  Incorrect open flag. ΓòÉΓòÉΓòÉ

ERROR: You specified an open flag value that cannot be used.

CAUSE: The open flag value associated with an AVA/2 resource is incorrect.

ACTION: Use an open flag value documented for the SAPI.H interface.


ΓòÉΓòÉΓòÉ 114. R67  Trigger name too long. ΓòÉΓòÉΓòÉ

ERROR: You specified a trigger name (for an ADDTRIGGER or a DROPTRIGGER
function) that exceeds 31 characters.

CAUSE: The trigger name exceeds the AVA/2 limit of 31 characters.

ACTION: Shorten the trigger name.


ΓòÉΓòÉΓòÉ 115. R68  File not found. ΓòÉΓòÉΓòÉ

ERROR: You specified a story, audio, dissolve, font or image file that could
not be found.

CAUSE: Some of the possible causes for this message are:

o You misspelled the file name.

o The file does not exist.

o The drive or path specified is incorrect.

o The file is not in the AVA/2 search path.

o An unsupported function name was specified.

AVA/2 searches for the file in this sequence:

o The current system directory
o The current story directory
o The directory where the AVA/2 executable files are located
o The directories specified by the UMPATH environment variable

ACTION: Correct the file name or path information.


ΓòÉΓòÉΓòÉ 116. R69  I/O error on file open. ΓòÉΓòÉΓòÉ

ERROR: You requested a file that could not be opened.

CAUSE:

Possible causes are:

o You misspelled the file name.

o The file does not exist.

o The name is already in use as the name of a directory.

o The file is in use by someone else.

o The file has read-only protection status.

o The FILES system limit was reached.

o The file's data has been damaged.

ACTION: Try the following:

o Verify the name of the file.

  If it is a new file, make sure the characters in the name are allowed by
  OS/2. A name must begin with an alphabetic character (A-Z, a-z), underscore,
  !, # or @. After the first character, the name can also contain alphabetic
  characters, underscore, !, and the digits 0-9. For example, Fred_3 is an
  acceptable name.
o Change the file protection status.
o Close some currently open files. or increase the value for the number of
  files in the FILES= statement in your CONFIG.SYS, shutdown OS/2, and then
  restart the system by pressing the Ctrl + Alt + Del keys.
o Create a new file on the same drive and try the same operation with the new
  file.
o Retry the operation after doing one of the above.


ΓòÉΓòÉΓòÉ 117. R70  I/O error on file read. ΓòÉΓòÉΓòÉ

ERROR: You requested a file that cannot be read.

CAUSE: The disk or diskette drive may be failing, or the data in the file has
been damaged.

ACTION: Try another file on the same drive or another file on another drive.


ΓòÉΓòÉΓòÉ 118. R71  I/O error on file write. ΓòÉΓòÉΓòÉ

ERROR: You are trying to save a file that cannot be saved.

CAUSE: There may be no space available or there is a problem with the disk or
diskette drive you are using.

ACTION: Try one of the following:

o Try saving the file on another drive.

o Return to OS/2 and free some disk space by deleting files and then try to
  save the file.


ΓòÉΓòÉΓòÉ 119. R72  General I/O error. ΓòÉΓòÉΓòÉ

ERROR: A general input/output error occurred.

CAUSE: Possible causes of this problem are:

o There is a problem with the disk or diskette drive.

o The file extension in the file name does not match the type specified.

o The file contents do not match the type implied by the file's extension.

o An internal error has occurred.

ACTION: Check each one of the possible conditions noted above. If an internal
error has occurred, Note the circumstances and information and report the error
to IBM.


ΓòÉΓòÉΓòÉ 120. R73  Story already playing. ΓòÉΓòÉΓòÉ

ERROR: You are trying to play a story while another story is already playing.

CAUSE: An application can only play one story at a time.

ACTION: Close the first story or wait until the running story completes.


ΓòÉΓòÉΓòÉ 121. R74  Story stopped by user. ΓòÉΓòÉΓòÉ

ERROR: You closed the play window or clicked on the stop button to stop the
story.

CAUSE: The user stopped the story.

ACTION: None required.  Restart the story when ready.


ΓòÉΓòÉΓòÉ 122. R75  Unable to load database access routines. ΓòÉΓòÉΓòÉ

ERROR: Your story could not access the database requested.

CAUSE: The AVA/2 database access routines require a specific dynamic link
library (DLL) module (called UTSMPLDB) in order to access the database. This
module is provided with Ultimedia Workplace/2. The DLL module was not found.
Possible causes are:

o Workplace/2 is not installed.

o The DLL is not in a directory listed in the LIBPATH line of the CONFIG.SYS
  file.

ACTION: Install Ultimedia Workplace/2 if database access is needed. If already
installed verify that the directory containing the DLL module is in the LIBPATH
line of your CONFIG.SYS file.


ΓòÉΓòÉΓòÉ 123. R76  Database not prepared for operation. ΓòÉΓòÉΓòÉ

ERROR: You attempted an operation on a database that was not ready for the
operation.

CAUSE:

Possible causes are:

o The database file is not open.

o The database file is not positioned to a database record.

ACTION: Use DBOPEN to open the database file before trying to read or write to
the database.


ΓòÉΓòÉΓòÉ 124. R77  Too many pipes open. ΓòÉΓòÉΓòÉ

ERROR: The pipe you are trying to use cannot be opened until another pipe is
closed.

CAUSE: Only 8 pipes can be open at a time. When a pipe is accessed using a
PCREATE, PREAD, or PWRITE function, the pipe is opened and left open.

ACTION: Use the PFINISH function to close one or more of the open pipes.


ΓòÉΓòÉΓòÉ 125. R78  Too many databases open. ΓòÉΓòÉΓòÉ

ERROR: The database file you are trying to use cannot be opened until another
database is closed.

CAUSE: Only 8 database files can be open at a time. When a database file is
accessed using a DBCREATE, DBOPEN, DBQUERYSTRING or DBQUERYFILE function, the
database file is opened and left open.

ACTION: Use the DBFINISH function to close one or more of your open database
files.


ΓòÉΓòÉΓòÉ 126. R79  Too many IPF files open. ΓòÉΓòÉΓòÉ

ERROR: The IPF file you are trying to use cannot be opened until another IPF
file is closed.

CAUSE: Only 6 IPF files can be open at a time. When an IPF file is accessed
using an IPFDISPLAY function, the IPF file is opened and left open.

ACTION: Use the IPFFINISH function to close one or more of your open IPF files.


ΓòÉΓòÉΓòÉ 127. R80  Unable to load pointer file. ΓòÉΓòÉΓòÉ

ERROR: You specified a custom mouse pointer file (using the POINTER function)
that could not be loaded.

CAUSE: Possible causes for this problem are:

o You misspelled the pointer file name

o The file name is missing the file extension.

o The pointer file is not in a directory that AVA/2 searches.

  AVA/2 searches for the file in the current system directory, current story
  directory, Ultimedia executables directory and in the directories specified
  by the UMPATH environment variable.

o The pointer file is not in a supported format.

  It must be in OS/2 2.0 format.

ACTION: Check the possible causes described above.


ΓòÉΓòÉΓòÉ 128. R81  No style matches the style number. ΓòÉΓòÉΓòÉ

ERROR: You specified a text style with the TEXTIN or TEXTOUT instruction that
was not available to the story.

CAUSE: AVA/2 must have the text style specified or have a specification saved
with the story.

ACTION: You can either edit the story and create a text style with the desired
number or change the style number on the TEXTIN or TEXTOUT instruction so that
it specifies an available style.


ΓòÉΓòÉΓòÉ 129. R82  The argument is beyond the range of values. ΓòÉΓòÉΓòÉ

ERROR: You specified an unacceptable value to an AVA/2 function.

CAUSE: The AVA/2 argument is beyond the range of values allowed by the
function.

ACTION: Correct the incorrect argument.  Refer to the AVA/2 Language Reference
to determine the range of values for the function.


ΓòÉΓòÉΓòÉ 130. R83  Unable to determine audio status. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 could not determine the status of the audio file.

CAUSE: Possible causes are:

o You misspelled the audio file name.

o The audio is not playing.

o The audio device does not support this function.

o There is a device hardware error

ACTION: Stop the story and restart it. If the problem persists, try shutting
down OS/2 and restarting your computer.


ΓòÉΓòÉΓòÉ 131. R84  Unable to set audio wait position. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 could not set an audio wait position.

CAUSE: To wait for a specific audio label or audio time, AVA/2 sets a cue
point. When that cue point is reached in the audio, AVA/2 is notified and ends
the wait condition. AVA/2 could not set the audio cue point. Possible causes
for this problem are:

o You misspelled the audio file name.

o The audio file is not currently active.

o The specified cue point already exists.

o The system limit for cue points has been reached.

ACTION: Stop the story and restart it. If the problem persists, try shutting
down OS/2 and restarting your computer.


ΓòÉΓòÉΓòÉ 132. R85  Unable to adjust audio volume. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to adjust the volume for the audio channel.

CAUSE: This is caused by an internal audio error.

ACTION: Note the circumstances and information and report the error to IBM.


ΓòÉΓòÉΓòÉ 133. R86  Unable to adjust audio balance. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to adjust the balance for the audio channel.

CAUSE: This is caused by an internal audio error.

ACTION: Note the circumstances and information and report the error to IBM.


ΓòÉΓòÉΓòÉ 134. R87  Unable to stop audio. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to stop the playing audio.

CAUSE: This is caused by an internal audio error.

ACTION: Note the circumstances and information and report the error to IBM.


ΓòÉΓòÉΓòÉ 135. R88  Unable to pause or resume audio. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to pause or resume playing audio.

CAUSE: Possible causes for this problem are:

o The audio file is not currently active.

o An internal audio error occurred.

ACTION: Stop the story and restart it. If the problem persists, note the
circumstances and information and report the error to IBM.


ΓòÉΓòÉΓòÉ 136. R89  Unable to play audio. ΓòÉΓòÉΓòÉ

ERROR: AVA/2 was unable to play the audio file.

CAUSE: Possible causes for this problem are:

o You misspelled the audio file name.

o The audio file does not exist.

o The audio file is in use on another channel or by another application.

o The audio channel is currently playing another audio file.

o The story has an unacceptable audio combination. For example:

   - Trying to play two stereo audio files.

     Since stereo uses both audio channels, no other audio can be played with
     it.

   - Both audio files are MIDI files.

     A MIDI file cannot play while another MIDI file is playing. (However, a
     MIDI file can play with a voice-quality audio file.)

   - One file was recorded at a different sample rate from the other.

o Your audio adapter does not support the type of audio used in this story.

o The audio file is an AVC audio file and the required ._AD file is missing.

  AVC audio files which have an extension of ._AU require a another file with
  the same name and an extension of ._AD.

o An internal audio error occurred.

ACTION: To correct this problem:

o To play two sounds at once use audio recorded at voice or music quality.

o If you are playing MIDI with a voice file, start the MIDI first.

o Check the audio file sampling rates and re-record the audio so that each file
  is in the same format.

o Play the audio files individually; issue a PLAY STOP instruction before
  playing the second file.

o Check that your audio adapter supports the audio type used in the story.

o If you are playing an AVC audio file, check that the required files (._AU and
  ._AD) are present in the same directory.

If it appears that an internal error occurred, note of the circumstances and
information and report the error to IBM.


ΓòÉΓòÉΓòÉ 137. R90  I/O session dropped. ΓòÉΓòÉΓòÉ

ERROR: The session reading your file was dropped.

CAUSE: Possible causes for this problem are:

o A network error occurred that prevented your file from being read.

o Multiple disk-intensive operations interfered with each other. This might
  occur, for example, if you are playing digital video while displaying an
  image.

ACTION: Restart the story.  If the problem persists, you need to:

o Restructure your story

o Move your images or video to the hard disk in your machine.


ΓòÉΓòÉΓòÉ 138. Audio not active ΓòÉΓòÉΓòÉ

ERROR: You entered a request to synchronize with a previously started audio
file but no PLAY statement for the specified Channel was found.

CAUSE: Possible causes are:

o The PLAY statement is missing.

o The wrong channel was selected.

ACTION: Try one of the following:

o Add the missing PLAY statement.

o Select the other channel.


ΓòÉΓòÉΓòÉ 139. Video not active ΓòÉΓòÉΓòÉ

ERROR: You entered a request to synchronize with a previously started video
file but no prior VPLAY statement was found.

CAUSE: Possible causes are:

o The VPLAY statement is missing.

ACTION: Try the following:

o Add the missing VPLAY statement.


ΓòÉΓòÉΓòÉ 140. Input file cannot be processed. ΓòÉΓòÉΓòÉ

ERROR: You attempted to browse a file but the browse failed. (The file name is
provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.

o The file does not exist or is empty.

o The format of the file is not supported by Browse.

o The file is in use by another process.

o A system input or output (I/O) error occurred while opening the file.

ACTION: Try the following:

o Correct the file name.

o Make sure the file exists.

o Get another copy of the file from another source.

o Verify that the browser you started is the proper browser for the format of
  the file.

o Stop the other process that is using the file.

o Try to browse the file again.


ΓòÉΓòÉΓòÉ 141. Unresolved DOS error ΓòÉΓòÉΓòÉ

ERROR: An operating system error has stopped the operation.

CAUSE: An operating system error cannot be resolved.

ACTION: Try one of the following:

o Retype the filename, making sure the drive, path, file name and extension are
  correct.

o Note the circumstances and information and report this error to IBM.


ΓòÉΓòÉΓòÉ 142. Directory not found ΓòÉΓòÉΓòÉ

ERROR: You specified a directory that cannot be found.

CAUSE: Possible causes are:

o You misspelled the directory name.

o The directory that you want does not exist.

ACTION: Try the following:

o Retype the filename, correcting the drive and path.

o Create the directory and put any required resources in it.


ΓòÉΓòÉΓòÉ 143. Not a DOS disk ΓòÉΓòÉΓòÉ

ERROR: You specified a disk that is not readable.

CAUSE: Possible causes are:

o The disk has not been formatted properly.

o The disk has not been formatted for a DOS or OS/2 system.

ACTION: Try one of the following:

o Check the disk in the drive.

o Format the disk.

o Run diagnostics or try another disk.


ΓòÉΓòÉΓòÉ 144. Drive locked ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a drive that is reserved by another process.

CAUSE: Possible causes are:

o Another process is using the drive and can not be interrupted.

o There is a hardware or program problem.

ACTION: Try one of the following:

o Stop the other process.

o Wait until the drive is free.

o Shutdown OS/2 and then restart the system.

o Note the circumstances and information and report this error to IBM.


ΓòÉΓòÉΓòÉ 145. File name too long ΓòÉΓòÉΓòÉ

ERROR: You specified either a file name or an extension that is too long.

CAUSE: Possible causes are:

o The file name is greater than 8 characters.

o The extension is greater than 3 characters.

o The fully qualified file name is more than 27 characters which is the maximum
  length that will fit in the story table.

ACTION: Try one of the following:

o Correct the file name or extension.

o Rename or relocate the file so that the fully qualified name is 27 characters
  or less.

o Use the UMPATH environment variable to specify the drive and path information
  making it unnecessary to qualify the file name in the story.


ΓòÉΓòÉΓòÉ 146. Unable to open profile data ΓòÉΓòÉΓòÉ

ERROR: The profile data file SE.PRO could not be opened.

CAUSE: Possible causes are:

o The file does not exist.

o You don't have permission to read the file.

ACTION: Try one of the following:

o Look for the file SE.PRO. It should be in the same directory where Builder/2
  is installed.

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.


ΓòÉΓòÉΓòÉ 147. Unable to save data to .INI file ΓòÉΓòÉΓòÉ

ERROR: Unable to save data to .INI file ULTITOOL.INI in the current working
directory or in a directory specified in the UMPATH system variable.

CAUSE: Possible causes are:

o You don't have permission to write to the disk or the file in the current
  working directory or in a directory specified in your UMPATH.

o Insufficient storage space is available.

ACTION: Try one of the following:

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for Builder/2.

   - Archive any large or infrequently used files on the drive where the
     ULTITOOL.INI file is being saved.

   - Rerun the program


ΓòÉΓòÉΓòÉ 148. Unable to save story ΓòÉΓòÉΓòÉ

ERROR: Unable to save the story.  Save cancelled.

CAUSE: Possible causes are:

o You don't have permission to write the file.

o The diskette is write protected.

o Insufficient storage space is available.

o The file specified is a directory.

o A component of the path prefix is not a directory.

ACTION: Try one of the following:

o Check the spelling of all path names.

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.

o If saving to a diskette, check the position of the write protect tab.

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for Builder/2.

   - Archive any large or infrequently used files on the drive where the story
     is being saved (the directory is provided in the error window).

   - Rerun the program

o Retype the file name (using Save As...).

o Export the file (using Export...).


ΓòÉΓòÉΓòÉ 149. Incorrect file extension ΓòÉΓòÉΓòÉ

ERROR: The story has an unrecognized file extension.

CAUSE: Possible causes are:

o You misspelled the story name.

o The story does not have a ._ST extension.

ACTION: Try the following:

o Respecify the name and file extension.

o Rename the file extension to ._ST


ΓòÉΓòÉΓòÉ 150. No story selected ΓòÉΓòÉΓòÉ

ERROR: You have not selected a story file.

CAUSE: Possible causes are:

o You clicked on one of the Authoring buttons before opening a story.

ACTION: Try the following:

o Open a new or existing story by selecting File from the menu, then select
  Open...

  For a new story, type the name of the story in the Open filename field. For
  an existing story, type the fully-qualified name of the story or select it
  from the Open window file list.


ΓòÉΓòÉΓòÉ 151. File already exists ΓòÉΓòÉΓòÉ

ERROR: You are trying to use Save as... to save a new file, but a file by that
name already exists.

CAUSE: Possible causes are:

o You misspelled the file name in the Save as... window.

o You didn't know a file by that name existed.

ACTION: Try the following:

o Change the story file name of the existing file, or the one that you are
  trying to save.


ΓòÉΓòÉΓòÉ 152. Out of memory ΓòÉΓòÉΓòÉ

ERROR: You are trying to do something that requires more memory than the system
can provide.

CAUSE: Possible causes are:

o There is not enough space left on the drive that contains the SWAPPER.DAT
  file.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Builder/2.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Move the SWAPPER.DAT file to a drive that has more space.

  If you move the SWAPPER.DAT file to another drive, you must also change the
  SWAPPATH variable in CONFIG.SYS file. Then shutdown OS/2 and restart the
  system.

o Add more memory if possible.

o Rerun the program


ΓòÉΓòÉΓòÉ 153. Error starting internal application ΓòÉΓòÉΓòÉ

ERROR: Builder/2 requested an internal application that could not be started.

CAUSE: Internal application unavailable.

ACTION: Note the circumstances and information and report this error to IBM.


ΓòÉΓòÉΓòÉ 154. Sync with video not valid based on video type ΓòÉΓòÉΓòÉ

ERROR: You entered a request to synchronize with video which is invalid for the
type of video being played.

CAUSE: Possible causes are:

o You are trying to Sync with video with a CD-XA video file.

o You are trying to Sync with video with a laserdisc video file.

ACTION: Try one of the following:

o For CD-XA, specify a time value to wait instead.

o For laserdisc, specify a frame to wait for instead using the following
  syntax:  F 123.


ΓòÉΓòÉΓòÉ 155. Fully qualified file name is too long...name truncated ΓòÉΓòÉΓòÉ

ERROR: You are trying to drop either an image file, an audio file, or a video
file into a Builder/2 story but the fully qualified file name is too long.  The
file name has been cut to fit in the story table.

CAUSE: Possible causes are:

o The fully qualified name of the object you are trying to drop into the
  Builder/2 story exceeds 27 characters.

ACTION: Try one of the following:

o Rename or relocate the object so that its fully qualified name is 27
  characters or less.  Then try to drag the object onto Builder/2 again.


ΓòÉΓòÉΓòÉ 156. No label name specified ΓòÉΓòÉΓòÉ

ERROR: You did not enter a label name in the Label Definition window.

CAUSE: Possible causes are:

o You left the Label Name field blank

o You entered only blanks in the Label Name field

ACTION: Try one of the following:

o Enter an acceptable label name

o Close the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 157. Unacceptable label name ΓòÉΓòÉΓòÉ

ERROR: You entered a label name that began with a digit.

CAUSE: A label cannot begin with a number. A label must begin with an
alphabetic character (A-Z, a-z), underscore, !, # or @. After the first
character, the label can also contain alphabetic characters, underscore, !, and
the digits 0-9. For example, PART_3 is an acceptable label.

ACTION: Try one of the following:

o Enter an acceptable label name

o Cancel the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 158. No key specified ΓòÉΓòÉΓòÉ

ERROR:  You did not enter or select a key name from the key drop down list.

CAUSE: Possible causes are:

o The key name was accidentally left blank when scope was set to "branch only"

ACTION: Try one of the following:

o Enter or select a key name

o Cancel the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 159. No trigger name specified ΓòÉΓòÉΓòÉ

ERROR: You did not enter a trigger name in the trigger entry field.

CAUSE: Possible cause:

o The trigger name was accidentally left blank when scope was set to "Branch
  Only"

ACTION: Try one of the following:

o Enter a trigger name

o Cancel the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 160. No trigger name specified ΓòÉΓòÉΓòÉ

ERROR: You did not enter a trigger name in the trigger entry field.

CAUSE: Possible cause:

o

o The trigger name was not included when creating an addtrigger or droptrigger
  statement.

ACTION: Try one of the following:

o Enter a trigger name

o Cancel the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 161. Unacceptable key value ΓòÉΓòÉΓòÉ

ERROR: The value entered in the Key input field is unacceptable.

CAUSE: Possible causes are:

o With Scope set for the Entire Story, you entered a non-numeric value that is
  not recognized as a valid key.

o You entered a negative number.  Numeric key values must be positive.

ACTION: Try one of the following:

o Select a value from the Key drop-down list.

o Enter a valid numeric value in the Key input field.

o Close the window by clicking on the Cancel button.


ΓòÉΓòÉΓòÉ 162. Unacceptable color value ΓòÉΓòÉΓòÉ

ERROR: You entered an unrecognized Clear to color value.

CAUSE: Possible causes are:

o You entered a non-numeric value that is not an acceptable color mnemonic

o You entered a numeric value that is not within the range of the current color
  palette

ACTION: Try one of the following:

o Enter one of the valid color mnemonics

o Use the color picker icon to choose a numeric value

o Cancel the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 163. Colors exceed the space available ΓòÉΓòÉΓòÉ

ERROR: You have exceeded the space available for specifying colors.

CAUSE: The column in the Text View for specifying colors is a limited space.

Check the following:

o The number of colors you are using.

o The size of the numbers that specify the colors you are using.

ACTION: Try one of the following:

o Split the color definition into two or more separate color frames.

o Reduce the number of colors you are using.

o Close the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 164. Missing old or new color ΓòÉΓòÉΓòÉ

ERROR: You specified a new or an old color without the corresponding value (the
other old or new color).

CAUSE: The old and new color must be specified as a pair.

Check to see that you have specified each color with both an old and a new
value.

ACTION: Try one of the following:

o Enter the missing old or new color value

o Close the window by clicking on the Cancel button


ΓòÉΓòÉΓòÉ 165. No system color map is available ΓòÉΓòÉΓòÉ

ERROR: It is not possible to access the system color map.

CAUSE: Possible causes are:

o The image you selected has no color map, and the system color map could not
  be accessed.

  When an image you select has no color map, Builder/2 uses the system color
  map. The system color map could not be accessed.

o No image was specified and the system color map could not be accessed.

ACTION: Try one of the following:

o Try selecting another image file with the File List button.

o Close the window by clicking on the Cancel button.

o Note the circumstances and information and report this error to IBM.


ΓòÉΓòÉΓòÉ 166. No color map ΓòÉΓòÉΓòÉ

ERROR: The file selected does not have a valid color map. The default system
color map will be used.

CAUSE: Possible causes are:

o You entered the name of a file that is not an image file.

o You entered the name of an image file that does not have an associated color
  map.

ACTION: Try one of the following:

o Using the File List button, select a valid image file.

o Continue selecting colors using the system color map.

o Close the window by clicking on the Cancel button.


ΓòÉΓòÉΓòÉ 167. Unable to open file for export ΓòÉΓòÉΓòÉ

ERROR: The file you want to export could not be opened.

CAUSE: Possible causes are:

o The file specified is a directory.

o A component of the path prefix is not a directory.

o You don't have permission to write the file.

o Insufficient storage space is available.

ACTION: Try one of the following:

o Correct the file name.

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for the Builder/2.

   - Archive any large or infrequently used files on the drive where the story
     is being exported (the directory is provided in the error window).

   - Rerun the program


ΓòÉΓòÉΓòÉ 168. Unable to open import file ΓòÉΓòÉΓòÉ

ERROR: The file you want to import could not be opened.

CAUSE: Possible causes are:

o The file specified does not exist.

o The file specified is a directory.

o A component of the path prefix is not a directory.

o You don't have permission to read the file.

ACTION: Try one of the following:

o Correct the file name and path.

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.


ΓòÉΓòÉΓòÉ 169. Out of memory ΓòÉΓòÉΓòÉ

ERROR: You are trying to import a file, but there is not enough memory.

CAUSE: There is not enough space left on the drive that contains the
SWAPPER.DAT file.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the Builder/2.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Move the SWAPPER.DAT file to a drive that has more space.

  If the SWAPPER.DAT file is moved to another drive, the SWAPPATH variable in
  the CONFIG.SYS file must be updated and then you must shutdown OS/2 and
  restart the computer.

o Add more memory if possible.

o Rerun the program


ΓòÉΓòÉΓòÉ 170. Unacceptable import file ΓòÉΓòÉΓòÉ

ERROR: You are trying to import a file that is not in the correct import file
format.

CAUSE: Possible causes are:

o The file does not have a recognizeable header in the file. The file was
  either modified after being exported, or was created incorrectly. The first
  column of the first line must start with: /*AVC*/

ACTION: Try one of the following:

o Verify the file name.

o Edit the file and make sure that the first column of the first line starts
  with: /*AVC*/

o If possible export the story and try to import it again.


ΓòÉΓòÉΓòÉ 171. Empty import file ΓòÉΓòÉΓòÉ

WARNING: The file you imported is empty.

CAUSE: There are no lines in the import file.

ACTION: Try one of the following:

o Add story lines to the import file.

o If possible, export the story and try to import again.


ΓòÉΓòÉΓòÉ 172. Invalid substory ΓòÉΓòÉΓòÉ

ERROR: While playing the current story a statement was processed that causes a
substory to be played.  The substory contains one or more errors, making it
invalid.

CAUSE: An error was detected on a line in a substory.

ACTION: Try one of the following:

o Open the substory that is named in the error message and correct the error on
  the line referenced in the error message.  Then, run the story again.


ΓòÉΓòÉΓòÉ 173. Unacceptable syntax ΓòÉΓòÉΓòÉ

ERROR: There is unrecognized syntax in the import file.

CAUSE: Possible causes are:

o The file was either modified after being exported or the file was created new
  with improper syntax.

ACTION: Try one of the following:

o Edit the import file and correct the problem.

o If possible export the story and try to import it again.


ΓòÉΓòÉΓòÉ 174. Import successful. ΓòÉΓòÉΓòÉ

INFORMATION: The imported story is now in the copy buffer.

CAUSE: The file has been imported successfully and is ready for pasting.

ACTION: Position the cursor (text view) or select the frame (graphics view)
where the imported story should be added. Click on Edit, and then Paste.


ΓòÉΓòÉΓòÉ 175. No search string specified. ΓòÉΓòÉΓòÉ

ERROR: You did not enter a string in the search string entry field.

CAUSE: The program needs information (a search string) to search for.

ACTION: Try one of the following:

o Enter a search string.

o Close the window by clicking on the Cancel button.


ΓòÉΓòÉΓòÉ 176. String not found. ΓòÉΓòÉΓòÉ

INFORMATION: You specified information (search string) that is not in the
story.

CAUSE: The specified search string was not found in the story.

ACTION: Try one of the following:

o Enter another search string and click on the OK button.

o Close the window by clicking on the Cancel button.


ΓòÉΓòÉΓòÉ 177. Text style changed ΓòÉΓòÉΓòÉ

WARNING: The current text style has been changed.

CAUSE: You changed the current Text Style Definition and then chose another
style. The changed fields will be lost.

ACTION: Try one of the following:

o Select "Yes" accept the new style.

  This sets the new style and discards any of the previous choices.

o Select "No" to keep your current style.


ΓòÉΓòÉΓòÉ 178. Printer not available ΓòÉΓòÉΓòÉ

Error: The printer you selected could not be opened for output. The print
request is cancelled.

CAUSE: Possible causes are:

o The printer is not properly connected to the system.

o There is a problem with the printer driver.

ACTION: Try the following:

o Make sure the printer is properly configured and connected.


ΓòÉΓòÉΓòÉ 179. WARNING:  Changes to image will be discarded. ΓòÉΓòÉΓòÉ

WARNING: You have made a request that will cause the changes made to the
current image to be discarded.

CAUSE: Possible causes are:

o Making a request to open another image file

o Making a request to close the Text Plane Support window

ACTION: Try one of the following:

o Click on the OK button to continue and the changes will be discarded.

o Cancel the request by clicking on the Cancel button.  Use Save or Save as to
  save the changes made to the current image.  Then, make your request again.


ΓòÉΓòÉΓòÉ 180. Literal text will be PERMANENTLY merged with image, do you wish to continue? ΓòÉΓòÉΓòÉ

INFO: You are merging the text plane with the image plane.  Once you do this,
you will NOT be able to edit text fields separately from the image.  The text
fields become part of the image itself.

CAUSE: Possible causes are:

o Selecting the menu option to merge the image and text planes together.

ACTION: Try one of the following:

o Click on OK to continue merging the image and text planes

o Click on CANCEL to cancel the request to merge the image and text planes


ΓòÉΓòÉΓòÉ 181. Unable to start Text Plane Support...terminating. ΓòÉΓòÉΓòÉ

ERROR: An internal error was encountered when trying to create the Text Plane
Support window.  Text Plane Support cannot continue, it must be terminated.

CAUSE: Possible causes are:

o Too many tasks already running on the system.

ACTION: Try one of the following:

o End one or more of the tasks you already have running and try starting Text
  Plane Support again.


ΓòÉΓòÉΓòÉ 182. Do you wish to select another font? ΓòÉΓòÉΓòÉ

ERROR: The font required could not be loaded. list.

CAUSE: Possible causes are:

o The required font was not installed or was subsequently removed from the
  system.

ACTION: Try one of the following:

o Click on YES to get a list of available fonts to select from.

o Click on NO to cancel the request.


ΓòÉΓòÉΓòÉ 183. Creating an AVC-type file with a non-standard extension, do you wish to continue? ΓòÉΓòÉΓòÉ

INFO: You are saving the image to a file name that does not have the '_IM'
extension typical of AVC-type images.  All images, regardless of the type
initially read in, are saved by Text Plane Support as AVC-type.

CAUSE: Possible causes are:

o You changed the '_IM' extension appended to the file name when you entered a
  file name.

o You accidentally erased the '_IM' extension appended to the file name shown
  in the Save as... file name field.

ACTION: Try one of the following:

o Click on YES to save the file to the name specified, even though the
  extension is not '_IM'.

o Click on NO to cancel the Save as... request.  Select Save as... again and
  ensure that the '_IM' extension is retained when keying a file name.


ΓòÉΓòÉΓòÉ 184. Current style has been modified, continue without saving changes? ΓòÉΓòÉΓòÉ

INFO: You have made a request that will cause the style changes made to be
discarded.

CAUSE: Possible causes are:

o You pressed the Esc key while in the Text Style Definition dialog.

o You pressed the Copy Style button on the Text Style Definition dialog, but
  changes have already been made to the current style.

ACTION: Try one of the following:

o Click on YES to continue and discard any changes made to the style.

o Click on NO to cancel the request.  Click on Accept to the save the style
  changes.


ΓòÉΓòÉΓòÉ 185. Unable to find any required font files (._FN extension)...terminating. ΓòÉΓòÉΓòÉ

ERROR: Text Plane Support was unable to find any of the required font files on
the system.  Text Plane Support cannot continue, it will be terminated.

CAUSE: Possible causes are:

o Font files were not loaded when Builder/2 was installed.

o Font files were subsequently deleted after Builder/2 was installed.

ACTION: Try one of the following:

o Copy one or more of the font files from the installation disks/CD-ROM back
  onto the system.  Then try starting Text Plane Support again.


ΓòÉΓòÉΓòÉ 186. About to delete selected field, do you wish to continue? ΓòÉΓòÉΓòÉ

INFO: You have made a request to delete the currently selected text field or
trigger field.

CAUSE: Possible causes are:

o You selected the menu option to delete a field or used the Ctrl+D accelerator
  key.

ACTION: Try one of the following:

o Click on YES to delete the currently selected text or trigger field.

o Click on NO to cancel the request to delete the currently selected trigger
  field.


ΓòÉΓòÉΓòÉ 187. About to delete all fields, do you wish to continue? ΓòÉΓòÉΓòÉ

INFO: You have made a request to delete all text and trigger fields defined on
the current image.

CAUSE: Possible causes are:

o You selected the menu option to delete all text and trigger fields.

ACTION: Try one of the following:

o Click on YES to delete all text and trigger fields on the image.

o Click on NO to cancel the request to delete all text and trigger fields.


ΓòÉΓòÉΓòÉ 188. A text or trigger field must be selected first. ΓòÉΓòÉΓòÉ

ERROR: You made a request for a function that requires that a text or trigger
field be selected.

CAUSE: Possible causes are:

o You selected an option from a menu.

o You pressed one of the Toolbox buttons.

ACTION: Try one of the following:

o Select either a text or trigger field on the image and try your request
  again.


ΓòÉΓòÉΓòÉ 189. An image file must be opened first. ΓòÉΓòÉΓòÉ

ERROR: You selected a function that requires that an image file be opened
before the function can be performed.

CAUSE: Possible causes are:

o Text Plane Support was started via Builder/2 or Perfect Image/2 but the image
  file could not be loaded.

o A request was made to open an image file, the open request failed, so there
  is currently no image loaded in Text Plane Support.

ACTION: Try one of the following:

o Select Open from the File menu and open an image file.

o Close the Text Plane Support window.


ΓòÉΓòÉΓòÉ 190. Text mode is currently inactive. ΓòÉΓòÉΓòÉ

ERROR: You have made a request that applies to text fields, but text mode is
currently inactive.

CAUSE: Possible causes are:

o You selected a menu option that specifically applies to text fields.

o You used an accelerator key sequence that performs a function that
  specifically applies to text fields.

ACTION: Try one of the following:

o Press the text mode button in the Toolbox to activate text mode.

o Select the text mode option on the View menu to activate text mode.

o Use accelerator key Ctrl+T to activate text mode.


ΓòÉΓòÉΓòÉ 191. Both text and trigger modes are currently inactive. ΓòÉΓòÉΓòÉ

ERROR: You have made a request that applies to either text or trigger fields,
but both modes are currently inactive.

CAUSE: Possible causes are:

o You selected a menu option that applies to text or trigger fields.

o You used an accelerator key sequence that performs a function that applies to
  text or trigger fields.

ACTION: Try one of the following:

o Press the Text fields Tool box button to activate text mode.

o Select Text fields on the View menu to activate text mode.

o Use accelerator key Ctrl+T to activate text mode.

o Press the Trigger fields Tool box button to activate trigger mode.

o Select Trigger fields on the View menu to activate trigger mode.

o Use accelerator key Ctrl+R to activate trigger mode.


ΓòÉΓòÉΓòÉ 192. Maximum number of text and/or trigger fields reached. ΓòÉΓòÉΓòÉ

ERROR: You are trying the create a new text or trigger field, but you are
already at the maximum allowed.

CAUSE: Possible causes are:

o The total number of text and trigger fields is 255.  This is the maximum
  number of text and trigger fields allowed.

ACTION: Try one of the following:

o Delete any text or trigger fields that are not needed. Try your request to
  add the new text or trigger fields again.


ΓòÉΓòÉΓòÉ 193. Insufficient memory available. ΓòÉΓòÉΓòÉ

ERROR: Memory required by Text Plane Support could not be acquired.

CAUSE: Possible causes are:

o Too many tasks already running on the system.

o Not enough disk space remaining for OS/2 swapper file to use as virtual
  memory.

ACTION: Try one of the following:

o Terminate one or more tasks already running on the System.

o Try to free up as much space on the fixed disk for the operating system to
  use as virtual memory.


ΓòÉΓòÉΓòÉ 194. File already exists, do you want to replace it? ΓòÉΓòÉΓòÉ

INFO: You are trying to save the image file to a new file name, but a file with
that name already exists.

CAUSE: Possible causes are:

o You mistyped the name in the Save as... filename field.

ACTION: Try one of the following:

o Click on YES to replace the existing image file.

o Click on NO to cancel the Save as... request, the existing file will NOT be
  replaced.  Then select Save as... from the File menu again and key a
  different name.


ΓòÉΓòÉΓòÉ 195. Requested point size not available for this font. ΓòÉΓòÉΓòÉ

ERROR: The point size required does not exist for the font selected.

CAUSE: Possible causes are:

o You selected a headline-size font (fonts ending with an H) which contains
  only large point sizes, and the required point size is non-headline size.

o You selected a normal font which contains various small to medium point
  sizes, and the required point size is headline-size.

ACTION: Try one of the following:

o If you picked a headline-size font, pick a normal-size font instead. If you
  picked a normal font, select a headline font.


ΓòÉΓòÉΓòÉ 196. File not found. ΓòÉΓòÉΓòÉ

ERROR: Either the file specified could not be found or a component required by
that file could not be found.

CAUSE: The operating system could not find the file or a component required by
the file you specified.  An example of a component is a font file (_FN
extension).  Images that contain text have the font name(s) carried within the
image.  The named fonts must be installed and available.

ACTION: Do one of the following:

o Check your spelling.
o Verify that the named file exists.
o Ensure that the font named in the error message is installed on the system in
  the appropriate directory.


ΓòÉΓòÉΓòÉ 197. Permission was denied when attempting to access a file. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a file that is not available to you.

CAUSE: The file is already in use or locked.

ACTION: Do one of the following:

o Retry the operation.
o find out what application is using the file.
o Contact your administrator.


ΓòÉΓòÉΓòÉ 198. Too many files are open at one time. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use too many files.

CAUSE: The FILES system limits the number of files that can be open at any one
time.  The limit has been reached.

ACTION: Try the following:

o Close some currently open files.
o Or increase the value  for the number of files in the FILES= statement in
  your CONFIG.SYS, shutdown OS/2, and then restart the system by pressing the
  Ctrl + Alt + Del keys.
o Retry the operation after doing one of the above.


ΓòÉΓòÉΓòÉ 199. The file is already being used by an application. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a file that is already in use.

CAUSE: The file system prevents you from using a file that is in use or locked.

ACTION: Try the following:

o Stop any active applications not needed to find out which application is
  using the file.
o Retry the operation later when the file may be available.
o Shutdown OS/2 and restart the system by pressing the Ctrl + Alt + Del keys.


ΓòÉΓòÉΓòÉ 200. The file name is not permitted. ΓòÉΓòÉΓòÉ

ERROR: You've used a file name that is not recognized by the file system.

CAUSE: The file system does not accept the file name containing the characters
you typed.

ACTION:

o Correct the file name

  In the OS/2 FAT file system:

   - File names can contain up to eight letters, digits, or the following
     special characters:

          $ % ' - _ @ { } ~ ! # ( )

   - File extensions can be a combination of up to three letters, digits, or
     special characters, preceded by a period.

  In the OS/2 high performance file system (HPFS):

   - The length of the complete path (drive, directories, and file name) cannot
     exceed 260 characters.
   - File names and directories can be up to 255 characters long.
   - Blank characters or periods are accepted within the name (but they are
     ignored at the end of a name). You can also use any of these special
     characters:

          + = ; , [ ]


ΓòÉΓòÉΓòÉ 201. The named file already exists. ΓòÉΓòÉΓòÉ

ERROR: You are trying to save a file that has the same name as an existing one.

CAUSE: The file system will not let you overwrite an existing file.

ACTION: Do the following:

o Select a different name.
o Erase or rename the existing file.
o Retry the operation.


ΓòÉΓòÉΓòÉ 202. The object was not found on disk. ΓòÉΓòÉΓòÉ

ERROR: You provided a name of an object that could not be found.

CAUSE: The file system could not find an object by that name.

ACTION: Do the following:

o Check your spelling.
o Check to see that the named file exists.


ΓòÉΓòÉΓòÉ 203. Not enough memory is available. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use more memory than the system has.

CAUSE: The system could allocate any more storage. None was available.

ACTION: Do the following:

o Close any windows that are not needed.
o Close all applications not being used.
o Archive any large or infrequently used files or delete any unnecessary files
  on the disk where the SWAPPER.DAT file exists.


ΓòÉΓòÉΓòÉ 204. No disk space is available on the named drive. ΓòÉΓòÉΓòÉ

ERROR: You are trying to store a file where no space is available.

CAUSE: The file you are trying to save is larger than the disk space available.

ACTION: Do the following:

o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk.
o Retry the operation.


ΓòÉΓòÉΓòÉ 205. The file extension is not permitted. ΓòÉΓòÉΓòÉ

ERROR: You specified a file extension that is not permitted.

CAUSE: Application does not recognize the file extension.

ACTION: Do the following:

o Check your spelling.
o Specify another file extension.


ΓòÉΓòÉΓòÉ 206. The drive named is either incorrect or not ready. ΓòÉΓòÉΓòÉ

ERROR: You specified a drive that doesn't exist or is not ready.

CAUSE: The system could not communicate with the named drive.

ACTION: Do the following:

o Check your spelling.
o Check the drive to see if it is ready.
o Retry the operation.


ΓòÉΓòÉΓòÉ 207. Unable to open image ΓòÉΓòÉΓòÉ

ERROR: Unable to open the image.  Open cancelled.

CAUSE: Possible causes are:

o The file specified is not a supported image type.

o No MMIO procedure is installed for the image format.

o The image has an unsupported bit count.

o Insufficient storage space is available.

o The file is being used by another application.

ACTION: Try one of the following:

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for your
     application.

   - Archive any large or infrequently used files on the drive where the image
     is being saved (the directory is provided in the error window).

   - Retry opening the image

o Release access to the image by other applications.

o Reinstall the MMIO procedures.

o Refer to the application documentation for supported image format bit counts.


ΓòÉΓòÉΓòÉ 208. Program cannot display this image. ΓòÉΓòÉΓòÉ

ERROR: You are attempting to display an image in an unsupported format.

CAUSE: The image is not displayable by this program. Possible causes are:

o The image is not one of the following formats:

   AVC image

   OS/2 1.3, OS/2 2.x, WIN 3.0 bitmap (BMP)

   PCX Image

   TIF image

   Targa image

o The image uses an unsupported data compression.

o The image contains an unsupported number of colors. Supported are 8 bit
  (pixel) images (256 colors).

ACTION: Use an image conversion program to convert the image to a supported
format.


ΓòÉΓòÉΓòÉ 209. This operation results in loss of AVC text, triggers, input and output fields. ΓòÉΓòÉΓòÉ

WARNING:  You are attempting an operation that results in loss of AVC text,
triggers, input and output fields.

CAUSE:  The image being modified by contains other objects in addition to the
image data, such as a separate text object.  These other objects will be
discarded if the operation is continued.

ACTION: Select OK to continue the operation and retain only the image data.


ΓòÉΓòÉΓòÉ 210. The named file already exists.  Select OK to complete the save. ΓòÉΓòÉΓòÉ

WARNING:  You tried to save an image using a file name that already exists on
disk.

CAUSE: The file name specified already exists on disk.

ACTION: Select OK to save the image using the file name specified.  The
existing file will be replaced.  Select Cancel to stop the save operation.


ΓòÉΓòÉΓòÉ 211. The image must be saved before editing text.  Select OK to save and continue. ΓòÉΓòÉΓòÉ

WARNING:  You tried to edit image text, but the image has not been saved to
disk.

CAUSE: Possible causes:

o The image is new and has never been saved to disk.
o The image has been modified since last being saved.

ACTION: Select OK to save the image and continue to the text editor. Select
Cancel to return without going to the text editor.


ΓòÉΓòÉΓòÉ 212. An error occurred when attempting locate the printer. ΓòÉΓòÉΓòÉ

ERROR:  You tried to print an image, but the printer was not found.

CAUSE: Possible causes:

o The printer is not ready or set up properly.
o The printer driver has a problem.
o The name of the printer is not correct.

ACTION: Check all of the possible causes, and then try to print again.


ΓòÉΓòÉΓòÉ 213. A GSP error occurred. ΓòÉΓòÉΓòÉ

ERROR: The Graphic Screen Processor (GSP) detected an error. The GSP and system
return codes are included in the message.

CAUSE: An internal error was detected while handling an image.

ACTION: Contact your administrator.


ΓòÉΓòÉΓòÉ 214. Window creation failed! ΓòÉΓòÉΓòÉ

ERROR: A window could not be created.

CAUSE: A system error was returned by the operating system while attempting to
create a window. Perfect Image/2 will stop.

ACTION: Restart the program. If this error repeats, contact your administrator.


ΓòÉΓòÉΓòÉ 215. Window positioning failed! ΓòÉΓòÉΓòÉ

ERROR: The window could not be repositioned.

CAUSE: The program detected an error while repositioning a window. The
operating system responded with an error. Perfect Image/2 will stop.

ACTION: Try one of the following:

o Restart the program.
o If the error continues contact your administrator.


ΓòÉΓòÉΓòÉ 216. Insufficient storage available. ΓòÉΓòÉΓòÉ

ERROR: You tried to do something that requires more memory than you have
available.

CAUSE: All available machine storage is being used. You may be out of disk
space or the system swapper file has reached its maximum capacity.

ACTION: Try one of the following and then retry the action:

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Archive any large or infrequently used files.
o Close any image windows that are not needed.
o Close all applications not being used.


ΓòÉΓòÉΓòÉ 217. Another instance of Perfect Image/2 is already ΓòÉΓòÉΓòÉ

using the video capture function.

ERROR: You are trying to use video capture, but it is already being used.

CAUSE: You are trying to access the Video Capture Adapter (VCA) with multiple
instances of Perfect Image/2. Only one instance is allowed to have access to
the adapter.

ACTION: Do one of the following:

o Use the other instance of Perfect Image/2 that has access to the VCA.
o End the other instance of Perfect Image/2 and retry the video capture
  initialization.
o


ΓòÉΓòÉΓòÉ 218. The VCA device driver ICDD.SYS can not be found. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use the Video Capture Adapter (VCA), but the device
driver ICDD.SYS cannot be found.

CAUSE: Possible causes are:

o The system device driver file (ICDD.SYS) is missing.
o The DEVICE statement for ICDD.SYS is missing in your CONFIG.SYS file.
This file should have been copied to the system during product installation.

ACTION: Do one of the following:

o Verify that a DEVICE statement for ICDD.SYS is in your CONFIG.SYS file. A
  statement similar to the following is needed in your CONFIG.SYS file in order
  to use the VCA:

        DEVICE= <your drive>:\<your directory>\BIN\ICDD.SYS

  For example, if the defaults are used for installation, the required DEVICE
  statement is:

        DEVICE=C:\PIMAGE\BIN\ICDD.SYS

o Reinstall Perfect Image/2


ΓòÉΓòÉΓòÉ 219. The VCA adapter card cannot be found. ΓòÉΓòÉΓòÉ

ERROR: You tried to use the Video Capture Adapter (VCA), but it was not
available.

CAUSE: You have not installed the adapter, or the DEVICE statement required in
your CONFIG.SYS is incorrect.

ACTION: Do one of the following:

o Install the Video Capture Adapter (VCA).
o Verify that a DEVICE statement for ICDD.SYS is in your CONFIG.SYS file. A
  statement similar to the following is needed in your CONFIG.SYS file in order
  to use the VCA:

        DEVICE= <your drive>:\<your directory>\BIN\ICDD.SYS

  For example, if the defaults are used for installation, the required DEVICE
  statement is:

        DEVICE=C:\PIMAGE\BIN\ICDD.SYS

o Reinstall Perfect Image/2


ΓòÉΓòÉΓòÉ 220. The VCA card contains bad TARAMs. ΓòÉΓòÉΓòÉ

ERROR: You were trying to use video capture when a hardware error occurred.

CAUSE: A hardware error was detected in the Video Capture Adapter (VCA) during
the video capture process.

ACTION: Contact your administrator.


ΓòÉΓòÉΓòÉ 221. A system error occurred using the VCA card. ΓòÉΓòÉΓòÉ

ERROR: Your were using the Video Capture Adapter (VCA) card when an error was
detected.

CAUSE: A system error was detected during video capture.

ACTION: Try one of the following:

o Restart the program.
o Run VCA diagnostic program.
o Contact your administrator.


ΓòÉΓòÉΓòÉ 222. Image has been modified.  Do you want to save it? ΓòÉΓòÉΓòÉ

WARNING: You are closing the image without saving the changes.

CAUSE: Perfect Image/2 will not discard changes you have made to images unless
you say it is OK to do so.

ACTION: Do one of the following:

o To save the image, click on Yes.
o To discard the changes, click on No
o To cancel the close and return to the image, click on Cancel.


ΓòÉΓòÉΓòÉ 223. Height is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered the height of an image that was not accepted.

CAUSE: The height is limited by two things:

o Any number from 1 to 9999.
o The amount of available memory and disk space available.

ACTION: Do one of the following:

o Enter a number from 1 to 9999.
o Enter a smaller number.


ΓòÉΓòÉΓòÉ 224. Width is out of range or too large. ΓòÉΓòÉΓòÉ

ERROR: You entered the width of an image that was not accepted.

CAUSE: The value for width must be within the range from 1 to 9999.

ACTION: Do one of the following:

o Enter a new number from 1 to 9999.
o Try a smaller number.


ΓòÉΓòÉΓòÉ 225. Hue is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for Hue that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value in degrees only (from
a negative 180 degrees to a positive 180 degrees). This covers the full
spectrum of color (360 degree color wheel).

ACTION: Enter any acceptable value for Hue: from 180 and -180.


ΓòÉΓòÉΓòÉ 226. Saturation is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for Saturation that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value in percentage only
(from a negative 100% to a positive 100%).

ACTION: Enter a saturation value from 100 to -100.


ΓòÉΓòÉΓòÉ 227. Contrast is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for contrast that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value in percentage only
(from a negative 100% to a positive 100%).

ACTION: Enter a contrast value from 100 to -100.


ΓòÉΓòÉΓòÉ 228. Brightness is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for brightness that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value in percentage only
(from a negative 100% to a positive 100%).

ACTION: Enter a brightness value from 100 to -100.


ΓòÉΓòÉΓòÉ 229. Shadow is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for shadow that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value for shadow from 0 to
255.  The value for shadow cannot be greater than the value for highlight.

ACTION: Enter a shadow value from 0 to 255 but not greater than highlight.


ΓòÉΓòÉΓòÉ 230. Highlight is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for highlight that cannot be accepted.

CAUSE: Perfect Image/2 lets you change the current value for highlight from 0
to 255.  The value for highlight cannot be less than the value for shadow.

ACTION: Enter a highlight value from 0 to 255 but not less than shadow.


ΓòÉΓòÉΓòÉ 231. Fuzz width is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for Fuzz width that cannot be accepted.

CAUSE: Perfect Image/2 lets you enter a value for fuzz width from 0 (no
blending) to 10 (a 10 pel depth for blending).

ACTION: Enter a fuzz width value from 0 to 10.


ΓòÉΓòÉΓòÉ 232. Transparency is out of range. ΓòÉΓòÉΓòÉ

ERROR: You entered a value for Transparency that cannot be accepted.

CAUSE: Perfect Image/2 lets you enter a value for Transparency from 0 (no
transparency) to 100 (the pasted segment is invisible).

ACTION: Enter a transparency value from 0 to 100.


ΓòÉΓòÉΓòÉ 233. <All Files> not acceptable as type ΓòÉΓòÉΓòÉ

ERROR: You entered <All Files> for image file type.

CAUSE: <All Files> can be used to show all file types in a selected directory,
but may not be used as an image file format type when saving an image.

ACTION: Enter an acceptable image file type before attempting to save the file.


ΓòÉΓòÉΓòÉ 234. An error occurred when attempting ΓòÉΓòÉΓòÉ

to save the profile settings.

ERROR: An error occurred when you tried saving the profile settings.

CAUSE: Perfect Image/2 could not save the profile settings in the ULTITOOL.INI
file. There may have been a system error when attempting to write to the file,
or the operating system could not find a read/write drive in the search path.

The search path is the:

o Current directory

o Directory where .EXE resides

o Path given in UMPATH environment variable

ACTION: Do one of the following:

o Set the current directory to a drive that can write data to disk.
o Verify that the directory in the UMPATH variable specifies a drive that can
  write data on a disk.


ΓòÉΓòÉΓòÉ 235. The file was not found. ΓòÉΓòÉΓòÉ

ERROR: You specified a file that could not be found.

CAUSE: The operating system could not find the file you specified.

ACTION: Do one of the following

o Check your spelling.
o Verify that the named file exists.


ΓòÉΓòÉΓòÉ 236. Permission was denied when attempting to access a file. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a file that is not available to you.

CAUSE: The file is already in use or locked.

ACTION: Do one of the following:

o Retry the operation.
o find out what application is using the file.
o Contact your administrator.


ΓòÉΓòÉΓòÉ 237. Too many files are open at one time. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use too many files.

CAUSE: The FILES system limits the number of files that can be open at any one
time.  The limit has been reached.

ACTION: Try the following:

o Close some currently open files.
o Or increase the value  for the number of files in the FILES= statement in
  your CONFIG.SYS, shutdown OS/2, and then restart the system by pressing the
  Ctrl + Alt + Del keys.
o Retry the operation after doing one of the above.


ΓòÉΓòÉΓòÉ 238. The file is already being used by an application. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a file that is already in use.

CAUSE: The file system prevents you from using a file that is in use or locked.

ACTION: Try the following:

o Stop any active applications not needed to find out which application is
  using the file.
o Retry the operation later when the file may be available.
o Shutdown OS/2 and restart the system by pressing the Ctrl + Alt + Del keys.


ΓòÉΓòÉΓòÉ 239. The file name is not permitted. ΓòÉΓòÉΓòÉ

ERROR: You've used a file name that is not recognized by the file system.

CAUSE: The file system does not accept the file name containing the characters
you typed.

ACTION:

o Correct the file name

  In the OS/2 FAT file system:

   - File names can contain up to eight letters, digits, or the following
     special characters:

          $ % ' - _ @ { } ~ ! # ( )

   - File extensions can be a combination of up to three letters, digits, or
     special characters, preceded by a period.

  In the OS/2 high performance file system (HPFS):

   - The length of the complete path (drive, directories, and file name) cannot
     exceed 260 characters.
   - File names and directories can be up to 255 characters long.
   - Blank characters or periods are accepted within the name (but they are
     ignored at the end of a name). You can also use any of these special
     characters:

          + = ; , [ ]


ΓòÉΓòÉΓòÉ 240. The named file already exists. ΓòÉΓòÉΓòÉ

ERROR: You are trying to save a file that has the same name as an existing one.

CAUSE: The file system will not let you overwrite an existing file.

ACTION: Do the following:

o Select a different name.
o Erase or rename the existing file.
o Retry the operation.


ΓòÉΓòÉΓòÉ 241. The object was not found on disk. ΓòÉΓòÉΓòÉ

ERROR: You provided a name of an object that could not be found.

CAUSE: The file system could not find an object by that name.

ACTION: Do the following:

o Check your spelling.
o Check to see that the named file exists.


ΓòÉΓòÉΓòÉ 242. Not enough memory is available. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use more memory than the system has.

CAUSE: The system could allocate any more storage. None was available.

ACTION: Do the following:

o Close any image windows that are not needed.
o Close all applications not being used.
o Archive any large or infrequently used files or delete any unnecessary files
  on the disk where the SWAPPER.DAT file exists.


ΓòÉΓòÉΓòÉ 243. No disk space is available on the named drive. ΓòÉΓòÉΓòÉ

ERROR: You are trying to store a file where no space is available.

CAUSE: The file you are trying to save is larger than the disk space available.

ACTION: Do the following:

o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk.
o Retry the operation.


ΓòÉΓòÉΓòÉ 244. The file extension is not permitted. ΓòÉΓòÉΓòÉ

ERROR: You specified a file extension that is not permitted.

CAUSE: Perfect Image/2 does not recognize the file extension.

ACTION: Do the following:

o Check your spelling.
o Specify another file extension.


ΓòÉΓòÉΓòÉ 245. The drive named is either incorrect or not ready. ΓòÉΓòÉΓòÉ

ERROR: You specified a drive that doesn't exist or is not ready.

CAUSE: The system could not communicate with the named drive.

ACTION: Do the following:

o Check your spelling.
o Check the drive to see if it is ready.
o Retry the operation.


ΓòÉΓòÉΓòÉ 246. Unable to open image ΓòÉΓòÉΓòÉ

ERROR: Unable to open the image.  Open cancelled.

CAUSE: Possible causes are:

o The file specified is not a supported image type.

o No MMIO procedure is installed for the image format.

o The image has an unsupported bit count.

o Insufficient storage space is available.

o The file is being used by another application.

ACTION: Try one of the following:

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for Perfect
     Image/2.

   - Archive any large or infrequently used files on the drive where the image
     is being saved (the directory is provided in the error window).

   - Retry opening the image

o Release access to the image by other applications.

o Reinstall Perfect Image/2 following the instructions in the Perfect Image/2
  Users Guide (to reinstall MMIO procedures).

o Refer to the Perfect Image/2 Users Guide for supported image format bit
  counts.


ΓòÉΓòÉΓòÉ 247. Unable to save image ΓòÉΓòÉΓòÉ

ERROR: Unable to save the image.  Save cancelled.

CAUSE: Possible causes are:

o You don't have permission to write the file.

o The diskette is write protected.

o Insufficient storage space is available.

o The file is being used by another application.

o The path specified is invalid.

ACTION: Try one of the following:

o Check the path name spelling.

o Check the access permissions on the file, directory, or drive.

  Method varies by file system type (for example, FAT, HPFS, or LAN drive).
  Contact your administrator.

o If saving to a diskette, check the position of the write protect tab.

o Make sure there is sufficient storage space:

   - Verify that your system meets the minimum requirements for Perfect
     Image/2.

   - Archive any large or infrequently used files on the drive where the image
     is being saved (the directory is provided in the error window).

   - Retry saving the file.


ΓòÉΓòÉΓòÉ 248. Unable to find file "UTSYSPAL.LUT". ΓòÉΓòÉΓòÉ

ERROR: Unable to find file "UTSYSPAL.LUT".  Perfect Image/2 will be closed.

CAUSE: Possible causes are:

o The file is not installed in your system.

o The environment variable UMPATH does not specify the directory where the file
  is stored.

ACTION: Try the following:

o Reinstall Perfect Image/2 following the instructions in the Perfect Image/2
  Users Guide.


ΓòÉΓòÉΓòÉ 249. Value entered is too long. Change not accepted. ΓòÉΓòÉΓòÉ

ERROR: You have entered too many characters for the field. (The field name is
provided in the error window.)

CAUSE: You have entered too many characters for the field.

ACTION: Re-enter the data.


ΓòÉΓòÉΓòÉ 250. Value conflicts with the field attribute.                          ter. ΓòÉΓòÉΓòÉ

ERROR: You have entered data which contradicts the field attribute. (The field
name is provided in the error window.)

CAUSE: Possible causes are:

o There is non-numeric data in a numeric field.
o Incorrect data for date, time, or timestamp field.
o Unacceptable data for logical field.
o Value is outside the range that is acceptable to integer or decimal field.

ACTION: Try one of the following:

o correct the value according to the field attribute format provided in this
  message.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 251. Can't open the database and table. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a database and table that cannot be opened. (The
database and table names are provided in the error window.)

CAUSE: Possible causes are:

o Incorrect database or table name.
o Incorrect logon userid or password.
o Incorrect Server id or Oracle.

ACTION: Try one of the following:

o Correct the database name, table name, logon userid, password,  or server ID
  and try it again.
o If you get this error message by double clicking the query result file, try
  running the query again.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 252. Cannot open database table. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a database that could not be opened. (The
database type and name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the database name.
o The file doesn't exist.
o The file exists but is not in the correct DBase format.

ACTION: Try one of the following:

o Use the correct DBase name.
o If you get this error message by double clicking the query result file, try
  running the query again.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 253. Database has been changed. Save the change ? ΓòÉΓòÉΓòÉ

ERROR: You tried to exit without saving the change to database.

CAUSE: The program asks for confirmation before saving the changes to the
database.

ACTION: Try one of the following:

o Click on 'Yes' if you want to save the changes and then exit the Query Result
  Viewer.
o Click on 'No' to exit the Query Result Viewer without saving the changes.
o Click on 'Cancel' to cancel to action of exiting the Query Result Viewer.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 254. Database is too big to view! ΓòÉΓòÉΓòÉ

ERROR: You are trying to display more records than the Query Result Viewer can
handle.

CAUSE: Possible causes are:

o A memory allocation error.

ACTION: Try one of the following:

o Rewrite the query so that less database records/rows are selected.
o Add more memory to your computer.
o Try to run it later when more resource is available.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 255. Busy loading another database. Please try later! ΓòÉΓòÉΓòÉ

ERROR: You tried to open another database while the Query Result Viewer is
already loading a database or query result.

CAUSE: Possible causes are:

o You are opening another database too soon.

ACTION: Try one of the following:

o Open the other database later.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 256. Can't not read database record. ΓòÉΓòÉΓòÉ

ERROR: The program encountered an error while fetching a record from SQL-like
database. The database and the cause of the error are reported in the window.

CAUSE: See the message for specific detail.

ACTION: Try one of the following:

o Try to open the database later.
o Contact your database administrator.


ΓòÉΓòÉΓòÉ 257. Can't not read database record.                                    e ? ΓòÉΓòÉΓòÉ

ERROR: The program encountered an error when fetching a record from a dBase IV
table.

CAUSE: See the message for specific detail.

ACTION: Try one of the following:

o Try to open the database later.
o Contact your database administrator.


ΓòÉΓòÉΓòÉ 258. Missing an input field! ΓòÉΓòÉΓòÉ

ERROR: You did not fill out all the information required to create or convert a
Light Table folder.

CAUSE: Possible causes are:

o You didn't fill out the Folder Name for the LTFolder query result.

o You didn't fill out the Folder Name or select the Title field for the
  database query result. The Title field is used as the object title for
  objects created in the folder.

ACTION: Enter the missing name(s).


ΓòÉΓòÉΓòÉ 259. Missing an input field! ΓòÉΓòÉΓòÉ

ERROR: You did not fill out all the information required to open an Oracle
table or an OS/2 Database Manager table.

CAUSE: Possible causes are:

o You didn't fill out the Database Name and/or Table name.

o You didn't fill out the userid or password.

o You didn't fill out the Server name.

ACTION: Enter the missing name(s).


ΓòÉΓòÉΓòÉ 260. SQL statement failed. ΓòÉΓòÉΓòÉ

ERROR: The program has generated a SQL statement that failed. (The statement
that failed is provided in the error window.)

CAUSE: Possible causes are:

o Incorrect field name or table name in SQL statement.

o Incorrect field value in SQL statement.

o No record in the table satisfies the criteria specified in the WHERE clause.

o You do not have authority to update the record in the table.

ACTION: Try one of the following:

o Check that the field exists in the table.

o Correct the value for the field in the SQL statement (the field that the SQL
  statement is updating) and save it again.

o Verify that you have the authority to change fields in the table specified in
  the SQL statement.

o Verify that the record (the record that satisfies the criteria specified in
  the WHERE clause) exists in the table.


ΓòÉΓòÉΓòÉ 261. Drag/Drop error: Unable to allocate memory ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but the system cannot allocate
enough memory.

CAUSE: System memory is unavailable.

ACTION: Try one of the following:

o Try to drag and drop the object again.

o Close unneeded applications or windows.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 262. Drag/Drop error: Unable to allocate memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but the system cannot allocate
more memory.

CAUSE: Memory is unavailable.

ACTION: Try one of the following:

o Try to drag and drop the object again.

o Close unneeded applications or windows.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 263. Drag/Drop error: Unable to access shared memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but memory is not available. (The named shared memory object is provided in the
error window.)

CAUSE: Memory is unavailable.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 264. Drag/Drop error: Unable to access drag data. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: The system is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Shutdown OS/2 and restart the system, then try to drag and drop the object
  again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 265. Drag/Drop error: Drop Operation is not allowed. ΓòÉΓòÉΓòÉ

ERROR: You are using a release of Query Result Viewer that does not permit
dropping objects.

CAUSE: This release does not support dropping objects.

ACTION: Avoid dropping objects or get a later release of Workplace/2.


ΓòÉΓòÉΓòÉ 266. Drag/Drop error: Unable to free unused resources. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: System is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Shutdown OS/2 and restart the system, then try to drag and drop the object
  again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 267. Drag/Drop error: Unable to free unused resources. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: System is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Shutdown OS/2 and restart the system, then try to drag and drop the object
  again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 268. Drag/Drop error: Unable to complete drag and drop. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: Possible causes are:

o The system is busy.
o Memory is not available.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Close unneeded applications or windows.
o Delete any unnecessary files on the disk
o Shutdown OS/2 and restart the system, then try to drag and drop the object
  again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 269. Drag/Drop error: Unable to access Container information. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: Possible causes are:

o Query Result Viewer is not responding.
o System is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Restart the Query Result Viewer.
o Shutdown OS/2 and restart the system, then try to drag and drop the object.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 270. Drag/Drop error: Unable to access Drag/Drop data. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: The system is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Restart the Query Result Viewer.
o Shutdown OS/2 and restart the system, then try to drag and drop the object.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 271. Drag/Drop error: Unable to access Drag/Drop data. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: The system is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Restart the Query Result Viewer.
o Shutdown OS/2 and restart the system, then try to drag and drop the object
  again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 272. Drag/Drop error: Cannot create data for Drag/Drop. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: Possible causes are:

o Query Result Viewer is not responding.
o The system is busy.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Close and Restart the Query Result Viewer.
o Shutdown OS/2 and restart the system, then try to drag and drop the object.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 273. Drag/Drop error: Unable to update target database. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object into a database but it fails.

CAUSE: Possible causes are:

o The program cannot put a record into the target database.
o The database is unavailable for write access.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Verify availability and access permissions of the database.
o Contact your database administrator.


ΓòÉΓòÉΓòÉ 274. Drag/Drop error: Closing database failed. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails. (The database name is provided in the error window.)

CAUSE: Possible causes are:

o The Program cannot open or close database.
o The database is being used by other programs.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Verify availability and access permissions of database.
o Contact your database administrator.


ΓòÉΓòÉΓòÉ 275. Drag/Drop error: Error in setting up Drag/Drop data record. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object using the Query Result Viewer
but it fails.

CAUSE: The drag and drop data record is too large.

ACTION: Try one of the following:

o Try to drag and drop the object again.
o Restart the Query Result Viewer.
o Shutdown OS/2 and restart the system.
o Try to drag and drop the object again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 276. Folder creation failed. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create a Light Table folder but the process failed.
(The cause of error is provided in the error window.)

CAUSE: Possible causes are:

o A memory allocation error.
o The Workplace/2 server for PM application is not running.
o The class dll for Light Table folder cannot be loaded.
o The message queue or event semaphore was destroyed.
o The system is busy.

ACTION: Try one of the following:

o Try the request later.
o Open the Templates folder and retry your request.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 277. Object creation in Light Table folder failed. ΓòÉΓòÉΓòÉ

ERROR: The LTDataFile object or LT Reference object creation failed. (The cause
of error is provided in the error window.)

CAUSE: Possible causes are:

o The system is busy.
o A memory allocation error.
o The Workplace/2 sever for PM application is not running.
o The class dll for the LT Reference object cannot be loaded.
o The message queue or event semaphore was destroyed.

ACTION: Try one of the following:

o Try the request later.
o Open the Templates folder and retry your request.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 278. Folder was created but not completed. ΓòÉΓòÉΓòÉ

ERROR: You created a Light Table folder, but encountering errors while creating
folder schema.

CAUSE: Possible causes are:

o Cannot get folder schema from the original Light Table folder

o Cannot put folder schema to the newly created Light Table folder

o Cannot get logon information from the original Light Table folder

o Cannot put logon information to the newly created Light Table folder

o Cannot get  EA schema from the original Light Table folder

o Cannot put  EA schema to the newly created Light Table folder

ACTION: Try one of the following:

o If original Light Table folder was deleted, renamed, or moved, do not try
  this request again, it will not work.
o Otherwise, you can try this request again.


ΓòÉΓòÉΓòÉ 279. Light Table folder conversion was completed with error ! ΓòÉΓòÉΓòÉ

ERROR: You have converted a Light Table folder but some LT Reference objects
within the folder were not created.

CAUSE: LTReference class DLL can't be loaded.

ACTION: None required.


ΓòÉΓòÉΓòÉ 280. Query Result contains no query information! ΓòÉΓòÉΓòÉ

ERROR: Your query result file (file type is LT Query Result) does not contain
query result information.

CAUSE: You did not perform the query via 'Run Query' from within the Query
Sequencer.

ACTION: Perform 'Run Query' from within the Query Sequencer folder where the
query result file resides.


ΓòÉΓòÉΓòÉ 281. No file extension for Light Table folder request.                            extension is rejected. ΓòÉΓòÉΓòÉ

ERROR: You are trying to attach a dBASE format file to a Light Table folder.
But this dBASE format file, which is actually the query result file is not
valid for it doesn't have file extension.

CAUSE: Query result file doesn't have file extension.

ACTION: Try these steps:

 1. Exit Query Result Viewer and then

    a. Change the title of the query result object to contain the character '.'

    b. Double click on the query result object

       This brings up the Query Result Viewer

    c. Retry the request.


ΓòÉΓòÉΓòÉ 282. Database open error. Changes can't be saved! ΓòÉΓòÉΓòÉ

ERROR: The program is trying to save changes to the database but the database
could not be opened. (The database name and actual cause of the error is
provided in the error window.)

CAUSE: Possible causes are:

o memory allocation error.
o See the message itself.

ACTION: Try one of the following:

o Try to save it later.
o Verify that the datbase still exist and retry the request.
o Contact your Administrator.


ΓòÉΓòÉΓòÉ 283. Cannot find original folder. No folder conversion performed! ΓòÉΓòÉΓòÉ

ERROR: You are trying to convert a query result file to a Light Table folder
but the original Light Table folder (from which the query result was generated)
could not be found. (The Light Table folder name is provided in the error
window.)

CAUSE: The original Light Table folder was deleted, renamed, or moved.

ACTION: Rerun the query from within the Query Sequencer and then try the
request again.


ΓòÉΓòÉΓòÉ 284. Can't save the change due to memory allocation error. ΓòÉΓòÉΓòÉ

ERROR: Unable to delete record or change field - memory allocation.

CAUSE: A memory allocation error.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o Try to do the change later.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 285. Cannot construct SQL statement - memory allocation.                 error. ΓòÉΓòÉΓòÉ

ERROR: memory allocation error.

CAUSE: Memory is unavailable.

ACTION: Try one of the following:

o Try to save the changes to database at a later time.
o Close unneeded applications or windows.
o Shutdown OS/2 and restart the system.


ΓòÉΓòÉΓòÉ 286. Input file cannot be processed. ΓòÉΓòÉΓòÉ

ERROR: You attempted to browse a file but the browse failed. (The file name is
provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.
o The file does not exist or is empty.
o The format of the file is not supported by Browse.
o The file is in use by another process.
o A system input or output (I/O) error occurred while opening the file.

ACTION: Try one of the following:

o Correct the file name.
o Make sure the file exists.
o Get another copy of the file from another source.
o Verify that the browser you started is the proper browser for the format of
  the file.
o Stop the other process that is using the file.
o Try to browse the file again.


ΓòÉΓòÉΓòÉ 287. No search string entered. ΓòÉΓòÉΓòÉ

ERROR: You attempted a search but the Search field was blank.

CAUSE: Possible causes are:

o You left the Search field blank.
o You entered blank characters only.

ACTION: Enter a search string.


ΓòÉΓòÉΓòÉ 288. Search string was not found. ΓòÉΓòÉΓòÉ

ERROR: You entered a string that was not found. (The search began at the
current line and searched to the end of the file. The search string is included
in the error window.)

CAUSE: Possible causes are:

o The string you are looking for does not exist.
o You misspelled the search string.
o The current line is beyond the last occurrence of the string.

ACTION: Try one of the following:

o Enter a new string.
o Correct the search string.
o Move to the top of the file.


ΓòÉΓòÉΓòÉ 289. Can't open the query file. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a Light Table Query file but it failed. (The
query file name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.
o The file doesn't exist.
o The file exists but is not a LT Query type.

ACTION: Try one of the following:

o Correct the file name.
o Create a LT Query file from a template.


ΓòÉΓòÉΓòÉ 290. Memory allocation error. ΓòÉΓòÉΓòÉ

ERROR: A memory allocation error stopped the process.

CAUSE: Memory is unavailable.

ACTION: Try one of the following:

o Close unneeded applications or windows.
o Shutdown OS/2 and restart the system.
o Try to edit the LT Query file again.


ΓòÉΓòÉΓòÉ 291. No Light Table folder exists. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to display the list of Light Table folders but no
Light Table folder exists.

CAUSE: The program cannot find a Light Table folder.

ACTION: Create a Light Table folder and try again.


ΓòÉΓòÉΓòÉ 292. Query is not LT Query type. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a Light Table query but the file type is not
correct. (The query file name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.
o The file is not a Light Table Query type.

ACTION: Try one of the following:

o Correct the file name.
o Create a Light Table Query file from a template.


ΓòÉΓòÉΓòÉ 293. Query file not found. ΓòÉΓòÉΓòÉ

ERROR: You were trying to open a Light Table Query file but it cannot be
opened. (The query file name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.
o The file does not exist.

ACTION: Try one of the following:

o Correct the file name.
o Create a Light Table Query file from a template.


ΓòÉΓòÉΓòÉ 294. SQL statement syntax error. ΓòÉΓòÉΓòÉ

ERROR: You are issuing an SQL statement with improper syntax.

CAUSE: Possible causes are:

o The SQL statement has improper syntax.
o There are missing or misspelled SQL keywords (for example, SELECT or FROM).

ACTION: Try one of the following:

o Issue an acceptable SQL statement.
o Correct keyword spelling.

  For example: SELECT * FROM tablename.


ΓòÉΓòÉΓòÉ 295. No Light Table folder selected. ΓòÉΓòÉΓòÉ

ERROR: You have not selected a Light Table folder name.

CAUSE: The program needs a Light Table folder name to continue.

ACTION: Select a Light Table folder name and try again.


ΓòÉΓòÉΓòÉ 296. Enter logon information. ΓòÉΓòÉΓòÉ

ERROR: You did not provide the required logon information for accessing the
database.

CAUSE: Possible causes are:

o For OS/2 Database Manager: the userid, password, or database name is missing.

o For Oracle: the userid, password, or server name is missing.

ACTION: Enter the logon information again.


ΓòÉΓòÉΓòÉ 297. Invalid character ' ' in Join Field Previous. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the Join Field Previous.

CAUSE: Blank or control characters are not allowed.

ACTION: Correct your input for Join Field Previous.


ΓòÉΓòÉΓòÉ 298. Invalid character ' ' in Join Field Next. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the Join Field Next.

CAUSE: Blank or control character are not allowed.

ACTION: Correct your input for Join Field Next.


ΓòÉΓòÉΓòÉ 299. Invalid character in Userid. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the Userid.

CAUSE: Blank or control character are not allowed.

ACTION: Correct the Userid.


ΓòÉΓòÉΓòÉ 300. Invalid character in Password. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the Password.

CAUSE: Blank or control character are not allowed.

ACTION: Correct the password.


ΓòÉΓòÉΓòÉ 301. Invalid character in database name. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the database name.

CAUSE: Blank or control character are not allowed.

ACTION: Correct the database name.


ΓòÉΓòÉΓòÉ 302. Invalid character in Server. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the server name.

CAUSE: Blank or control character are not allowed.

ACTION: Correct the server name.


ΓòÉΓòÉΓòÉ 303. Enter SQL statements. ΓòÉΓòÉΓòÉ

ERROR: You did not provide the SQL statements.

CAUSE: SQL statements are not there.

ACTION: Enter the SQL statements.


ΓòÉΓòÉΓòÉ 304. Invalid character in Tablename. ΓòÉΓòÉΓòÉ

ERROR: You entered an invalid character ' ' in the table name.

CAUSE: Blank or control character are not allowed.

ACTION: Correct the table name.


ΓòÉΓòÉΓòÉ 305. Light Table folder has no schema. ΓòÉΓòÉΓòÉ

ERROR: You have queried a Light Table folder that has no defined schema
definition. (The Light Table folder name is provided in the error window.)

CAUSE: The folder must have a schema definition.

ACTION: Open the Light Table folder schema setting notebooks page and define
new schema for the Light Table folder.


ΓòÉΓòÉΓòÉ 306. Out of memory - cannot allocate more memory. ΓòÉΓòÉΓòÉ

ERROR: You have no more memory available.

CAUSE: Memory resources are being used.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Workplace/2.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 307. Cannot open database ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a database but an error prevented it. (The
database and table name is provided in the error window.)

CAUSE: Possible causes are:

o A misspelled database or table name.
o Database table or file is already opened.
o Incorrect logon userid.
o Incorrect logon password.
o Incorrect server ID.
o A memory allocation error.

ACTION: Try one of the following:

o Close any other open sessions of the same database table.

o Correct database or table name, logon userid/password, or server ID.

o Shutdown OS/2 and restart the system.

o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 308. Error caused by database query ΓòÉΓòÉΓòÉ

ERROR: You are trying to do a database query but an error has stopped it. (The
query object name is provided in the error window.)

CAUSE: An incorrect SELECT query statement.

ACTION: Modify your SELECT query statement.


ΓòÉΓòÉΓòÉ 309. Cannot get database schema information. ΓòÉΓòÉΓòÉ

ERROR: You are running a query but the program cannot get database schema
information for the query. (The query object name is provided in the error
window.)

CAUSE: Possible causes are:

o Database schema has an incorrect data type.
o A memory allocation error.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Workplace/2.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o Rerun the query.

o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 310. Cannot create a new database table ΓòÉΓòÉΓòÉ

ERROR: Your database table could not be created due to an error. (The name of
the new database table is provided in the error window.)

CAUSE: Possible causes are:

o There is not enough disk space.
o You misspelled the table name.
o There already is a database file by that name.
o Unacceptable database file name or schema
o Incorrect logon information

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Workplace.

o Archive any large or infrequently used files in the C: drive (root
  directory).

o Erase or archive infrequently used files in your database.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o Rerun the query.

o If the query still fails, call your service representative.


ΓòÉΓòÉΓòÉ 311. Error occurred while getting database records. ΓòÉΓòÉΓòÉ

ERROR: You are trying to get a record from an SQL-like database but an error
stopped the process. (The query filename is provided in the error window.)

CAUSE: Possible causes are:

o The incorrect record was found.
o No record was found.
o A system error occurred.

ACTION: Try one of the following:

o Make sure that the database file or table you are querying contains proper
  records.
o Try again later.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 312. Error occurred while putting database records. ΓòÉΓòÉΓòÉ

ERROR: You were trying to put a record into an SQL-like database but an error
stopped the process. (The table name is provided in the error window.)

CAUSE: Possible causes are:

o The database record does not match the database.
o A memory allocation error.
o A system error.

ACTION: Try one of the following:

o Correct the record.

o Verify that your system meets the minimum requirements for Workplace/2.

o Close unneeded applications or windows.

o Archive any large or infrequently used files.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o Rerun the query.

o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 313. Cannot put extended attribute information in query result. ΓòÉΓòÉΓòÉ

ERROR: Failed to put extended attribute information in the query result object.

CAUSE: Possible causes are:

o Extended Attribute query information is not in proper format.
o A memory allocation error.
o A sharing violation.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o Rerun the query.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 314. Cannot get extended attributes information. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to get extended attributes information but an
error stopped the process. (The query object name s provided in the error
window.)

CAUSE: Possible causes are:

o No extended attributes information was found in the file.
o A memory allocation error
o A sharing violation.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o Rerun the query.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 315. Cannot get extended attributes logon information. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to get extended attributes logon informaton but an
error stopped the process. (The query object name is provided in the error
window.)

CAUSE: Possible causes are:

o A memory allocation error
o A sharing violation.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.

o Rerun the query.

o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 316. Cannot get folder schema information. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to get folder schema information but an error
stopped the process.

CAUSE: Possible causes are:

o The extended attributes do not exist.
o A memory allocation error.

ACTION: Try one of the following:

o Define new schema definitions for the Light Table folder and try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 317. Cannot populate folder. ΓòÉΓòÉΓòÉ

ERROR: The program trying to populate the Light Table folder, but an error
stopped the process. (The folder name is provided in the error window.)

CAUSE: Possible causes are:

o Could not get folder schema information.
o The database key field has no value.
o A memory allocation error.

ACTION: Try one of the following:

o Define database value for the key field in Light Table folder details view
  and try again.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 318. DOS read or write operation failed. ΓòÉΓòÉΓòÉ

ERROR: You are trying to read or write a file but an error stopped the process.

CAUSE: Possible causes are:

o You do not have read access to the file.
o The file has read-only protection status.
o A system error occurred.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.

o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 319. Failed to start ltqrv.exe ΓòÉΓòÉΓòÉ

ERROR: You ran a query but the query result viewer would not start.

CAUSE: Possible causes are:

o Program ltqrv.exe does not exist.
o ltqrv.exe is not in the PATH.
o A memory allocation error occurred.
o The stack size is too small.

ACTION: Try one of the following:

o Double click the query result object to view the result.

o Verify that the ltqrv.exe is in a directory included in your current PATH
  statement.

o Make sure that program ltqrv.exe exists.

o Shutdown OS/2, restart the system, and rerun the query.

o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 320. Error occurred doing a Query result column-join. ΓòÉΓòÉΓòÉ

ERROR: You are trying to do a column join but an error stopped the process.

CAUSE: Possible causes are:

o Query on the database failed.
o Get database schema failed.
o Create database table or file failed.
o Get database record failed.
o Put database record failed.

ACTION: Contact your service representative.


ΓòÉΓòÉΓòÉ 321. Light table folder has no multimedia objects ΓòÉΓòÉΓòÉ

ERROR: The light table folder to be queried contains no multimedia objects.
(The folder name is provided in the error window.)

CAUSE: Possible causes are:

o Light Table folder only contains non-multimedia objects.

o Light Table folder is empty.

ACTION: Drag and drop multimedia objects to the light table folder.


ΓòÉΓòÉΓòÉ 322. Incorrect SQL like query statement ΓòÉΓòÉΓòÉ

ERROR: The query has incorrect SELECT query statement.

CAUSE: Possible causes are:

o The syntax of your SQL like query statement is incorrect.

o Your query statement is missing "SELECT" or "FROM" keywords

ACTION: Correct your SELECT query statement.


ΓòÉΓòÉΓòÉ 323. Join operation exceeds system capacity. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to join a sequence of query results, but there are
too many of them.

CAUSE: The program joins a sequence of query results when it encounters a Query
Result object or a Visual Query object in the query sequence. The number of
query results to be joined has caused a buffer to fill up.

ACTION: Reduce the number of query results to be joined by inserting an
intermediate Query Result object in the query sequencer.


ΓòÉΓòÉΓòÉ 324. Drag/Drop error: Cannot render data for dropped object. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Query Result Viewer but an
error stopped the process.

CAUSE: Shared memory is not available.

ACTION: Try one of the following:

o Try the same drag and drop again.

o Shutdown OS/2 and restart the system, then try the same drag and drop again.

o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 325. Drag/Drop error: Cannot end data transfer. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Query Result Viewer but an
error stopped the process.

CAUSE: Shared memory is not available.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Shutdown OS/2 and restart the system, then try the same drag and drop again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 326. Drag/Drop error: Cannot find the class. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Query Result Viewer but the
class cannot be found. (The class it was trying to find is provided in the
error window.)

CAUSE: The object class is not loaded or initialized.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Check the class list for WPDataFile and LT Reference
o Shutdown OS/2 and restart the system.


ΓòÉΓòÉΓòÉ 327. Drag/Drop error: Cannot create the dropped object. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Query Result Viewer but an
error stopped the process.

CAUSE: Object class is not loaded or initialized.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Check the class list for WPDataFile and LT Reference
o Shutdown OS/2 and restart the system.
o Try the same drag and drop again.


ΓòÉΓòÉΓòÉ 328. Drag/Drop error: Cannot get the named shared memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Query Result Viewer but an
error stopped the process.

CAUSE: Shared memory is not available.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Close and restart the Query Result Viewer.
o Shutdown OS/2 and restart the system, then try the same drag and drop again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 329. Drag/Drop error: Cannot free the named shared memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but an error stopped the
process.

CAUSE: Shared memory is not available.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Shutdown OS/2 and restart the system, then try the same drag and drop again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 330. Drag/Drop error: Cannot get the real name of the object. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but an error stopped the
process.

CAUSE: Possible causes are:

o The object is not available.
o The directory where the object is located may be locked.

ACTION: Try one of the following:

o Try the same Drag/Drop again.
o Find out if the directory is locked or busy.


ΓòÉΓòÉΓòÉ 331. Drag/Drop error: Cannot allocate memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but a memory error stopped the
process.

CAUSE: No Memory is available.

ACTION: Try one of the following:

o Try the drag and drop again.

o Close unneeded applications or windows.

o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.

o Shutdown OS/2 and restart the system.

o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 332. Drag/Drop error: Cannot allocate memory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag and drop an object but a memory error stopped the
process.

CAUSE: No memory is available.

ACTION: Try one of the following:

o Try the drag and drop again.
o Close unneeded applications or windows.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 333. Error getting folder schema. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open the details view for the folder but the schema
defined for this folder is inaccessible.

CAUSE: Possible causes are:

o The attached database may not be available.
o The schema may not be set up correctly.

ACTION: Try one of the following:

o Check the schema definition via the notebook page.
o Check for availability of the database.


ΓòÉΓòÉΓòÉ 334. Error on record creation. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create a new record in the database but the program
cannot create it. (The database access error number is provided in the error
window.)

CAUSE: Possible causes are:

o The attached database may not be available.
o You do not have write access to the database.

ACTION: Try one of the following:

o Check to see if the database is available.
o Check the access permissions of the database.


ΓòÉΓòÉΓòÉ 335. Error on record update. ΓòÉΓòÉΓòÉ

ERROR: You are trying to update a record in the database but an error stopped
the process. (The database access error number is provided in the error
window.)

CAUSE: The database is unavailable for write access.

ACTION: Check the availability and access permissions of database.


ΓòÉΓòÉΓòÉ 336. Error on field edit format. ΓòÉΓòÉΓòÉ

ERROR: The data you entered in the record was not accepted. (The database
access error number is provided in the error window.)

CAUSE: The wrong format was entered for the schema field type.

ACTION: Try one of the following:

o Re-enter data in the correct format.
o Check schema field type.


ΓòÉΓòÉΓòÉ 337. Unable to allocate memory. ΓòÉΓòÉΓòÉ

ERROR: You need more memory to complete the operation but the system is unable
to allocate any memory.

CAUSE: Memory is unavailable.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Workplace/2 as
  specified in the Users Guide.
o Close unneeded applications or windows to free up memory resources.
o Shutdown OS/2 and restart the system.


ΓòÉΓòÉΓòÉ 338. Unable to load dialog for creating LT Reference. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use Create LT Reference but the program is unable to
create a dialog window.

CAUSE: The program cannot create dialog window.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 339. Unable to insert 'Media Browser' menu item into the data ΓòÉΓòÉΓòÉ

file's open submenu.

ERROR: You are trying to display the data file's open submenu but an error
stopped the process of adding 'Media Browser' to the open submenu.

CAUSE: The program cannot insert new menu item to the open submenu.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 340. Unable to insert 'Create LT Reference' into context menu.  . ΓòÉΓòÉΓòÉ

ERROR: You are trying to display the data file's context menu but an error
stopped the process of adding "Create LTReference" to the context menu.

CAUSE: The program cannot insert new menu item to the context menu.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 341. Light Table folder not selected. ΓòÉΓòÉΓòÉ

ERROR: You have not selected a Light Table folder as the target folder for this
operation.

CAUSE: The program requires a folder as a target.

ACTION: Try one of the following:

o Select a Light Table folder for this operation
o Cancel the operation


ΓòÉΓòÉΓòÉ 342. Error initializing dialog for creating LT Reference. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create an LT Reference but an error stopped a window
from being opened.

CAUSE: The program cannot open a window.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 343. Unable to register window class. ΓòÉΓòÉΓòÉ

ERROR: You are using the Media Browser but the program could not register
window class for Media Browser.

CAUSE: The program could not register the window class.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 344. Unable to create standard window. ΓòÉΓòÉΓòÉ

ERROR: You are using the Media Browser but the program cannot create a standard
window.

CAUSE: The program cannot create a window for the Media Browser.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 345. Unable to create the LT Reference object. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create an LT Reference object but an error stopped the
process.

CAUSE: The program cannot create the LT Reference object.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 346. Unable to process default thumbnail. ΓòÉΓòÉΓòÉ

ERROR: The thumbnail image cannot be processed.

CAUSE: Possible causes are:

o The default thumbnail does not exist in the UMPATH.
o The default thumbnail file is corrupted.

ACTION: Try one of the following:

o Copy the default thumbnail from product diskette to UMPATH, then try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 347. Unable to find the class. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create an LT Reference object but the object class
cannot be found. (The class name is provided in the error window.)

CAUSE: The object class is not loaded or initialized.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 348. Unable to get the real name of the object. ΓòÉΓòÉΓòÉ

ERROR: You are trying to perform operations on the object but the object could
not be found.

CAUSE: Possible causes are:

o The object is not loaded or is unavailable.
o The directory (where the object is located) is locked.

ACTION: Try one of the following:

o Try the same operation again later.
o Check if the directory is in use or locked.


ΓòÉΓòÉΓòÉ 349. Remove Existing Schema stored in Extended Attributes? ΓòÉΓòÉΓòÉ

ERROR: You are trying to remove existing schema stored in extended attributes.

CAUSE: The program verifies that you really want to discard the existing
schema.

ACTION: Try one of the following:

o Press Ok to discard the existing schema.
o Press Cancel to keep the existing schema.


ΓòÉΓòÉΓòÉ 350. Error: Could not get schema. Press Undo. ΓòÉΓòÉΓòÉ

ERROR: You are trying to access the folder schema information but the program
could not get the original schema from the folder.

CAUSE: Possible causes are:

o The folder was deleted, renamed or moved.
o A memory allocation error

ACTION: Try one of the following:

o If the folder was renamed or moved, close the settings notebook and try
  again.
o If the folder was deleted, do not try again.
o Shutdown OS/2 and restart the system.
o Close any applications or windows not in use.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 351. Remove Existing Schema stored in Database? ΓòÉΓòÉΓòÉ

ERROR: You are trying to remove existing schema stored in the Database.

CAUSE: The program verifies that you really want to change the Database type.

ACTION: Try one of the following:

o Press Ok to discard the existing schema.
o Press Cancel to keep the existing schema.


ΓòÉΓòÉΓòÉ 352. Error: Could not open the schema in extended attributes. ΓòÉΓòÉΓòÉ

ERROR: You are trying to access the folder schema information but the program
could not open the schema in the extended attributes.

CAUSE: Possible causes are:

o The folder has been renamed.
o The schema in extended attributes is already open.
o A memory allocation error.

ACTION: Try one of the following:

o Close then reopen the settings notebook and try again.
o Close other windows associated with this schema.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 353. Error: Could not store schema in extended attributes. ΓòÉΓòÉΓòÉ

ERROR: The schema could not be stored in the extended attributes.

CAUSE: Possible causes are:

o The schema is already open.
o A memory allocation error.

ACTION: Try one of the following:

o Close other windows associated with this schema.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 354. Error: Could not close schema stored in extended attributes. ΓòÉΓòÉΓòÉ

ERROR: The schema could not be closed in the extended attributes.

CAUSE: Possible causes are:

o Another instance of this schema is in use
o A memory allocation error

ACTION: Try one of the following:

o Close other windows associated with this schema.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 355. Error: Logon Information failed. ΓòÉΓòÉΓòÉ

ERROR: The logon information could not be accessed.

CAUSE: Possible causes are:

o Another instance of this schema is in use
o A memory allocation error

ACTION: Try one of the following:

o Close other windows associated with this schema.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 356. Error: Could not open database. ΓòÉΓòÉΓòÉ

ERROR: You are trying to access a database table that could not be opened.

CAUSE: Possible causes are:

o Incorrect logon information.
o The database table is already open.
o A memory allocation error.

ACTION: Try one of the following:

o Enter the correct logon information.
o Close any other open sessions of the database table.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 357. Error: Cannot get schema field names from database. ΓòÉΓòÉΓòÉ

ERROR: You are trying to use a database but the program cannot get the schema
field names from the database.

CAUSE: Possible causes are:

o Another instance of this database table is already open
o A memory allocation error

ACTION: Try one of the following:

o Close any other session associated with this database table.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 358. Error: Could not close schema stored in database. ΓòÉΓòÉΓòÉ

ERROR: You are trying to save the schema in a database, but the program could
not close the database.

CAUSE: Possible causes are:

o Another instance of this database table is in use
o A memory allocation error

ACTION: Try one of the following:

o Close other sessions associated with this database table.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 359. Please use the Schema Editor to create new schema fields. ΓòÉΓòÉΓòÉ

ERROR: This is a new database table. Please press DB Edit... to add new schema
fields.

CAUSE: The program verifies that you are creating a new database table.

ACTION:

o Press Ok to get out of the message box..
o Press DB EDit... to add new schema fields.


ΓòÉΓòÉΓòÉ 360. Schema definition has changed. Want to save the changes? ΓòÉΓòÉΓòÉ

ERROR: You are trying to exit without saving changes.

CAUSE: The program verifies that you really want to discard the changes.

ACTION: Try one of the following:

o Press Yes to save the changes.
o Press No to exit without saving changes.


ΓòÉΓòÉΓòÉ 361. Field size cannot be blank. ΓòÉΓòÉΓòÉ

ERROR: You have entered an unacceptable value as the field size.

CAUSE: The field size must be within the acceptable range.

ACTION: Enter an acceptable value for field size. Consult the User's Guide for
a complete description of acceptable values and formats allowed for each type
of database supported.


ΓòÉΓòÉΓòÉ 362. No trailing or embedded blanks allowed. ΓòÉΓòÉΓòÉ

ERROR: You have entered data that contains blanks.

CAUSE: The program checks for trailing or embedded blanks.

ACTION: Enter the data without blanks.


ΓòÉΓòÉΓòÉ 363. Remove all blanks within numbers. ΓòÉΓòÉΓòÉ

ERROR: You typed numbers that contained blanks.

CAUSE: Blanks within a number are not allowed.

ACTION: Enter the number without blanks.


ΓòÉΓòÉΓòÉ 364. Numbers allowed only. ΓòÉΓòÉΓòÉ

ERROR: You entered characters other than numbers.

CAUSE: Only numbers are accepted.

ACTION: Enter numbers only.


ΓòÉΓòÉΓòÉ 365. The size for the field is too large. ΓòÉΓòÉΓòÉ

ERROR: You specified too large a size for this field type. (The field type and
size limit are provided in the error window.)

CAUSE: The field size must be within the acceptable range.

ACTION: Enter a value within the allowable range. Consult the User's Guide for
a complete description of acceptable values and formats allowed for each type
of database supported.


ΓòÉΓòÉΓòÉ 366. Size cannot be zero ΓòÉΓòÉΓòÉ

ERROR: You have provided a size of zero.

CAUSE: The size must be greater than zero.

ACTION: Enter a size within the acceptable range. Consult the User's Guide for
a complete description of acceptable values and formats allowed for each type
of database supported.


ΓòÉΓòÉΓòÉ 367. Field name must contain at least one non-blank character ΓòÉΓòÉΓòÉ

ERROR: You have entered a field name with only blank characters.

CAUSE: The field name must have at least one non-blank character.

ACTION: Enter an acceptable field name. Consult the User's Guide for a complete
description of acceptable values and formats allowed for each type of database
supported.


ΓòÉΓòÉΓòÉ 368. Field name contains an unacceptable character. ΓòÉΓòÉΓòÉ

ERROR: You specified a field name that is not acceptable. (The character in
error is provided in the error window.)

CAUSE: The program checks the field name for acceptable characters.

ACTION: Enter an acceptable field name. Consult the User's Guide for a complete
description of acceptable values and formats allowed for each type of database
supported.


ΓòÉΓòÉΓòÉ 369. A field type must be selected from the drop-down list ΓòÉΓòÉΓòÉ

ERROR: You've specified an unrecognized field type.

CAUSE: Only acceptable field types can be selected.

ACTION: Select a type from the drop-down list.


ΓòÉΓòÉΓòÉ 370. Error: There is not enough memory to continue. ΓòÉΓòÉΓòÉ

ERROR: You are using a process that requires more memory but there is none
available.

CAUSE: Possible causes are:

o Not enough memory
o A memory allocation error

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for Workplace/2.
o Close unneeded applications or windows.
o Shutdown OS/2 and restart the system.
o Retry the operation.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 371. Error: The Folder Join Field is not acceptable. ΓòÉΓòÉΓòÉ

ERROR: You specified a Folder Join Field that cannot be used.

CAUSE: The field has been modified or deleted.

ACTION: Try one of the following:

o Verify that the field exists (use the schema editor).
o Select another field.


ΓòÉΓòÉΓòÉ 372. Error: The Folder Join Field was not found. ΓòÉΓòÉΓòÉ

ERROR: The Folder Join Field was not found and the Schema is incorrect.

CAUSE: The Folder Join Field name was modified or deleted.

ACTION: Try one of the following:

o Verify that the Folder Join Field exists (use the schema editor).
o Select another Folder Join field.


ΓòÉΓòÉΓòÉ 373. Error: The Database Join Field was not found. ΓòÉΓòÉΓòÉ

ERROR: The Database Join Field was not found and the Schema is incorrect.

CAUSE: The Database Join Field name was modified or deleted.

ACTION: Try one of the following:

o Verify that the Database Join Field exists (use the schema editor).
o Select another Database Join field.


ΓòÉΓòÉΓòÉ 374. Error: The Database Join Field is the wrong type. ΓòÉΓòÉΓòÉ

ERROR: You are using a Database Join Field with an incorrect Schema.

CAUSE: The Database Join Field type can only be an ASCII or VARCHAR character
string.

ACTION: Select either ASCII or VARCHAR types for the Database Join Field.


ΓòÉΓòÉΓòÉ 375. Error: Could not save Schema. ΓòÉΓòÉΓòÉ

ERROR: The Schema could not be saved.

CAUSE: Possible causes are:

o You do not have write access to the database.
o Another instance of the database table or extended attributes is already in
  use.
o A memory allocation error.

ACTION: Try one of the following:

o Close other instances that access this schema.
o If the symptom persists, contact your administrator.
o Shutdown OS/2 and restart the system.


ΓòÉΓòÉΓòÉ 376. Error: Could not save logon information. ΓòÉΓòÉΓòÉ

ERROR: Logon information was not saved.

CAUSE: A memory allocation error.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 377. Error: Could not replace schema. ΓòÉΓòÉΓòÉ

ERROR: The Schema could not be updated.

CAUSE: A memory allocation error.

o You do not have write access to the database.
o Another instance of the database table or extended attributes is already in
  use.
o A memory allocation error.

ACTION: Try one of the following:

o Close other instances that acess this schema.
o Shutdown OS/2 and restart the system.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 378. Error: The database alias name was not found ΓòÉΓòÉΓòÉ

ERROR: OS/2 database name does not exist

CAUSE: Possible causes are:

o You misspelled the database name.
o The database does not exist.

ACTION: Try one of the following:

o Specify an existing database.
o Use your database product to create a database.


ΓòÉΓòÉΓòÉ 379. Error: Validation failed. ΓòÉΓòÉΓòÉ

ERROR: A database error occurred during validation. (The database message is
provided in the error window.)

CAUSE: To determine the cause, see the database message.

ACTION: Try one of the following:

o Try to save and validate later.
o Use the message to determine what is wrong.
o If the symptom persists, contact your administrator.


ΓòÉΓòÉΓòÉ 380. Only one decimal point allowed. ΓòÉΓòÉΓòÉ

ERROR: You have entered more than one decimal points.

CAUSE: Only one decimal point allowed.

ACTION: Enter one decimal point.


ΓòÉΓòÉΓòÉ 381. Decimal field size not specified correctly. ΓòÉΓòÉΓòÉ

ERROR: You have entered wrong field size.

CAUSE: The program checks for field size.

ACTION: Enter the data with right field size.


ΓòÉΓòÉΓòÉ 382. Field size cannot exceed the limit. ΓòÉΓòÉΓòÉ

ERROR: You typed field size that exceed the limit. (The limit is provided in
the error window.)

CAUSE: The field size must be within the acceptable range.

ACTION: Enter a value within the allowable range. Consult the User's Guide for
a complete description of acceptable values and formats allowed for each type
of database supported.


ΓòÉΓòÉΓòÉ 383. Precision cannot exceed total number of digits. ΓòÉΓòÉΓòÉ

ERROR: You entered the precision greater than the total number of digits.

CAUSE: Program checks the precision.

ACTION: Enter the precision less or eqaul to the number of digits.


ΓòÉΓòÉΓòÉ 384. Precision cannot exceed field size minus two. ΓòÉΓòÉΓòÉ

ERROR: You entered the precision greater than the total number of digits minus
two.

CAUSE: Program checks the precision.

ACTION: Enter the correct precision.


ΓòÉΓòÉΓòÉ 385. First character of a field name must be a letter. ΓòÉΓòÉΓòÉ

ERROR: You specified the first character of a field name wrong.

CAUSE: The first character of a field name must be A thru Z.

ACTION: Enter a correct field name.


ΓòÉΓòÉΓòÉ 386. Duplicate field name. ΓòÉΓòÉΓòÉ

ERROR: You have provided a duplicate field name.

CAUSE: No duplicate field name allowed.

ACTION: Enter a different name for the field name.


ΓòÉΓòÉΓòÉ 387. Field definition has changed. Want to save the changes? ΓòÉΓòÉΓòÉ

ERROR: You are trying to exit without saving changes.

CAUSE: The program verifies that you really want to discard the changes.

ACTION: Try one of the following:

o Press Apply to save the changes.
o Press Cancel to exit without saving changes.


ΓòÉΓòÉΓòÉ 388. Invalid pathname entered.  Please try again. ΓòÉΓòÉΓòÉ

ERROR: You have entered an invalid pathname.

CAUSE: You have entered an invalid pathname.

ACTION: Re-enter the pathname.


ΓòÉΓòÉΓòÉ 389. Pathname entered is not a Light Table folder. ΓòÉΓòÉΓòÉ

ERROR: You have entered a pathname which is not a Light Table folder.

CAUSE: You have entered a pathname but the pathname is not a Light Table
folder.

ACTION: Re-enter the pathname.


ΓòÉΓòÉΓòÉ 390. User ID not entered. ΓòÉΓòÉΓòÉ

ERROR: The user ID field is blank.

CAUSE: You did not enter a user ID.

ACTION: Enter a user ID.


ΓòÉΓòÉΓòÉ 391. Password not entered. ΓòÉΓòÉΓòÉ

ERROR: The password field is blank.

CAUSE: You did not enter a password.

ACTION: Enter a password.


ΓòÉΓòÉΓòÉ 392. Logon failure. ΓòÉΓòÉΓòÉ

ERROR: The attempt to log on to the database failed.

CAUSE: Possible causes are:

o You entered an undefined user ID.
o You entered an incorrect password.
o The Oracle server you are trying to log on to is not connected.
o The location of the DB2/2, OS/2, or DDCS/2-to-Host database that you are
  trying to log on to is not known.

The message gives the cause of the error as reported by the database manager,
and it varies according to the type of database:

o Oracle:

   - An incorrect userid or password is reported by message ORA-01017.
   - An unconnected server is reported by message ORA-03121.

o DB2/2 or OS/2 database on local system:

   - An incorrect userid or password is reported by QELIB Error: Login
     incorrect.
   - An unknown database is reported by message SQL1013.

o DB2/2 or OS/2 database on server:

   - An incorrect userid or password is reported by message SQL1093.
   - An unknown database is reported by QELIB Error: Login incorrect.

o DDCS2 to Host:

   - An incorrect userid or password is reported by ...
   - An unknown database is reported by ...

ACTION: Determine the type of error, and do one of the following:

o If the user ID or password is incorrect, enter a correct user ID and
  password.

o If the server is not connected or the database is unknown, cancel the logon
  dialog and correct the problem.


ΓòÉΓòÉΓòÉ 393. Error occurred while opening database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to open the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 394. Error occurred while closing database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to close the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 395. Error occurred while creating database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 396. Error occurred while adding record to database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to add a record to the
database table. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 397. Error occurred while updating database record. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to update the database
record. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 398. Error occurred while querying database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to query the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 399. Error occurred while getting database record. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to get a database record.
(The database table name and the error are provided in the error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 400. Error occurred during committing database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to commit the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 401. Error occurred while creating index for database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create index for the
database table. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 402. Error occurred while deleting record from database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to delete a record from
the database table. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 403. Error occurred while deleting database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to delete the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 404. Error occurred while reading database heading information. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the database
heading information. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 405. Error occurred during rollback process for database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to rollback the process
for the database table. (The database table name and the error are provided in
the error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 406. Error: window creation failed. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create a window.

CAUSE: The program cannot create a window.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 407. Error: window positioning failed. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to position the window.

CAUSE: The program cannot position the window.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 408. Error occurred during creating message queue. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create a message queue.

CAUSE: Possible causes are:

o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 409. Error occurred during window initialization. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to initialize the window.

CAUSE: Possible causes are:

o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 410. No help is available. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to locate the help file.

CAUSE: Possible causes are:

o The help file does not exist.
o The help file has been renamed.
o The help file is not in the correct path.

ACTION: Try one of the following:

o Copy the help files from the install package to the disk.
o Update the CONFIG.SYS file with the correct help path.


ΓòÉΓòÉΓòÉ 411. Help terminated dur to error. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to terminate the help
operation.

CAUSE: Possible causes are:

o The help file is corrupted.
o A memory allocation error.

ACTION: Try one of the following:

o Copy the help files from the install package to the disk.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 412. Help error occurred. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is processing the on-line help.

CAUSE: Possible causes are:

o The help file is corrupted.
o A memory allocation error.

ACTION: Try one of the following:

o Copy the help files from the install package to the disk.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 413. Help error. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to process the on-line
help.

CAUSE: Possible causes are:

o The help file is corrupted.
o A memory allocation error.

ACTION: Try one of the following:

o Copy the help files from the install package to the disk.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 414. Error: could not read masked file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the masked file.
(The masked file name is provided in the error window.)

CAUSE: Possible causes are:

o The masked file is corrupted.
o The masked file does not exist.
o The masked file has invalid format.
o A memory allocation error.

ACTION: Try one of the following:

o Supply the correct masked file name and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 415. Error: could not read image file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the image file.
(The image file name is provided in the error window.)

CAUSE: Possible causes are:

o The image file is corrupted.
o The image file does not exist.
o The image file has invalid format.
o A memory allocation error.

ACTION: Try one of the following:

o Supply the correct image file name and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 416. Error: could not read image file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the image file.
(The image file name is provided in the error window.)

CAUSE: Possible causes are:

o The image file is corrupted.
o The image file does not exist.
o The image file has invalid format.
o A memory allocation error.

ACTION: Try one of the following:

o Supply the correct image file name and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 417. Error: Unable to allocate resources. ΓòÉΓòÉΓòÉ

ERROR: You have no more memory available.

CAUSE: Memory resources are being used.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 418. Error: Unable to allocate resources. ΓòÉΓòÉΓòÉ

ERROR: You have no more memory available.

CAUSE: Memory resources are being used.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 419. Error: Unable to allocate resources. ΓòÉΓòÉΓòÉ

ERROR: You have no more memory available.

CAUSE: Memory resources are being used.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 420. Error: Internal database is corrupted. ΓòÉΓòÉΓòÉ

ERROR: The internal database table is corrupted. (The database table name is
provided in the error window.)

CAUSE: Possible causes are:

o The database table has been updated incorrectly.
o The database table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Undo the updates to the database table.
o Recreate the database table.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 421. Error: Unable to update feature table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to update the feature
table. (The feature table name is provided in the error window.)

CAUSE: Possible causes are:

o The database table has been updated incorrectly.
o The database table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Undo the updates to the database table.
o Recreate the database table.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 422. Unable to open file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to open the file. (The
file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.

ACTION: Try one of the following:

o Restore the file if it does not exist.
o Close other use of the file and try again.
o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 423. Unable to read from file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read from the file.
(The file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.
o The file has invalid format.

ACTION: Try one of the following:

o Restore the file if it does not exist.
o Close other use of the file and try again.
o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 424. Unable to write to file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to write to the file. (The
file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.
o The file has invalid format.
o The file is read-only.

ACTION: Try one of the following:

o Supply another file name and try again.


ΓòÉΓòÉΓòÉ 425. Unable to create thread. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create a thread.

CAUSE: Possible causes are:

o A memory allocation error.
o Protection violation.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or windows.
o Archive any large or infrequently used files.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 426. Unable to kill thread. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to kill the thread.

CAUSE: Possible causes are:

o An internal processing error occured.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 427. Unable to suspend thread. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to suspend the thread.

CAUSE: Possible causes are:

o An internal processing error occured.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 428. Unable to resume thread. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to resume the thread.

CAUSE: Possible causes are:

o An internal processing error occured.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 429. First character must be a letter. ΓòÉΓòÉΓòÉ

ERROR: You specified the first character of a field name wrong.

CAUSE: The first character must be A thru Z.

ACTION: Enter a correct name.


ΓòÉΓòÉΓòÉ 430. The character is invalid. ΓòÉΓòÉΓòÉ

ERROR: You enterfied the first character of a field name wrong. (The invalid
character is displayed in the error window.)

CAUSE: The first character must be A thru Z.

ACTION: Enter a correct name.


ΓòÉΓòÉΓòÉ 431. Second character of SERVER is invalid. ΓòÉΓòÉΓòÉ

ERROR: The second character of the SERVER name you enetered is incorrect.

CAUSE: You entered the SERVER name incorrectly.

ACTION: Enter the correct SERVER name.


ΓòÉΓòÉΓòÉ 432. Field cannot be blank. ΓòÉΓòÉΓòÉ

ERROR: The field can not be left blank.

CAUSE: You did not enter the required field.

ACTION: Enter the required field.


ΓòÉΓòÉΓòÉ 433. Invalid or no Catalog has been specified. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to load the Catalog, but the Catalog does not
exist. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o You specified an invalid Catalog name.
o You specified a Catalog name which does not exist.

ACTION: Try one of the following:

o Click 'Abort' to exit the program.
o Click 'Retry' to reload the Catalog.
o Click 'Ignore' to respecify the Catalog name.


ΓòÉΓòÉΓòÉ 434. Catalog is read only. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to update the Catalog, but the Catalog is read
only. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o You did not know that the Catalog is read only and try to save information to
  it.
o You open a wrong Catalog.

ACTION: Try one of the following:

o Open another read/write Catalog and continue the process.
o Do not do any classification operation to the read-only Catalog.


ΓòÉΓòÉΓòÉ 435. This is not a Catalog. ΓòÉΓòÉΓòÉ

ERROR: The program does not recognize the name supplied as a Catalog name. (The
Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o You specified a wrong Catalog name.
o You open a wrong Catalog.

ACTION: Try one of the following:

o Resupply the Catalog name and try again.


ΓòÉΓòÉΓòÉ 436. This is not a Catalog. ΓòÉΓòÉΓòÉ

ERROR: The program does not recognize the name supplied as a Catalog name. (The
Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o You specified a wrong Catalog name.
o You open a wrong Catalog.

ACTION: Try one of the following:

o Resupply the Catalog name and try again.


ΓòÉΓòÉΓòÉ 437. Error occurred while computing database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to compute the data in the
database table. (The database table name is provided in the error window.)

CAUSE: Possible causes are:

o The database table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the database table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 438. Error occurred while computing distributed average color ΓòÉΓòÉΓòÉ

table.

ERROR: An error occurred while the program is trying to compute the data in the
distributed average color table. (The distributed average color table name is
provided in the error window.)

CAUSE: Possible causes are:

o The distributed average color table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the distributed average color table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 439. Error occurred while computing histogram table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to compute the data in the
histogram table. (The histogram table name is provided in the error window.)

CAUSE: Possible causes are:

o The histogram table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the histogram table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 440. Error occurred while computing texture table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to compute the data in the
texture table. (The texture table name is provided in the error window.)

CAUSE: Possible causes are:

o The texture table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the texture table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 441. Error occurred while computing shape table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to compute the data in the
shape table. (The shape table name is provided in the error window.)

CAUSE: Possible causes are:

o The shape table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the shape table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 442. Error occurred while computing layout table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to compute the data in the
layout table. (The layout table name is provided in the error window.)

CAUSE: Possible causes are:

o The layout table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Re-classify the area in the layout table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 443. There is no record to be computed in this Catalog. ΓòÉΓòÉΓòÉ

ERROR: You are trying to analyze the data in the Catalog, but there is no
record to be computed in this Catalog.

CAUSE: Possible causes are:

o You specify the Catalog name incorrectly.

ACTION: Try one of the following:

o Specify the correct Catalog name and try again.


ΓòÉΓòÉΓòÉ 444. No features selected - Image Analyzer will not start. ΓòÉΓòÉΓòÉ

ERROR: You are trying to analyze the data in the Catalog, but no features are
selected for analyzing.

CAUSE: Possible causes are:

o You did not select the features correctly.

ACTION: Try one of the following:

o Reselect the features to be calculated and try again.


ΓòÉΓòÉΓòÉ 445. Feature Vector tables have been successfully updated. ΓòÉΓòÉΓòÉ

INFORMATION: The program has successfully updated all the data in the features
vector tables.

CAUSE: The program acknowledges the user of the successful completion of the
operation.


ΓòÉΓòÉΓòÉ 446. Feature Vector tables may not be valid for quering ΓòÉΓòÉΓòÉ

purpose due to error.

ERROR: An error occurred while the program is trying to analyze the data in the
feature vector tables.  This resulted in the feature vector tables not valid
for quering.

CAUSE: Possible causes are:

o The feature vector tables are corrupted.

ACTION: Try one of the following:

o Reselect the features to be calculated and try again.
o If the symptom persists, call you service representative.


ΓòÉΓòÉΓòÉ 447. Unable to access control information for Catalog. ΓòÉΓòÉΓòÉ

ERROR: The program is not able to access the control information for the
Catalog. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o The control file is corrupted.
o The control file does not exist.

ACTION: Try one of the following:

o Click on 'OK' to regenerate the control file.
o Click on 'Cancel' to cancel the operation.


ΓòÉΓòÉΓòÉ 448. Catalog contains unsupported database type. ΓòÉΓòÉΓòÉ

ERROR: The Catalog contains database type which is not supported by the
program. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o The Catalog is created by other source with unsupported database type.

ACTION: Try one of the following:

o Recreate the Catalog with supported database type and try again.


ΓòÉΓòÉΓòÉ 449. This is not a valid parameter. ΓòÉΓòÉΓòÉ

ERROR: You have entered a parameter that is neither a Catalog name nor the name
of a displayable image. (The parameter is provided in the error window.)

CAUSE: Possible causes are:

o The image name or Catalog name was spelled incorrectly.
o The image name entered is not a displayable image.
o The extension ".CLS" was not specified for the Catalog name.

ACTION: Try one of the following:

o Reinvoke the Image Classifier with a correct image name and/or Catalog name.
o To display an image, select the "Image - Open" menu item from the Image
  Classifier menu bar.
o To select a Catalog, select the "Catalog - New" or "Catalog - Open" menu item
  from the Image Classifier menu bar.


ΓòÉΓòÉΓòÉ 450. No Catalog is loaded. ΓòÉΓòÉΓòÉ

ERROR: There is no Catalog currently loaded.  A Catalog must be loade for the
Image Classifier to continue.

CAUSE: Possible causes are:

o The creation of the new Catalog is not completed.

ACTION: Try one of the following:

o To create a new Catalog, select the "Catalog - New" menu item from the Image
  Classifier menu bar.
o To open an existing Catalog, select the "Catalog - Open" menu item from the
  Image Classifier menu bar.
o Reinvoke the Image Classifier with a valid Catalog name.


ΓòÉΓòÉΓòÉ 451. The drag information could not be accessed. ΓòÉΓòÉΓòÉ

ERROR: An error occured accessing a DRAGINFO structure required for a
successful drag/drop.

CAUSE: Possible causes are:

o The memory block required for the drag/drop was not allocated properly.

ACTION: Try one of the following:

o Close any windows that are not needed.
o Close all applications not being used.
o Archive any large or infrequently used files or delete any unnecessary files
  on the disk. where the SWAPPER.DAT file exists.
o Rerun the program.


ΓòÉΓòÉΓòÉ 452. Wrong RMF. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object, but the rendering mechanism and format
are not supported for the dragged object.

CAUSE: Possible causes are:

o You dragged an unsupported object.

ACTION: Try one of the following:

o Select a supported object and drag again.


ΓòÉΓòÉΓòÉ 453. An area has not been selected. ΓòÉΓòÉΓòÉ

ERROR: An area must be selected or masked before adding to the Catalog or
dragging/dropping to a sampler.

CAUSE: Possible causes are:

o The user presses the classiay button from the toolbox or selects the "Catalog
  - Add area" menu item from the Image Classifier menu bar before an area has
  been selected or masked.
o The user attempts to drag/drop from the image to a sampler before an area has
  been selected or masked.

ACTION: Try one of the following:

o Use the select or mask tools to select an area before you add it to the
  Catalog or drag/drop to a sampler.
o If the whole image is to be added to the Catalog or drag/dropped to a
  sampler, select the "Edit - Select all" menu item from the Image Classifier
  menu bar.


ΓòÉΓòÉΓòÉ 454. The thumbnail was not created. ΓòÉΓòÉΓòÉ

ERROR: An error occured while the thumbnail file and mask files were eing
created.

CAUSE: Possible causes are:

o The application required more storage than was currently available.
o An internal processing error occured.
o A unique thumbnail name could not be generated.

ACTION: Try one of the following:

o If this message was preceded by a memory allocation error, do the following:

   - Close any windows that are not needed.

   - Close all applications not being used.

   - Archive any large or infrequently used files or delete any unnecessary
     files on the disk where the SWAPPER.DAT file exists.

   - Rerun the program.

o If this message was preceded by a message indicating a thumbnail name could
  not be generated, do the following:

   - Retry the operation using another Catalog.

   - Retry the operation using another Image.

o If any other message preceded this message, retry the same operation.


ΓòÉΓòÉΓòÉ 455. Unable to load Image Analyzer program. ΓòÉΓòÉΓòÉ

ERROR: You are trying to do the Analyze function from the Image Classifier, but
the Image Analyzer program can not be loaded.

CAUSE: Possible causes are:

o The Image Analyzer program does not exist.
o The Image Analyzer program has been renamed.
o The Image Analyzer program is in a directory which is not in the correct
  path.

ACTION: Try one of the following:

o Reinstall Ultimedia Manager/2 if the Image Analyzer program does not exist.
o Rename the Image Analyzer program back to the correct name.
o Include the directory where the Image Analyzer program resides in the PATH
  statement and reboot the system.


ΓòÉΓòÉΓòÉ 456. Drag/Drop error: Cannot end data transfer. ΓòÉΓòÉΓòÉ

ERROR: You are trying to drag an object using the Image Classifier but an error
stopped the process.

CAUSE: Shared memory is not available.

ACTION: Try one of the following:

o Try the same drag and drop again.
o Shutdown OS/2 and restart the system, then try the same drag and drop again.
o If the symptom persists, call your administrator.


ΓòÉΓòÉΓòÉ 457. Unable to calculate the masked area correctly. ΓòÉΓòÉΓòÉ

ERROR: An unknown error occured calculating the coordinates of the area.

CAUSE: Possible causes are:

o Internal error.

ACTION: Try one of the following:

o Remove the currently defined area from the image and recreate a new one.


ΓòÉΓòÉΓòÉ 458. Could not calculate the selected or masked area ΓòÉΓòÉΓòÉ

ERROR: An error occured attempting to find the rectangular area surrounding the
defined area.

CAUSE: Possible causes are:

o A memory allocation error occured (if this is the case, a memory allocation
  error would have preceded this error message).
o Internal error.

ACTION: Try one of the following:

o If this message was preceded with a memory allocation error message, follow
  the suggested actions for that message.
o Remove the currently defined area from the image and recreate a new one.


ΓòÉΓòÉΓòÉ 459. Could not generate a thumbnail name ΓòÉΓòÉΓòÉ

ERROR: A unique thumbnail name could not be generated for the area on the image
displayed.

CAUSE: Possible causes are:

o More than 99 sub-areas have been selected from this particular image within
  the same Catalog.
o A memory allocation error occured.

ACTION: Try one of the following:

o Retry the operation using another Catalog.
o Retry the operation using another Image.
o Close any windows that are not needed.
o Close all applications not being used.
o Archive any large or infrequently used files or delete any unnecessary files
  on the disk where the SWAPPER.DAT file exists.


ΓòÉΓòÉΓòÉ 460. Drag/Drop - Could not open mask file ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to open the mask file.

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.

ACTION: Try one of the following:

o Restore the file if it does not exist.
o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 461. Database could not be updated ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to update the database.

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 462. Scheme object count could not be updated ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to update the object count
of the Catalog.

CAUSE: Possible causes are:

o The Catalog is locked by other use.
o An internal error.

ACTION: Try one of the following:

o Release other use of the Catalog, and try again.
o Shut down OS/2 and reboot the system, then try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 463. SQL Error ΓòÉΓòÉΓòÉ

ERROR: The program encountered a SQL error. (The error information is provided
in the error window.)

CAUSE: Possible causes are:

o The database table is corrupted.
o The logon information is incorrect.

ACTION: Try one of the following:

o Check the error information and correct it accordingly.


ΓòÉΓòÉΓòÉ 464. Error deleting file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while deleting the file. (The file name is provided in
the error window.)

CAUSE: Possible causes are:

o The file is used by other programs.

ACTION: Try one of the following:

o Close other use of the file and try again.


ΓòÉΓòÉΓòÉ 465. Catalog already exists and cannot be created. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create a new Catalog, but the Catalog name you
specified already exists.

CAUSE: Possible causes are:

o You misspelled the Catalog name.
o You are trying to open an existing Catalog, but didn't choose the correct
  menu option.

ACTION: Try one of the following:

o Correct the Catalog name and try again.
o Select "Catalog - Open" to open the existing Catalog.


ΓòÉΓòÉΓòÉ 466. A Catalog has already been specified as a parameter. ΓòÉΓòÉΓòÉ

ERROR: You specified two or more Catalog names as parameters for Image
Classifier.

CAUSE: Possible causes are:

o You entereded too many Catalog names.

ACTION: Try one of the following:

o Continue the program using the first Catalog name supplied.
o Reinvoke the program with correct parameters.


ΓòÉΓòÉΓòÉ 467. Parameters following the second parameter are ignored. ΓòÉΓòÉΓòÉ

ERROR: You entered more than two parameters for Image Classifier.

CAUSE: Possible causes are:

o You entered too many parameters.

ACTION: Try one of the following:

o Continue the program using the first two parameters supplied.
o Reinvoke the program with correct parameters.


ΓòÉΓòÉΓòÉ 468. DB Error ΓòÉΓòÉΓòÉ

ERROR: The program is trying to access the database but an error stopped the
process. (The error codeis provided in the error window.)

CAUSE: Possible causes are:

o Another instance of this database table is already in use.
o A memory allocation error.

ACTION: Try one of the following:

o Close any other session associated with this database table.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 469. The Catalog does not exist. ΓòÉΓòÉΓòÉ

ERROR: You are trying the open the Catalog, but the Catalog does not exist.
(The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the Catalog name.
o The Catalog does not exist.

ACTION: Try one of the following:

o Click 'OK' to create the Catalog.
o Click 'Cancel' to exit the open catalog function.


ΓòÉΓòÉΓòÉ 470. The default Catalog does not exist.  One will be created. ΓòÉΓòÉΓòÉ

ERROR: You are trying to bring up the program using default Catalog, but the
default Catalog does not exist. (The default Catalog name is provided in the
error window.)

CAUSE: Possible causes are:

o The default Catalog has been deleted.
o The default Catalog has been renamed.

ACTION: Try one of the following:

o Click 'OK' to create the default Catalog.
o Click 'Cancel' to respecify the Catalog name.


ΓòÉΓòÉΓòÉ 471. No Catalog name was specified. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create a new Catalog or open an existing Catalog, but
the Catalog name is not specified.

CAUSE: Possible causes are:

o You did not enter the Catalog name.

ACTION: Try one of the following:

o Enter the Catalog name in the enty field.
o Select the Catalog from the New/Open Catalog dialog.


ΓòÉΓòÉΓòÉ 472. Using default Catalog name extension CLS. ΓòÉΓòÉΓòÉ

ERROR: The Catalog name specified does not have the correct extension CLS.

CAUSE: Possible causes are:

o You specified the Catalog name without extension.
o You specified the Catalog name with invalid extension.

ACTION: Try one of the following:

o
o Reenter the Catalog name.
o Accept the default extension CLS.


ΓòÉΓòÉΓòÉ 473. The Catalog will not be created. ΓòÉΓòÉΓòÉ

ERROR: The program will not create the Catalog. (The Catalog name was provided
in the error window.)

CAUSE: Possible causes are:

o

ACTION: Try one of the following:

o


ΓòÉΓòÉΓòÉ 474. The mask is too large to display on this image. ΓòÉΓòÉΓòÉ

ERROR: The area selected for redisplay is too large for the image which it is
to be displayed upon.

CAUSE: Possible causes are:

o An area was created from one image and an attempt was made to display it upon
  a smaller image.

ACTION: Try one of the following:

o Redisplay the area upon a large image.
o Select a smaller area to redisplay.


ΓòÉΓòÉΓòÉ 475. The named shared memory already exists ΓòÉΓòÉΓòÉ

ERROR: The program is trying to allocate the shared memory but the named shared
memory already exists.

CAUSE: Possible causes are:

o An internal error.

ACTION: Try one of the following:

o Shut down and reboot the system, and try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 476. An error occurred outlining the area. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while outlining the area.

CAUSE: Possible causes are:

o An internal error.

ACTION: Try one of the following:

o Shut down and reboot the system, and try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 477. An error occured writing the image thumbnail to a file ΓòÉΓòÉΓòÉ

ERROR: An error occured while writing the image thumbnail to a file.

CAUSE: Possible causes are:

o The application required more storage than was currently available.
o An internal processing error occured.

ACTION: Try one of the following:

o Close unneeded applications or windows.
o Shutdown OS/2 and restart the system.
o If the symptom persists, call the service representative.


ΓòÉΓòÉΓòÉ 478. Removing the feature will result in all data being deleted. ΓòÉΓòÉΓòÉ

ERROR: You are changing the settings of the Catalog by removing feature(s) from
it.  A warning message is displayed to warn you about the consequences. (The
features you are trying to delete is provided in the warning window.)

CAUSE: Possible causes are:

o You understand the consequences of removing the feature and wish to continue.
o You didn't know the consequences of the changes you are making and this is
  the time to cancel it.

ACTION: Try one of the following:

o Press OK to proceed the changes you want to make.
o Press Cancel to discard the change.


ΓòÉΓòÉΓòÉ 479. Error accessing the specified drive or directory. ΓòÉΓòÉΓòÉ

ERROR: You are trying to access the specified drive or directory, but an error
stopped the process.

CAUSE: Possible causes are:

o The specified drive or directory is not available.

ACTION: Try one of the following:

o Reconnect the unavailable drive and try again.  .


ΓòÉΓòÉΓòÉ 480. Error reading Catalog's control file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the Catalog's
control file.

CAUSE: Possible causes are:

o You specified a wrong name for Catalog.
o You opened a Catalog which does not have a control file.
o The control file is corrupted.

ACTION: Try one of the following:

o Open another Catalog.
o Regenerate the control file and try again.


ΓòÉΓòÉΓòÉ 481. Server name required for Oracle Catalog. ΓòÉΓòÉΓòÉ

ERROR: You are trying to create a Catalog with Oracle database type, but you
did not specify the server name required.

CAUSE: Possible causes are:

o You did not enter the required server name.

ACTION: Try one of the following:

o Enter the server name and try again.


ΓòÉΓòÉΓòÉ 482. ULTITOOL.INI file is invalid. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to save the state information to the ULTITOOL.INI
file, but the file is invalid.

CAUSE: Possible causes are:

o The ULTITOOL.INI file is corrupted.
o The ULTITOOL.INI file has invalid format.

ACTION: Try one of the following:

o Delete the invalid the ULTITOOL.INI and try again.


ΓòÉΓòÉΓòÉ 483. Category not defined in the sampler. ΓòÉΓòÉΓòÉ

ERROR: You specified a category for an area in the Catalog, but the category
has not been defined in the category sampler.

CAUSE: Possible causes are:

o You specified the category name incorrectly.
o You have not define the new category in the category sampler.

ACTION: Try one of the following:

o Correct the category if it is incorrect.
o Define the new category sampler for later query.


ΓòÉΓòÉΓòÉ 484. No areas classified for the image displayed. ΓòÉΓòÉΓòÉ

ERROR: You are trying to display the areas of the image, but no areas were
calssified for the image.

CAUSE: Possible causes are:

o You have not added any area of the image to the Catalog.

ACTION: Try one of the following:

o Add areas of the image to the Catalog and then display the areas.
o Load other images and then display the areas.


ΓòÉΓòÉΓòÉ 485. Category name changed. Update areas with new name? ΓòÉΓòÉΓòÉ

ERROR: You have changed the category name, and there are areas defined in the
Catalog with this category name.

CAUSE: The program asks for updating the changed category name in the Catalog.

ACTION: Try one of the following:

o Click on 'Yes' to update the category name in the Catalog.
o Click on 'No' to not update the category name in the Catalog.


ΓòÉΓòÉΓòÉ 486. Error accessing control information for Catalog. ΓòÉΓòÉΓòÉ

area.

ERROR: An error occurred while the program is trying to access the control
information for the Catalog. (The Catalog name is provided in the error window)

CAUSE: Possible causes are:

o The control file is corrupted.
o The control file is missing.
o An internal processing error occured.

ACTION: Try one of the following:

o Reconstruct the control file and try again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 487. BIC is cleaning up database tables. ΓòÉΓòÉΓòÉ

area.

ERROR: The program is cleaning up the database tables and updating the Catalog
control information.

CAUSE: The program acknowledge the user about the progress of cleaning up
database tables and updating Catalog control information.

ACTION: Try one of the following:

o Wait for the process to finish.


ΓòÉΓòÉΓòÉ 488. BIC: image name is missing. ΓòÉΓòÉΓòÉ

ERROR: The program is expecting an image name as a parameter. (The correct
syntax for invoking the program is provided in the error window.)

CAUSE: Possible causes are:

o You did not supply the image name.

ACTION: Try one of the following:

o Reinvoke the program with the correct syntax.


ΓòÉΓòÉΓòÉ 489. BIC: directory name is missing. ΓòÉΓòÉΓòÉ

ERROR: The program is expecting a directory name as a parameter. (The correct
syntax for invoking the program is provided in the error window.)

CAUSE: Possible causes are:

o You did not supply the directory name.

ACTION: Try one of the following:

o Reinvoke the program with the correct syntax.


ΓòÉΓòÉΓòÉ 490. BIC: list of files name is missing ΓòÉΓòÉΓòÉ

ERROR: The program is expecting a list of image names as parameters. (The
correct syntax for invoking the program is provided in the error window.)

CAUSE: Possible causes are:

o You did not supply the list of image names.

ACTION: Try one of the following:

o Reinvoke the program with the correct syntax.


ΓòÉΓòÉΓòÉ 491. BIC: mask name is missing. ΓòÉΓòÉΓòÉ

ERROR: The program is expecting a mask name as a parameter. (The correct syntax
for invoking the program is provided in the error window.)

CAUSE: Possible causes are:

o You did not supply the maks name.

ACTION: Try one of the following:

o Reinvoke the program with the correct syntax.


ΓòÉΓòÉΓòÉ 492. BIC: Catalog name is missing. ΓòÉΓòÉΓòÉ

ERROR: The program is expecting a Catalog name as a parameter. (The correct
syntax for invoking the program is provided in the error window.)

CAUSE: Possible causes are:

o You did not supply the Catalog name.

ACTION: Try one of the following:

o Reinvoke the program with the correct syntax.


ΓòÉΓòÉΓòÉ 493. Image name does not exist. ΓòÉΓòÉΓòÉ

ERROR: You supply an image name as a parameter to the program, but the image
name does not exist. (The image name is provided in the error window.)

CAUSE: Possible causes are:

o The image name does not exist.
o You entered the image name incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct image name.


ΓòÉΓòÉΓòÉ 494. List file name does not exist. ΓòÉΓòÉΓòÉ

ERROR: You supply a list of file names as parameters to the program, but the
file name does not exist. (The list of file names is provided in the error
window.)

CAUSE: Possible causes are:

o The list of file names do not exist.
o You entered the list incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct list file name.


ΓòÉΓòÉΓòÉ 495. Error creating control data for classified area. ΓòÉΓòÉΓòÉ

area.

ERROR: An error occurred while the program is trying to create the control data
for the classified area of the image file. (The image file name is provided in
the error window)

CAUSE: Possible causes are:

o The application required more storage than was currently available
o An internal processing error occured.

ACTION: Try one of the following:

o Close any unneeded windows or application to free the space.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 496. Error creating control data for classified area. ΓòÉΓòÉΓòÉ

area.

ERROR: An error occurred while the program is trying to create the control data
for the classified area of the image file. (The image file name is provided in
the error window)

CAUSE: Possible causes are:

o The application required more storage than was currently available
o An internal processing error occured.

ACTION: Try one of the following:

o Close any unneeded windows or application to free the space.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 497. Error creating control data for classified area. ΓòÉΓòÉΓòÉ

area.

ERROR: An error occurred while the program is trying to create the control data
for the classified area of the image file. (The image file name is provided in
the error window)

CAUSE: Possible causes are:

o The application required more storage than was currently available
o An internal processing error occured.

ACTION: Try one of the following:

o Close any unneeded windows or application to free the space.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 498. BIC: Directory is empty. ΓòÉΓòÉΓòÉ

ERROR: You supply a directory name as a parameter to the program, but the
directory is empty. (The directory name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the directory name.
o You have not copied image files to the directory for classification.

ACTION: Try one of the following:

o Reinvoke the program with another directory name.


ΓòÉΓòÉΓòÉ 499. BIC: List file is empty. ΓòÉΓòÉΓòÉ

ERROR: You supply a list of file names as a parameter to the program, but the
list is empty. (The list file is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the list file name.

ACTION: Try one of the following:

o Reinvoke the program with another list file name.


ΓòÉΓòÉΓòÉ 500. There is no image selected. ΓòÉΓòÉΓòÉ

ERROR: The program expects to process images for batch classification, but no
image is selected.

CAUSE: Possible causes are:

o You did not select any image.

ACTION: Try one of the following:

o Select the image file and try again.


ΓòÉΓòÉΓòÉ 501. BIC: could not find image name. ΓòÉΓòÉΓòÉ

ERROR: You supply an image name as a parameter to the program, but the image
name does not exist. (The image name is provided in the error window.)

CAUSE: Possible causes are:

o The image name does not exist.
o You entered the image name incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct image name.


ΓòÉΓòÉΓòÉ 502. BIC: could not find directory name. ΓòÉΓòÉΓòÉ

ERROR: You supply a directory name as a parameter to the program, but the
directory name does not exist. (The directory name is provided in the error
window.)

CAUSE: Possible causes are:

o The directory name does not exist.
o You entered the directory name incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct directory name.


ΓòÉΓòÉΓòÉ 503. BIC: could not find listfile name. ΓòÉΓòÉΓòÉ

ERROR: You supply a list of file names as parameters to the program, but the
list of file names does not exist. (The list of file names is provided in the
error window.)

CAUSE: Possible causes are:

o The list of file names does not exist.
o You entered the list of file names incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct list of file names.


ΓòÉΓòÉΓòÉ 504. BIC: could not find mask name. ΓòÉΓòÉΓòÉ

ERROR: You supply a mask name as a parameter to the program, but the mask name
does not exist. (The mask name is provided in the error window.)

CAUSE: Possible causes are:

o The mask name does not exist.
o You entered the mask name incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct mask name.


ΓòÉΓòÉΓòÉ 505. BIC: could not find Catalog name. ΓòÉΓòÉΓòÉ

ERROR: You supply a Catalog name as a parameter to the program, but the Catalog
name does not exist. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o The Catalog name does not exist.
o You entered the Catalog name incorrectly.

ACTION: Try one of the following:

o Reinvoke the program with the correct Catalog name.


ΓòÉΓòÉΓòÉ 506. Catalog creation error: database can't be connected by ΓòÉΓòÉΓòÉ

user.

ERROR: You are trying to create a Catalog, but the database can not be
connected by the specified user. (The database name and UserID are provided in
the error window)

CAUSE: Possible causes are:

o The database has already be used by other user.

ACTION: Try one of the following:

o Release other use of the database and try again.


ΓòÉΓòÉΓòÉ 507. Catalog creation error: database has already been used ΓòÉΓòÉΓòÉ

by other Catalog.

ERROR: Database has already been used by another Catalog. (The database name
and Catalog name are provided in the error window)

CAUSE: Possible causes are:

o

ACTION: Try one of the following:

o


ΓòÉΓòÉΓòÉ 508. Catalog creation error: userid specified cannot be logged ΓòÉΓòÉΓòÉ

on.

ERROR: Userid cannot be logged on. (The userid is provided in the error window)

CAUSE: Possible causes are:

o The userid supplied in invalid.

ACTION: Try one of the following:

o Supply a valid userid.


ΓòÉΓòÉΓòÉ 509. Catalog creation error: userid has already been used by ΓòÉΓòÉΓòÉ

other Catalog.

ERROR: Userid has already been used by other Catalog. (The userid and Catalog
name are provided in the error window)

CAUSE: Possible causes are:

o The userid supplied is used by other Catalog.

ACTION: Try one of the following:

o Release the userid used by other Catalog, and try again.


ΓòÉΓòÉΓòÉ 510. Catalog creation error: can't create table. ΓòÉΓòÉΓòÉ

ERROR: Cannot create specified table(s). (The table name is provided in the
error window)

CAUSE: Possible causes are:

o Not enough space.
o Other unique internal error.

ACTION: Try one of the following:

o


ΓòÉΓòÉΓòÉ 511. Catalog creation error: can't create table in the database. ΓòÉΓòÉΓòÉ

ERROR: Cannot create database table for specified database. (The table name and
database name are provided in the error window)

CAUSE: Possible causes are:

o

ACTION: Try one of the following:

o


ΓòÉΓòÉΓòÉ 512. Error occurred attempting to save profile settings. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to save the profile information to the
ULTITOOL.INI file but an error occurred while saving the information.

CAUSE: Possible causes are:

o There may have been a system error when attempting to write to the file.
o The ULTITOOL.INI file is corrupted.
o The operating system could not find a read/write drive in the search path.

  The search path is the:

   - Current directory

   - Directory where .EXE resides

   - Path given in UMPATH environment variable

ACTION: Try one of the following:

o Delete the ULTITOOL.INI file and try again.
o Set the current directory to a drive that can write data to disk.
o Verify that the directory in the UMPATH variable specifies a drive that can
  write data on a disk.


ΓòÉΓòÉΓòÉ 513. File extension for query file must be '.iq'. ΓòÉΓòÉΓòÉ

ERROR: You are trying to save the query to a query file, but the query file
name does not have a valid extension '.iq'. (The suggested query file name is
provided in the error window)

CAUSE: Possible causes are:

o You specified the query file without extension.
o You specified the query file with extension other than '.iq'.

ACTION: Try one of the following:

o Click on 'Yes' to save the query using the suggested query file name in the
  error window.
o Click on 'No' to not save the query.
o Click on 'Cancel' to cancel the save operation.


ΓòÉΓòÉΓòÉ 514. Can't start image browser. ΓòÉΓòÉΓòÉ

ERROR: You are trying to start the image browser, but the image file does not
exist. (The image file name is provided in the error window.)

CAUSE: Possible causes are:

o The file has invalid format.
o The file does not exist.

ACTION: Try one of the following:

o Restore the file and try again.


ΓòÉΓòÉΓòÉ 515. Query file has invalid format or does not exist. ΓòÉΓòÉΓòÉ

ERROR: You are trying to open a query file, but the query file you specified is
not correct. (The query file name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the file name.
o The file has invalid format.
o The file does not exist.

ACTION: Try one of the following:

o Correct the file name.
o Delete the query file, and reconstruct the query again.


ΓòÉΓòÉΓòÉ 516. Query has been modified.  Save the query? ΓòÉΓòÉΓòÉ

ERROR: You tried to exit the Image Query program without saving the change to
the query file.

CAUSE: The program asks for confirmation before exiting the Image Query
program.

ACTION: Try one of the following:

o Click on 'Yes' if you want to save the changes and then exit the Image Query
  program.
o Click on 'No' to exit the Image Query program without saving the changes.
o Click on 'Cancel' to cancel the exit operation and return to the Image Query
  program.


ΓòÉΓòÉΓòÉ 517. Query has been cancelled.  See the result? ΓòÉΓòÉΓòÉ

ERROR: You cancelled the query process while the query is not complete.

CAUSE: The program asks for partial display of the query results.

ACTION: Try one of the following:

o Click on 'Yes' if you want to see the query result.
o Click on 'No' to exit the message box.


ΓòÉΓòÉΓòÉ 518. File already exists.  Want to overwrite it? ΓòÉΓòÉΓòÉ

ERROR: You tried to save the current query to an existing query file. (Query
file name is provided in the error window.)

CAUSE: Possible causes are:

o You do want to overwrite the existing query file.
o You misspelled the file name.

ACTION: Try one of the following:

o Click on 'Yes' if you want to overwrite the existing query file.
o Click on 'No' to reenter the query file name.
o Click on 'Cancel' to cancel the save operation.


ΓòÉΓòÉΓòÉ 519. No write permission to query file. ΓòÉΓòÉΓòÉ

ERROR: You tried to save the current query to a read-only query file. (Query
file name is provided in the error window.)

CAUSE: Possible causes are:

o You didn't realize that it is a read-only query file.
o You misspelled the file name.

ACTION: Try one of the following:

o Click on 'Yes' to reenter the query file name in the 'Save' dialog.
o Click on 'No' to exit the 'Save' or 'Save as' option.


ΓòÉΓòÉΓòÉ 520. Conflict between weight settings and Catalog. ΓòÉΓòÉΓòÉ

ERROR: You are trying to run a query, but the query can not be run because
there is a conflict between the weight settings of the query and the Catalog
features.

CAUSE: Possible causes are:

o You open a Catalog which does not have the feature you want to do the query
  on.

ACTION: Try one of the following:

o Deselect the features from the weight settings of the query that are not
  supported in the Catalog.
o Delete the sample in the query which is not supported in the Catalog.
o Open another Catalog which has the feature you want to query.


ΓòÉΓòÉΓòÉ 521. Unable to open file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to open the file. (The
file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.

ACTION: Try one of the following:

o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 522. Unable to read from file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read from the file.
(The file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.
o The file has invalid format.

ACTION: Try one of the following:

o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 523. Unable to write to file. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to write to the file. (The
file name is provided in the error window.)

CAUSE: Possible causes are:

o The file name does not exist.
o The file name is supplied incorrectly
o The file is locked by other users.
o The file has invalid format.
o The file is read-only.

ACTION: Try one of the following:

o Supply the correct file name and try again.


ΓòÉΓòÉΓòÉ 524. Unable to open database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to open the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 525. Unable to read database schema. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read the database
heading information. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 526. Unable to read database record from database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to read a database record.
(The database table name and the error are provided in the error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 527. Unable to write database record to database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to write a record to the
database table. (The database table name and the error are provided in the
error window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.

ACTION: Try one of the following:

o Supply the correct logon information and try again.
o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 528. Unable to close database table. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to close the database
table. (The database table name and the error are provided in the error
window.)

CAUSE: Possible causes are:

o The database table does not exist.
o The database table is corrupted.
o Logon information supplied is incorrect.
o A memory allocation error.
o An internal processing error occured.


ΓòÉΓòÉΓòÉ 529. Column is missing from database table. ΓòÉΓòÉΓòÉ

ERROR: A column is missing from the database table. (The database table name
and the error are provided in the error window.)

CAUSE: Possible causes are:

o The column was deleted from the database table.
o The database table is corrupted.
o An internal processing error occured.

ACTION: Try one of the following:

o Add the column to the database table.
o Reconstruct the database table.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 530. Cannot create database table. ΓòÉΓòÉΓòÉ

ERROR: Your database table can not be created due to error. (The database table
name and the error are provided in the error window.)

CAUSE: Possible causes are:

o There is not enough disk space.
o You misspelled the table name.
o There already is a database file by that name.
o Incorrect logon information.

ACTION: Try one of the following:

o Verify that your system meets the minimum requirements for the product.
o Close unneeded applications or window.
o Delete any unnecessary files on the disk where the SWAPPER.DAT file exists.
o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 531. Window creation failed. ΓòÉΓòÉΓòÉ

ERROR: An error occurred while the program is trying to create a window.

CAUSE: The program cannot create a window.

ACTION: Try one of the following:

o Shutdown OS/2 and restart the system, then try the same operation again.
o If the symptom persists, call your service representative.


ΓòÉΓòÉΓòÉ 532. Catalog does not exist. ΓòÉΓòÉΓòÉ

ERROR: The program is trying to load the Catalog, but the Catalog name does not
exist. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o The Catalog name does not exist.
o You entered the Catalog name incorrectly.

ACTION: Try one of the following:

o Correct the Catalog name and try again.


ΓòÉΓòÉΓòÉ 533. Catalog contains unanalyzed areas or deleted records, run ΓòÉΓòÉΓòÉ

Image Analyzer.

ERROR: The Catalog loaded contains unanalyzed areas which should be analyzed
before running the query. (The Catalog name is provided in the error window.)

CAUSE: Possible causes are:

o New areas were added to the Catalog but has not been analyzed yet.
o Records were deleted from the the Catalog.

ACTION: Try one of the following:

o Run the Image Analyzer and then try the query.


ΓòÉΓòÉΓòÉ 534. Object has invalid data, run Image Analyzer. ΓòÉΓòÉΓòÉ

ERROR: The Catalog loaded contains invalid data.

CAUSE: Possible causes are:

o Database record were updated incorrectly.

ACTION: Try one of the following:

o Run the Image Analyzer and then try the query.


ΓòÉΓòÉΓòÉ 535. Parameter is neither a Catalog nor a query file. ΓòÉΓòÉΓòÉ

ERROR: You specified a parameter for the Image Query program, but the parameter
is neither a Catalog name nor a query file name.  This parameter is ignored.
(The parameter is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the name.
o You supplied the parameter incorrectly.

ACTION: Try one of the following:

o Reinvoke the Image Query with a correct Catalog name and/or query file name.
o To select the query file, select the "Query - Open" menu item from the Image
  Query menu bar.
o To select a Catalog, select the "Query - Open Catalog" menu item from the
  Image Query menu bar.


ΓòÉΓòÉΓòÉ 536. This is not a Catalog. ΓòÉΓòÉΓòÉ

ERROR: The name supplied withe the program is not a Catalog name. (The Catalog
name is provided in the error window.)

CAUSE: Possible causes are:

o You misspelled the name.
o You supplied the parameter incorrectly.

ACTION: Try one of the following:

o Reinvoke the Image Query with a correct Catalog name and/or query file name.
o To select a Catalog, select the "Query - Open Catalog" menu item from the
  Image Query menu bar.