HPlogo HP Data Entry and Forms Management System (VPLUS) Reference Manual: HP 3000 MPE/iX Computer Systems > Appendix B VPLUS Error Messages

VPLUS Intrinsic Error Messages
» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

VOPENTERM and VCLOSETERM Messages

ErrorMessageCause/Action
001
Internal error: Terminal file initialization failed. failed.
FCONTROL or FSETMODE intrinsic
002
Your terminal is not supported by VPLUS.
VPLUS works on the HP terminals listed in Appendix G.
003
VPLUS does not run on a series I.

VPLUS does not run on an HP Series I computer system.

004
The terminal status request failed.

VOPENTERM's request for terminal status failed. Check that strapping is correct. May also be data comm problem.

005
The terminal allocation failed.
Message used only with the 2640A terminal, which is not supported by VPLUS. Reserved words in the COMAREA are not initialized to zeroes.
006
The terminal needs the H strap in (closed).
Refer to Appendix G for instructions on how to strap your terminal for VPLUS.
007
Internal error: HP2640 mode could not be correctly set.
Possible block mode or data comm problem.
008
Internal error: HP2645 mode could not be correctly set.
See error 007.
009
The terminal open failed. (FSERR !)
FOPEN intrinsic failed.
010
The terminal close failed. (FSERR !)
FCLOSE intrinsic failed.
011
Sorry, this device is not supported by VPLUS.
Refer to Appendix G for a list of supported terminals.
012
The HP2640B needs straps A, C, H in (closed); D, F, G out.
You must strap this terminal (and the 2644A) yourself; other terminals are strapped automatically. (Refer to Appendix G.)
013
The HP2644A needs straps A, C, H in (closed); D, G out.
You must strap this terminal (and the 2640B) yourself; other terminals are strapped automatically. (Refer to Appendix G.)
014
The HP2645A/41A/48A needs straps A, C, H, J in (closed); D, G out.
Note that these terminals should be configured automatically by VPLUS.
015
Terminal type incorrectly determined.
Possible block mode or data comm problem. Check straps. Note: 2645 multipoint straps should never be touched!
016
Internal error HP2645A multipoint terminal mode not correctly set.
See error 015.
017
Comarea too short for run-time HP3075/6 terminals.
The Comarea must be 85 words for HP 3075/6 terminals. Set terminals. Comarealen to 85.
018
Non-page/block mode terminal types not supported.
Redefine terminal type. (Note: VPLUS requires a terminal which supports page/block mode.)
019
Internal error: FDEVICECONTROL should not return ccg.
See System Manager.
021
Invalid terminal type.
TERMTYPE used is a printer terminal type

General Messages

ErrorMessageCause/Action
020
Error detected by host language.
Check the Comarea item FILERRNUM for the host language error number.
021
Invalid terminal type.
See 021 above.
023
Environment control file access failed.

VOPENFORMF and VCLOSEFORMF Messages

ErrorMessageCause/Action
040
Internal error: DLSIZE failed; there is not enough DL area space.
Stack size or MAXDATA too small. Re-PREP your application program with a larger MAXDATA parameter.
041
Internal error: DLSIZE failed; the stack is frozen.
Stack size or MAXDATA too small. Re-PREP your application program.
042
Formsfile name not passed to VOPENFORMF.
The name of the forms file to be opened must be included in the call to VOPENFORMF.
043
Comarea length may not be less than 60.
The Comarea length as specified by the item Comarealen must be 60 words for HP terminals and 85 words for data capture devices.
044
Comarea length is too large.
The Comarea length as specified by the item comarealeng must not be longer than the longest length documented.
045
TERMINAL or FORMSFILE has not yet been opened.

046
Unrecognized Comarea language code passed.

