Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

LIBORBCMD Messages 100-199

100	ERROR: No interfaces found.
	Description	On a COMPILE operation, no interfaces were found for generating the specified files.
	Action	Include an interface in the definition file.
101	ERROR: Missing conditional expression.
	Description	In the definition file, a #if clause is not followed by a conditional expression.
	Action	Add a conditional expression to the #if clause.
102	ERROR: Missing right parenthesis.
	Description	A closing parethesis is missing from a conditional expression, an actual parameter list, or a parameter list.
	Action	Add a closing parenthesis.
103	ERROR: Syntax error in contant expression.
	Description	A constant expression contains a syntax error.
	Action	Verify the syntax of the expression.
104	ERROR: Missing colon for conditional expression.
	Description	A colon is missing from a conditional expression.
	Action	Add the colon between the arguments.
105	ERROR: Vertical whitespace within pp directive.
	Description	A preprocessor directive contains vertical whitespace character(s).
	Action	Remove the vertical whitespace character(s).
106	ERROR: Constant value too large.
	Description	A constant value is too large.
	Action	Verify the value of the constant and adjust the value.
107	FATAL: Unexpected end of file before finish of pp directive.
	Description	During the preprocessing on the definition file, the end of file was encountered before the preprocessor directive was finished.
	Action	Verify the definition file; finish the preprocessor directive.
108	ERROR: Illegal token on pp directive line..
	Description	An illegal token was found on a preprocessor directive line.
	Action	Verify the preprocessor directive; remove the token.
109	ERROR: Missing parentheses for macro argument list.
	Description	The parentheses required for the macro argument list are missing from a macro definition.
	Action	Add parentheses to the argument list.
110	ERROR: Too few actual parameters in macro call.
	Description	A macro call contains too few actual parameters.
	Action	Add the parameters to the macro call.
111	ERROR: Too many actual parameters in macro call.
	Description	A macro call contains too many actual parameters.
	Action	Remove the additional parameters from the macro call.
112	ERROR: Argument is not an identifier.
	Description	A preprocessor directive or macro formal argument is not an identifier, or the argument is missing.
	Action	Verify the argument and correct it.
113	ERROR: Out of place directive ignored.
	Description	A preprocessor directive is out of place and has been ignored.
	Action	Remove the preprocessor directive.
114	ERROR: Missing argument in pp directive.
	Description	An argument is missing from a preprocessor directive.
	Action	Add an argument to the directive.
115	ERROR: Unrecognized preprocessing directive.
	Description	An unrecognized preprocessor directive was specified.
	Action	Remove the preprocessor directive.
116	ERROR: Missing #endif directive.
	Description	An #endif directive was not found before the end of file.
	Action	Add the missing #endif directive.
117	ERROR: File does not end in unescaped newline.
	Description	A file must end in an unescaped newline.
	Action	Add the newline.
118	ERROR: Illegal header name.
	Description	A header name is illegally terminated, has an illegal form, or contains characters after the name.
	Action	Verify the header name and correct it.
119	ERROR: Missing macro name identifier.
	Description	The macro name identifier argument is missing from a define directive.
	Action	Add the macro name identifier.
120	ERROR: Macro name can not be redefined or undefined.
	Description	System and predefined macros such as defined cannot be redefined or undefined by the user.
	Action	Choose a different macro name.
121	ERROR: Missing operand.
	Description	The WLE IDL preprocessor encountered a missing operand to the # or ## operators in a macro definition.
	Action	Add an operand.
122	ERROR: Non ANSI line directive.
	Description	This form of the line directive is not supported by the ANSI standard.
	Action	Correct the line directive.
123	ERROR: User defined error text: `ErrorText'.
	Description	This is the error text from a #error directive.
	Action	Verify the #error directive.
124	ERROR: Too many tokens in macro expansion.
	Description	There are too many tokens in the macro expansion.
	Action	Verify the macro.
125	ERROR: Formal parameter definition is not unique.
	Description	The definition of the formal parameter is not unique.
	Action	Change the name of the formal parameter.
126	INFO: The macro has been redefined. The redefinition is now in effect.
	Description	A macro has been redefined. The new definition will be used instead of the original definition.
	Action	Remove the original definition of the macro.
127	ERROR: Invalid proxy wildcard.
	Description	This combination of Remote User, Remote Host, and Local Username is not supported.
	Action	Remove the wildcard specification for the Remote Host or Local Username.
128	ERROR: No typecode repository id.
	Description	The typecode is an anonymous type and contains no repository ID. This is an internal error only.
	Action	Contact BEA Customer Support.
129	WARN: No repository Id for `val'.
	Description	WLE was unable to create a repository Id for 'val'. This is an internal error.
	Action	Contact BEA Customer Support.
