|
|
LIBFML MESSAGES
LIBFML MESSAGES 1-99
1 |
ERROR: Fielded buffer not aligned |
|
Description |
An FML function was called with a fielded buffer that is not properly aligned. Most machines require half-word alignment. |
|
Action |
Use Falloc to get back a dynamically allocated, properly aligned buffer. |
|
See Also |
Falloc(3fml) |
|
2 |
ERROR: Buffer not fielded |
|
Description |
A buffer was passed to an FML function that is not a fielded buffer, that is, that has not been properly initialized. |
|
Action |
Use Finit to initialize a buffer allocated directly by the application, or use Falloc dynamically to allocate and initialize a fielded buffer. |
|
See Also |
Falloc(3fml), Finit(3fml) |
|
3 |
ERROR: No space in fielded buffer |
|
Description |
An attempt was made to add a field to a buffer, change a field to a larger value within a buffer, merge two buffers, or otherwise modify a buffer, and not enough space is available to complete the operation. |
|
Action |
Use Frealloc dynamically to allocate a larger buffer or use Fcpy to copy the buffer to a larger buffer, and retry the operation. |
|
See Also |
Fcpy(3fml), Frealloc(3fml) |
|
4 |
ERROR: Field not present |
|
Description |
When trying to find, change, or delete a field, the specified field identifier and/or field occurrence did not exist in the fielded buffer. |
|
Action |
Check your request to make sure you have specified a field that is in the buffer. |
|
See Also |
Fchg(3fml), Fdelete(3fml) Ffind(3fml) |
|
5 |
ERROR: Unknown field number or type |
|
Description |
An invalid field identifier was specified for an FML function, or an invalid field number (0 or greater than 8192) was specified, or Fname could not find the associated field identifier for the specified name. |
|
Action |
Most of the FML functions can return this error; see the manual page associated with the function that returned this error. Check your code to make sure the field specified is valid. |
|
6 |
ERROR: Invalid field type |
|
Description |
An invalid (unknown) field type was specified to an FML function, or an invalid type was specified for a particular operation (for example, a non-string field was specified for a string operation). |
|
Action |
Specify the proper field type or field identifier. |
|
See Also |
Fmkfldid(3fml), Ftypcvt(3fml), Ftype(3fml), Fvall(3fml), Fvals(3fml) |
|
7 |
ERROR: UNIX system call error |
|
Description |
An error occurred during a UNIX system call when opening a field table file or view description file, or when reading or writing an FML buffer. |
|
Action |
Check that the environment variables are set correctly for the field table and view files, and that the files have read permission. |
|
See Also |
Fread(3fml), Fwrite(3fml), Fextread(3fml), field_tables(5) |
|
8 |
ERROR: Unknown field name |
|
Description |
A field name could not be mapped into a field identifier. |
|
Action |
Check that the environment variables are set correctly for the field table files and that the files have read permission. |
|
See Also |
Fldid(3fml),Fextread (3fml),field_tables (5) |
|
9 |
ERROR: Memory allocation failed |
|
Description |
An attempt dynamically to allocate memory from the operating system using malloc () failed. |
|
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. |
|
10 |
ERROR: Bad syntax in boolean expression |
|
Description |
The syntax of a boolean expression passed to Fboolco is invalid. This message is also generated on failure to evaluate the boolean expression in Fboolev and Ffloatev and indicates that an invalid or corrupted value was passed to these functions. It is also generated when an invalid input format is read by Fextread . |
|
Action |
Correct the format of the boolean expression being processed by Fboolco or the external FML buffer format being processed by Fextread . |
|
See Also |
Fboolco(3fml), Fextread(3fml) |
|
11 |
ERROR: Cannot find or open field table |
|
Description |
When processing the field tables, one of the field tables was not found. |
|
Action |
Check that the environment variables are set correctly for the field table files and that the files have read permission. |
|
See Also |
field_tables(5) |
|
13 |
ERROR: Invalid argument to function |
|
Description |
An invalid argument (other than an invalid fielded buffer, field identifier, or field type) was passed to an FML function. This can be a NULL parameter where a non-NULL parameter was expected, invalid buffer sizes, etc. |
|
Action |
See the manual page associated with the error return for the correct parameter values. |
|
14 |
ERROR: Destructive concurrent access to field table |
|
Description |
While reading the FML field tables, the program detected a concurrent change to the tables by another process. |
|
Action |
Re-execute the program after the FML field tables have been updated. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|