OSF DCE Problem Determination Guide

Error Messages and Status Codes
Action: Change the data limit field or parameter referenced by the <kw>([first_is]) clause
to integer data type.
0x1328312a NIDL_FLDXMITCFMT
Severity: Varies Component: idl
Text: A structure field cannot be of a presented type for which the transmitted type is
conformant
Explanation: IDL does not allow a structure field whose type has a <kw>([transmit_as])
attribute where the transmissible type is conformant.
Action: Use a valid IDL construct.
0x1328305c NIDL_FLOATCONSTNOSUP
Severity: Varies Component: idl
Text: Floating point constants not supported
Explanation: Floating point constants cannot be specified in IDL.
Action: Remove the <kw>(float) constant specification.
0x13283005 NIDL_FLOATPROM
Severity: Varies Component: idl
Text: Must compile stubs with ANSI C compiler to avoid promotion of float to double in
operation %1$s
Explanation: The operation contains a <kw>(float) parameter passed by value. Non-
ANSI C compilers that do not support function prototypes, automatically promote
<kw>(float) to <kw>(double). Function prototypes within generated C stubs are
conditional on the IDL_PROTOTYPES preprocessor symbol. When you compile a stub
with a non-ANSI C compiler, IDL_PROTOTYPES must not be defined (causing the non-
prototyped definitions to compile) and thus causing <kw>(float) to <kw>(double)
promotion. This breaks the marshalling logic in the stub, that expects a <kw>(float), not a
<kw>(double).
Action: Problems do not occur as long as you compile stubs with an ANSI C compiler.
However, to maximize portability, it is highly recommended that you modify any
<kw>(float) parameter passed passed by value or a <kw>(float) passed by reference. This
message is informational.
0x1328312d NIDL_FORPOINTER
Severity: Varies Component: idl
Text: Warning: FORTRAN INTEGER*%1$lu used for IDL pointer type
Explanation: FORTRAN does not have a generic explicit pointer type. IDL maps
pointer references to INTEGER*<v>(n) in the generated FORTRAN header file.
Action: It is up to the FORTRAN application code to correctly manage the generated
INTEGER*<v>(n) object as a pointer.
124330 Tandem Computers Incorporated 2−411