050
Forms File open failed. 
(FSERR !)
FOPEN intrinsic failed. Check forms file name.
051
The file is not a VPLUS Forms File.
Check the formfile parameter to make sure the file name is correct.
052
Internal error: Forms File FGETINFO failed. (FSERR !)
FGETINFO intrinsic failed.
053
Forms File probably hasn't been compiled. (FSERR !)
Run FORMSPEC and compile the forms file.
060
The program supplied COMAREA extension is too small.
If you are using BASIC, check word 4 of COMAREA (USRBUFLEN), and increase the length of the COMAREA extension.
061
Internal error: Failure to obtain required PASCAL Heap area.

062
Internal error: Failure to return PASCAL Heap area.

063
Failure to close Forms File. (FSERR !)

An error occurred while trying to close the forms file. Check that the forms file is open before VCLOSEFORMF is called.

067
Invalid form store size specified.
A number outside the range of -1 to 255 is specified in the FORM'STORE'SIZE variable, which is the 39th word of the VPLUS communication area.
068
VPLUS internal error; there is not enough DL area space.
For languages other than BASIC,
069
VPLUS internal error; the stack is frozen.
See error 041.
9001
Native Language Support software not installed

Check with System Manager to install Native Language Support software.

9002
Language specified is not configured on this system.
Select another language or check with System Manager to configure the desired language.
9500
Language of forms file is not configured on this system.
See System Manager to configure the language or use forms files on a system with that language configured.

VOPENBATCH and VCLOSEBATCH Messages

ErrorMessageCause/Action
070
Forms file was re-complied since last using this batch.
You may want to specify a different batch file name since the forms file has been changed since the specified batch file was last used with the forms file.
071
A forms file must be opened before opening a batch file.
Call VOPENFORMF before calling VOPENBATCH
072
The file does not appear to be an existing batch file.
Check the batch file name you specified; if this is a new file, it will be created automatically and then opened.
073
A different forms file created this batch.
You opened a forms file that is not the forms file associated with the batch files specified. See 070.
074
Batch file not yet opened.

080
Batch file open failed 
(FSERR !)
Refer to the file system error to determine the cause of the open failure. Check file name.
081
Can't read the batch file's user label (FSERR !)
FREADLABEL intrinsic failed.
082
Internal error: Batch file FGETINFO failed. (FSERR !)
FGETINFO intrinsic failed.
084
Can't write user label to batch file (FSERR !)
FWRITELABEL intrinsic failed.
085
Internal error: Batch file close failed. (FSERR !)
FCLOSEBATCH intrinsic failed. Refer to the file system error to determine the cause of the close failure.

Access Method Messages

ErrorMessageCause/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.
Fast form files require 500 words of space in the COMAREA extension. If you are coding in BASIC, list the forms file to find how many words are needed for the extension, and increase the COMAREA field USERBUFLEN to this number. If the application is not written in BASIC, increase the MAXDATA parameter on the PREP or RUN command.
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.

VGETNEXTFORM Messages

ErrorMessageCause/Action
100
Can't find the next form. (FSERR !) program.
Check form name in application.
101
Form $HEAD does not apply, since no forms have been displayed.
NFNAME in COMAREA is $HEAD, but this specification only applies when forms have been displayed.
102
An invalid COM'REPEAT value was supplied programmatically.
REPEATAPP in COMAREA should be set to one of the codes:
0 - no repeat/append
1 - repeat current form
2 - repeat & append current form
103
An invalid COM'NFOPT value was supplied programmatically.
The next form option in FREEZAPP of COMAREA can be:
0 - clear current form, display next form
1 - append next form to current form
2 - freeze current form, append next form
104
Formsfile not compiled for this run-time terminal.
The type of terminal is being used has not been selected for use with the forms file. Specify the terminal type in the FORMSPEC Terminal Selection menu, then recompile the forms file. If you open a forms file and then call VGETNEXTFORM without opening the terminal, you must compile the forms file for a 264X terminal
105
HP3075/6 terminal with numeric only display is not supported.
VPLUS does not run on the numeric display HP3075/6 terminals.
106
HP3077 terminal is not supported except for opening and closing.
VPLUS only opens and closes the HP3077 terminal; no other functions can be performed.

VMERGE Messages

Following are the messages produced by the VMERGE utility. The cause of each, and the action you may take is also described.