130	INFO: Object `ObjectName' is not in the IDL file. Please remove the #pragma from the IDL file.
	Description	A UUID was found for an object that does not exist.
	Action	Remove the #pragma from the OMG IDL file.
131	INFO: `Name' is a non-standard context property.
	Description	This context property is not a standard CORBA context. A standard context property is a sequence of alphanumeric, '.', '_', and '*' characters. The first character must be an alphabetic character. An asterisk may be used only as the last character of the string. WLE context property names can contain the additional '&', '-', ' ', ':' characters. In addition, the first character does not have to be alphabetic.
	Action	Correct the context property if standard CORBA context property names are desired.
132	INFO: `Name' cannot be both a module and an interface; compilation errors will occur.
	Description	A module name and an interface name are the same. Compilation errors will occur in the C++ stubs.
	Action	This is an informational message; no action is necessary.
133	INFO: `Name' cannot be the same as its container; compilation errors will occur.
	Description	A type name and its container name are the same. Compilation errors will occur in the C++ stubs.
	Action	This is an informational message; no action is necessary.
134	ERROR: `Name' data type not yet supported in this context.
	Description	The data type specified is not supported by the WLE product in this context.
	Action	Specify a supported WLE data type.
135	INFO: The long name option or qualifier was ignored.
	Description	C++ does not require the use of options or qualifiers to handle long names. There is no ANSI standard for routine name length in C++, so this option was ignored, and the long name was generated. The limit for the length is restricted only by the compiler.
	Action	This is an informational message; no action is necessary.
136	ERROR: Invalid Protocol Type Name.
	Description	The protocol type specified is invalid.
	Action	Specify a valid protocol type value.
137	ERROR: An error occurred while creating a TypeCode.
	Description	The TypeCode could not be created due to an error.
	Action	See any associated error messages.
138	ERROR: This statement requires the IOP protocol.
	Description	This statement requires that the IOP protocol be specified when OMG IDL files are loaded or compiled.
	Action	Ensure that you have specified the IOP protocol option or qualifier when loading the repository or compiling OMG IDL files.
139	WARN: The transaction policy for `interface' is inconsistent with its inheritance
	Description	The transaction policy inherited by the interface is inconsistent with the transaction policy specified for the implementation in the ICF file. This can occur when an interface inherits from the interface CosTransactions::TransactionalObject, but is implemented with a transaction policy of ignore or never.
	Action	Determine whether the interface is transactional, and modify the ICF file associated with the OMG IDL file to appropriately update the transaction policy of its implementation. Alternatively, define an alternate, nontransactional inheritance for the interface. Note that the stubs and skeletons generated from the OMG IDL and ICF files will support nontransactional requests; however, because of the transaction policy of ignore or never, errors could occur if transactional requests are attempted.
141	WARN: Missing interface.
	Description	While attempting to parse an IDL file, the IDL compiler encountered a construct where a CORBA Interface specifier was expected but not found.
	Action	Edit the IDL file to include an interface specifier.
142	WARN: Missing valuetype.
	Description	While attempting to parse an IDL file, the IDL compiler encountered a construct where a value type specifier was expected but not found.
	Action	Edit the IDL file to include an value type name.
143	WARN: Valuetype declarations are not allowed inside interfaces or valuetypes.
	Description	While parsing a value type or interface definition, a definition for a new value type was encountered. Value type may not be defined within an interface or another value type.
	Action	Restructure your IDL definitions so that value types are only defined within modules (or at the top level).
144	ERROR: No full valuetype definition found for `type'.
	Description	A forward definition was found for the value type type, but the IDL file did not contain a full definition.
	Action	Add a complete definition for this value type to the IDL file.
145	ERROR: Valuetype forward reference missing abstract modifier.
	Description	When an abstract value type is declared in a forward reference, then that forward reference must also be abstract. We encountered a forward definition for an anstract value type which did not contain the abstract qualifier.
	Action	Edit the IDL file to include an abstract qualifier on the forward reference.
146	ERROR: Valuetype forward reference contains abstract modifier while valuetype does not.
	Description	When an abstract value type is declared in a forward reference, then that forward reference must also be abstract. We encountered a forward definition for an anstract value type but when the value type was fully defined it did not contain an abstract qualifier.
	Action	Edit the IDL file so that the forward reference and the valuetype definition agree.
147	ERROR: Valuetype `type' not fully defined yet.
	Description	A forward definition was found for the value type type, but the IDL file did not contain a full definition before the value type was used in a context that required it. For example, one value type cannot inherit from another value type before it is fully defined.
	Action	Add a complete definition for this value type to the IDL file before it is used.
