TRPC Messages 1300-1399

1301

ERROR: Constant expression in union arm cannot be a string constant or NULL

Description

In an IDL file, a union arm case value was a string constant or NULL, or a constant expression evaluating to one of these. For example,

typedef union switch(long u1) {
  case "abc": short u1; /* error */
  case NULL: short u2; /* error */
} t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1302

ERROR: Variable not specified for [switch_is]

Description

In an IDL file, a non-encapsulated union was defined with a [switch_is()] attribute that was missing the variable name. For example,

typedef [switch_type (long) ] union t1 {
  [case (1,3)] float u1;
  [case (2)] short u2;
  [default] ;
} t1;
void op1([switch_is(),in]t1 p1);

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1303

ERROR: Too many enumeration values

Description

In an IDL file, an enumeration was defined with more than 32767 values.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1304

ERROR: [v1_struct] attribute not supported

Description

In an IDL file, the [v1_struct] attribute was specified. This attribute is only for backward compatibility with NIDL V1 and is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1305

ERROR: [v1_enum] attribute not supported

Description

In an IDL file, the [v1_enum] attribute was specified. This attribute is only for backward compatibility with NIDL V1 and is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1306

ERROR: [align()] attribute not supported

Description

In an IDL file, the [align()] attribute was specified. This attribute is not part of the standard but proposed in some dialects; it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1307

ERROR: [min_is()] attribute not supported

Description

In an IDL file, the [min_is()] attribute was specified. This attribute is not part of the standard but proposed in some dialects; it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1310

ERROR: [v1_string] attribute not supported

Description

In an IDL file, the [v1_string] attribute was specified. This attribute is only for backward compatibility with NIDL V1 and is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1311

ERROR: [v1_array] attribute not supported

Description

In an IDL file, the [v1_array] attribute was specified. This attribute is only for backward compatibility with NIDL V1 and is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1312

ERROR: Transmitted type cannot be conformant or be or contain pointer

Description

In an IDL file, a type definition had a [transmit_as()] attribute. The transmitted type had or contained a pointer or was a conformant array (transmission of conformant structures is supported). For example,

typedef long conf[]; 
typedef [transmit_as(conf)] long t1; /* error */
typedef [ptr]long *longp;
typedef [transmit_as(longp)] long t2; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1313

ERROR: The void type can only be used for context handles and operation return

Description

In an IDL file, a type definition had a [transmit_as()] attribute and the transmitted type was type void. For example,

typedef void t1; 
typedef [transmit_as(t1)] long t2; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1314

ERROR: All attribute variables are null

Description

In an IDL file, one of the size attributes (size_is, max_is, min_is, length_is, last_is, or first_is) was specified but no attribute variables are specified within the size attribute. For example,

void op1([in,max_is()]long p1[]); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1315

WARN: [unique] not supported; [ptr] assumed

Description

In an IDL file, the [unique] pointer attribute was specified. This attribute is not part of the standard but proposed in some dialects; it is not supported. For further processing, [ptr] was assumed instead.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1316

WARN: [idempotent] attribute not supported - ignored

Description

In an IDL file, the [idempotent] attribute was specified. This attribute need not be supported in TxRPC (although part of DCE/RPC); it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1317

WARN: [broadcast] attribute not supported - ignored

Description

In an IDL file, the [broadcast] attribute was specified. This attribute need not be supported in TxRPC (although part of DCE/RPC); it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1318

WARN: [maybe] attribute not supported - ignored

Description

In an IDL file, the [maybe] attribute was specified. This attribute need not be supported in TxRPC (although part of DCE/RPC); it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1319

ERROR: Can't specify transaction attribute at interface and operation levels

Description

In an IDL file, a transaction attribute ([transaction_mandatory] or [transaction_optional]) was specified at both the interface level and on an operation. For example,

[uuid(0679E900-A387-110F-9215-930269220000),
transaction_mandatory]
interface INTERFACE
{
[transaction_mandatory]void op1(void);
}

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1320

ERROR: Can't specify transaction attribute at interface and operation levels

Description

In an IDL file, a transaction attribute ([transaction_mandatory] or [transaction_optional]) was specified at both the interface level and on an operation. For example,

[uuid(0679E900-A387-110F-9215-930269220000),
transaction_mandatory]
interface INTERFACE
{
[transaction_mandatory]void op1(void);
}

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1321

ERROR: Syntax error

Description

In an IDL file, a "void" was specified for an operation that had more than one parameter. "void" is only valid if an operation has only one parameter and it appears by itself. For example,

void op1([in]long p1, void); /* error */ 
void op2(void); /* correct */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1322

