|
|
|
|
|
|
3200 |
ERROR: Unable to obtain remote services information from shared memory | |
|
|
Description |
Shared memory information for the remote service was not available. Severe shared memory error. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3201 |
ERROR: Unable to obtain remote services information from shared memory | |
|
|
Description |
Shared memory information for the remote service was not available. Severe shared memory error. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3203 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3204 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3205 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3206 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3207 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3208 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3209 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3210 |
ERROR: Unable to obtain remote services information from shared memory | |
|
|
Description |
Shared memory information for the remote service was not available. Severe shared memory error. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3211 |
ERROR: BEA TOP END routing error (TP_SERVICE) for BEA TUXEDO client request | |
|
|
Description |
The service to be accessed by the BEA TUXEDO client was not active on the BEA TOP END node at the time of the request. |
|
Action |
Start all necessary BEA TOP END server processes on the desired nodes and retry the request. | |
|
3212 |
ERROR: Invalid input buffer | |
|
|
Description |
Could not retrieve the BEA TUXEDO system headers from the BEA TUXEDO client request message. The message may be corrupted. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3213 |
ERROR: Invalid input buffer | |
|
|
Description |
Could not retrieve the BEA TUXEDO system headers from the message. The message may be corrupted. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3214 |
ERROR: Invalid input buffer | |
|
|
Description |
Could not retrieve the BEA TUXEDO system headers from the BEA TUXEDO response message. The message may be corrupted. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3215 |
ERROR: COMPOS_HDR or COMPOS_FML TCMs is missing in the BEA TUXEDO client request message | |
|
|
Description |
Could not retrieve the BEA TUXEDO system headers ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3216 |
ERROR: COMPOS_HDR or COMPOS_FML TCMs is missing in the BEA TUXEDO reply message | |
|
|
Description |
Could not retrieve the BEA TUXEDO system headers ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3217 |
ERROR: Failed to get field val from message | |
|
|
Description |
The TOP END Domain Gateway could not retrieve the /Q related parameter from the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3218 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
|
Description |
The TOP END Domain Gateway could not add the /Q related parameter to the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3219 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
|
Description |
The TOP END Domain Gateway could not add the /Q related parameter to the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3220 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
|
Description |
The TOP END Domain Gateway could not add the /Q related parameter to the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3221 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
|
Description |
The TOP END Domain Gateway could not add the /Q related parameter to the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3222 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
|
Description |
The TOP END Domain Gateway could not add the /Q related parameter to the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3223 |
ERROR: Invalid /Q request | |
|
|
Description |
An invalid or unsupported |
|
Action |
Modify your BEA TUXEDO client application to specify valid /Q | |
|
See Also |
Programming a BEA TUXEDO Application Using C
| |
|
3224 |
ERROR: Invalid /Q request | |
|
|
Description |
An invalid hour value (greater than 24) is specified in the /Q |
|
Action |
Modify your BEA TUXEDO client application to specify valid schedule time. | |
|
See Also |
Programming a BEA TUXEDO Application Using C
| |
|
3225 |
ERROR: Failed to get val field from message | |
|
|
Description |
The TOP END Domain Gateway could not retrieve the /Q related parameter from the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3226 |
ERROR: Failed to get val field from message | |
|
|
Description |
The TOP END Domain Gateway could not retrieve the /Q related parameter from the message ( |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3227 |
ERROR: Received RTQ response message with incorrect length | |
|
|
Description |
The length of the response the TOP END Domain Gateway received from the BEA TOP END RTQ server for the BEA TUXEDO client /Q request was not correct. The message may be corrupted. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3228 |
ERROR: Invalid transaction key (>0) specified in the RTQ request message | |
|
|
Description |
Unsupported parameter, transaction key was specified in the BEA TOP END RTQ request. |
|
Action |
Modify your BEA TOP END RTQ client application so that unsupported parameters and features are not used. | |
|
See Also |
BEA TOP END Recoverable Transaction Queuing Guide | |
|
3229 |
ERROR: Invalid schedule time parameter specified in the RTQ request message | |
|
|
Description |
An invalid value for the schedule time parameter was specified in the BEA TOP END RTQ request. |
|
Action |
Modify your BEA TOP END RTQ client application to use proper values of the supported parameters. | |
|
See Also |
BEA TOP END Recoverable Transaction Queuing Guide | |
|
3230 |
ERROR: Invalid buffer type | |
|
|
Description |
The incoming BEA TOP END message was not in FML32 format. However, the expected incoming buffer type was specified as FML32. The request was dropped. |
|
Action |
Modify the | |
|
See Also |
| |
|
3231 |
ERROR: _tmfmsg_create() failed to create the message | |
|
|
Description |
An attempt to allocate a NULL buffer for internal use failed. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3232 |
ERROR: alldata is null | |
|
|
Description |
Could not find the remote node specific structure. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3233 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3234 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3235 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3236 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3237 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3238 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3239 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3240 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3241 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3242 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3243 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3244 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3245 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3246 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3247 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3248 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3249 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3250 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3251 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3252 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3253 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3254 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3255 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3256 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3257 |
ERROR: DIF dialogue had invalid type | |
|
|
Description |
The message sent to the BEA TOP END system appears to be malformed. Response to the BEA TOP END system dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3258 |
ERROR: Invalid dialogue request type | |
|
|
Description |
The message sent to the BEA TOP END system appears to be malformed. Response to the BEA TOP END system dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3259 |
ERROR: alldata is null | |
|
|
Description |
Could not find the remote node specific structure. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3260 |
ERROR: alldata is null | |
|
|
Description |
Could not find the remote node specific structure. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3261 |
ERROR: alldata is null | |
|
|
Description |
Could not find the remote node specific structure. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3262 |
ERROR: Memory allocation error | |
|
|
Description |
An attempt to allocate memory dynamically from the operating system failed. |
|
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
|
3263 |
ERROR: Received out-of-range nct_event. | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3264 |
ERROR: Action data incorrect - null context | |
|
|
Description |
An internal gateway context structure could not be found while generating a BEA TOP END NI protocol response message. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3265 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3266 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3267 |
ERROR: Called with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3268 |
ERROR: Called with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3269 |
ERROR: HNI outgoing format ready message translation invoked with illegal nct_event | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
3270 |
ERROR: HNI outgoing format ready messaged invoked with illegal record type | |
|
|
Description |
A TOP END Domain Gateway internal error has occurred. The message being processed was dropped. |
|
Action |
Contact your BEA TUXEDO System Customer Support. | |
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|