[Top] [Prev] [Next] [Bottom]

3. TxRPC Messages 1200-1299

1200	ERROR: Duplicate union arm name 'name'
	Description	In an IDL file, a union had more than one element with the same name. For example, typedef union switch (short u1) { case 0: ; case 1: long u1; case 2: short u1; /* error */ } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1201	ERROR: Duplicate default case in union
	Description	In an IDL file, a union was defined with more than one default case. For example, typedef union switch (short u1) { case 0: ; default: long u1; default: short u2; /* error */ } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1202	ERROR: Duplicate case value val
	Description	In an IDL file, a union was defined with more than one case having the same discriminant value. The duplicate value, val, was printed. Note that a value can be hidden in a constant definition or enumeration. For example, const short val1 = 1; typedef union switch (short u0) { case 0: ; case 1: long u1; case val1: short u2; /* error */ } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1203	ERROR: Function parameters must have the [in] attribute
	Description	In an IDL file, a function pointer was used as a parameter that had the [out] attribute. For example, typedef [ptr]void (op1)([in]long p1); void op2([out]op1 p1); /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1204	ERROR: Binding [handle] parameter must have [in] or [in,out] attribute
	Description	In an IDL file, a parameter with the [handle] attribute, appearing as the first parameter (a binding handle), did not have the [in] or [in,out] attribute. For example, typedef [handle] long myhandle; void op1([out]myhandle handle); / error / void op2([in,out]myhandle handle); /* correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1205	ERROR: Binding handle_t parameter must have [in] attribute
	Description	In an IDL file, a parameter with the handle_t type, appearing as the first parameter (a binding handle), did not have the [in] attribute ([out] cannot be specified). For example, typedef handle_t myhandle; void op1([out]myhandle handle); / error / void op2([in]myhandle handle); / correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1206	ERROR: Binding handle parameter cannot have [ptr] attribute
	Description	In an IDL file, a parameter with the [handle] attribute or handle_t type, appearing as the first parameter (a binding handle), had the [ptr] attribute. For example, typedef [handle] long myhandle; typedef handle_t myhandle2; void op1([in,ptr]myhandle handle); / error / void op2([in,ptr]myhandle2 handle); /* error / void op3([in,ref]myhandle handle); /* correct / void op4([in,ref]myhandle handle); /* correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1207	ERROR: handle_t as first parameter cannot have [transmit_as()] attribute
	Description	In an IDL file, a parameter with the handle_t type, appearing as the first parameter (a binding handle), had the [transmit_as()] attribute. For example, typedef [transmit_as(long)]handle_t myhandle; void op1([in,ref]myhandle handle); / error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1208	ERROR: handle_t type must be first parameter
	Description	In an IDL file, a parameter with the handle_t data type was not the first parameter. For example, void op1([in]long p1, [in,ref]handle_t handle); / error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1209	ERROR: Duplicate parameter name val
	Description	In an IDL file, an operation was defined with multiple parameters with the same name. For example, void op1([in]long p1, [in]long p1); /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1210	WARN: Parameter name val differs from existing parameter in case only
	Description	In an IDL file, an operation was defined with multiple parameters with names that differ only in case. This warning was generated only when tidl was run with the "-port case" option.
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1211	ERROR: Struct name not defined
	Description	In an IDL file, a structure name (tag) was defined or used without members and was never completely defined within the file. For example, typedef struct t1 t1; typedef struct t2 { struct t3 s1; } t2; / error if struct t1 never defined / / error if struct t3 never defined */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1212	ERROR: Union name not defined
	Description	In an IDL file, a union name (tag) was defined or used without elements and was never completely defined within the file. For example, typedef union t1 t1; typedef struct t2 { union t3 s1; } t2; / error if union t1 never defined / / error if union t3 never defined */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1213	ERROR: handle_t type not known
	Description	While compiling an IDL file, tidl was unable to find the description of the handle_t type. This indicates a problem with the tbase.idl file which was installed under $TUXDIR/include/rpc/tbase.idl.