ERROR: Syntax error

Description

In an IDL file, an operation was defined with no parameters ("void") but had parameter attributes. For example,

void op1([in]void); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1323

WARN: [ignore] attribute not allowed on parameter

Description

In an IDL file, the [ignore] attribute was specified for a parameter (it is allowed only for pointers within structures). For example,

void op1([in,ignore]long *p1);

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1324

WARN: [shape] attribute not supported - ignored

Description

In an IDL file, the [shape] attribute was specified. This attribute is not part of TxRPC but proposed in some dialects; it is not supported.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1326

ERROR: Function pointers supported only in local mode

Description

In an IDL file, the interface header had a [uuid()] and not a [local] attribute, and a function pointer type was defined. Function pointers are only supported in [local] mode. For example,

typedef void (*op1)([in]long *p1); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1327

ERROR: Function types supported only in local mode

Description

In an IDL file, the interface header had a [uuid()] and not a [local] attribute, and a function type was defined. Function types are only supported in [local] mode. For example,

typedef void op1([in]long *p1); /* error */ 
void op2([in]long *p1); /* correct */

Action

If this definition was simply for generating a header file, delete the [uuid()] attribute and add a [local] attribute. Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1328

ERROR: [represent_as] cannot be specified for type used as a size attribute

Description

In an IDL file, a size attribute variable for a conformant or varying array has the [represent_as] attribute. For example,

/* IDL File */ 
typedef long t1;
void op([max_is(p2),in]long p1[], [in]t1 p2);
/* ACS file */
typedef [represent_as(long)]t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1329

ERROR: [out_of_line] identifier name must be less than 29 characters in length

Description

In an ACS file, the name of a type that was specified as [out_of_line] had a name that was greater than 28 characters in length. For example,

/* ACS file */ typedef
[out_of_line]t2345678901234567890123456789;

Action

Change the ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1330

WARN: [explicit_handle] not supported

Description

In an ACS file, the [explicit_handle] attribute was specified. This attribute need not be supported in TxRPC IDL-only (although part of DCE/RPC); it is not supported. If [explicit_handle] is specified and the first parameter of the operation is not a binding handle, a binding handle will be added with the name IDL_binding_handle. While providing some compatibility with DCE, the binding handle is not transmitted from the client to the server.

Action

Change the ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1331

WARN: [implicit_handle] not supported

Description

In an ACS file, the [implicit_handle] attribute was specified. This attribute need not be supported in TxRPC IDL-only (although part of DCE/RPC); it is not supported. Specifically, the binding handle is not transmitted from the client to the server.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1334

ERROR: Type name used in [transmit_as()] clause cannot have [represent_as()]

Description

The transmitted type, typename, has the [represent_as] attribute.

Action

Change the IDL or ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1335

ERROR: Type name with [represent_as] must be less than 21 characters in length

Description

In an ACS file, a type whose name was greater than 20 characters was defined with the [represent_as] attribute. For example,

typedef [represent_as(t1)] t123456789012345678901; /* error */

Action

Change the IDL and ACS input files and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1336

WARN: Use ACS include for definition of name

Description

In an ACS file, a [represent_as()] attribute was defined and the name of the type, name, that was not known (not defined in the IDL file). In this case, a header file is needed to define the type (or the C language compiler will not be able to compile the stubs properly). The preferred method of including the header file is via the ACS include statement. For example,

typedef [represent_as(undef)] t1; /* warning for undef */

Action

None.

See Also

BEA TUXEDO TxRPC Guide

1337

ERROR: Operation name not found

Description

In an ACS file, an operation, name, was defined that was not defined in the IDL file. For example,

[code]op1(); /* error if op1 not in IDL file */

Action

Change the IDL or ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1338

ERROR: [comm_status] operation must have type error_status_t

Description

In an ACS file, an operation was defined to have a [comm_status] return but the operation was not defined to return error_status_t. For example,

/* IDL file */ 
long op1(void);
/* ACS file */
[comm_status]op1(); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1339

ERROR: [fault_status] operation must have type error_status_t

Description

In an ACS file, an operation was defined to have a [fault_status] return but the operation was not defined to return error_status_t. For example,

/* IDL file */ long op1(void);
/* ACS file */
[fault_status]op1(); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1340

WARN: [comm_status] specified more than once for operation name - ignored

Description

In an ACS file, the [comm_status] attribute was specified for more than one parameter, or for a parameter and the operation return. For example,

/* IDL file */ 
error_status_t op1([out]error_status_t *p1);
/* ACS file */
[comm_status]op1([comm_status] p1); /* error */

