![]() |
![]() |
|
|
1 |
ERROR: malloc() failed | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. Re-execute the vuform command. | |
See Also |
| |
2 |
ERROR: Couldn't find system form formname | |
|
Description |
The vuform program was not able to find the specified system form, formname, or an I/O error was found while reading the specified form. |
Action |
Check that the | |
See Also |
| |
5 |
ERROR: Couldn't find formname | |
|
Description |
The vuform program was not able to find the specified form, formname, or an I/O error was found while reading the specified form. This error was produced while the vuform command was trying to initialize a MENU type form. |
Action |
Check that the | |
See Also |
| |
11 |
ERROR: this page already has a home field | |
|
Description |
This error is provided by the vuform command during a cross validation of the lastval function. This cross validation found that there is more than one field declared as a Home field on the corresponding page. Only one field can be the Home field. |
Action |
For each field, enter Attribute Mode (that is, type cf) and verify the value of the Home field attribute. Only one field is allowed to be the Home field. | |
See Also |
| |
12 |
ERROR: this page already has an initial field | |
|
Description |
This error is provided by the vuform command during a cross validation of the lastval function. This cross validation found that there is more than one field declared as an Initial field on the corresponding page. Only one field can be the Initial field. |
Action |
For each field, enter Attribute Mode (that is, type CF) and verify the value of the Initial field attribute. Only one field is allowed to be the Initial field. | |
See Also |
| |
13 |
ERROR: this form already has a menu field | |
|
Description |
This page already has a menu field (MENU). Only one MENU type field is allowed on a form. |
Action |
Do not define a new MENU type field. Edit the field attribute parameters and delete the values provided for the Menu Type and Argument: fields. | |
See Also |
| |
14 |
ERROR: invalid menu type (choose MENU or FORMEXIT) | |
|
Description |
This error is returned by vuform during the definition of the parameters for a variable field. The field labeled Menu type: takes either the MENU or the FORMEXIT keyword. Another value has been specified. |
Action |
Check the value of the field labeled Menu type:; it must be MENU or FORMEXIT. The remainder of the specification of the MENU or the FORMEXIT statement must be entered on the lines following the label Argument:. | |
See Also |
| |
15 |
ERROR: no spaces allowed in display code string | |
|
Description |
There should be no spaces between display flags. This error is produced by the vuform command while validating the display flags for a particular field. |
Action |
Re-enter the value of the display flags without spaces. | |
See Also |
| |
16 |
ERROR: invalid display code - use digits 0 through 9 | |
|
Description |
A display flag must be a digit between 0 and 9, where 0 is the normal mode, 1 is standout mode, 2 is inverse video, 3 is bold, 4 is dim, 5 is blink, 6 is invisible, 7 is underline, 8 is protected, and 9 is alternate character set. This error is produced by the vuform command while validating the display flags for a particular field. |
Action |
Correct and re-enter the value of the display flags. | |
See Also |
| |
17 |
ERROR: duplicate display code | |
|
Description |
A display flag can only be specified once. This error is produced by the vuform command while validating the display flags specified for a particular field. |
Action |
Correct and re-enter the value of the display flags field. | |
See Also |
| |
18 |
ERROR: FML id not found in field tables | |
|
Description |
This error is produced by the vuform program while validating the FML name given to a particular field in the field attribute form. The FML id must be defined in the corresponding field table. |
Action |
Check the | |
See Also |
| |
19 |
ERROR: argument specification not consistent with type | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Default type: field. A value for the Argument: field has been specified but no value has been given to the Default type: field. A default type (the value of the Default type: field) must be specified in this case. |
Action |
Specify a default type value for the Default type: field, or delete the value of the Argument: field. | |
See Also |
| |
20 |
ERROR: type requires argument | |
|
Description |
This error is issued by vuform while validating the argument specification for a variable field. The error occurred during the definition of the Default type: field. A value for the Default type: field has been specified but no value has been given to the Argument: field. An argument value for the Argument: field must be specified. |
Action |
Specify an argument value for the Argument: field, or delete the value of the Default type: field. | |
See Also |
| |
21 |
ERROR: argument specification not consistent with type | |
|
Description |
This error is produced by vuform while validating the validation specification for a variable field. The error occurred during the specification of the Validation type: field. A value for the Argument: field has been specified but no value has been given to the Validation type: field. A value for the Validation type: field must be specified. |
Action |
Type a value for the Validation type: field, or delete the value of the Argument: field. | |
See Also |
| |
22 |
ERROR: validation type does not take an argument | |
|
Description |
This error is produced by vuform while validating the validation specification for a variable field. The error occurred during the specification of the Validation type: field. A value for the Argument: field has been specified but the value provided for the Validation type: field does not take an argument. For example, ALPHA, ALNUM, INTEGER, and NUMERIC are validation types that do not take arguments. |
Action |
Do not specify a value for the Argument: field. Correct the value and proceed with editing the form. | |
See Also |
| |
23 |
ERROR: type requires argument | |
|
Description |
This error is produced by vuform while validating the validation specification for a variable field. A value for the Validation type: field has been specified that requires an argument but no value for the Argument: field has been provided. |
Action |
Specify a value for Argument: field. | |
See Also |
| |
24 |
ERROR: argument specification not consistent with type | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Argument: field for a Menu type: field, but the Menu type: field has not been set to either MENU or FORMEXIT. |
Action |
Set the value for the Menu type: field to MENU or FORMEXIT, or delete the value for the Argument: field. | |
See Also |
| |
25 |
ERROR: MENU field must be unprotected | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the field has not been marked as unprotected. |
Action |
Set the protected field indication to "n". | |
See Also |
| |
26 |
ERROR: type requires argument | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but no value for the Argument: field has been specified. |
Action |
Specify a value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
27 |
ERROR: regular expression syntax error | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Validation type: field as RE (regular expression). The associated argument is an invalid regular expression. |
Action |
Specify a value for the Argument: field that is a valid regular expression, or delete the Validation type: field value. | |
See Also |
| |
28 |
ERROR: bad function specification | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Validation type: field as FUNC (function). The associated argument is an invalid function specification. |
Action |
Specify a value for the Argument: field that is a valid function specification, function(string_arg), or delete the Validation type: field value. | |
See Also |
| |
29 |
ERROR: bad range specification | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Validation type: field as NR (numeric range). The associated argument is an invalid numeric range (for example, a closing bracket is missing). |
Action |
Specify a value for the Argument: field that is a valid numeric range, or delete the Validation type: field value. | |
See Also |
| |
30 |
ERROR: bad range specification | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Validation type: field as IR (integer range). The associated argument is an invalid integer range (for example, a closing bracket is missing). |
Action |
Specify a value for the Argument: field that is a valid integer range, or delete the Validation type: field value. | |
See Also |
| |
31 |
ERROR: floating point constant in integer range specification | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Validation type: field as IR (integer range). The associated argument is an invalid integer range (the numbers specified are not integers). |
Action |
Specify a value for the Argument: field that is a valid integer range, or delete the Validation type: field value. Use a numeric range (NR) if floating point values are desired. | |
See Also |
| |
32 |
ERROR: Cannot have null menu/formexit value | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:jump_type values, but one of the entries is missing the menu_value (either the field value starts with an equal sign or an equal sign follows a comma). |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
33 |
ERROR: values for FORMEXIT must be F0-F9 or F11 or * | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:jump_type values where menu_value must be F1 through F09, F11, or *. |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
34 |
ERROR: expected '=' in menu/formexit list | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:jump_type values, but one of the entries is missing the equal sign (a menu_value was followed by white space but no equal sign). |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
35 |
ERROR: invalid menu/formexit type | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:jump_type values, but one of the entries has an invalid menu_type. |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
36 |
ERROR: expected ':' in menu/formexit line | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:jump_type values, but one of the entries is missing the colon (the character following the menu_type and optional white space is not a colon). |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
37 |
ERROR: invalid action type | |
|
Description |
This error is produced by vuform while validating the argument specification for a variable field. The error occurred during the specification of the Menu type: field as either MENU or FORMEXIT, but the Argument: field is invalid. The format of the field should be a comma-separated list of menu_value=menu_type:action_type values, but one of the entries has an Action (A or a) menu_type, with an invalid action_type. |
Action |
Specify a valid value for the Argument: field, or delete the value for the Menu type: field. | |
See Also |
| |
64 |
ERROR: Signal caught - vuform exiting additional_information | |
|
Description |
This message is printed when vuform processing is interrupted by a signal, usually a BREAK signal sent by the user hitting the BREAK key on the terminal. additional_information may be printed if vuform has additional information relating to the form being processed. |
Action |
Restart vuform and reformat the mask information. | |
See Also |
| |
65 |
ERROR: Signal caught - vuform exiting | |
|
Description |
This message is printed when vuform processing is interrupted by a signal, usually a BREAK signal sent by the user hitting the BREAK key on the terminal. |
Action |
Restart vuform and reformat the mask information. | |
See Also |
| |
66 |
ERROR: program_name - unknown terminal type term_type | |
|
Description |
The terminal type indicated is not known on this system and therefore cannot be used with vuform. |
Action |
Correct TERM environment variable setting to one understood on the local system, or run vuform from a terminal that has a known type. | |
See Also |
| |
68 |
ERROR: program_name - form dimensions, cols X rows, are too large for screen, cols X rows | |
|
Description |
The dimensions of the form to be processed by vuform are too large for the screen or window in use. The form dimensions come from the command line of vuform via the -c and -r options or default to 80 by 23 respectively. |
Action |
Run vuform from a bigger window or reduce the size of the form being created. | |
See Also |
| |
69 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
vuform creates a file with the same basename as that specified on the command line, but with a ".M" suffix appended to the end (if it does not already exist). This error occurs when the file name specified is invalid for use on the vuform command line for one of the following reasons:
|
Action |
Modify the file name used on the vuform command line to conform to the restrictions specified above. | |
See Also |
| |
74 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
75 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
77 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
78 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
80 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
82 |
ERROR: file_name is either an invalid file name or too long | |
|
Description |
See Message No. 69 above. |
Action |
See Message No. 69 above. | |
See Also |
| |
90 |
ERROR: rows must be between 1 and rows | |
|
Description |
When trying to reset the number of rows on form using ":rows=", the value specified was too large. The value must be between 1 and rows, where rows is dependent on the screen and/or window size. |
Action |
Run vuform from a bigger window or reduce the row size value specified. | |
See Also |
| |
92 |
ERROR: cols must be between 1 and cols | |
|
Description |
When trying to reset the number of columns on form using ":cols=", the value specified was too large. The value must be between 1 and cols, where cols is dependent on the screen and/or window size. |
Action |
Run vuform from a bigger window or reduce the column size value specified. | |
See Also |
| |
94 |
ERROR: unknown command: string | |
|
Description |
A command mode string, beginning with a colon, was entered but is not a valid vuform command. |
Action |
Enter a valid command mode string, as listed in the | |
See Also |
| |
95 |
ERROR: formname - bad magic number | |
|
Description |
The form formname specified for processing by vuform is not a valid form or was generated with an earlier version of the software (it has an invalid magic number). |
Action |
Make sure that the correct form name was specified and that it was compiled with the current version of the software. If necessary, de-compile it with the old version of the software and re-compile it with the new version. | |
See Also |
| |
99 |
ERROR: read failed for formname - FML id, field_number (field_type), not found in any field table | |
|
Description |
While reading the specified form, formname, the field name for field number field_number and type field_type could not be found (for example, Fname failed). |
Action |
Check the | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|