OSF DCE Problem Determination Guide

Action: Correct the syntax of the <kw>(endpoint) speciﬁcation.

0x1328316c NIDL_NOFLTPARAM

Severity: Varies Component: idl

Text: Warning: A [fault_status] parameter has no utility in this operation

Explanation: A <kw>([fault_status]) parameter is used in an operation where no fault

can ever occur. An example is an encoding services operation, i.e. one using

<kw>([encode]) or <kw>([decode]) - there is no remote entity from which a fault might

be received.

Action: Perhaps you meant to use a <kw>([comm_status]) attribute. If not, the parameter

can be removed from the operation or the <kw>([fault_status]) attribute can be removed

from the parameter.

0x132830ae NIDL_NONINTEXP

Severity: Varies Component: idl

Text: Non-integer values are not allowed in expressions

Explanation: One of the values in the expression is not an integer (or one that can be

promoted to integer).

Action: Correct the expression to contain only integer values.

0x13283025 NIDL_NONPORTCHAR

Severity: Varies Component: idl

Text: Warning: Character constant cannot be portable across character sets

Explanation: You used an integer value to specify a character. This cannot be portable

across different character sets (ASCII and EBCDIC).

Action: Consider your portability requirements.

0x1328316b NIDL_NOPORTANON

Severity: Varies Component: idl

Text: Warning: Use of anonymous %1$s may not be portable across C compilers

Explanation: The source IDL contains an IDL language construct, such as an

<kw>(enum), declared as an unnamed type within another deﬁnition. The generated stub

code will compile cleanly under some C compilers, but generate errors from others. The

potential errors are due to differences in the scoping of identiﬁers across C compilers.

Action: Use a <kw>(typedef) statement to deﬁne the base <kw>(type) as a named type,

then use the type name in any subsequent declarations in place of an anonymous

deﬁnition.

0x13283168 NIDL_NOPORTATTR

2− 440 Tandem Computers Incorporated 124330