Action

Change the ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1341

WARN: [fault_status] specified more than once for operation name - ignored

Description

In an ACS file, the [fault_status] attribute was specified for more than one parameter, or for a parameter and the operation return. For example,

/* IDL file */ 
error_status_t op1([out]error_status_t *p1);
/* ACS file */
[fault_status]op1([fault_status] p1); /* error */

Action

Change the ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1342

ERROR: Value val overflows long

Description

The lexical analyzer encountered an integer value that was too large to fit into a 32-bit long integer. For example,

const unsigned long l = 0xEE6B28000;  /* error */
const unsigned long l = 0356326240000; /* error */
const unsigned long l = 4000000000;  /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1345

WARN: No hex digits follow \x

Description

The lexical analyzer encountered a '\x' character constant. The value was treated as the character x since it was not followed by any hexadecimal characters.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1346

WARN: Dubious escape \char

Description

The lexical analyzer encountered a character constant with an escape that was not one of the defined escape sequences (e.g., tab, newline, etc.). The character was treated as if the backslash did not appear. For example,

const char i = '\i'; /* warning */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1347

WARN: Character escape \octal does not fit in character

Description

The lexical analyzer encountered a character constant with an octal escape sequence that was too large to fit into a character (greater than 0377). For example,

const char c = '\477'; /* warning */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1348

ERROR: Character escape val does not fit in character

Description

The lexical analyzer encountered a character constant with a hexadecimal escape sequence that was too large to fit into a character (greater than \xff). For example,

const char i = '\xfff'; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1349

ERROR: Newline in character constant

Description

The lexical analyzer encountered a character constant that begins on one line and ends on another line. Often, this indicates a missing quote. For example,

const char i = '\xf 
f'; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1351

ERROR: Invalid parenthesis

Description

In an IDL file, the [uuid] attribute had an extra left parenthesis within the value. For example,