Action	Check that TUXDIR was set correctly and tbase.idl installed, and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1214	ERROR: Interface name must be less than len characters in length
	Description	In an IDL file, the interface name was too long. The interface name may be the smaller of 17 characters, or 19 minus the number of digits in the major and minor version numbers. The maximum length for the interface name based on the length of the version number was printed in len. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000), version(20.20)] interface t2345678901234567 /* error - must be 16 */ This was a fatal error. Note that message 1067 indicates a warning of further truncation during code generation, due to implementation limitations. The limitation is 13 minus the number of digits in the major and minor version numbers (6 characters smaller).
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1216	ERROR: Type for constant 'name' doesn't agree with expression
	Description	In an IDL file, a constant definition type does not match the type of the constant expression. For example, const long c1 = "abc"; /* error / const boolean c2 = 'a'; / error / const char c3 = TRUE; / error / const char c4 = 3; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1217	ERROR: Value is too big for unsigned short name
	Description	In an IDL file, an unsigned short constant was defined whose expression value is too large (less than 0 or greater than 65535). For example, const unsigned short c = 400000; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1218	ERROR: Value is too big for short name
	Description	In an IDL file, a short constant was defined whose expression value is too large (less than -32768 or greater than 32767). For example, const short c = 400000; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1219	ERROR: Value is too big for unsigned small name
	Description	In an IDL file, an unsigned small constant was defined whose expression value is too large (less than 0 or greater than 255). For example, const unsigned small c = 257; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1220	ERROR: Value is too big for small name
	Description	In an IDL file, a small constant was defined whose expression value is too large (less than -128 or greater than 127). For example, const small c = 128; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1221	ERROR: Operation that returns a pointer cannot have [ref] attribute
	Description	In an IDL file, an operation was defined that returns a pointer and had the [ref] attribute. If the pointer attribute was not specified, it correctly defaults to [ptr]. For example, [string,ref]char rstrcat([in,string]char p1, /* error / [in,string]char p2); [string]char rstrcat([in,string]char p1, [in,string]char p2); / ok */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1222	ERROR: Can't define anonymous structure or union in operation return
	Description	In an IDL file, a structure or union was defined as an operation return (that had not been previously defined) but a tag was not specified. The definition must have a structure or union tag. For example, struct {long s1;} op1(void); /* error / struct struct1 {long s1;} op2(void); / correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1223	ERROR: Conformant structure must be passed by reference
	Description	In an IDL file, an operation was defined with a conformant structure parameter that does not have an explicit pointer. Conformant structure parameters must have a pointer. For example, typedef struct { long s1; [max_is(s1)]long s2[]; }t1; void op1([in]t1 p1); /* error / void op2([in]t1 p1); /* ok */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1224	ERROR: Name name redeclared
	Description	In an IDL file, an operation was defined with the same name as a typedef, constant, or enumeration value name, or another operation name. These names are all in the same name space and must be unique. For example, typedef struct { long s1; }t1; void t1(void); /* error / const long t2 = 3; void t2(void); / error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1225	WARN: Name name differs from existing type in case only
	Description	In an IDL file, an operation was defined with the a name that differs only in case from a typedef or constant name. This warning was generate only if the "-port case" option was specified. For example, typedef struct { long s1; }T1; void t1(void); /* warning / const long t2 = 3; void T2(void); / warning */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1226	ERROR: Duplicate function name name
	Description	In an IDL file, an operation was defined with the same name as another operation. For example, void t1(void); void t1(void); /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1227	WARN: Function name name differs from existing function in case only
	Description	In an IDL file, an operation was defined with a name that differs only in case from another operation. For example, void t1(void); void T1(void); /* warning */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1228	ERROR: Can't define anonymous structure or union in operation prototype
	Description	In an IDL file, a structure or union was defined as a parameter (that had not been previously defined) but a tag was not specified. The definition must have a structure or union tag. For example, void t1([in]struct {long s1;} p1); /* error / void t2([in]struct struct1 {long s1;} p1); / correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1229	ERROR: Incomplete structure/union
	Description	In an IDL file, a structure or union reference was specified before the associated structure or union had been completely defined. In this situation, only a pointer to the incomplete structure or union can be defined. This is most often used for self-referencing data structures; remember in this case to use the [ptr] attribute so the last pointer on the chain can be NULL. For example, typedef struct t1 { struct t1 s1; /* error / } t1; typedef struct t2 { [ptr]struct t2 s1; /* correct */ } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1230	ERROR: Parameter must have [in] attribute, [out] attribute, or both
	Description	In an IDL file, a parameter is defined without a directional attribute. For example, void op1(long p1); /* error / void op2([in]long p1); / correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1231	ERROR: error_status_t type not known
	Description	While compiling an IDL file, tidl was unable to find the description of the error_status_t type. This indicates a problem with the tbase.idl file which was installed under $TUXDIR/include/rpc/tbase.idl.
Action	Check that TUXDIR was set correctly and tbase.idl installed, and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1232	ERROR: Parameter name not found for operation op
	Description	In an ACS file, a parameter, name, specified for an operation, op, was not found in the associated IDL file. Often, this indicates simply a typographical error. For example, op1 (badname); /* error if badname not defined for op1 in idl */
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1233	ERROR: [comm_status] parameter must have type [out] error_status_t *
	Description	In an ACS file, a parameter was declared to be a [comm_status] parameter but its type was not declared properly in the IDL file.
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1234	ERROR: [comm_status] specified for more than one attribute for operation op - ignored
	Description	In an ACS file, more than one parameter was declared to be a [comm_status] parameter for an operation. All but the first [comm_status] attribute for the operation are ignored.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1235	ERROR: [fault_status] parameter must have type [out] error_status_t *
	Description	In an ACS file, a parameter was declared to be a [fault_status] parameter but its type was not declared properly in the IDL file.
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1236	ERROR: [fault_status] specified for more than one attribute for operation op
	Description	In an ACS file, more than one parameter was declared to be a [fault_status] parameter for an operation. All but the first [fault_status] attribute for the operation are ignored.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1237	ERROR: [switch_is(name)] not found
	Description	In an IDL file, a non-encapsulated union was defined but the [switch_is()] variable, name, was not found. If the non-encapsulated union was within a structure, then name must be another element in the structure at the same level. If the non-encapsulated union was a parameter, then name must be another parameter for the operation. For example, typedef [switch_type (long) ] union t1 { [case (1,3)] float u1; [case (2)] short u2; [default] ; } t1; typedef struct { [switch_is(s1)] union t1 s2; /* s1 not found / } t2; typedef struct { [switch_is(s1)] union t1 s2; / correct / long s1; } t3; void op1([in,switch_is(p1)] union t1 p2); / p1 not found / void op2([in]long p1, [in,switch_is(p1)] union t1 p2); / correct */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1238	ERROR: Union discriminator type name must be long, short, small, char, boolean, or enum
	Description	In an IDL file, a non-encapsulated union was defined with an invalid [switch_is()] variable type (a string, structure, or union). This error will also be generated if the type was a pointer within a structure, if the type had multiple pointers, or was an array. For example, typedef [switch_type (long) ] union t1 { [case (1,3)] float u1; [case (2)] short u2; [default] ; } t1; typedef struct { [switch_is(s2)] union t1 s1; long s2; / error - pointer in struct / } t2; void op1([in,switch_is(p2)]union t1 p1,[in]long p2); / error / void op2([in,switch_is(p2)]union t1 p1,[in]char p2); /* error / void op3([in,switch_is(p2)]union t1 p1,[in]long p2[10]); / error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1239	ERROR: [switch_type] doesn't match [switch_is(name)] type
	Description	In an IDL file, a non-encapsulated union was defined where the type specified in the [switch_type()] attribute does not match the type of name in the [switch_is()] attribute. For example, typedef [switch_type (long) ] union t1 { [case (1,3)] float u1; [case (2)] short u2; [default] ; } t1; void op1([in,switch_is(p2)]union t1 p1,[in]short p2); /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1240	ERROR: Constant identifier name not previously defined
	Description	In an IDL file, an identifier, name, was used in an expression but had not been previously defined. For example, typedef long t1[notdefined]; /* error / const short t2 = notdefined2 + 3; / errodeor */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1241	ERROR: Incomplete structure/union
	Description	In an IDL file, a parameter was defined using a structure or union type whose definition was not complete (i.e., its members have not been defined). Only pointers to incomplete structures or unions are allowed. For example, typedef struct t1 t1; void op1([in]struct t1 p1); /* error / void op2([in]struct t1 p1); /* correct */ typedef struct t1 { long s1; } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1242	WARN: Interface name name1 in ACS file doesn't match name2
	Description	In an ACS file, the specified interface name, name1, doesn't match the interface name specified in the IDL file, name2.
Action	Change the ACS or IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1243	WARN: [in_line] and [out_of_line] can only be applied to non-scaler types
	Description	In an ACS file, the [in_line] or [out_of_line] attribute was specified for a data type that was a scaler. These attributes can only be specified for structures, unions, context handles, arrays, and pipes.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1244	ERROR: [represent_as] cannot be specified for conformant or varying arrays
	Description	In an ACS file, a [represent_as()] attribute was specified for a type that was or contained either a conformant or varying array. For example, /* IDL / typedef long conf[]; typedef struct { long s1; [max_is(s1)]conf s2; } t1; / ACS / typedef [represent_as(long)]conf; / error / typedef [represent_as(long)]t1; / error */
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1245	ERROR: [represent_as] cannot be specified for types that are or contain pointers
	Description	In an ACS file, a [represent_as()] attribute was specified for a type that was or contained a pointer. For example, /* IDL / typedef long t1; typedef struct { long s1; } t2; / ACS / typedef [represent_as(long)]t1; / error / typedef [represent_as(long)]t2; / error */
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1247	ERROR: [represent_as] cannot be specified for pipe types or types used as the base type in a pipe definition
	Description	In an ACS file, a [represent_as()] attribute was specified for a type that was a pipe type or was the base type in a pipe definition. For example, /* IDL / typedef long pipebase_t; typedef pipe long pipe_t; typedef pipe pipebase_t pipe2_t; / ACS / typedef [represent_as(long)]pipe_t; / error / typedef [represent_as(long)]pipebase_t; / error */
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1249	ERROR: Type name not defined
	Description	In an ACS file, a typedef name was specified for a type that had not been defined in the IDL file. For example, typedef [represent_as(long)]badname; /* error if badname not defined */
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1251	ERROR: [uuid] redeclared
	Description	In an IDL file, a uuid value was specified more than once. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000), uuid(7E291480-A2B0-110F-89E9-930269220000)] /* error */ interface inter
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1252	ERROR: Can't specify both [local] and [uuid]
	Description	In an IDL file, both the [uuid] and [local] attributes are specified. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000), local] /* error */ interface inter
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1253	WARN: [version] redeclared
	Description	In an IDL file, the version number was specified more than once. The last version number specified is used. For example, version 1.0 is used for the following: [uuid(7E291480-A2B0-110F-89E9-930269220000),version(0.0), version(1.0)]
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1254	WARN: [version] major greater than 65535; reset to 0
	Description	In an IDL file, the major version number was not within the valid range (0 to 65535, inclusive). A default of 0 was used. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000),version(70000.0)]
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1255	WARN: [version] minor greater than 65535; reset to 0
	Description	In an IDL file, the minor version number was not within the valid range (0 to 65535, inclusive). A default of 0 was used. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000),version(1.70000)]
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1256	WARN: [endpoint] not supported - ignored
	Description	In an IDL file, an [endpoint] attribute was specified. This attribute is not supported and is ignored. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000),endpoint("t1")]
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1257	ERROR: Can't specify both [local] and [uuid]
	Description	In an IDL file, both the [uuid] and [local] attributes are specified. For example, [local, uuid(7E291480-A2B0-110F-89E9-930269220000)] /* error */ interface inter
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1258	ERROR: pointer_default specified more than once
	Description	In an IDL file, the [pointer_default] attribute was specified more than once. The second and other instances were ignored. For example, [uuid(7E291480-A2B0-110F-89E9-930269220000),pointer_default(ptr), pointer_default(ptr)] /* warning */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1259	ERROR: [uuid] or [local] attribute must appear if an operation is defined
	Description	In an IDL file, an operation was defined but neither [uuid] nor [local] were defined in the interface heading.
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1261	ERROR: Missing semi-colon
	Description	An error occurred while parsing an IDL file. The error was most likely a missing semi-colon. This error may cause other errors to be flagged that are not actually errors (e.g., names or tags may not be defined, etc.). For example, void op1(void) /* error */ void op2(void);
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1262	ERROR: Non-integer value in constant expression
	Description	In an IDL file, a non-integer value appears in the arithmetic expression for a constant. For example, const char a = "abc"; const long b = a + 1; / error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1263	WARN: More than one binding handle attribute specified
	Description	In an ACS file, [explicit_handle] is specified when another binding handle attribute has already been specified. All but the first binding handle attribute are ignored.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1264	WARN: More than one binding handle attribute specified
	Description	In an ACS file, [implicit_handle] is specified when another binding handle attribute has already been specified. All but the first binding handle attribute are ignored.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1265	WARN: More than one binding handle attribute specified
	Description	In an ACS file, [auto_handle] is specified when another binding handle attribute has already been specified. All but the first binding handle attribute are ignored.
