|
» |
|
|
|
Access Method Messages | |
Error | Message | Cause/Action |
---|
086 | Access method: file code error.
|
| | 087 | Access method: Attempt to add a duplicate key.
|
| | 088 | Access method: Internal error. Key insertion location error.
|
| | 089 | Access method: Internal error. Block not present.
|
| | 090 | Access method: Attempt to open an old file as new.
|
| | 091 | Access method: Internal error. Key block buffer error,
|
| | 092 | Access method: Internal error. Invalid key block number.
|
| | 093 | Access method: Internal error. Block not verified.
|
| | 094 | Access method: Record not found.
|
| | 095 | Access method: Not enough space in extension for the directory.
|
| Increase the MAXDATA parameter on the PREP or RUN command. Check the FORMSPEC listing for directory size. | 096 | Access method: Internal error. Parent block not found.
|
| | 097 | Access method: Internal error. Illegal entry number.
|
| | 098 | Access method: The file is not a KSAMless forms/ ref file.
|
| | 099 | Access method: The file is at EOF.
|
| |
Screen Definition Messages | |
Error | Message | Cause/Action |
---|
101 | Form is too big, overflowed the screen buffer.
|
| Maximum screen buffer size
is 7984 bytes. Reduce the size of your form. | 102 | Form ! is too big to becompiled.
|
| Form code record has exceeded
8K bytes. Maximum number of fields is 127. Reduce the number of
fields, size of screen, or amount of processing specifications. | 103 | An END FIELD must have a matching START FIELD.
|
| Check your screen design
to make sure that each "end field" delimiter has a matching "begin field"
delimiter. If your delimiters are the unprinted kind (ESC [and ESC]),
it may be more convenient to delete the line containing the delimiters
and to replace them. | 106 | Internal error: All of the screen was not read correctly.
|
| Possibly a missing record terminator.
Press ENTER again. If the error still occurs, reduce the size of the
form or of the processing specifications. | 107 | A name cannot be longer than 15 characters.
|
| Limit your form, field, or save
field names to 15 characters. | 108 | A name cannot have embedded " "'s or "."'s.
|
| Blanks and periods not allowed
in names. | 109 | A name must start with an alphabetic character.
|
| Special characters and digits
are not allowed. | 110 | A name cannot have embedded " "'s or "."'s.
|
| See error 108. | 111 | A name can only contain alphas, digits and "_"'s.
|
| Letters (A-Z), (a-z), numbers
(0-9), or an underline ( _ ) are allowed in a name. | 112 | Internal error: Unexpected CR.
|
| Unexpected carriage return. | 113 | Internal error: Screen terminator never found.
|
| See message for error 106. Also
make sure enough terminal buffers are configured to complete the
rest of the screen. The number of buffers can be increased to 255. | 114 | Internal error: Expected LF after CR.
|
| Line feed expected after
carriage return. | 115 | A field must contain a name.
|
| Each field on the screen must
have a name within the field boundaries. | 116 | Internal error writing screen message. (COM'STATUS !!!!)
|
| | 117 | Terminal error initializing new screen. (COM'STATUS !!!!)
|
| | 118 | Terminal error writing new screen. (COM'STATUS !!!!)
|
| | 119 | Terminal error writing new screen. (COM'STATUS !!!!)
|
| | 120 | Terminal error initializing old screen. (COM'STATUS !!!!)
|
| | 121 | Terminal error writing old screen. (COM'STATUS !!!!)
|
| | 122 | Terminal error reading screen. (COM'STATUS !!!!)
|
| See error 106. | 123 | Error writing the screen source. File full? (FSERR!!!!)
|
| Could not write the screen source
record to the form file. First try to correct the problem using the
information given in the File System error message. If you are unsuccessful,
try the following: a) The file may be full. Build a larger file
using the :BUILD command and FCOPY> b) A system crash or abort may have corrupted the
form. Re-enter all menus defining the form. c) If the above intrinsics
fail, delete the form and recreate it. | 124 | Internal error reading the screen source for form !. (FSERR !!!)
|
| Could not read the screen
source record from the forms file. See error 123. | 125 | A name can only be in the first line of the field.
|
| If a field is continued on a second
line, the name must be in the first line. | 126 | A name can only be in the first line of the field.
|
| See error 125. | 127 | Internal error: Allocate of GLOB'SCREEN failed.
|
| | 128 | Error writing the global screen record. File full? (FSERR!!!!)
|
| See error 123. | 129 | Internal error: Allocate of STBL failed.
|
| Could not allocate stack space
for symbol table. | 130 | Error writing STBL to the forms file. File full? (FSERR!!!!)
|
| See error 123. | 131 | INTERNAL ERROR: changing screen of family.
|
| | 132 | Only 128 fields are allowed in a form.
|
| Reduce the number of fields in the form. |
Field Symbol Table Messages | |
Error | Message | Cause/Action |
---|
301 | Internal error: FST ALLOCATE for form ! failed.
|
| FST is Field Symbol Table.
See error 129. | 302 | Internal error: Field symbol table for form ! is missing.
|
| See error 123. Could not
find Field Symbol Table for old form in form file. Press ENTER on screen design to re-create FST. | 303 | Error writing FST to forms file. File full?
|
| Could not write FST record in
forms file. See error 123. | 304 | Internal error: FST does not have any more room.
|
| Renumber the form in batch mode. | 305 | The name must be unique for this form.
|
| The field name is the same as
another field name in the same form. | 306 | Internal error: FST search range error.
|
| Field Symbol Table search problem.
See error 304. | 307 | Internal error: FST field length changed.
|
| Field Symbol Table access problem.
See error 304. | 308 | Internal error: FST start order.
|
| Field Symbol Table structure
problem. See error 304. | 309 | Internal error: FST end order.
|
| Field Symbol Table structure problem.
See error 304. | 313 | Internal error: FST unreferenced error.
|
| Field Symbol Table structure problem.
See error 304. | 314 | Internal error: In form !, field ! has an invalid screen order.
|
| Field Symbol Table structure
problem. See error 304. | 315 | The field could not be found.
|
| Field name does not exist. | 316 | Internal error: FST update screen order.
|
| See error 308. | 317 | The field number must be unique for this form.
|
| See error 308. | 319 | In form !, screen order for field ! is out of bounds.
|
| See error 304. | 320 | Internal error: FST wrap loop.
|
| See error 308. | 321 | Internal error reading FST for form !. (FSERR !!!)
|
| See errors 123, 303. | 322 | Internal error storing FST for form !. (FSERR !!!)
|
| See errors 123, 303. | | Internal error: CFG ALLOCATE for form ! failed.
|
| | | The field number cannot be more than 256.
|
| Too many modifications have been made to the
screen for this form. The form must be rebuilt from scratch or renumbered
in batch. |
Menu Processing Utility Messages | |
Error | Message | Cause/Action |
---|
601 | Must be B, H, I, U, 1-8, in any combination, or NONE.
|
| Enhancement code is incorrect;
check and correct. | 604 | The name cannot have embedded blanks.
|
| A field or form name has embedded
blank; delete blank or use underline (_). | 605 | The form name must be unique for this forms file.
|
| Form name duplicates another form
name in file; make name unique. | 606 | Must be NUMn, DIG, IMPn, MDY, DMY, YMD, or CHAR.
|
| Data type incorrect; use one of
the listed codes - n indicates number of decimal positions. | 608 | Must be 0 (optional), R (required), P (process) or D (display only).
|
| Field type incorrect; use one
of the listed codes. | 609 | Internal error: Global allocate failed.
|
| | 610 | Error writing globals buffer. File full? (FSERR!!!!)
|
| See error 123. | 611 | For a NUMn data type, n must be a digit.
|
| Use digit (0-9) after NUM data
type to indicate number of decimal positions. | 612 | For the IMPn data type, n is required.
|
| You must specify the number
of implied decimal places in an IMP type field. | 613 | The name cannot be a reserved word.
|
| Refer to the list of the FORMSPEC
reserved words. | 615 | Color pair value must be between 1 and 8.
|
| |
Menu Init and Processing Messages | |
Error | Message | Cause/Action |
---|
701 | The name cannot be blank.
|
| The form name must be specified
on FORM menu. | 702 | The next form name cannot be blank.
|
| Specify a particular next form
name, or $HEAD, $END, $RETURN, or $REFRESH. | 703 | Error trying to open the forms file. (FSERR!!!!)
|
| Refer to the File System Error
number for the cause of the open failure. Check form name. Do not
use the key file if the form file is old. | 704 | The window line must be a number between 0 and 24, inclusive.
|
| Correct window specification on
GLOBALS menu. | 705 | Must be N (no repeat), R (repeat), or A (repeat and append).
|
| Correct Repeat Option on FORMS
menu. | 706 | Must be C (clear), A (append), or F (freeze, then append).
|
| Correct Next Form option on FORMS
menu. | 707 | Internal error writing top lines to terminal.then append).
|
| Field Menu. | 708 | Internal error writing terminal initialization.(COM'STATUS !!!!)
|
| | 709 | Internal error writing field specs to terminal. (COM'STATUS !!!!)
|
| Field Menu. | 710 | Error in VREADFIELDS. (COM'STATUS !!!!)
|
| | 711 | Internal error reading the terminal, unformatted. (COM'STATUS !!!!)
|
| Screen read error or processing
specification read error. | 712 | Internal error positioning the cursor. (COM'STATUS !!!!)
|
| | 713 | Error in VSHOWFORM. (COM'STATUS !!!!)
|
| | 714 | Internal error writing the window. (COM'STATUS !!!!)
|
| | 715 | Internal error writing the Field Menu source record.(FSERR!!!!)
|
| | 716 | Internal error writing the error cursor pos' n. (COM'STATUS !!!!)
|
| | 717 | Internal error writing the field top lines. (COM'STATUS !!!!)
|
| Field Menu. | 718 | Error in VGETNEXTFORM for Main Menu. (COM'STATUS !!!!)
|
| | 719 | Error in VSHOWFORM for Main Menu. (COM'STATUS !!!!)
|
| | 720 | Error in VREADFIELDS for Main Menu. (COM'STATUS !!!!)
|
| | 721 | Selection cannot be blank.
|
| Enter a value in the MAIN menu
selection box. | 722 | The form could not be found.
|
| Form specified on MAIN menu not
found in forms file. In batch mode, form not found in current forms
file. | 723 | Selection must be one of the characters listed below.
|
| Enter one of the specified characters
in the MAIN menu selection box. | 724 | This selection requires a form name to be supplied.
|
| Specify a form name in the appropriate
box, or enter a different character in the selection box. | 725 | Err writing form int'm. rec for form !. File Full? (FSERR !!!)
|
| See error 123. Field Symbol Table
error. | 726 | Internal error initializing the form!.
|
| | 727 | A forms file has not yet been specified, so selection is invalid.
|
| To copy or compile from MAIN menu,
forms file must have been specified on FORMS FILE menu. | 728 | File does not exist. Press ENTER to create file.
|
| | 734 | There was an error trying to open this forms file. (FSERR !!!!)
|
| | 736 | Internal error reading the forms file. (FSERR !!!!)
|
| | 740 | There are no forms in this forms file.
|
| Specified forms file has
no defined forms. | 742 | Save field length cannot be blank.
|
| Enter number of characters in
save field on SAVE FIELD menu. | 743 | Save field length must be an integer greater than 0.
|
| | 744 | This save field already exists.
|
| Use a new save field name. | 745 | A forms file can only have 20 save fields.
|
| | 746 | There are no save fields in this forms file.
|
| | 747 | The save field name cannot be blank.
|
| Enter a save field name on the
SAVE FIELD menu. | 748 | WARNING: Forms file modified and not compiled.Press EXIT to exit.
|
| You modified the forms file and
then pressed EXIT. If you want to compile before terminating FORMSPEC, press
MAIN, otherwise press EXIT again. | 749 | This file is a Fast Forms File and cannot be modified.
|
| You are attempting to modify a
fast forms file; use the forms file name you originally specified. | 750 | This file is a Reformat file; use REFSPEC to modify it.
|
| Specify a forms file name,
or RUN REFSPEC.PUB.SYS to modify the reformat file. | 751 | This file is not a VPLUS Forms File.
|
| You specified an incorrect file
name. | 752 | Error opening the Fast Forms File. (FSERR !!!!)
|
| | 753 | Error reading the forms file. (FSERR !!!!)
|
| | 754 | Error writing to the Fast Forms File. File full? (FSERR !!!!)
|
| See error 123. | 755 | Error finding the correct record. (FSERR !!!!)
|
| | 756 | Error reading the chained records. (FSERR !!!!)
|
| | 757 | Error opening the old Fast Forms File. (FSERR !!!!)
|
| | 758 | Error purging the old Fast Forms File. (FSERR !!!!)
|
| | 759 | Error closing the Fast Forms File. (FSERR !!!!)
|
| | 760 | The old file is not a VPLUS Fast Forms File.
|
| The fast forms file name you specified
is not an existing VPLUS fast forms file. | 761 | This file is not a VPLUS forms file.
|
| See error 751. | 762 | Fast forms file name must be specified if key file is specified.
|
| You are trying to compile to a
fast forms file without naming the data file. | 763 | Copy/rename/delete I/O error. (FSERR !!!!)
|
| See error 123. | 764 | Error when deleting an old record.
|
| See error 123. | 765 | The specified family is not defined.
|
| | 766 | Cannot change screen, the form is a family member.
|
| User pressed ENTER on the screen of a child form or attempted to change the
screen. Press REFRESH (f4) to repaint the original and press NEXT (f6) to go to the field menus. | 767 | Cannot change family of the form.
|
| Do not attempt to change
the name in the "Reproduced from" field of the form menu. | 768 | | A write to file FORMLIST failed. Check for
a valid file equation or for spooling problems. |
Batch Mode Messages | |
Error | Message | Cause/Action |
---|
769 | Invalid batch mode command.
|
| FORMSPEC expected a valid batch
mode command or parameter. | 770 | Warning: Forms file modified and not compiled.
|
| The forms file must be compiled
before it can be used. | 771 | Could not open command and not compiled.
|
| Check file name, security,
or if in use elsewhere. | 772 | Could not open list file.
|
| Check file name, security, or
if in use elsewhere. | 774 | In form !, field !, "!" is undefined:
|
| An error was found in a field
during compilation. (See next error message printed.) | 775 | Internal error in form !, field !:
|
| An error was found in a field
during compilation. (See next error message printed.) | 776 | Form !, field ! has semantic error:
|
| An error was found in a field
during compilation. The syntax of the statement in the field may
be correct, but its meaning is wrong. (See next error message printed.) | 777 | Form !, field ! has a data type error:
|
| An error was found in a field
during compilation. Data type inconsistent with specification. (See
next error message printed.) | 778 | Form !, field ! hasa syntactic error:
|
| Statement syntax is incorrect.
(See next error message printed.) | 780 | Commands must be preceded by a FILE command.
|
| Current forms file must be specified. | 781 | | Form name must be specified. | 782 | | Forms file name must be specified. | 783 | Missing fast forms file name.
|
| Fast forms file name must be specified
when "INTO" is used. | 784 | | Too many parameters were specified
for the command. | 785 | Expecting "TO form-name".
|
| The form name must be specified
when "TO" is used. | 786 | Expecting "IN forms-file" or "TO form-name".
|
| COPY command must include either "IN file" or "TO newform". | 787 | Expecting "INTO fast-forms-file".
|
| The only option for the COMPILE command is "INTO" followed by the fast forms file name. | 788 | Internal error in FORMSPEC processing.
|
| See System Manager. | 789 | All commands ignored until next FILE command.
|
| Either a command was not recognized
or an error occurred with a FILE command. | 790 | | |
RELATE Command Messages | |
Error | Messages | Cause/Action |
---|
791 | Child cannot have the same name as parent.
|
| Same form name was specified as
the parent and child form. | 792 | Form is already child of that parent.
|
| The forms are already related. | 793 | Child form is already related to another parent.
|
| A child cannot have more than
one parent. | 794 | Form specified as child cannot have any children.
|
| A child form cannot be a parent. | 795 | Form layout of child must be the same as parent.
|
| The form layouts must be identical,
including field tags. | 796 | Field numbers of child must be the same as parent.
|
| When the field numbers do not
match, the forms cannot be related. | 797 | Correct syntax is: "RELATE child-form-name TO parent-form-name".
|
| Arguments in the batch mode command
were mistyped. | 798 | KSAM forms files can no longer be modified - use CONVERT. PUB.SYS.
|
| Refer to Appendix H for instructions. | 799 | Cannot change color forms file on a non-color terminal.
|
| | 800 | Internal error in color conversion.
|
| |
Menu Controller Messages | |
Error | Messages | Cause/Action |
---|
802 | The PREV key is not appropriate; there are no previous menus.
|
| You are currently at the first
menu; press NEXT to go to the next menu, NEXT FORM to display the next form menu, or use the MAIN menu to
select a particular menu. | 803 | The function key just hit is not defined for this mode.
|
| | 804 | Internal error reading source record from forms file. (FSERR !!!!)
|
| See error 123 | 805 | Internal error getting next form !. (COM'STATUS !!!)
|
| | 806 | Error in VSHOWFORM. (COM'STATUS !!!!)
|
| | 807 | Error in VREADFIELDS. (COM'STATUS !!!!)
|
| | 808 | Error in VGETBUF. (COM'STATUS !!!!)
|
| | 809 | Error writing source to forms file. File full? (FSERR !!!!)
|
| See error 123. | 811 | Internal error reading form record for form !. (FSERR !!!)
|
| See error 123. | 812 | Internal error reading globals record. (FSERR !!!!)
|
| See error 123. | 813 | Internal error allocating GLOB'SCREEN for form !.
|
| | 814 | Internal error allocating STBL for form !.
|
| | 815 | NEXT is not meaningful until a forms file name is specified.
|
| Enter a forms file name on the
FORMS FILE menu. (Exit if necessary and run FORMSPEC again to display
the menu.) | 816 | NEXT is not appropriate, since there are no more forms.
|
| Use PREV or PREV FORM key, or go to the MAIN menu to request a particular form. | 817 | The save field could not found.
|
| | 820 | The PREV FORM key is not appropriate; there are no previous forms.
|
| Use NEXT or NEXT FORM key, or go to the MAIN menu to request a particular form. | 821 | Internal error allocating the globals buffer.
|
| | 822 | This value is required and cannot be blank.
|
| | 823 | Enter "Y" to go to function key labels menu.
|
| To define global function key
labels, enter "Y" on the last line of the GLOBALS menu. To define form
function key labels, enter "Y" on the Function Key Label line of the FORM menu. | 824 | Pause interval may not be negative.
|
| The Split Message Pause must be
between 1 and 99. | 825 | Invalid error light (A ... P, @@).
|
| Enter a valid error light (a letter
of the alphabet or the @@ character). | 826 | Invalid Multifunction reader definition (MARKS or HOLES).
|
| Enter either of the valid Multifunction
reader definitions. | 827 | Field may only have the values "YES" or "NO".
|
| The valid options for Corner Cut
Required are YES or NO. | 828 | Illegal combination of options for the Multifunction reader.
|
| The combinations HOLES with Clock
On and MARKS with NONE are not valid. | 829 | Invalid Multifunction reader definition (COD, CAD, NONE).
|
| Enter one of the valid Multifunction
reader definitions. | 830 | Invalid barcode type (UPC, EAN, I25, I39, MAT, ILV).
|
| Enter one of the valid Barcode
Reader types. | 831 | Internal error: Writing device intermediate record (FSERR !!!!)
|
| | 832 | Invalid combination of PAUSE INTERVAL and WAIT FOR USER
|
| If Split Message Pause is specified,
Wait for User must be NO. | 833 | Enter "CONTINUE" only, or press a function key.
|
| Only CONTINUE may be entered
in this field. | 834 | NEXT is not appropriate until the forms file has been adjusted.
|
| The specified forms file is an
old version and must be adjusted before going further. | 835 | Place name of form to be listed within List Form field.
|
| | 836 | | | 837 | Enter ''Y'' to go to Data Type Conversion Menu.
|
| |
Init and Compile Messages | |
Error | Message | Cause/Action |
---|
902 | For form !, the next form ! has not been defined.
|
| The next form name specified
does not exist in the forms file. Change the next form name or create
a form with that name. | 903 | The head form ! has not been defined.
|
| The head form specified on the
globals menu does not exist in the forms file. Create a form with
the head form name or change the head form on the globals menu. | 904 | Internal error closing FORMSPEC forms file. (COM'STATUS !!!!)
|
| | 905 | Internal error closing the terminal file. (COM'STATUS !!!!)
|
| | 909 | Error writing the global code record. File full? (FSERR !!!!)
|
| See error 123. | 911 | Error writing form code record for form !. File full? (FSERR !!!)
|
| See error 123. | 912 | Internal error reading screen source for form !. (FSERR !!!)
|
| | 913 | Internal error closing your forms file. (FSERR !!!!)
|
| | 915 | Initial value contains system constant,
|
| | 916 | In form !, the field name ! is not unique.
|
| Duplicate field name found in
indicated form; use FIELD menu to change field name. | 917 | Error writing field names table for form !. File full? (FSERR !!!)
|
| | 918 | Error writing save field table for form !. File full? (FSERR !!!)
|
| See error 123. | 919 | The initial value is too long.
|
| The initial value is longer than
the length of the field as defined on the screen menu. Use the screen
menu to lengthen the field or shorten the initial value on the field
menu. | 920 | The initial value contains an invalid DIG value.
|
| A DIG type field may contain only
digits (0-9), no decimal point, commas, or sign. | 921 | The initial value contains an invalid NUM value.
|
| A NUM type field may contain only
digits, decimal point, a sign. | 922 | The initial value contains an invalid numeric value.
|
| This field may only have a numeric
value; no letters or special characters. | 923 | Internal error: For form !, allocating local buffer for field !.
|
| | 924 | Internal error: For form !, reading source for field !. (FSERR !!)
|
| See error 123. | 925 | In form !, field ! has an invalid initial value.
|
| The initial value specified does
not match the field data type. | 926 | In form !, field name !is a reserved word.
|
| Check list of reserved words and
change field name. | 927 | The initial value contains an invalid MDY date value.
|
| Make sure date is in order
month day year, is a valid date, spelled correctly. | 928 | The initial value contains an invalid DMY date value.
|
| Make sure date is in order day
month year, is a valid date, spelled correctly. | 929 | The initial value contains an invalid YMD date value.
|
| Make sure date is in order year
month day, is a valid date, spelled correctly. | 932 | The initial value contains an invalid IMP value.
|
| An implied decimal field may contain
only digits, decimal point, commas, sign. | 950 | EDIT statements are not allowed in the INIT phase.
|
| Field edits cannot be performed
in the INIT phase; move statement to FIELD phase. | 951 | EDIT statements are not allowed in the FINISH phase.
|
| Field edits cannot be performed
in the FINISH phase; move statement to FIELD phase. | 952 | Only a field, save field, or implied current field is allowed.
|
| | 953 | Only one character is allowed in a FILL statement.
|
| Enter single character surrounded
by quotes. | 954 | Only 10 or 11 is allowed in a CDIGIT statement.
|
| CDIGIT tests only modulo 10 or
modulo 11 check digits. | 994 | In form !, field !, "!" is undefined; press NEXT to see error.
|
| Indicated specification is not
recognizable; NEXT will display FIELD menu so you can make correction and
then press ENTER. | 995 | Internal error in form !, field ! ; press NEXT to see error.
|
| NEXT displays FIELD menu and another message with the cursor
positioned to the location of the error so you can correct the specification
and then press ENTER. | 996 | Form !, field ! has a semantic error; press NEXT to see error.
|
| NEXT displays FIELD menu so you can correct the error and then NEXT to see error. press ENTER. The syntax of your statement may be correct, but its
meaning is in error. | 997 | Form !, field ! has a data type error; press NEXT to see error.
|
| Data type inconsistent with specification; NEXT displays NEXT to see error. FIELD menu so you can correct data type
or specification and press ENTER. | 998 | Form !, field ! has a syntactic error; press NEXT to see error.
|
| NEXT displays FIELD menu so you can correct statement syntax
and then press ENTER. | 999 | Field processing specification syntax error.
|
| Correct syntax of statement and then press ENTER. error. |
Scanner Messages | |
Error | Messages | Cause/Action |
---|
1001 | Too many levels of
indenting, limit is !!!!. | Only 10 levels of nesting are
allowed. | 1002 | Improper indenting,
statement groups must be vertically aligned. | IF and ELSE parts at same nesting
level must be indented vertically aligned the same amount. Maximum
levels of nesting for IF is eight levels. | 1003 | Improper indenting,
must be within outer level of indenting. | An ELSE or subsequent IF starts
to the left of first IF statement. | 1010 | More left braces
than right braces were found. | Braces must match; add right brace,
or delete extra left brace. | 1011 | More right braces
than left braces were found. | Braces must match; add left brace,
or delete extra right brace. | 1030 | Token is too long,
limit is !!!! characters. | A string exceeds 120 characters.
Correct and press enter. | 1031 | A $ may only appear
with a system defined name, like $empty. | A $ cannot be part of a name unless
it is one of the system defined names (see TABLE 03-01). | 1032 | Expected a statement
beginning. | Syntax error. The cursor is positioned
to the location of the error. | 1033 | String is too long,
limit is !!!! characters. | | 1034 | String must end with
a quote. | A literal string (character constant)
must be enclosed within quotes. | 1035 | String must begin
with a quote. | When continuing a string to the
next line, close the quotes, put an & at the end of first line,
enclose string on second line within quotes. | 1036 | Only a comment may
appear on the same line after an ampersand. | An ampersand (&) is used
to continue a string; it cannot be followed by another statement,
only a comment starting with a \. | 1037 | A date constant must
end with an exclamation point. | A date used as a constant
must be enclosed within exclamation points. | 1038 | Date constant
is too long, limit is !!!! characters. | | 1039 | Date constant must be a valid
MDY date. | Date constants must be in the order: month day
year, and must be valid dates. |
Parser Messages | |
Error | Messages | Cause/Action |
---|
1094 | Invalid name: no field or save field with this name is defined.
|
| A valid field name is expected | 1095 | | | 1096 | | See error 1098. | 1097 | Data type error: Data types must be compatible.
|
| Data type and value in processing
specification do not correspond. | 1098 | Field processing specification syntax error.
|
| Statement is incorrect. Cursor is positioned
to the location of the error. Correct and press enter. |
Apply Errors | |
Error | Message | Cause/Action |
---|
1101 | Left operand must be type DIG, NUMn, IMPn, or an expression.
|
| An arithmetic operand is expected
as destination of SET or comparison or an expression. statement. Cursor is
positioned to the location of the error. | 1102 | Both operands must be type DIG, NUMn, IMPn, or an expression.
|
| Arithmetic operands expected in SET or comparison statement. Cursor is positioned to the
location of the error. | 1103 | Operand must be type DIG, NUMn, IMPn, or an expression.
|
| Arithmetic operand expected in SET or comparison statement. | 1104 | Operand data types must be compatible.
|
| Operands of the same data
type are expected in a SET or comparison statement. | 1105 | Operand types must agree unless source is a field or a save field.
|
| Operands must be the same data
type unless the source is a field or save field name. | 1106 | Right operand must be type CHAR.
|
| A character type value is expected
as source of SET or comparison statement. | 1107 | Left operand must be a field or a save field.
|
| Destination operand of SET
statement may only be a field or save field name. | 1108 | NFORM name must be a FORM name in quotes, or a type CHAR field.
|
| In CHANGE NFORM statement, the next form is identified by its name in
quotes, by a char type field containing the form name, or by a system constant
such as $HEAD. | 1109 | MINLEN operand must be type DIG, NUMn, IMPn, or a number.
|
| The minimum field length is specified
as a positive integer, or a name of a numeric field. | 1110 | CDIGIT operand must be 10 or 11.
|
| CDIGIT checks only modulo 10 or
11 check digits. | 1120 | Too many statements, code for entire form is too big.
|
| At compilation, the form information
generated does not fit into the maximum record size of 12000 bytes.
Reduce the number of fields or processing specifications. | 1130 | Improper indenting, statement groups must be vertically aligned.
|
| Corresponding IF and ELSE parts
of IF statement must start in same column. | 1131 | Syntax error: A name is not expected here.
|
| A name occurs where a reserved
word is expected. Check spelling, correct and press ENTER. | 1132 | Syntax error: The statement is incomplete.
|
| A valid statement ends unexpectedly.Correct and
press ENTER. | 1133 | Syntax error: Unexpected symbol.
|
| A special character is not expected
here. | 1923 | Internal error: Unexpected auto-indent.
|
| Internal error in IF-THEN-ELSE statement. | 1924 | Internal error: Error numbers are inconsistent.
|
| | 1925 | Internal error: MEM size is inconsistent with ARRAYSIZE.
|
| | 1926 | Internal error: XEVAL recursion underflow.
|
| | 1927 | Internal error: Invalid node in XEVAL.
|
| | 1928 | Internal error: Invalid MATCH operand in XEVAL.
|
| | 1929 | Internal error: Date conversion failed in XEVAL.
|
| | 1930 | Internal error: XEVAL recursion overflow
|
| | 1931 | Internal error: INEXT conversion failed.
|
| | 1932 | Internal error: Operand must be character string constant.
|
| | 1933 | Internal error: Invalid operand in APPLY.
|
| | 1934 | Internal error: Invalid operand in type check.
|
| | 1935 | Internal error: Invalid operand in MATCH.
|
| | 1936 | Internal error: Invalid operand in CDIGIT.
|
| | 1937 | Internal error: Invalid right operand.
|
| | 1938 | Internal error: Invalid left operand.
|
| | 1939 | Internal error: Invalid source operand.
|
| | 1940 | Internal error: Invalid Dtype in type checking.
|
| | 1941 | Internal error: EXTIN conversion failed.
|
| | 1942 | Internal error: Bad id number.
|
| | 1943 | Internal error: Bad screen order number.
|
| | 1944 | Internal error: MEM dispose failed.
|
| | 1945 | Internal error: Lexic level underflow.
|
| | 1946 | Internal error: Invalid leading blanks.
|
| | 1947 | Internal error: Invalid Dtype in scanner.
|
| | 1948 | Internal error: MEM allocate failed.
|
| | 1949 | Internal error: Invalid production.
|
| | 1950 | Internal error: Scanner error.
|
| | 1951 | Invalid local edit combination.
|
| An invalid combination of local edits has been specified
in the CONFIG phase of the field processing specifications. |
Pattern Compile Messages | |
Error | Message | Cause/Action |
---|
2101 | A "(", ")", "[" , or "] is not paired in pattern.
|
| MATCH statement contains odd number of parentheses or brackets. | 2102 | Invalid character found in pattern.
|
| A character in the expression
is not recognized as a valid character in the pattern. | 2104 | End of pattern found prematurely.
|
| Pattern characters were found
after the end of the pattern was found. | 2105 | Second character in range is lower than first.
|
| A range (a:b) is transposed, or
else a colon was not preceded by an exclamation point. | 2203 | | Either split the pattern into
smaller patterns (with IF statements), or simplify the pattern. | 2900 | Internal error :COMPILE'PATTERN failed.
|
| |
Release Messages | |
Error | Message | Cause/Action |
---|
3097 | Invalid data type conversion notation.
|
| Enter the correct data type to
which the specified data type should be converted. | 3098 | Data Type Conversion Record has not been defined.
|
| Use the Data Type Conversions
Menu to set the default data type conversions. | 3100 | Internal error: Could not create list process.
|
| | 3101 | Internal error: Could not send mail to list process.
|
| | 3102 | Internal error: Mail from list was lot.
|
| | 3104 | Formsfile reopen failed.Press PREV to reopen.(FSERR !!!!)
|
| | 3105 | Internal error: List could not close the formsfile.
|
| | 3106 | Internal error: List could not close the formsfile.
|
| | 3107 | Internal error: could not flush current form to the forms file.
|
| | 3108 | Internal error: could not flush the field table to the forms file.
|
| | 3109 | Internal error: could not flush the globals to the forms file.
|
| | 3110 | Internal error: could not close the formsfile.
|
| | 3111 | List could not open the FORMSPEC formsfile. (FSERR !!!!).
|
| | 3112 | Internal error: List could not close the FORMSPEC formsfile.
|
| | 3113 | List could not find form !in the FORMSPEC formsfile.
|
| | 3114 | List write failed. (FSERR !!!!)
|
| | 3115 | FORMSPECLINESPERPAGE JCW must be between 1 and 150. List failed.
|
| | 3116 | FORMSPECLINESPERPAGE JCW must be between 1 and 150.
|
| |
| | | | | NOTE: In most cases, the corrective action is clearly implied
by the message. "Internal Errors" are serious; they imply a corrupted
forms file and/or a program error. Call your SE. | | | | |
Application-Ready Buffer (ARB) Errors | |
Error | Message | Cause/Action |
---|
3403 | Internal error: ARB detail record missing.
|
| | 3405 | This field must not be blank.
|
| Enter the required information
in the field. | 3406 | This field accepts only contiguous digits.
|
| Remove any spaces between the
digits. | 3407 | Must specify number of decimals here.
|
| | 3409 | Internal error: could not update ARB Detail record.
|
| | 3412 | Internal error: Field Symbol Table record missing.
|
| | 3413 | | You cannot reproduce the form
fields on the ARB because they do not exist. | 3414 | Internal error: Data Type Conversion record missing.
|
| | 3416 | Internal error: Could not create ARB Detail record.
|
| | 3418 | Internal error: could not create ARB Map record.
|
| | 3420 | | You cannot create two ARBs for
one form. If you want to create a new ARB, you must delete the old
one first. | 3423 | Warning: Run-time errors may result from default data conversions.
|
| You may have specified incompatible
data conversions. Check your data type to make sure that data conversions
are legitimate. If your code has made provision for these anomalies, you
may disregard the warning. | 3424 | Warning: ARB length adjusted to match data type.
|
| You specified a length for an
ARB field that was too long or too short. | 3425 | Length must be greater than zero.
|
| | 3426 | Field was not found in ARB.
|
| | 3429 | | | 3433 | Form ! has duplicate field names.
|
| Correct the name duplication in
the field menu and retry. | 3450 | First field of range is missing; specify a name or number.
|
| | 3451 | Number specified is not in current ARB range.
|
| | 3452 | ARB is full; no more fields may be added.
|
| An ARB may hold up to 256 fields. | 3453 | Please enter a valid ARB field name.
|
| Check the syntax of the name you
have entered. | 3455 | Range is reversed; try 'leading-field/trailing field'.
|
| You have reversed the order of
the fields you want to manipulate. The field that appears first on
the ARB must appear first in the command. | 3456 | Please enter a valid command (Add, Move, Rename or DELETE).
|
| | 3457 | That command cannot be abbreviated. Please try again.
|
| | 3458 | ARB field name is too long; maximum length is 15 characters.
|
| | 3459 | Please specify Before or After, or leave blank.
|
| | 3460 | ARB field name to be added already exists in ARB.
|
| You cannot duplicate an ARB field
name; choose a new name or delete the other field first. | 3461 | Internal error: Selection routine approved an unknown command.
|
| | 3462 | New (Destination) name already exists in ARB.
|
| Select a name that does
not already exist. | 3465 | A destination entry requires that Before or After be specified.
|
| If you do not want to specify
Before or After, you must leave the Destination field blank. | 3466 | An ARB field name must start with an alphabetic character.
|
| | 3467 | No imbedded blanks are allowed in an ARB field name.
|
| | 3468 | Legal ARB field name characters are A-Z, 0-9 and '_'.
|
| | 3469 | An ARB field name cannot ne a reserved word.
|
| Choose a new name for the field. | 3473 | ARB field name must be specified; numeric reference is not allowed.
|
| | 3474 | Second field of range is missing; specify ARB field name or number.
|
| | 3475 | Internal error: SearchRec did not locate field in ARB Add.
|
| | 3476 | A range cannot be moved to a destination within itself.
|
| | 3498 | Internal error: VGETBUFFER failed (COM'STATUS !!!!)
|
| | 3499 | Internal error: VPUTBUFFER failed (COM'STATUS !!!!)
|
| |
| | | | | NOTE: In most cases, the corrective action is clearly implied
by the message. "Internal Errors" are serious;
they imply a corrupted forms file and/or a program error. Call your
SE. | | | | |
ARB Compile Errors | |
Error | Message | Cause/Action |
---|
3500 | In ARB !, field ! has no corresponding screen field.
|
| Either delete the ARB field, or
add a field to the associated screen. | 3501 | In ARB !, field ! has an incorrect length.
|
| Change the ARB field length to
match the length of the corresponding screen field. | 3502 | In ARB !, field ! has an incorrect ARB type.
|
| Check the permitted conversion
types and correct the ARB data type. | 3503 | Internal error: IN ARB !,missing source record for field !.
|
| |
More Menu Init and Processing ErrorsErrors | Message | Cause/Action |
---|
7001 | Correct syntax is: "Field formname fieldtag/name", then menu specs.
|
| | 7002 | Unable to open screen file.
|
| | 7003 | WARNING: No new screenfile specified. Old screenfile was closed.
|
| | 7004 | Correct syntax is: "ADD formname [\comments]".
|
| | 7005 | Correct syntax is: "READD formname [new formname] [\comments]"
|
| | 7006 | A screen layout file is not currently open.
|
| | 7007 | End of file when reading screen layout file.
|
| | 7008 | File system error when reading screen layout file.
|
| | 7009 | Form name in screen file record not equal to current form name.
|
| | 7010 | Cannot find screen record for form.
|
| | 7011 | Cannot find screen record for form.
|
| | 7012 | Write of screen record to screen layout file failed.
|
| | 7013 | WARNING: if ADD command, form created with no screen.
|
| | 7014 | WARNING: if READD, screen not updated (form renamed?)
|
| | 7015 | Correct syntax is: "FKLABELS formname [[ogon]eystring1...[ogon]eystringn]".
|
| | 7016 | Screenfile contains an invalid character.
|
| | 7017 | Missing datatype parameter
|
| | 7018 | Missing field type parameter.
|
| | 7019 | Missing field enhancement parameter.
|
| | 7020 | SELECTTERM update parameters must be separated by commas.
|
| | 7021 | Missing new FORMSPEC language ID.
|
| | 7022 | FIELD update parameters must be separated by commas.
|
| | 7023 | | | 7024 | Renumber was not necessary for !.
|
| | 7025 | Form is family child; renumber family by specifying parent form !.
|
| | 7026 | Internal error: unable to fetch form head.
|
| | 7027 | There are no forms in the current file.
|
| | 7028 | | | 7029 | Recovering file -- PLEASE WAIT.
|
| | 7030 | | | 7031 | Number of errors = !!!! Number of warnings = !!!!
|
| | 7032 | There are no compiled forms in the current file.
|
| | 7033 | No update values specified. Command ignored.
|
| | 7034 | **** End of compiled forms listing ****
|
| | 7035 | | | 7036 | | | 7037 | | | 7038 | New function key labels must be preceded by ˙
|
| | 7039 | | | 7040 | Forms file is being
converted to new format. | | 7041 | | | 7042 | Sorry. That command
has not been implemented. | | 7043 | Missing ARB field
name. | | 7044 | | | 7045 | ADDARBFIELD ARBname fieldname [BEFORE/AFTER fieldname]
|
| | 7046 | Missing field name in "BEFORE/AFTER fieldname".
|
| | 7047 | MODARBFIELD
ARBname fieldname { length, type } | | 7048 | MOVEARBFIELD ARBname
field [ field ] [ BEFORE/AFTER FIELD ] | | 7049 | SCREENTOARB [ char, date, dig, num, imp ]
|
| | 7050 | ARBTOSCREEN [ char, int, real, pack, zone
|
| | 7051 | RENAMEARBFIELD ARBname oldfieldname newfieldname
|
| |
Native Language Support Errors | |
Error | Message | Cause/Action |
---|
8000 | This edit statement is not valid for international forms files.
|
| | 8001 | Edit contains data inconsistent with language of this forms file.
|
| | 8002 | Edit contains language-dependent data. | | 8003 | Edit contains data not compatible with the language of this forms file.
|
| | 8004 | Invalid initial value for International forms file.
|
| | 9001 | Native language support software not installed.
|
| | 9002 | Language specified is not configured on this system.
|
| | 9003 | Character set specified is not configured on this system.
|
| | 9004 | Internal error: National table is not present.
|
| | 9005 | Internal error: Bad NLT extra data segment.
|
| | 9006 | Internal error: Bad LDST extra data segment.
|
| | 9007 | Error calling native language support intrinsic.
|
| | 9008 | Error calling native language support intrinsic.
|
| | 9009 | Error calling native language support intrinsic.
|
| | 9010 | Internal error: NLINFO item out of range.
|
| | 9011 | WARNING: Language not configured, change or hit ENTER to proceed.
|
| | 9012 | This edit requires a configured language.
|
| | 9014 | Attempted setting a language- dependent forms file to another language.
|
| | 9015 | NATIVE-3000 is currently the only selection available.
|
| | 9016 | Invalid date value for international forms file.
|
| | 9017 | Internal Error: Error updating language ID - try again.
|
| | 9070 | Internal Error: writing terminal selection source record failed
|
| | 9500 | Language of forms file is not configured on this system.
|
| | 9998 | Language ID must be 0 to 999 or -1 for international forms file.
|
| | 9999 | Call to native language support intrinsic failed.
|
| |
|