MessageCause/ActionAction

hp32209V.UU.FF VMERGE (c) Hewlett-Packard Co. 1992 ALL RIGHTS RESERVED

Header generated at the start of VMERGE processing. No action required.
*****Internal processing error (VM1001)An unexpected condition has been detected by VMERGE.

Preserve the input files for diagnosis and contact HP rep.

Begin VMERGE Processing ... (VM1003)Given at the start of processing. No action required.
No consistency check required, AUX file is $NULLSelf-explanatory.

Consistency check of MASTER and AUX file begun ...(VM1005)Self-explanatory.

Input files are consistent (VM1006)The consistency check of MASTER and AUX has been completed, and the files have been found consistent. No action required.
***** Input files are not consistent (VM1007)The consistency check of MASTER and AUX has been completed, and the files have been found inconsistent. (Normally an explanatory message indicating why they are inconsistent will have been issued prior to this one.) The OUTPUT file will not be produced.Adjust the input files to overcome the indicated inconsistency and rerun VMERGE
End of VMERGE Processing. (VM1009)Self-explanatory.None
***** Form name table could not be allocated (VM1400)An attempt to allocate an extra data segment to hold a form name table for the MASTER or AUX forms has failed.Consult with your system administrator to determine why this failure occurred on your system. This is probably due to limitations on the number of Extra Data Segments that can be created in your configured environment
***** Form name table overflow (VM1401)More forms have been found in the MASTER or AUX file than can be accommodated in the form name table.

Contact your HP rep.

***** Conflicting data in MASTER forms file (VM1402)Invalid or inconsistent data has been found in the MASTER file.Recreate the file and rerun VMERGE. If the problem persists, contact your HP rep.
***** Conflicting data in AUX forms file (VM1403) Invalid or inconsistent data has been found in the AUX file. Recreate the file and rerun VMERGE. If the problem persists, contact your HP rep
**** Error accessing table in an extra data segment (VM1404)An attempt to access data in an extra data segment was rejected by the MPE operating system.

Rerun VMERGE. If the problem persists, contact your HP rep.

***** Version of MASTER file format not supported by VMERGE (VM1500)The MASTER file was compiled with a version of FORMSPEC that is not supported by VMERGE. (Versions prior to B.03.03 are not supported.)

Reconstruct the file with the current version of FORMSPEC.

***** Version of AUX file format not supported by VMERGE (VM1501)The AUX file was compiled with a version of FORMSPEC that is not supported by VMERGE. (Versions prior to B.03.03 are not supported.)

Reconstruct the file with the current version of FORMSPEC.