Action	Change the ACS input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1277	ERROR: Integer overflow
	Description	In an IDL file, the addition of two operands in an arithmetic expression caused an integer overflow. For example, const long l = 2000000000 + 2000000000; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1280	ERROR: Integer overflow
	Description	In an IDL file, the multiplication of two operands in an arithmetic expression caused an integer overflow. For example, const long l = 2000000000 * 2000000000; /* error */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1282	ERROR: Division by 0 in constant expression
	Description	In an IDL file, a constant expression contained a division by 0. For example, const long l = 2000000000 / 0;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1284	ERROR: Division by 0 in constant expression
	Description	In an IDL file, a constant expression contained a division by 0 (using the modulus operator). For example, const long l = 2000000000 % 0;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1290	ERROR: Type name not defined
	Description	In an IDL file, a type used in the definition of another type was not defined. For example, typedef t1 t2; /* error if t1 not previous defined */
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1291	ERROR: Duplicate member name - membername
	Description	In an IDL file, more than one member within the same structure had the same name, membername. For example, typedef struct { long s1; long s1; /* error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1292	ERROR: Conformant element must be the last element in a structure
	Description	In an IDL file, a structure had a conformant element that was not the last element in the structure. For example, typedef struct { [size_is(s2)]long s1[]; long s2; /* error - conformant element not last / } t1; typedef struct { long s1; [size_is(s1)]long s2[]; / correct */ } t2;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1293	ERROR: Context handle cannot be specified for structure member
	Description	In an IDL file, a structure had a member that was a context handle. For example, typedef [context_handle]void ch_t; typedef struct { [context_handle] void s1; /* error / ch_t s2; / error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1294	ERROR: handle_t type cannot be specified for structure member
	Description	In an IDL file, a structure had a member that was a handle_t type. For example, typedef handle_t hand; typedef struct { handle_t s1; /* error / hand s2; / error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1295	ERROR: Pipe type cannot be specified for structure member
	Description	In an IDL file, a structure had a member that was a pipe type. For example, typedef pipe long pipe_t; typedef struct { pipe_t s2; /* error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1296	ERROR: Structure member cannot be a function pointer
	Description	In an IDL file, a structure had a member that was a function pointer. For example, typedef [ptr]long (fp)([in]long p1); typedef struct { fp s1; / error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1297	ERROR: Structure member cannot be a function
	Description	In an IDL file, a structure had a member that was a function. For example, typedef long func([in]long p1); typedef struct { func s1; /* error */ } t1;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide
1299	ERROR: Discriminator type must be long, short, small, char, boolean, or enum
	Description	In an IDL file, a non-encapsulated union was defined with an invalid [switch_type()] variable type (a string, structure, or union), or an encapsulated union had an invalid switch() variable type. This error will also be generated if the type was a pointer or an array. For example, typedef [ptr]long t1; typedef [switch_type (t1) ] union { / error / [case (2)] short u2; [default] ; } t2; typedef union switch(t1 u1) { / error */ case 2: short u2; default: ; } t3;
Action	Change the IDL input file and re-run the tidl program.
See Also	BEA TUXEDO TxRPC Guide

[Top] [Prev] [Next] [Bottom]