[uuid((0679E900-A387-110F-9215-930269220000)] /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1353

ERROR: Invalid parenthesis

Description

In an IDL file, the [version] attribute had an extra left parenthesis within the value. For example,

[local, version((0.0)] /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1354

ERROR: Newline in string literal

Description

The lexical analyzer encountered a string literal that begins on one line and ends on another line. For example,

const char *str = "first second";

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1355

WARN: Character escape \octal does not fit in character

Description

The lexical analyzer encountered a character string with an octal escape sequence that was too large to fit into a character (greater than 0377). For example,

const char *str = "error \477";

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1356

ERROR: Character escape val does not fit in character

Description

The lexical analyzer encountered a character string with an hexadecimal escape sequence that was too large to fit into a character (greater than \xff). For example,

const char *str = "error \x242";

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1357

WARN: Dubious escape \char

Description

The lexical analyzer encountered a character literal with an escape that was not one of the defined escape sequences (e.g., tab, newline, etc.). The character was treated as if the backslash did not appear. For example,

const char *str = "error \e  ";

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1358

ERROR: End of input reached without terminating comment

Description

The lexical analyzer encountered an end-of-file while within a comment. For example,

const char *str = "string"; /* end of file error

Note: That this error message will not be printed if the file was processed by the C pre-processor (which will detect the error); use -no_cpp to turn off pre-processing.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1359

ERROR: Identifier or number must be preceded and followed by white space or punctuation

Description

The lexical analyzer encountered a number or an identifier that was not preceded or followed by white space or a punctuation character. Usually this indicates a typographical error. For example,

const long sec_per_min = 60; 
const long hour_per_sec = 60sec_per_min; /* missing * */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1360

WARN: Character '\xchar' not portable

Description

The lexical analyzer encountered a character in a character constant or character string constant that is not in the portable character set (0x20 to 0x7e, inclusive). For example,

const char control_A = '\1'; /* warning */

Action

No action required.

See Also

BEA TUXEDO TxRPC Guide

1361

ERROR: End of input reached without terminating double quote

Description

The lexical analyzer encountered an end-of-file while within a character string literal. For example,

const char *str = "error noend /* end of file error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1362

ERROR: Reached count errors; exiting

Description

The tidl command encountered more than count errors (default 50) and was quitting. To get all errors printed, use the -error all option.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1363

ERROR: Reached count errors; exiting

Description

The tidl command encountered more than count errors (default 50) and was quitting. To get all errors printed, use the -error all option.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1365

WARN: Identifier ident is too long - truncating to 31 characters

Description

The lexical analyzer encountered an identifier that was more than 31 characters in length. The identifier is truncated to 31 characters and processing continues. This may cause further

processing errors. For example,

const long t2345678901234567890123456789012 = 60;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1366

ERROR: Character constant too long 'const'

Description

The lexical analyzer encountered an octal character constant that was more than 6 characters in length. For example,

const char c = '\e0000006';

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1367

ERROR: Invalid character constant const

Description

The lexical analyzer encountered a character constant that was multiple characters in length and not one of the valid escape sequences. For example,

const char l = 'ab';

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1372

ERROR: Duplicate interface name 'inter_name' in file filename1 and file filename2

Description

In an imported IDL file, filename1, an interface name was a duplicate of the interface name of a previously processed IDL file filename2.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1373

ERROR: Can't import [local] interface from non-local interface

Description

An IDL file with the [local] interface was imported by another IDL file that does not have the [local] interface.

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1374

ERROR: [switch_is] attribute not allowed on union arm

Description

In an IDL file, a [switch_is] attribute was defined for a union arm. The [switch_is] attribute can appear only with a non-encapsulated union and non-encapsulated unions cannot appear in union arms. For example,

typedef [switch_type (long) ] union t1 {
  [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

1375

ERROR: [switch_is] specified for encapsulated union

Description

In an IDL file, a [switch_is] attribute was specified for an encapsulated union. [switch_is] is allowed only for non-encapsulated unions. For example,

typedef union switch (short u0) t1 { 
case 0: ;
  case 1:
  case 2: short u2;
  case 3:
  case 4: long u3;
} t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1376

ERROR: [switch_type] specified for encapsulated union

Description

In an IDL file, an encapsulated union was defined with the [switch_type] attribute. For example,

typedef [switch_type(long)]union switch (short u0) t1 { /* error */ 
  case 0: ;
  case 1:
  case 2: short u2;
  case 3:
  case 4: long u3;
} t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1377

ERROR: Missing [max_is()] or [size_is()] value for 'name'

Description

In an IDL file, a pointer was defined as a conformant array because the [min_is()] attribute was specified, but the maximum size was not defined via a [size_is()] or [max_is()] attribute. For example,

void op1([in,min_is(p2)]long *p1, [in]long p2);

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1378

ERROR: Types with [represent_as] cannot be nested

Description

In an ACS file, a type was specified as a [represent_as()] type that already had its own [represent_as()] attribute. For example,

/* IDL File */ typedef long t1;
typedef long t2;
/* ACS file */
typedef [represent_as(long)]t1;
typedef [represent_as(t1)]t2; /* error */

Action

Change the ACS input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1379

ERROR: The void type can only be used for context handles and operation return

Description

In an IDL file, an array of the void data type was defined. For example,

typedef void t1[10]; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1380

ERROR: The void type can only be used for context handles and operation return

Description

In an IDL file, a pipe type was defined based on the void data type. For example,

typedef pipe void t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1381

ERROR: Union arm may not contain [ref] pointer

Description

In an IDL file, a union arm was defined with a [ref] pointer attribute. For example,

typedef union switch(long u1) {
  case 0: short u2;
  default: [ref]long *u3; /* error */
} t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1383

ERROR: attrib value 'name' must not have [transmit_as] attribute

Description

In an IDL file, an attribute variable was defined (e.g., for an array size attribute) that had the [transmit_as()] attribute. For example,

typedef [transmit_as(long)]long t1; 
void op1([max_is(p2),in]long p1[],[in]t1 p2); /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1384

ERROR: Type name has [represent_as(rep1)] and [represent_as(rep2)

Description

In an ACS file, a type was defined with more than [represent_as()] attribute. For example,

/* IDL file */ 
typedef long t1;
/* ACS file */
typedef [represent_as(t2)]t1;
typedef [represent_as(t3)]t1; /* error */

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1385

ERROR: Attribute not allowed on tagged structure or union declaration

Description

In an IDL file, a tagged structure or union declaration had an attribute specified. For example,

[transaction_mandatory]struct t1 { /* error */
  long s1;
};

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1386

ERROR: attrib value 'name' must not be a pointer to a field

Description

In an IDL file, an attribute variable (e.g., for defining an array size) was defined as a pointer to a structure field. When a conformant or varying array is defined within a structure, a pointer cannot be used. For example,

typedef struct {
  [ref]long *s1;
  [max_is(*s1)]long s2[]; /* error */
} t1;

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide

1387

ERROR: Invalid FBFR usage

Description

The FBFR type was used in an invalid position (in a varying or conformant array, with a transmit as attribute, with pipe, or without a pointer).

Action

Change the IDL input file and re-run the tidl program.

See Also

BEA TUXEDO TxRPC Guide