|
|
3001 |
ERROR: Link connection cannot be made | |
|
Description |
An attempt to establish a connection with the BEA TOP END system has failed. The BEA TUXEDO request could not be completed. See surrounding messages for more information as to the cause of the connection failure. |
Action |
Determine the cause of the connection failure and take the recommended action. | |
3002 |
ERROR: Could not suspend action | |
|
Description |
An internal error occurred that inhibited the ability to suspend an action. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3003 |
ERROR: Invalid input buffer | |
|
Description |
Could not retrieve the BEA TUXEDO system headers from the BEA TUXEDO client request message. This error may have been caused by a corrupted message. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3004 |
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. | |
3005 |
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. | |
3006 |
ERROR: Invalid request: either not a SERVICE type entry or CONV = 1 | |
|
Description |
The TOP END Domain Gateway was expecting a |
Action |
Check the BEA TUXEDO client application to make sure that the correct service name is specified. Also, verify that the | |
See Also |
| |
3007 |
ERROR: Unsupported user data type | |
|
Description |
The buffer type of the BEA TUXEDO user message is not supported. Only |
Action |
Modify the BEA TUXEDO application to ensure only supported buffer types are sent. | |
3008 |
ERROR: User buffer type does not match the configured data type | |
|
Description |
The buffer type of the user message does not match the buffer type configured for the requested service. |
Action |
Modify the BEA TUXEDO application to send only the configured buffer types. | |
See Also |
Programming a BEA TUXEDO Application Using C
| |
3009 |
ERROR: User buffer length(val) is > max_buf_size(val) | |
|
Description |
The buffer length of the message val exceeds the value of the limit max_buf_size supported by the TOP END Domain Gateway. The TEDG supports messages up to a length of 30K (30X1024) for request/response type messages and up to 30,000 for /Q to RTQ requests. |
Action |
Modify the user application so that message buffers are not sent that exceed the maximums supported by the TEDG. | |
See Also |
Using the BEA TUXEDO TOP END Domain Gateway | |
3010 |
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. | |
3011 |
ERROR: XDR conversion failed for outgoing message | |
|
Description |
XDR encoding of the user data failed for an outgoing message. The error was probably caused by data corruption. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3012 |
ERROR: No more free system dialogue ids available | |
|
Description |
Could not allocate a BEA TOP END system dialog ID for a BEA TUXEDO client request. This problem can occur when there is a significant amount of concurrent dialogs established between the BEA TUXEDO client and the BEA TOP END system nodes, exhausting all the free dialog ids (max: 2e32). |
Action |
Wait for a dialog to become available and resubmit the request, or shut down some of your BEA TUXEDO and BEA TOP END applications. | |
3013 |
ERROR: alldata is null | |
|
Description |
Could not find the remote node specific structure. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3014 |
ERROR: Stale message received from the BEA TOP END system | |
|
Description |
A stale message was received. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3015 |
ERROR: RESET or ABORT_ORDER received for the TPNOREPLY request | |
|
Description |
THE BEA TOP END system generated a |
Action |
Gather more error information on the BEA TOP END node and contact your BEA TUXEDO System Customer Support. | |
3016 |
ERROR: RESET or ABORT_ORDER received for the BEA TUXEDO client request | |
|
Description |
THE BEA TOP END system generated a |
Action |
Gather more error information on the BEA TOP END node and contact your BEA TUXEDO System Customer Support. | |
3017 |
ERROR: BEA TOP END Routing error (TP_SERVICE) for the BEA TUXEDO client TPNOREPLY 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. | |
3018 |
WARN: Dropping LMA attachment | |
|
Description |
A BEA TOP END server application was attempting to send a response message with Large Message Architecture (LMA) attachment data. However, the TOP END Domain Gateway does not support LMA. The attachment information was dropped. |
Action |
Modify the BEA TOP END server application to eliminate use of the LMA feature. | |
See Also |
BEA TOP END Application Programmer's Guide
| |
3019 |
WARN: Ignoring Output format | |
|
Description |
A BEA TOP END server application was attempting to send a service response with format information. However, the TOP END Domain Gateway does not support formats. The format information was ignored. |
Action |
Modify the BEA TOP END server application to eliminate use of the format feature. | |
See Also |
BEA TOP END Application Programmer's Guide | |
3020 |
ERROR: Received unexpected status from the BEA TOP END system | |
|
Description |
The BEA TOP END server reported a bad status on a service request. The error condition was reported to the BEA TUXEDO client. |
Action |
Examine the BEA TOP END logs for possible information as to the cause of the service failure. | |
3021 |
ERROR: TP_APPL_CONTEXT flag set in the BEA TOP END response for a SERVICE request | |
|
Description |
A BEA TOP END server application responded with the |
Action |
If conversational behavior is desired, modify the | |
See Also |
| |
3022 |
ERROR: Invalid request: not a QSPACE type entry | |
|
Description |
The service entry associated with a BEA TUXEDO /Q enqueue request is not a |
Action |
Check the value of the | |
See Also |
| |
3023 |
ERROR: Invalid /Q request | |
|
Description |
The TOP END Domain Gateway received a request other than |
Action |
Modify your BEA TUXEDO /Q client application so that only | |
See Also |
| |
3024 |
ERROR: Failed to get val field from message | |
|
Description |
This error is generated when the TOP END Domain Gateway can not retrieve the /Q related parameter from the message (val = |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3025 |
ERROR: Bad QNAME specified in the /Q request | |
|
Description |
The TOP END Domain Gateway did not find a matching |
Action |
Check your BEA TUXEDO /Q client application or the TOP END Domain Gateway | |
See Also |
| |
3026 |
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. | |
3027 |
ERROR: Failed to add fields to COMPOS_FML buffer | |
|
Description |
The TOP END Domain Gateway failed to build the /Q response buffer. This is a gateway internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3028 |
ERROR: _tmfmsg_cleate() failed to create the message | |
|
Description |
The TOP END Domain Gateway failed to create the /Q message. This is a gateway internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3029 |
ERROR: Failed to attach the COMPOS_FML or COMPOS_HDR TCMs in the message | |
|
Description |
The TOP END Domain Gateway failed to build the /Q message. This is a gateway internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3030 |
ERROR: Invalid RTQ request message length | |
|
Description |
The RTQ request received from the BEA TOP END client has an incorrect length for the RTQ header. This is BEA TOP END internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3031 |
ERROR: No RTQ header and user data present in the message | |
|
Description |
The RTQ request received from the BEA TOP END client is missing the RTQ header. This is a gateway internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3032 |
ERROR: Version incompatibility between TEDG and RTQ library | |
|
Description |
The internal version of the RTQ request received from the BEA TOP END system is different from the version supported by the TOP END Domain Gateway. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3033 |
ERROR: Invalid parameter, req_info.flags = flags, specified in the RTQ request message | |
|
Description |
The invalid flags parameter is specified in the RTQ request message from the BEA TOP END system. |
Action |
Check the TOP END Domain Gateway documentation to determine the supported parameters and correct your BEA TOP END client application so that it does not send improper or invalid parameters. | |
See Also |
BEA TOP END Application Programmer's Guide
| |
3034 |
WARN: Ignoring the Tag text specified in the RTQ request message | |
|
Description |
The TOP END Domain Gateway does not support the RTQ tag text parameter and ignores any tag text specified in the RTQ request message via the |
Action |
Correct your BEA TOP END RTQ client application so that the tag text is not sent in the | |
See Also |
BEA TOP END Recoverable Transaction Queuing Guide
| |
3035 |
WARN: RTQ request received with input format, ignoring input format | |
|
Description |
The TOP END Domain Gateway does not support BEA TOP END screen formats and ignores any input format specified in the RTQ request message via the |
Action |
Correct your BEA TOP END RTQ client application so that the input format is not sent in the | |
See Also |
BEA TOP END Recoverable Transaction Queuing Guide
| |
3036 |
ERROR: Unable to find local service in shared memory | |
|
Description |
Shared memory information for the local service was not available. Severe shared memory error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3037 |
ERROR: Matching QNAME not found for RTQ request in the LSVC table | |
|
Description |
There is no matching |
Action |
Check your BEA TOP END RTQ client application for the | |
See Also |
| |
3038 |
ERROR: _fencdec32() failed to decode a FML32 buffer | |
|
Description |
The TOP END Domain Gateway failed to perform the XDR conversion on the received buffer. This is a gatway internal error. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3039 |
ERROR: time() returned -1 | |
|
Description |
An operating system error caused the system call to fail. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3040 |
ERROR: localtime() returned -1 | |
|
Description |
An operating system error caused the system call to fail. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3060 |
ERROR: Called with illegal nct_event | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3061 |
ERROR: Called with illegal record type | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3062 |
ERROR: DIF dialogue had invalid type | |
|
Description |
The message from the BEA TOP END system appears to be malformed. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3063 |
ERROR: Invalid dialogue request type | |
|
Description |
The message from the BEA TOP END appears to be malformed. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3070 |
ERROR: No action function was found for an HNI event! | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3071 |
ERROR: Received out-of-range nct_event. | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3072 |
ERROR: Received out-of-range priority. | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3073 |
ERROR: Event list does not exist. | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. | |
3091 |
ERROR: _gw_nw_response_from_te_tx failed | |
|
Description |
A TOP END Domain Gateway internal error has occurred. The dialog with the BEA TOP END system was reset. |
Action |
Contact your BEA TUXEDO System Customer Support. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|