---

2. TxRPC Messages 1100-1199

---

1100	WARN: Unreachable case label: labelvalue
	Description	In an IDL file, a union was defined with a case label, labelvalue, that cannot be reached because it was not in the range defined by the discriminant. For example, typedef union switch (short discriminant) myunion { case 100000: long u1; /* warning */ default: long u2; } myunion;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1101	ERROR: [context_handle] identifier must be less than 24 characters in length
	Description	In an IDL file, the name of a type or a parameter with the [context_handle] attribute was longer than 23 characters in length. For example, typedef [context_handle]void *t23456789012345678901234; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1102	ERROR: [handle] identifier must be less than 25 characters in length
	Description	In an IDL file, the name of a type or a parameter with the [handle] attribute was longer than 24 characters in length. For example, typedef [handle]void *t234567890123456789012345; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1103	ERROR: Variable declarations not supported
	Description	In an IDL file, a variable was declared. Only types, constants, and operations can be declared. For example, long l1; /* error */ typedef long l2; /* ok */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1104	ERROR: [transmit_as] identifier must be less than 22 characters in length
	Description	In an IDL file, the name of a type with the [transmit_as] attribute was longer than 21 characters in length. For example, typedef [transmit_as(long)] short *t234567890123456789012; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1105	ERROR: The void * type can only be used for context handles
	Description	In an IDL file, a structure or union field, or a parameter had a type of "void *" but does not have the [context_handle] attribute. For example, typedef void *t1; typedef struct { [ptr] void *s1; /* error */ t1 s2; /* error */ } t2; void op1([in]t1 p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1106	ERROR: [context_handle] may only be specified for void * parameter
	Description	In an IDL file, a parameter had a [context_handle] attribute but the base data type had more than one pointer to a void. For example, typedef void **t1; void op1([in,context_handle]t1 p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1107	ERROR: The void type can only be used for context handles and operation return
	Description	In an IDL file, a structure or union field, or a parameter had a "void" data type but does not have a [context_handle] attribute. For example, typedef void t1; typedef struct { void s1; /* error */ t1 s2; /* error */ } t2; void op1([in]t1 p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1108	ERROR: Pointers to context handles valid only on parameters
	Description	In an IDL file, a structure or union field, or a type definition had a pointer to a type with the [context_handle] attribute. For example, typedef [context_handle]void *t1; typedef t1 *t2; /* error */ typedef struct { [context_handle]void **s1; /* error */ [context_handle]t3 s1; /* error */ } t4;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1109	ERROR: Functions or function pointers are not valid in conformant arrays
	Description	In an IDL file, a conformant array (with at least one open bound) of function pointers or functions was defined. For example, typedef long (*t1)(void); typedef t1 t2[]; /error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1110	ERROR: Array function return and function arrays not allowed
	Description	In an IDL file, an array of functions or a function returning an array was defined. For example, typedef long (t1)(void); typedef long (t2)(void)[3]; /* error */ typedef t1 t3[3]; /* error */ typedef long (t2)[3](void); /* error */
	Action	Try returning a structure that contains the array. Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1111	ERROR: Cannot have a pointer to a varying array
	Description	In an IDL file, a pointer to a varying array (an array with one or more varying dimensions defined by first_is, length_is, or last_is) was defined. For example, typedef struct { long length; [length_is(length)]long (*s1)[10]; /* error */ } t1; void op1([in]long length, [in,length_is(length)]long (*p2)[10]); /* error */
	Action	Try using a pointer to the structure containing the varying array. Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1112	ERROR: Cannot have [string] attribute for varying array
	Description	In an IDL file, a varying array (an array with one or more varying dimensions defined by first_is, length_is, or last_is) had the [string] attribute. Since the length of the value is determined at run-time by the non-NULL length of string, the varying attributes are not allowed. For example, typedef [string]char str[10]; typedef struct { long length; [length_is(length)]str s1; /* error */ } t1; void op1([in]long length, [in,length_is(length)]str p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1113	ERROR: [transmit_as] cannot be specified for pipe types
	Description	In an IDL file, a type definition had the [transmit_as] attribute but the data type was a "pipe". For example, typedef pipe long t1; typedef [transmit_as(long)]t1 t2; /* error */ typedef [transmit_as(long)]pipe long t3; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1114	ERROR: [transmit_as] cannot be specified for conformant arrays or structures, or varying arrays
	Description	In an IDL file, a type definition had the [transmit_as] attribute but the data type was a conformant array, conformant structure, or varying array. For example, typedef long t1[]; typedef struct { long max; [max_is(max)]t1 s1; }t2; typedef [transmit_as(long)]t1 t3; /* error */ typedef [transmit_as(long)]t2 t4; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1115	ERROR: [transmit_as] cannot be specified for types used as the base type in a pipe definition
	Description	In an IDL file, a type definition had the [transmit_as] attribute but the data type was a typed used in a "pipe" type definition. For example, typedef long pipebase; typedef pipe pipebase t1; typedef [transmit_as(long)]pipebase t3; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1116	ERROR: [transmit_as] cannot be specified for [context_handle] attribute
	Description	In an IDL file, a type definition had the [transmit_as] attribute but the data type had the [context_handle] attribute. For example, typedef [context_handle] void *ch_t; typedef [transmit_as(long)]ch_t t2; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1117	ERROR: The base type for a pipe cannot be a conformant type
	Description	In an IDL file, a type definition for a pipe had a base data type that was a conformant array or structure. For example, typedef long t1[]; typedef struct { long max; [max_is(max)]long s1[]; }t2; typedef pipe t1 t3; /* error */ typedef pipe t2 t4; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1118	ERROR: The base type for a pipe cannot be the [context_handle] attribute
	Description	In an IDL file, a type definition for a pipe had a base data type that was a context handle. For example, typedef [context_handle]void *ch_t; typedef pipe ch_t t1; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1119	ERROR: The base type for a pipe cannot be the handle_t type
	Description	In an IDL file, a type definition for a pipe had a base data type that was a handle_t type. For example, typedef handle_t handle; typedef pipe handle t1; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1120	ERROR: The base type for a pipe cannot be the pipe type
	Description	In an IDL file, a type definition for a pipe had a base data type that was itself a pipe type. For example, typedef pipe long pipe_t; typedef pipe pipe_t t1; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1121	ERROR: The base type for a pipe cannot be or contain a pointer
	Description	In an IDL file, a type definition for a pipe had a base data type that was or contained a pointer. For example, typedef long *longp; /* error */ typedef struct { [ref]long *s1; } t2; typedef pipe longp t3; /* error */ typedef pipe t2 t4; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1122	ERROR: Handle parameter not allowed in function pointer
	Description	In an IDL file, a type definition for a function pointer contained a handle_t parameter. For example, typedef void (*t1)([in]handle_t p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1123	ERROR: Pipe identifier must be less than 30 characters in length
	Description	In an IDL file, the name of a type in a pipe type definition was longer than 29 characters in length. For example, typedef pipe short t23456789012345678901234567890; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1124	ERROR: Operation return cannot be a pipe
	Description	In an IDL file, an operation return type was of type pipe. For example, typedef pipe short t1; t1 op1(void); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1125	ERROR: Pointers to pipes valid only on parameters
	Description	In an IDL file, a structure or union field, or a function return had a pointer to a pipe type. This is only allowed for parameters. For example, typedef pipe short *t1; typedef struct { t1 s1; /* error */ } t2;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1126	ERROR: [ptr] attribute not valid on pipe parameters
	Description	In an IDL file, a type definition for a pipe contained the [ptr] attribute. For example, typedef [ptr]pipe short *t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1127	WARN: [switch_is] specified for non-union type - ignored
	Description	In an IDL file, a [switch_is()] attribute was specified for a parameter or a structure field with a data type that was not a union. This attribute was ignored and processing continued. For example, typedef struct { long s1; } t1; void op1([in]long p1, [switch_is(p1),in]t1 p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1128	WARN: [switch_type] specified for non-union type - ignored
	Description	In an IDL file, a type definition contained a [switch_type()] attribute for a type that was not a union. For example, typedef [switch_type (long) ] long t1; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1129	ERROR: [switch_is] must be specified for non-encapsulated union
	Description	In an IDL file, a non-encapsulated union parameter or structure field does not have a [switch_is()] attribute. For example, typedef [switch_type (long) ] union { [case (1,3)] float u1; [case (2)] short u2; [default] ; typedef struct { t1 s1; /* error */ } t2; void op1([in]t1 p1); /* error */ void op2([in,switch_is(p2)]t1 p1, [in]long p2); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1130	ERROR: [switch_type] must be specified for non-encapsulated union
	Description	In an IDL file, a type definition for a non-encapsulated union does not contain a [switch_type()] attribute. For example, typedef union { /* error */ [case (1,3)] float u1; [case (2)] short u2; [default] ; } t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1131	ERROR: Tag redeclared - tagvalue
	Description	In an IDL file, a structure or union tag was redeclared (e.g., a structure or union tag was declared twice, a structure tag was re-declared as a union tag, or an encapsulated union tag was re-declared as a non-encapsulated union). For example, typedef struct s1 { long e1; } t1; typedef struct s1 { /* error */ long e1; } t2; typedef union s1 switch (long discriminant) { /* error */ case 0: long e1; } t3;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1132	ERROR: Type typeval not defined
	Description	In an IDL file, a type was used that had not been previously defined. For example, typedef t1 t2; /* error - t1 not defined */ typedef struct { t1 s1; /* error */ } t3;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1133	ERROR: Duplicate attr_val attribute
	Description	In an IDL file, an attribute value, attr_val, was specified more than once for a single type, field, or parameter. For example, typedef [ptr,ptr]long *t1; /* error */ typedef struct { [string,string]char *s1; /* error */ } t2; void op1([in,in]long p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1134	ERROR: Can't specify [context_handle] with [transmit_as]
	Description	In an IDL file, a type definition with the [transmit_as] attribute contains a [context_handle] attribute. For example, typedef [context_handle,transmit_as(long)]void *t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1135	ERROR: Can't specify [min_is] with [string]
	Description	In an IDL file, the [min_is] and [string] attributes were defined for the same field or parameter. For example, void op1([in,min_is(min),string]char p1[*..*], [in]long min); /* error */
	Action	Try removing the [min_is()] attribute. Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1136	ERROR: Can't specify [max_is] with [size_is]
	Description	In an IDL file, the [max_is] and [size_is] attributes were defined for the same field or parameter. For example, void op1([in,max_is(p2),size_is(p2)]char p1[], [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1137	WARN: Pointed-to type name name must be less than 29 characters in length
	Description	In an IDL file, a type name that has a pointer reference has a name longer than 28 characters in length. This may cause the compilation to fail since the generated function names for marshalling the type may not be unique.
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1138	ERROR: Can't specify [first_is] with [string]
	Description	In an IDL file, the [first_is] and [string] attributes were defined for the same field or parameter. For example, void op1([in,first_is(p2),string]char p1[10], [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1139	ERROR: Can't specify [last_is] with [length_is]
	Description	In an IDL file, the [last_is] and [length_is] attributes were defined for the same field or parameter. For example, void op1([in,last_is(p2),length_is(p2)]char p1[10], [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1140	ERROR: Can't specify [string] with [length_is] or [last_is]
	Description	In an IDL file, the [first_is] and [string] attributes were defined for the same field or parameter. For example, void op1([in,length_is(p2),string]char p1[10], [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1143	ERROR: More than one pointer attribute specified
	Description	In an IDL file, the [ptr] and [ref] attributes were defined for the same type definition, field or parameter. For example, void op1([in,ptr,ref]char *p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1146	ERROR: Both [code] and [nocode] specified
	Description	In an ACS file, the [code] and [nocode] attributes were defined for the same interface or operation. For example, [nocode,code]op1(); /* error */
	Action	Change the ACS input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1148	ERROR: Both [in_line] and [out_of_line] specified
	Description	In an ACS file, the [in_line] and [out_of_line] attributes were defined for the same type definition or interface. For example, [in_line,out_of_line]type t1; /* error */
	Action	Change the ACS input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1151	ERROR: Can't specify both [transaction_mandatory] and [transaction_optional]
	Description	In an IDL file, the [transaction_mandatory] and [transaction_optional] attributes were defined for the same interface or operation. For example, [transaction_mandatory,transaction_optional] void op1(void); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1152	ERROR: Array elements cannot be conformant structures or arrays
	Description	In an IDL file, an array was defined whose elements are either a conformant structure or a conformant array. For example, typedef struct { long e1; [max_is(e1)]long conf[]; } confstruct; void op([in,max_is(p2)]confstruct *p1, [in]long p2);
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1153	ERROR: Non-integer array bound
	Description	In an IDL file, the lower bound (or size if only a single bound was specified) for an array dimension was not an integer or a type whose derived type was an integer. Integer types must be (unsigned) long, short, and small. For example, const char *size = "abc"; typedef char t1[size]; /* error */ typedef char t2[size..3]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1154	ERROR: Non-zero lower bound not supported in C
	Description	In an IDL file, the lower bound for an array dimension was not 0 or was an open lower bound. For example, typedef char t1[-1..2]; /* error */ typedef char t2[*..2]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1155	ERROR: Non-integer array bound
	Description	In an IDL file, the upper bound for an array dimension was not an integer or a type whose derived type was an integer. Integer types must be (unsigned) long, short, and small. For example, const char *size = "abc"; typedef char t2[0..size]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1156	ERROR: Upper bound must be greater than lower bound
	Description	In an IDL file, the lower bound was greater than the upper bound for an array dimension. For example, typedef char t1[0..-4]; /* error */ typedef char t1[-4]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1157	ERROR: sizetype value 'var' must be type long, short, or small
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array was not of type long, short, or small. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, void op1([in,first_is(p2)]char p1[10], [in]char p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1158	ERROR: sizetype value 'var' must not be declared as a pointer
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array was declared as a pointer in the attribute but not in its definition. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, void op1([in,first_is(*p2)]char p1[10], [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1159	ERROR: sizetype value 'var' must be declared as a pointer
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array was not declared as a pointer in the attribute but was a pointer in its definition. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, void op1([in,first_is(p2)]char p1[10], [in]long *p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1160	ERROR: sizetype value 'var' must not have [ptr] attribute
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array had the [ptr] attribute in its definition. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, void op1([in,out,first_is(*p2)]char p1[10], [in,out,ptr]long *p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1161	ERROR: sizetype parameter 'var' must have [in] attribute
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array does not have the [in] attribute in its definition, but the array itself had the [in] attribute. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, void op1([in,out,first_is(*p2)]char p1[10], [out]long *p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1162	ERROR: Array elements cannot be conformant structures or arrays
	Description	In an IDL file, an array of conformant structures or conformant arrays was defined.
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1163	ERROR: sizetype value 'var' not defined
	Description	In an IDL file, the parameter name or field name var used to specify the array size for a conformant or varying array was not defined. sizetype may be one of [first_is()], [last_is()], [length_is()], [min_is()], [max_is()], or [size_is()]. For example, typedef struct { long s1; [max_is(wrong)]long s2[]; /* error */ }t1; void op1([in,out,first_is(*wrong2)]char p1[10], [out]long *p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1164	ERROR: Array elements cannot be conformant structures or arrays
	Description	In an IDL file, an array of conformant structures or conformant arrays was defined. For example, typedef long conf[]; /* conformant array */ typedef struct { long s1; [max_is(s1)]conf s2; /* conformant struct */ } confstruct; typedef conf t3[10]; /* error */ typedef conf t4[10]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1165	ERROR: Array elements cannot be type pipe
	Description	In an IDL file, an array of pipes was defined. For example, typedef pipe long pipe_t; typedef pipe_t t2[10]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1166	ERROR: Array elements cannot be type handle_t
	Description	In an IDL file, an array of handle_t types was defined. For example, typedef handle_t t2[10]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1167	ERROR: Cannot have a pointer to a conformant array
	Description	In an IDL file, a pointer to a conformant array was defined. If necessary, use a pointer to a structure with a conformant array. For example, typedef long conf[]; /* conformant array */ typedef struct { long max; [max_is(max)]conf s1; /* conformant struct */ } t1; void op([in, max_is(max)]conf *p1, [in]long max); /* error */ void op2([in]t1 *p1); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1168	ERROR: Array elements cannot be or have [context_handle] attribute
	Description	In an IDL file, an array was defined with elements that have the [context_handle] attribute. For example, typedef [context_handle] void *ch_t; typedef ch_t array[10]; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1169	ERROR: Missing [min_is()] value for var
	Description	In an IDL file, a conformant array var, was missing one or more [min_is()] attribute variables. One [min_is()] attribute variable is needed for each array dimension where the lower bound is open. For example, void op1([in,min_is(p2)]char p1[*..1][*..2],[in]long p2); /*error*/ void op2([in,min_is(p2,p2)]char p1[*..1][*..2],[in]long p2); /*correct*/
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1170	ERROR: Cannot have [min_is()] value for dimension dim
	Description	In an IDL file, a conformant array had a [min_is()] attribute variable for an array dimension that was fixed (i.e., not open). For example, void op1([in,min_is(p2,p2)]char p1[1][*..2], [in]long p2); /* error */ void op2([in,min_is(,p2)]char p1[1][*..2], [in]long p2); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1171	ERROR: Missing [max_is()] or [size_is()] value for 'var'
	Description	In an IDL file, a conformant array var, was missing one or more [max_is()] or [size_is()] attribute variables. One [max_is()] or [size_is()] attribute variable is needed for each array dimension where the upper bound is open. For example, void op1([in,max_is(p2)]char p1[][], [in]long p2); /* error */ void op2([in,max_is(p2,p2)]char p1[][], [in]long p2); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1172	ERROR: Cannot have [max_is()] or [size_is()] value for dimension dim
	Description	In an IDL file, a conformant array had a [max_is()] or [size_is()] attribute variable for an array dimension that was fixed (i.e., not open). For example, void op1([in,max_is(p2,p2)]char p1[1][2], [in]long p2); /* error */ void op1([in,max_is(,p2)]char p1[1][], [in]long p2); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1173	ERROR: Too many [min_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [min_is()] attribute variables. One [min_is()] attribute variable is needed for each array dimension where the lower bound is open. This error also occurs when defining the [min_is()] attribute for a variable that was not an array. For example, void op1([in,min_is(p2,p2)]char p1[*..1], [in]long p2); /* error */ void op2([in,min_is(p2)]char p1[*..1], [in]long p2); /* correct */ void op3([in,min_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1174	ERROR: Too many [max_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [max_is()] attribute variables. One [max_is()] attribute variable is needed for each array dimension where the upper bound is open. This error also occurs when defining the [max_is()] attribute for a variable that was not an array or a pointer treated as an array. For example, void op1([in,max_is(p2,p2)]char p1[], [in]long p2); /* error */ void op1([in,max_is(p2)]char p1[], [in]long p2); /* correct */ void op1([in,max_is(p2)]char *p1[], [in]long p2); /* correct */ void op1([in,max_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1175	ERROR: Too many [size_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [size_is()] attribute variables. One [size_is()] attribute variable is needed for each array dimension where the upper bound is open. This error also occurs when defining the [size_is()] attribute for a variable that was not an array or a pointer treated as an array. For example, void op1([in,size_is(p2,p2)]char p1[], [in]long p2); /* error */ void op2([in,size_is(p2)]char p1[], [in]long p2); /* correct */ void op3([in,size_is(p2)]char *p1, [in]long p2); /* correct */ void op4([in,size_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1176	ERROR: Too many [length_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [length_is()] attribute variables. One [length_is()] attribute variable can be specified for each array dimension. This error can also occur when a pointer was intended to be treated as an array (using [size_is()] or [max_is()]) but the array size was missing, or if the defined type was not an array. For example, void op1([in,length_is(p2,p2)]char p1[10], [in]long p2); /* error */ void op2([in,length_is(p2)]char p1[10], [in]long p2); /* correct */ void op3([in,length_is(p2)]char *p1, [in]long p2); /* error */ void op4([in,length_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1177	ERROR: Too many [last_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [last_is()] attribute variables. One [last_is()] attribute variable can be specified for each array dimension. This error can also occur when a pointer was intended to be treated as an array (using [size_is()] or [max_is()]) but the array size was missing, or if the defined type was not an array. For example, void op1([in,last_is(p2,p2)]char p1[10], [in]long p2); /* error */ void op2([in,last_is(p2)]char p1[10], [in]long p2); /* correct */ void op3([in,last_is(p2)]char *p1, [in]long p2); /* error */ void op4([in,last_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1178	ERROR: Too many [first_is()] values specified
	Description	In an IDL file, a structure field or parameter was defined with too many [first_is()] attribute variables. One [first_is()] attribute variable can be specified for each array dimension. This error can also occur when a pointer was intended to be treated as an array (using [size_is()] or [max_is()]) but the array size was missing, or if the defined type was not an array. For example, void op1([in,first_is(p2,p2)]char p1[10], [in]long p2); /* error */ void op2([in,first_is(p2)]char p1[10], [in]long p2); /* correct */ void op3([in,first_is(p2)]char *p1, [in]long p2); /* error */ void op4([in,first_is(p2)]char p1, [in]long p2); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1180	ERROR: [string] attribute valid only for one-dimensional char, byte, or byte structure
	Description	In an IDL file, the [string] attribute was specified for a data type that was not a one-dimensional array of characters or bytes (or a pointer treated as a one-dimensional array), or a simple structure that contains only byte fields. For example, typedef [string]struct { struct { byte s1; /* error */ } s1; } t1; typedef [string,ref] char *t2[10]; /* error */ typedef [string,ref] char *t3; /* correct */ typedef [string] char t4[10]; /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1181	ERROR: Pointers to handle_t type are allowed only for parameters
	Description	In an IDL file, pointer to a handle_t type was defined in a type or field definition; this is allowed only for parameters. For example, typedef [ref]handle_t *handlep_t; /* error */ void op1([in,ref]handle_t *p1); /*correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1182	ERROR: [context_handle] may not have [ptr] attribute
	Description	In an IDL file, a context handle parameter was defined with the [ptr] pointer attribute. For example, typedef [context_handle] void *ch_t; void op1([in,ptr]ch_t **t1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1183	ERROR: [ignore] attribute may only be specified for pointers
	Description	In an IDL file, an [ignore] attribute was specified for a structure field that was not a pointer. For example, typedef struct { [ignore]long l; /* error */ } t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1184	ERROR: [context_handle] may only be specified for void * parameter
	Description	In an IDL file, a structure field or parameter was defined with the [context_handle] attribute but the data type was not "void *". For example, typedef struct { [context_handle]long p1; /* error */ } t1; void op1([context_handle,in]long p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1185	ERROR: Pointer attribute can only be specified for array parameters or pointer types
	Description	In an IDL file, a type or field definition contained a [ref] or [ptr] pointer attribute but the definition did not contain an explicit pointer (i.e., "*"). This error occurs for a parameter definition that was not an array or explicit pointer. Note that this error also occurs when specifying a pointer attribute on a "void *" data type. For example, typedef [ref]long t1; /* error */ typedef [context_handle,ptr] void *ch_t; /* error */ typedef struct { [ref]long s1; /* error */ } t3;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1186	ERROR: [out] parameter must be passed by reference
	Description	In an IDL file, a parameter was defined with the [out] attribute but does not have an explicit pointer ("*") and was not an array. For example, void op1([out]long p1); /* error */ void op1([out]long *p1); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1187	ERROR: Pointer attribute not defined for 'var'
	Description	In an IDL file, a structure or union field or typedef contained a pointer without a pointer attribute, or a field, type, or parameter had more than one pointer and the [pointer_default()] attribute was not set. For example, typedef long *t1; /* error */ typedef struct { long *s1; /* error */ }t2; void op1([in]long **p1); /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1188	ERROR: [out, ptr] not allowed - [in] attribute needed
	Description	In an IDL file, a parameter was defined with the [out] and [ptr] attributes but not the [in] attribute. For example, void op1([out,ptr]long *p1); /* error */
	Action	Either add the [in] attribute or change the [ptr] attribute to [ref]. Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1189	ERROR: An [out] conformant [string] must have [max_is] or [size_is]
	Description	In an IDL file, a [string] parameter was defined as [out] but was not defined as a fixed array nor does it not have the [max_is] or [size_is] attributes. This combination makes it impossible to determine the size of the string to allocate in the server stub. For example, void op1([out,string]char *p1); /* error */ void op2([out,string]char p1[10]); /* correct */ void op3([out,string,max_is(p2)]char *p1, [in]long p2); /* correct */
	Action	Either make the variable a fixed array (which will still be variable in length based on where the NULL occurs), or specify the [max_is()] or [size_is()] attribute. Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1190	ERROR: An [out] conformant array must be a top-level parameter or under a full pointer
	Description	In an IDL file, a conformant array was defined in an [out,ref] parameter. It must either were defined as a top-level [out] parameter, or under a full pointer ([ptr]). For example, typedef long conf[]; typedef struct { long s1; [max_is(s1)]conf s2; } t2; typedef struct { long s1; [ptr,max_is(s1)]long *s2; /* full pointer */ } t3; void op1([out,ref]t2 *p1); /* error */ void op2([in,out,ptr]t2 *p1); /* correct */ void op3([out,max_is(p2)]conf p1, [in]long p2); /* correct */ void op4([out]t3 *p1); /* correct */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1192	ERROR: Identifier redeclared - name
	Description	In an IDL file, a duplicate name was used for a typedef, constant, or enumeration value name, or an operation name. These names are all in the same name space and must be unique. For example, typedef long t1; typedef long t1; /* error */ typedef enum { t1 } t1; /* two errors */ const long t1 = 1; /* error */
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1193	WARN: [ignore] attribute not allowed on union arm - ignored
	Description	In an IDL file, the [ignore] attribute was specified for a union arm. The attribute was ignored and processing continued. For example, typedef union switch (short u1) { case 0: ; case 1: [ignore,ptr]long *l; /* error */ } t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1194	ERROR: Context handles may not be members of a union
	Description	In an IDL file, a union arm was defined to be a context handle. For example, typedef union switch (short u1) { case 0: ; case 1: [context_handle]void *handle; /* error */ } t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1195	ERROR: Conformant arrays may not be members of a union
	Description	In an IDL file, a union arm was defined to be a conformant structure or array. For example, typedef struct { long s1; [max_is(s1)]long s2[]; /* conformant structure */ } t1; typedef union switch (short u1) { case 0: ; case 1: t1 u2; /* error */ case 2: long u3[]; /* error */ } t2;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1196	ERROR: Function pointers may not be members of a union
	Description	In an IDL file, a union arm was defined to be a function pointer. For example, typedef union switch (short u1) { case 0: ; case 1: [ptr]long (*u2)(void); /* error */ } t1;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1197	ERROR: Pipes may not be members of a union
	Description	In an IDL file, a union arm was defined to be a pipe or a type derived from a pipe. For example, typedef pipe long pipe_t; typedef union switch (short u1) { case 0: ; case 1: pipe_t u2; /* error */ } t2;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide
1198	ERROR: handle_t values may not be members of a union
	Description	In an IDL file, a union arm was defined to be a handle_t type. For example, typedef union switch (short u1) { case 0: ; case 1: handle_t u2; /* error */ } t2;
	Action	Change the IDL input file and re-run the tidl program.
	See Also	BEA TUXEDO TxRPC Guide

---

---