Warning: Error enhancement settings differ (VM1504)The error enhancement settings differ in the MASTER and AUX files. None. (The value from the MASTER file is retained in OUTPUT.
Warning: Window display line settings differ (VM1505)The display line settings differ in the MASTER and AUX files. None. (The value from the MASTER file is retained in OUTPUT.)
Warning: Error window color settings differ (VM1506)The error window color settings differ in the MASTER and AUX files. None. (The value from the MASTER file is retained in OUTPUT.)
Warning: Window enhancement settings differ (VM1507)The window enhancement settings differ in the MASTER and AUX files.None. (The value from the MASTER file is retained in OUTPUT.
***** Terminal Specific settings differ (VM1508)The terminal settings differ in the MASTER and AUX files. Revise the files to make them compatible and rerun the utility
***** Language ID settings differ (VM1509)The language id settings differ in the MASTER and AUX files.Revise the files to make them compatible and rerun the utility.
***** Number of databases differ (VM1510)The number of databases differ in the MASTER and AUX files.Revise the files to make them compatible and rerun the utility
***** Save fields specifications differ (VM1521)The save field specifications differ in the MASTER and AUX files.Revise the files to make them compatible and rerun the utility. The save field specifications must be identical in all respects in both input files.
***** Global function key labels differ (VM1531)The global function key labels differ in the MASTER and AUX files. Revise the files to make them compatible and rerun the utility
***** 307x terminal settings differ (VM1541)The 307x terminal settings differ in the MASTER and AUX files.

Revise the files to make them compatible and rerun the utility

Form name "nnnnnnnnnnnnnnn" found in MASTER file (VM1601)

Documents that the named form was found in the MASTER file

None
Form name "nnnnnnnnnnnnnnn" found in AUX file (VM1603)Documents that the named form was found in the AUX file. None
***** MASTER and AUX contain duplicate form name(s) (VM1611)Forms with the same name were found in both the MASTER and AUX filesRemove or rename the duplicate forms from one file and rerun VMERGE.
***** Duplicate form name: nnnnnnnnnnnnnnn (VM1612)Identifies a form name found in both the MASTER and AUX files. Remove or rename the duplicate form one file and rerun VMERGE
***** Unattached messages; use fast forms files (VM1613)Messages have been found that are not associated with any form. OUTPUT file is not produced.

Compile the input files and produce fast forms files. Use the fast forms files as input to VMERGE

***** MASTER file could not be opened (VM1700)The file designated as MASTER could not be opened. Remove the impediment to opening the file and rerun VMERGE. (The file may not exist under the designated name, or may be already open for exclusive use, etc.)
***** Error reading MASTER file (VM1701)An error occurred in attempting to read the MASTER file.

Regenerate the file and rerun VMERGE.

***** Error in MASTER file data (VM1702)An inconsistency was found in the data in the MASTER file. Recreate the file and rerun the utility. If the problem persists contact your HP rep.
MASTER file opened (VM1703)Self-explanatory. None
***** MASTER file type is not VFORM or VFAST (VM1704)Self-explanatoryDesignate the correct file and rerun VMERGE.
MASTER file designated as: fff ... f (VM1705)

Shows the full pathname of the MASTER file.

None

***** MASTER file has not been compiled (VM1706)Self-explanatory.

Compile the MASTER file and rerun VMERGE.

***** AUX file could not be opened (VM1800)The file designated as AUX could not be opened. Remove the impediment to opening the file and rerun VMERGE. (The file may not exist under the designated name or may be already open for exclusive use, etc.
***** Error reading AUX file (VM1801)An error occurred in attempting to read the AUX file.

Regenerate the file and rerun VMERGE.

***** Error in AUX file data (VM1802)An inconsistency was found in the data in the AUX file.Recreate the file and rerun the utility. If the problem persists contact your HP rep.
AUX file opened (VM1803)Self-explanatory.None
***** AUX file type is not VFORM or VFAST (VM1804)Self-explanatory.

Designate the correct file and rerun VMERGE.

AUX file designated as: fff ... f (VM1805)Shows the full pathname of the AUX file.None.
***** AUX file has not been compiled (VM1806)Self-explanatory.

Compile the AUX file and rerun VMERGE.

***** OUTPUT file could not be opened (VM1900)Self-explanatory.

Remove the impediment to opening the OUTPUT file and rerun VMERGE.

**** Error writing OUTPUT file (VM1901)Self-explanatory.Correct the problem that has caused the write error and rerun VMERGE. You may need to consult with your system administrator to determine the problem.
OUTPUT file opened (VM1903)Self-explanatory.

None.

***** OUTPUT file type is not VFAST (VM1904)The file designated as OUTPUT pre-exists but is not of type VFAST.

This is viewed as an error since it is assumed that the user has unintentionally designated the name of a file being used for other purposes. Redesignate the OUTPUT file (or purge the old file if the name is correct) and rerun VMERGE.

OUTPUT file designated as: fff ... f (VM1905)Shows the full pathname of the OUTPUT fileNone
Error closing OUTPUT file (VM1906

Self-explanatory.

Correct the problem that has caused the error and rerun VMERGE. You may need to consult with your system administrator to determine the problem
***** OUTPUT file purged (VM1911)Inconsistency or some other problem has prevented the OUTPUT file from being successfully generated. To avoid confusion, the file is purged.Correct the underlying problem and rerun VMERGE
***** OUTPUT file pre-existed and could not be purged (VM1912)An attempt to purge the existing file with the name designated for the OUTPUT file failed.Make sure that the correct file name has been designated. If so, determine why it could not be purged and remove the impediment

VSHOWFORM Messages

ErrorMessageCause/Action
130
Internal Error: Terminal write failed. (FSERR !)
FWRITE intrinsic failed.
131
Internal error: Color conversion failed.

VREADFIELDS Messages

ErrorMessageCause/Action
150
The supplied read buffer (dbuf) is too small.
The data buffer in memory is too small for the data on the form. Check application program DBUF array size and DBUFLEN.
151
Internal error: An expected DC2 from the terminal was missing.
Block mode or data comm problem. Press REFRESH.
152
Internal error: A read terminator (an RS or a GS) was expected.
Press ENTER again. Also try REFRESH. If problem recurs, check DBUFLEN in application program. Possible block mode or data comm problem.
153
 A status request was pending, so the terminal read was invalid.

Application program requested terminal status, then called VREADFIELDS.

154
An unrecognized escape sequence was read.
Possible softkey problem. Press REFRESH or perhaps RESET to correct.
155
Read length error.
Length of data actually read is less than expected for current form.
160
Internal error: Terminal Read Failed (FSERR!)
FREAD intrinsic failed. If user timeouts were enabled in the user application, a time out has occurred.
161
Field too long for HP3075/6 terminals.
The maximum length of a field on the HP 3075/6 terminals is 200 characters.
162
Terminal Power Failure detected.
A power failure has been detected on an HP 3075/6 terminal.
163
Invalid error light.
Valid error lights are letters of the alphabet or the @@ character.
164
HP3075/6 Terminal printer is out of paper.
Load the printer with a roll of paper.
165
Device is not supported by VPRINTLOCAL.
The terminal must be an HP 3075A or HP 3076A.
166
HP3075/6 Terminal does not have a printer.

Your terminal is not equipped with a printer.

VPRINTFORM Messages

ErrorMessageCause/Action
190
Can't open the printfile. (FSERR !)
FOPEN intrinsic failed. Refer to file system error to determine the cause.
191
Can't write to the print file. (FSERR !)
FWRITE intrinsic failed.

VINITFORM, VFIELDEDITS, and VFINISH Messages

ErrorMessageCause/Action
202
The required field is empty.
A required field in current form is blank.
203
Invalid field type.
Valid field types are: 0(optional), R(required), D(display only), P(Process even if blank).
204
The field can only contain digits.
The field is specified as type DIG, but it contains characters other than 0-9.
205
The field can only contain a number.
The field is specified as type NUM, but it contains characters other than 0-9, decimal point, comma, or plus or minus sign.
206
The field can only contain a number, with max ! decimal places.
Reduce the number of digits to the right of the decimal point with max ! decimal to n.
207
The field can only contain a number (! decimal places implied).
The field is specified as type IMPn, but it contains characters other than 0-9, implied). decimal point, comma, or plus or minus sign. Also, there could be more than n digits to the right of the decimal point.
208
The field must be a valid date, in DMY order.
The data in a DMY field is not a valid date, or is not in order: day, month, year.
209
The field must be a valid date, in MDY order.
The data in a DMY field is not a valid date, or is not in order: day, month, year.
210
The field must be a valid date, in YMD order.
The data in a YMD field is not a valid date, or is not in order: year, month, day.
211
Internal error: Invalid field data type.

Field table problem.

212
Error during data conversion between family members.
A data conversion error has been detected by VINITFORM when converting between family members. Check for field type compatibility problems in the form family in the forms file.
220
Internal error: Invalid destination.
Code execution problem.
222
 An edit test failed.
The default field edit error message had been provided. Check the data you entered in the field against the processing specifications.
321
Attempted a SET into a numeric field that is too short.
The destination of a SET statement has fewer characters too short. than the number being moved to it.
323
Internal error: Invalid op code.
Code execution problem.
325
Attempted a SET into a date field that is too short.
The destination of a SET statement has fewer characters than the value being moved to it.
326
Internal error in field.

327
User-defined error for this field.
A FORMSPEC custom error message is associated with this field, but could not be correctly retrieved from forms file.
328
The field cannot contain a negative number (Dtype DIG).
A minus sign is in a field whose data type is DIG, only digits (0-9) allowed.
330
Internal error: Invalid op in logical eval.
 Code execution problem.
331
Range error. Low value is greater than high value.
The first value is in an IN/NIN range is greater than the second value (for a:b, a>b)
332
Check digit requested on empty field.
CDIGIT is specified for a field that contains no data. There must be a value in order to test the check digit.
333
Check digit requested on field containing only + or - sign.
CDIGIT is specified for a field that has no value except a sign; there must be a value in order to test the check digit.
334
Check digit requested on field containing special characters.
CDIGIT only operates on numeric (0-9) or alphabetic (A-Z) values. characters.
335
Check digit 10 is invalid for modulus 11 calculation.
Since value has remainder greater than 9, it has no possible modulus 10 check digit. Use CDIGIT 11.
336
Internal error: Check digit modulus must be 10 or 11.

337
Check digit validation string contains only one character.
A field whose value is to be checked by a modulus calculation must contain at least two characters.
340
Division by zero was attempted.
Expression in field processing statement evaluated to division by zero.
341
Attempted a SET from a field containing an invalid number.
A numeric value is expected as the source of a SET statement, but the source is not a valid number.
344
Internal error: Invalid op in long eval.

345
Overflow in an add operation.
Value is outside 4-word REAL range. Range of 4-word REAL is from approximately 8.636 times 10^(-78) to 1.158 times 10^77.
346
Overflow in a subtract operation.
See error 345.
347
Overflow in a multiply operation.

See error 345.

348
Overflow in a divide operation.
See error 345.
349
Overflow in a percent operation.

See error 345.

350
Index expression out of range in an "index of" numeric statement.
In an index retrieve operand (index OF element, element...) the index evaluates to a digit greater than the number of elements in the list. (Numeric operands).
351
Overflow in a negate operation.
See error 345.
360
Attempted a SET from a field containing an invalid date.
A date is expected as the source of a SET statement, but the date is not valid.
363
Internal error: Invalid op in double eval.

364
Index expression out of range in an "index of" date statement.
See error 350. (Date operands)
370
Internal error: Invalid op in text eval.

371
 Index expression out of range in an "index of" text statement.
See error 350. (CHAR operands)
380
The index expression evaluates to "empty."
An arithmetic expression used as the index in an index OF element, element.. operand is blank or zero.

VREADBATCH Messages

ErrorMessageCause/Action
400
Can't read the batch file record. (FSERR !)
FREADDIR intrinsic failed.
401
Warning: Can't browse a batch file with variable length records.
Browse mode is illegal for batch records which are not fixed length.

VWRITEBATCH Messages

ErrorMessageCause/Action
450Can't write the batch record. (FSERR !)FWRITEDIR intrinsic failed.

VSETERROR, VGETFIELD, VPUTFIELD, VPUTtype, and VGETtype Messages

ErrorMessageCause/Action
500
A field with the field number supplied does not exist.
The fieldnum parameter contains a value that is not a field number in the current form.
501
The field number supplied is out of range.
The fieldnum parameter contains a value greater than any field number associated with the current form.
502
The field requested is in error.
The field specified by the fieldnum parameter contains invalid data.
503
The field requested is empty.
The field specified by the fieldnum parameter contains no data.
504
Error converting field to numeric type.
VGETtype tried to convert value to a numeric type, and failed. Check conversion rules. (For VGETINT, message, indicates attempt to convert number > 32767; receiving field is unchanged.)
505
Error converting numeric type to ASCII.
VPUTtype tried to convert a numeric value to a character string and failed. Check conversion rules.
506
A DIGIT field cannot contain a negative number.
A value in a DIG type field has a minus sign; DIG values may only be digits (0-9).
507
Function key labels option is disabled.
The COMAREA item LABEL'OPTION must be set to one before opening the forms file.
508
Error reading function key values from forms file (FSERR !!!!)
An error occurred while trying to read the function key label definitions from the forms file.
509
Invalid input parameter to function key intrinsics.

An invalid value has been passed as the FORM-OR-GLOB or KEY-NUM parameter to VGETKEYLABELS, VSETKEYLABEL, or VSETKEYLABELS intrinsics.

510
A field with the screen order supplied does not exist.

515

WARNING: Sign in field not stored in unsigned variable.
If the NUMDIGITS is positive, the intrinsic assumes the destination variable for the GET is unsigned. If the parameter is negative, the destination is assumed to be signed.

VGETBUFFER and VPUTBUFFER ARB Messages

ErrorMessageCause/Action
519
ARB flag is set but no ARB record is found.
This is an application-specified conversion,
but the forms file does not contain an ARB record. Do the following: 1. Initialize ARB conversion flag to 0 if conversion is not desired.
2. Use FORMSPEC to add the necessary ARB record.
3. Check for possible corruption of the
formsfile.
520
ARB conversion type specified is not supported.
Check for possible corruption of the formsfile.
521
ARB record length exceeded maximum limit.
Check for possible corruption of the formsfile.
522
IEEE conversion is not supported in this version.
This application-specified IEEE conversion is not yet supported.Check the IEEE conversion flag in the Comarea.
523
ARB record does not contain the minimum amount of information required.
Check for possible corruption of the formsfile.
524
ARB record does not contain theminimum amount of information required.

525Error converting YMD type to YYMMDD format.

526

Error converting MDY type to YYMMDD type.

527
Error converting DMY type to YYMMDD format.

528
Internal error: converting 
Julian to YYMMDD format.

529
YYMMDD variable parameter does not contain a valid date.

530
Internal error: converting 
Julian to date type.

531
Attempted to place date  into short date field (less than 8 
char).

VGETLANG and VSETLANG Messages

ErrorMessageCause/Action
9002
Language specified is not configured on this system.
Select another language or check with System Manager to configure the desired language.
9014
Attempted setting a language dependent forms file to another language.
VSETLANG can only be used with international forms files.

VCHANGEFIELD Messages

ErrorMessageCause/Action
850
Invalid field type specification.
Field type incorrect; use one of the listed codes.
851
Invalid data type specification.
Data type incorrect; use one of the listed codes - n indicates number of decimal positions.
852
Invalid enhance type specification.
Enhancement code is incorrect; check and correct.
853
Internal error: invalid field type.
Internal.
854
Internal error: invalid data type.
Internal.
855
Internal error: invalid enhance type.
Internal.
856
Invalid VCHANGEFIELD specification type.
Value must be 1-6.

VPLACESURSOR Intrinsic

ErrorMessageCause/Action
800
Cannot place cursor to display only fields.
Field number must be for an input field.

INFO Intrinsic Messages

ErrorMessageCause/Action
601
Invalid input parameters to INFO intrinsic.

602
Form specified to FORMINFO does not exist.

603
INFO intrinsic: Form field list read error (FSERR !!!!).

604
INFO intrinsic: Form record read error (FSERR !!!!).

605
FF version is old. Must recompile to use FORMINFO intrinsic.

606
Invalid field specified to FIELDINFO intrinsic.
Make sure that the field name is correctly spelled if the field name is the key; make sure that the field name parameter is 16 bytes long, and padded with ASCII blanks. If the field number is used as the key, be certain that this number is the actual field number.
607
Invalid form # specified to FORMINFO intrinsic.

Forms Loading Messages

ErrorMessageCause/Action
700
No such form in terminal form storage memory.
The specified form is not purged because it does not exist in the form storage directory.
701
Terminal form storage memory is full.
The specified form is not loaded because the form storage memory is full.
702
Requested loan of blankform name.



FORMSPEC Error Messages
  		 


SNA DHCF Intrinsic Messages  
Feedback to webmaster