Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
106 |
ERROR: pattern_value is a bad pattern | |
|
Description |
The search pattern, pattern_value, specified using the "/" or "?" command, is an invalid regular expression (for example, an unfinished character class). |
Action |
Re-enter the command with a valid regular expression. | |
See Also |
| |
108 |
WARN: pattern not found | |
|
Description |
The search pattern specified using the "/" or "?" command (search forward/backward for the field matching the specified pattern) was not found. |
Action |
No action required. | |
See Also |
| |
110 |
WARN: pattern not found | |
|
Description |
The search pattern specified using the "/" or "?" command was not found. |
Action |
No action required. | |
See Also |
| |
111 |
WARN: field name not found | |
|
Description |
The search pattern specified using the ' or " command (search forward/backward for the field associated with the specified FML field name) was not found. |
Action |
No action required. | |
See Also |
| |
114 |
WARN: field name not found | |
|
Description |
The field specified using the ' or " command (search forward/backward for the field associated with the specified FML field name) was not found. |
Action |
No action required. | |
See Also |
| |
115 |
ERROR: write failed - FML id, field_name not found in any field tables | |
|
Description |
While writing the current form, the field name field_name could not be found (for example, Fldid failed). |
Action |
Check the | |
See Also |
| |
116 |
ERROR: write failed - FML id needed | |
|
Description |
While writing the current form, a field was encountered that did not yet have an FML field name associated with it, such that the field identifier for the field could not be determined. |
Action |
Associated a field name with the field and re-execute the command. | |
See Also |
| |
117 |
ERROR: write error - couldn't create temp file | |
|
Description |
When writing the current form, vuform was unable to create and open a temporary file for writing in the current directory. |
Action |
Check that the current directory has write and execute permissions set correctly. | |
See Also |
| |
118 |
ERROR: write error - UFORM source in filename | |
|
Description |
The form compilation failed but no output was generated by the mask compiler. The source for the form is left in filename. |
Action |
After executing vuform, trying compiling the form manually using mc filename. | |
See Also |
| |
119 |
ERROR: write error; UFORM source in filename1; message from mc in filename2 | |
|
Description |
The form compilation failed. The source for the form is left in filename1. Output generated by the mask compiler is left in filename2. |
Action |
After executing vuform, trying compiling the form manually using mc filename1. | |
See Also |
| |
120 |
ERROR: could not create filename | |
|
Description |
While writing the form, vuform was able to compile the form with mc but could not create the output file, filename. |
Action |
Check that the output file has write permission set correctly, and that the directory has write and execute permissions set correctly. | |
See Also |
|