148	ERROR: `type' is not a valid valuebox type.
	Description	While parsing the IDL file, the type type was found in a context where only a valuebox type may be used.
	Action	Edit the IDL file to resolve this inconsistency.
149	ERROR: `type' is not an valuetype.
	Description	While parsing the IDL file, the type type was found in a context where only a value type may be used.
	Action	Edit the IDL file to resolve this inconsistency.
150	WARN: Duplicate base valuetype `val'.
	Description	While parsing the IDL file, a definition for a value type was found with the same name as a previous definition within the same module.
	Action	Edit the IDL file to rename one of the value types.
151	ERROR: abstract valuetype can not inherit from stateful valuetype `val'.
	Description	While parsing an IDL file, a definition for an abstract value type was found which inherited from a stateful value type. Abstract value types may only inherit from other abstract value types.
	Action	Edit the IDL file to resolve this inconsistency.
152	ERROR: a stateful valuetype can not inherit from more than one stateful valuetype.
	Description	While parsing an IDL file, a definition for a value value type was found which included more than one stateful value type in its inheritance list. Stateful value types may only inherit from a single stateful parent.
	Action	Edit the IDL file to resolve this inconsistency.
153	ERROR: `val' is not an interface.
	Description	While parsing a value type definition, a name was found in a supports clause which was not an interface. Value types may only support interfaces.
	Action	Edit the IDL file to resolve this inconsistency.
154	WARN: Duplicate supports interface `val'.
	Description	While parsing a value type definition, an interface name was found in a supports clause more than once.
	Action	Edit the IDL file to resolve this inconsistency.
155	ERROR: a valuetype can not support more than one non-abstract interface.
	Description	While parsing a value type definition, more than one non-abstract interface was found in a supports clause.
	Action	Edit the IDL file to resolve this inconsistency.
156	WARN: truncatable can not be specified for a custom value type.
	Description	A value type definition was found which was both truncatable and used custom marshalling. These marshalling strategies are inconsitent and only one may be used.
	Action	Edit the IDL file to resolve this inconsistency.
157	ERROR: an inherited stateful valuetype must be specified as the first valuetype in the list.
	Description	A stateful value type may inherit from a single stateful value type and multiple abstract value types. If it inherits from a stateful value type, then that value type must be specified first in the inheritance list.
	Action	Edit the IDL file to re-order the inheritance list.
158	ERROR: non-custom valuetype can not inherit from custom valuetype `val'.
	Description	A value type definition was found which inherited from a custom value type. Normal valuetype marshalling is incompatible with custom marshalling, and a non-custom value type may not inherit from a custom value type.
	Action	Edit the IDL file to resolve this inconsistency.
159	WARN: factory initializer declarations are only allowed inside valuetypes.
	Description	While parsing an IDL file, the IDL compiler encountered a factory initializer definition outside of a valuetype definition. Factory initializers are only relevant to value types.
	Action	Edit the IDL file to resolve this inconsistency.
160	WARN: a truncatable valuetype can not inherit from a non-truncatable stateful valuetype.
	Description	Truncatable value types may inherit from a single truncatable stateful value type and multiple abstract value types. Truncatable value types may not inherit from non-truncatable stateful value types or custom value types.
	Action	Edit the IDL file to resolve this inconsistency.
161	WARN: The fixed literal is invalid.
	Description	While parsing an IDL file, the IDL compiler encountered a fixed literal with a non-numeric value.
	Action	Edit the IDL file to include a value fixed literal.
162	ERROR: abstract interface can not inherit from non-abstract interface `val'.
	Description	While parsing an IDL file, a definition for an abstract interface was found which inherited from a concrete interface. Abstract interfaces may only inherit from other abstract interfaces.
	Action	Edit the IDL file to resolve this inconsistency.
163	WARN: Missing comma in fixed type definition.
	Description	While parsing an IDL file, the IDL compiler encountered a syntax error in a fixed type definition.
	Action	Fixed definitions are in the form "fixed". Edit the IDL file to correct this syntax.
164	WARN: Missing positive integer in fixed type definition.
	Description	While parsing an IDL file, the IDL compiler encountered a syntax error in a fixed type definition.
	Action	Fixed definitions are in the form "fixed". Edit the IDL file to correct this syntax.
165	ERROR: Boxed value type cannot be forward referenced.
	Description	The IDL compiler has processed a forward reference to a valuetype which was subsequently defined as a valuebox. Valuebox types may not be forward referenced.
	Action	Edit the IDL to reorder the type definiitons so that a forward reference is not necessary, or change the valuebox to a value type.