LIBSCA Messages 100-199
|
|
101
ERROR: ATMI Binding - Invalid service type: servicetype
Description
The service type value must be either 'RequestResponse' or 'Oneway'. The default is 'RequestResponse'
Action
Check the setting of the
See Also
ATMI binding element reference
102
ATMI Binding - Could not find service type for method method
Description
No
Action
Check the setting of the
See Also
ATMI binding element reference
103
ERROR: ATMI Binding - syntax error in @requires keyword
Description
The @requires keyword contains an invalid value.
Action
Check the setting of the @requires keyword.
See Also
ATMI binding element reference
104
ERROR: ATMI Binding - Oneway service type conflicts with requires=propagatesTransaction
Description
An attempt to reference a 'Oneway' service within a transaction has been made. This is not supported.
Action
Check the setting of the @requires keyword, or
See Also
ATMI binding element reference
105
ERROR: ATMI Binding - propagatesTransaction specified without a valid timeout value
Description
An attempt to reference a service in a transactional call without a timeout value has been made.
Action
Check that the service requires to be called in transactional mode, or specify a timeout value using the
106
ERROR: ATMI Binding - only 1 parameter should be used for a STRING buffer
Description
An attempt to reference a service configured with STRING has been made using a method containing more that one parameter.
Action
Check the service interface, or buffer type setting in SCDL.
See Also
SALT SCA Programming Guide.
107
ERROR: Cannot allocate STRING buffer of size size
Description
An internal error occurred while attempting to allocate space for a STRING type buffer.
Action
Contact Oracle Technical Support.
108
ERROR: Cannot allocate STRING buffer of size size
Description
An internal error occurred while attempting to allocate space for a STRING type buffer.
Action
Contact Oracle Technical Support.
109
ERROR: ATMI Binding - invalid parameter type for Tuxedo STRING buffer
Description
The method parameter for a reference to a service made with a Tuxedo STRING buffer must be of type char *, char [] or std::string.
Action
Check the interface code.
See Also
SALT SCA Programming Guide.
110
ERROR: ATMI Binding - only 1 parameter should be used for an MBSTRING buffer
Description
An attempt to reference a service configured with MBSTRING has been made using a method containing more that one parameter.
Action
Check the service interface, or buffer type setting in SCDL.
See Also
SALT SCA Programming Guide.
111
ERROR: Cannot allocate MBSTRING buffer of size size
Description
An internal error occurred while attempting to allocate space for an MBSTRING type buffer.
Action
Contact Oracle Technical Support.
112
ERROR: Cannot allocate MBSTRING buffer of size size
Description
An internal error occurred while attempting to allocate space for an MBSTRING type buffer.
Action
Contact Oracle Technical Support.
113
ERROR: ATMI Binding - invalid parameter type for Tuxedo MBSTRING buffer
Description
The method parameter for a reference to a service made with a Tuxedo MBSTRING buffer must be of type wchar_t *, wchar_t [] or std::wstring.
Action
Check the interface code.
See Also
SALT SCA Programming Guide.
114
ERROR: ATMI Binding - only 1 parameter should be used for a CARRAY, X_OCTET, or XML buffer
Description
An attempt to reference a service configured with CARRAY, X_OCTET or XML has been made using a method containing more that one parameter.
Action
Check the service interface, or buffer type setting in SCDL.
See Also
SALT SCA Programming Guide.
115
ERROR: ATMI Binding - CARRAY, X_OCTET, or XML buffer specified but wrong parameter type specified
Description
The method parameter for a reference to a service made with a Tuxedo CARRAY, X_OCTET or XML buffer must be of type CARRAY_T, X_OCTET_T or XML_T respectively.
Action
Check the interface code.
See Also
SALT SCA Programming Guide.
116
ERROR: ATMI Binding - Syntax error in value input buffer specification
Description
The syntax for a VIEW32 input buffer specification is: VIEW32/.
Action
Check SCDL setting.
See Also
ATMI binding element reference.
117
ERROR: ATMI Binding - Syntax error in value input buffer specification
Description
The syntax for a VIEW/X_COMMON/X_C_TYPE input buffer specification is: VIEW/, X_COMMON/ or X_C_TYPE/.
Action
Check SCDL setting.
See Also
ATMI binding element reference.
118
ERROR: ATMI Binding - value input buffer not supported in this release
Description
The buffer type reported is invalid or not supported.
Action
Check the setting in the SCDL code.
See Also
ATMI binding element reference.
119
ERROR: ATMI Binding - Invalid return type for STRING buffer
Description
The method return type for a reference to a service made with a Tuxedo STRING buffer should be either char * or std::string.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
120
ERROR: Cannot allocate STRING buffer of size size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo STRING reply.
Action
Contact Oracle Technical Support.
121
ERROR: ATMI Binding - Invalid return type for MBSTRING buffer
Description
The method return type for a reference to a service made with a Tuxedo MBSTRING buffer should be either wchar_t * or std::wstring.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
122
ERROR: Cannot allocate MBSTRING buffer of size size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo MBSTRING reply.
Action
Contact Oracle Technical Support.
123
ERROR: ATMI Binding - Invalid return type for CARRAY, X_OCTET, or XML buffer
Description
The method return type for a reference to a service made with a Tuxedo CARRAY, X_OCTET or XML buffer should be CARRAY_T *, X_OCTET_T * or XML_T * respectively.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
124
ERROR: Cannot allocate type buffer of size size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo reply of the indicated type.
Action
Contact Oracle Technical Support.
125
ERROR: ATMI Binding - Invalid return type for FML/FML32 buffer
Description
The method return type for a reference to a service made with a Tuxedo FML or FML32 buffer should be commonj::sdo::DataObjectPtr.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
126
ERROR: Cannot allocate type buffer of default size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo reply of the indicated type.
Action
Contact Oracle Technical Support.
127
ERROR: ATMI Binding - Syntax error in value output buffer specification
Description
The syntax for a VIEW32 output buffer specification is: VIEW32/.
Action
Check SCDL setting.
See Also
ATMI binding element reference.
128
ERROR: ATMI Binding - Invalid return type for VIEW32 buffer
Description
The method return type for a reference to a service made with a Tuxedo VIEW32 buffer should be commonj::sdo::DataObjectPtr.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
129
ERROR: Cannot allocate type buffer of size size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo reply of the indicated type.
Action
Contact Oracle Technical Support.
130
ERROR: ATMI Binding - Syntax error in value output buffer specification
Description
The syntax for a VIEW, X_COMMON or X_C_TYPE output buffer specification is: VIEW/, X_COMMON/ or X_C_TYPE/.
Action
Check SCDL setting.
See Also
ATMI binding element reference.
131
ERROR: ATMI Binding - Invalid return type for type buffer
Description
The method return type for a reference to a service made with a Tuxedo VIEW, X_COMMON or X_C_TYPE buffer should be commonj::sdo::DataObjectPtr.
Action
Check the method interface.
See Also
SALT SCA Programming Guide.
132
ERROR: Cannot allocate type buffer of size size
Description
An internal error occurred when attempting to allocate memory space for a Tuxedo reply of the indicated type.
Action
Contact Oracle Technical Support.
133
ERROR: ATMI Binding - Cannot start transaction: message
Description
An error occurred when attempting to start a transaction. More information on the nature of the error is also provided.
Action
No action required.
See Also
LIBTUX system messages.
134
ERROR: ATMI Binding - Cannot get transaction level: message
Description
An internal error occurred in transactional processing.
Action
Contact Oracle Technical Support.
135
ERROR: ATMI Binding - Problem calling servicename due to errormessage
Description
An error occurred when calling the indicated service. More information on the nature of the error is also provided.
Action
No action required.
See Also
LIBTUX system messages.
136
ERROR: ATMI Binding - Problem calling servicename due to errormessage
Description
An error occurred when calling the indicated service. More information on the nature of the error is also provided.
Action
No action required.
See Also
LIBTUX system messages.
137
ERROR: ATMI Binding - Invalid return type for STRING buffer
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
138
ERROR: ATMI Binding - Invalid return type for MBSTRING buffer
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
139
ERROR: ATMI Binding - Invalid return type for CARRAY, XML, or X_OCTET buffer
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
140
ERROR: Tuxedo service returned NULL data when expected output type is FML
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
141
ERROR: Tuxedo service returned NULL data when expected output type is FML32
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
142
ERROR: Tuxedo service returned NULL data when expected output type is VIEW32
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
143
ERROR: Tuxedo service returned NULL data when expected output type is VIEW, X_COMMON, or X_CTYPE
Description
The return type for this method is incompatible with the Tuxedo buffer type configured.
Action
Check method and/or SCDL.
144
ERROR: Cannot allocate type buffer of size size
Description
An internal error occurred when attempting to allocate output memory space for the indicated buffer type.
Action
Contact Oracle Technical Support.
146
ERROR: Cannot find view viewname
Description
During data transformation, the VIEW or VIEW32 file indicated could not be found or is invalid.
Action
Verify the VIEW/VIEW32 SCDL settings, or that the VIEW/VIEW32 environment variables are set.
147
ERROR: Cannot find view viewname
Description
During data transformation, the VIEW or VIEW32 file indicated could not be found or is invalid.
Action
Verify the VIEW/VIEW32 SCDL settings, or that the VIEW/VIEW32 environment variables are set.
148
ERROR: FLD_DECIMAL not supported for SALT SCA
Description
There is no SDO type equivalent to the Tuxedo-specific FLD_DECIMAL type. The corresponding field is ignored.
Action
No action required.
149
ERROR: Unknown view member type type
Description
An internal error occurred while processing a VIEW or VIEW32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
150
ERROR:SDO Runtime Exception
Description
An internal error occurred while processing a VIEW or VIEW32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
151
ERROR: Cannot get next field in FML32 or FML buffer: errormessage
Description
An internal error occurred while processing a FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
152
ERROR: Cannot get next field identifier identifier in FML32 or FML buffer: errormessage
Description
An internal error occurred while processing a FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
153
ERROR: Character data being converted to boolean is set to value instead of 'T' or 'F'
Description
An attempt to convert an element declared xsd:boolean has been performed during FML or FML32 to SDO data conversion. Valid values are 'T' or 'F'.
Action
Check you program to make sure that data is initialized properly.
154
ERROR: FLD_PTR is not supported in SALT SCA
Description
A field of type FLD_PTR has been encountered in an FML32 buffer while attempting to convert to SDO. This is currently not supported.
Action
Make sure that your program does not attempt to send FLD_PTR fields to an SCA client or server.
155
ERROR: Unknown field type type found in buffer
Description
A field of unknow type has been encountered during FML or FML32 to SDO conversion.
Action
Contact Oracle Technical Support.
156
ERROR: SDO Runtime Exception: exception
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
157
ERROR: Cannot find field id for field fieldname
Description
The field id necessary to perform SDO to FML or FML32 conversion has not been found.
Action
Make sure that the field tables and field table locations are correct either in SCDL or environment, and/or that the field table(s) is (are) valid.
See Also
ATMI binding element reference.
158
ERROR: Cannot determine length of FML or FML32 field fieldname
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
159
ERROR: Cannot get FML or FML32 field fieldname from buffer
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
160
ERROR: Cannot get FML32 field fieldname from buffer
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
161
ERROR: Containment fields not supported for 16-bit FML
Description
The Tuxedo FML buffer format does not support nesting, transformation of SDO objects containing other SDO objects is not supported in this context.
Action
Use the Tuxedo FML32 buffer type instead.
162
ERROR: DataObjectPtr only allowed in interfaces when using VIEW/X_COMMON/X_C_TYPE/VIEW32 Tuxedo buffer
Description
An attempt to use a type other than commonj::sdo::DataObjectPtr in conjunction with a VIEW/X_COMMON/X_C_TYPE/VIEW32 Tuxedo buffer has been made.
Action
Check the interface used, make sure the correct type is employed.
163
ERROR: Fnext or Fnext32 failed
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
164
ERROR: Could not find field name for field ID identifier. Verify the field tables configuration.
Description
The field name corresponding to the field identifier indicated could not be resolved.
Action
Make sure that the field tables and field table locations are correct either in SCDL or environment, and/or that the field table(s) is (are) valid.
See Also
ATMI binding element reference.
165
ERROR: Problem getting embedded FLD_VIEW32 buffer: errormessage
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
166
ERROR: Problem getting embedded FLD_FML32 field fieldname: errormessage
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
167
ERROR: FLD_PTR field type not supported for SALT SCA
Description
A field of type FLD_PTR has been encountered in an FML32 buffer while attempting to convert to SDO. This is currently not supported.
Action
Make sure that your program does not attempt to send FLD_PTR fields to an SCA client or server.
168
ERROR: Field type type not supported for SALT SCA
Description
An internal error occurred while processing an FML or FML32 buffer in SCA data transformation.
Action
Contact Oracle Technical Support.
169
ERROR: No type schemas defined for complex input type in SCA mode. Check configuration. errormessage
Description
In SCA to SCA communications, complex data must be described using XML schemas.
Action
Make sure schemas for complex types are present in the component or client location, and that they are valid.
See Also
SALT SCA Programming Guide.
170
ERROR: No type schemas defined for complex input type type. Check configuration. errormessage
Description
In SCA to SCA communications, complex data must be described using XML schemas. The input type indicated is not described by a schema.
Action
Make sure schemas for complex types are present in the component or client location, and that they are valid.
See Also
SALT SCA Programming Guide.
171
ERROR: Cannot find occurrence occurrence of field identifier in buffer
Description
An interface with a series of individual parameters has been used, but a discrepancy between data sent and data received has been detected.
Action
Verify that the client and component interfaces match.
173
ERROR: Occurrence occurrence of character field identifier being converted to bool has value value which is not 'T' or 'F'
Description
During the FML or FML32 to series of parameter conversion, a FLD_CHAR element has been detected with a value incompatible with the destination parameter.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
174
ERROR: Field identifier of type FLD_SHORT has signature type instead of expected signature short or unsigned short
Description
An incorrect FML or FML32 type has been encountered for the indicated method signature.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
175
ERROR: Field identifier of type FLD_LONG has value value which is outside the range of signature unsigned int
Description
A potential overflow has been detected when converting an FML or FML32 buffer to a series of parameters.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
176
ERROR: Field identifier of type FLD_LONG has value value which is outside the range of signature int
Description
A potential overflow has been detected when converting an FML or FML32 buffer to a series of parameters.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
177
ERROR: Field identifier of type FLD_LONG has signature type instead of expected signature long, unsigned long, int, unsigned int, long long, or unsigned long long
Description
An incorrect FML or FML32 type has been encountered for the indicated method signature.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
178
ERROR: Field identifier of type FLD_FLOAT has signature type instead of expected signature float
Description
An incorrect FML or FML32 type has been encountered for the indicated method signature.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
179
ERROR: Field identifier of type FLD_DOUBLE has signature type, which is not mapped to double or long double
Description
An incorrect FML or FML32 type has been encountered for the indicated method signature.
Action
Check the sending program if running in ATMI to SCA mode, or make sure the client and component use the same interface if running in SCA to SCA mode.
180
ERROR: No type schemas defined for complex return type in SCA mode. Check configuration. errormessage
Description
In SCA to SCA communications, complex data must be described using XML schemas.
Action
Make sure schemas for complex types are present in the component or client location, and that they are valid.
181
ERROR: No type schema defined for complex return type type. Check configuration. errormessage
Description
In SCA to SCA communications, complex data must be described using XML schemas.
Action
Make sure schemas for complex types are present in the component or client location, and that they are valid.
182
ERROR: Fnext operation failed during dynamic construction of SDO type
Description
An internal error occurred while attempting to allocate space for a STRING type buffer.
Action
Contact Oracle Technical Support.
183
ERROR: Field type FLD_PTR not supported for SALT SCA
Description
A field of type FLD_PTR has been encountered in an FML32 buffer while attempting to convert to SDO. This is currently not supported.
Action
Make sure that your program does not attempt to send FLD_PTR fields to an SCA client or server.
184
ERROR: Field type type not supported for SALT SCA
Description
An internal error occurred while attempting to allocate space for a STRING type buffer.
Action
Contact Oracle Technical Support.
185
ERROR: Cannot find field TUX_RTNLONG in buffer
Description
The service method used returns a long or unsigned long value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
186
ERROR: Cannot find field TUX_RTNLONG in buffer
Description
The service method used returns a long long value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
187
ERROR: Cannot find field TUX_RTNLONG in buffer
Description
The service method used returns a unsigned long long value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
188
ERROR: Cannot find field TUX_RTNLONG in buffer
Description
The service method used returns a int value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
189
ERROR: Cannot find field TUX_RTNLONG in buffer
Description
The service method used returns a unsigned int value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
190
ERROR: Cannot find field TUX_RTNSHORT in buffer
Description
The service method used returns a short value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
191
ERROR: Cannot find field TUX_RTNFLOAT in buffer
Description
The service method used returns a float value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
192
ERROR: Cannot find field TUX_RTNDOUBLE in buffer
Description
The service method used returns a double value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
193
ERROR: Cannot find field TUX_RTNDOUBLE in buffer
Description
The service method used returns a long double value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
194
ERROR: Cannot find field TUX_RTNCHAR in buffer
Description
The service method used returns a char value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
195
ERROR: Cannot find field TUX_RTNCHAR in buffer
Description
The service method used returns a bool value, but the ATMI binding could not find a corresponding type in the returned buffer.
Action
Verify the program interface.
See Also
SALT SCA Programming Guide.
196
ERROR: Character data being converted to boolean is set to 'value' instead of 'T' or 'F'
Description
The service method used returns a bool value, but the ATMI binding found invalid data in the returned buffer.
Action
Verify the sending program or interface used.
See Also
SALT SCA Programming Guide.
198
ERROR: View Buffer is NULL
Description
The VIEW or VIEW32 buffer returned to an SCA client is empty or invalid.
Action
Check that the server or SCA component program is returning correct data.
 |
 |
 |