|
|
A BLOCKING timeout has occurred on an outbound request
|
| |
|
A blocking time out has occurred on a request to the host.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Check configuration and increase the BLOCKTIME value, if needed.
|
|
|
|
| |
|
An internal error has been detected processing the action.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_acall has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_connect has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot open SNA connection
|
| |
|
Unable to allocate a network context. gw_nw_AllocNwCtx failed.
|
| |
|
See previously printed ULOG message for cause.
|
|
|
Initialization of environment failed
|
| |
|
Unable to initialize the conversation environment.
|
| |
|
See previously printed ULOG message for cause.
|
|
|
|
| |
|
An internal error has been detected processing the action.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_convsend has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_disconnect has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to send data on sna_conv_idx <number>.
|
| |
|
A network error has occurred while processing a send to the CRM. gw_nw_convsend failed.
|
| |
|
Determine if CRM is still active. Look for other ULOG messages that specify a reason for this failure.
|
|
|
External encode/decode service returned error: \n\tTUXEDO code (<number>) <text>
|
| |
|
A Tuxedo error has occurred in the Data Integration portion of the product.
|
| |
|
Use the Tuxedo error to resolve the Data Integration problem. If unable to resolve the problem, contact BEA Customer Support.
|
|
|
Cannot create external decode action!
|
| |
|
An internal error has occurred in the Data Integration portion of the product.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot create external encode action!
|
| |
|
An internal error has occurred in the Data Integration portion of the product.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_decode has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, gw_nw_encode has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Context data incorrect - null context index
|
| |
|
An internal error has been detected, gw_nw_decode has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Context data incorrect - null context index
|
| |
|
An internal error has been detected, gw_nw_encode has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot malloc sna structures
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot malloc remote domain structure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot malloc local SNA structure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to obtain local snadom information from shmem
|
| |
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot malloc remote service structure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot malloc remote SNA structure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Can't create listener for this GATEWAY
|
| |
|
An internal error has been detected, gw_nw_init was unable to create a listener.
|
| |
|
Contact BEA Customer Support.
|
|
|
NO SNA conversations waiting for startup
|
| |
|
No conversations are waiting at startup.
|
| |
|
No action needs to be taken.
|
|
|
Unable to set APPC_GATEWAY environment variable
|
| |
|
An internal error has been detected, _gp_get_nodename failed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure for RDOM table
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure for SNALINK table
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure for CRM table
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory Allocation Failure for SNASTACK table
|
| |
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to access SNALINK information from memory
|
| |
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to access CRM information from memory
|
| |
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to convert CRM network address for <text>
|
| |
|
An error has occurred while trying to contact the CRM during startup.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Probably due to a configuration problem.
|
|
|
Unable to access SNASTACK information from memory
|
| |
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to build internal network tables
|
| |
|
An internal error has been detected, gw_nw_build_nwtbls failed.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Probably due to a configuration problem.
|
|
|
Unable to connect to CRM <text>
|
| |
|
An error has occurred while trying to contact the CRM during startup.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Possible reasons are:
- The CRM server was not configured in the
UBBCONFIG.
- The
//host:port parameters as specified in the DMCONFIG and the CRM command line parameters in the UBBCONFIG do not agree
|
|
|
Unable to SIGNON to CRM <text>
|
| |
|
An error has occurred while signing on to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to send STACK <text> configuration to CRM <text>
|
| |
|
An error has occurred while sending the stack configuration to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to send SNALINK <text> configuration to CRM <text>
|
| |
|
An error has occurred while sending the link configuration to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to send START message to CRM <text>
|
| |
|
An error has occurred while sending the START command to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to send SHUTDOWN message to CRM <text>
|
| |
|
An error has occurred while sending the SHUTDOWN command to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
STATE ERROR occurred during initialization, SHUTTING DOWN
|
| |
|
An internal state error has occurred start up.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unknown message type received from CRM during initialization
|
| |
|
An unknown message has been received from CRM.
|
| |
|
Contact BEA Customer Support.
|
|
|
GATEWAY FAILS to complete connection to the CRM during initialization
|
| |
|
Connection to CRM is incomplete.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to send SHUTDOWN message to CRM <text>
|
| |
|
GWSNAX is unable to send the SHUTDOWN command to CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. The CRM process has probably already terminated.
|
|
|
Unable to access codepage table [<text>], reason=<text> (<number>)
|
| |
|
Tuxedo Mainframe Adapter for SNA Gateway is unable to find the file for the listed codepage for the reason specified. If reason is "Error 0", the (<number>) value is the return code from the codepage read routine.
3 - Can't allocate memory
11 - Unsupported format version
|
| |
|
Examine the DMCONFIG to determine if the CODEPAGE for a remote domain is specified incorrectly. Correct and retry.
|
|
|
Codepage for Remote Domain <Remote Domain Name> : Codepage
|
| |
|
Examine the ULOG for more information regarding the Codepage used for the remote domain.
|
| |
|
No action needs to be taken.
|
|
|
Unable to complete initialization with CRM
|
| |
|
Connection to CRM is incomplete.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to obtain new convid id for this request
|
| |
|
An internal error has been detected, gw_nw_getnxt_cd has returned a failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Action data incorrect - null action index
|
| |
|
An internal error has been detected in gw_nw_recv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to send data on sna_conv_idx <number>
|
| |
|
An error has occurred while sending reply data ( gw_nw_reply) to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_clr_convid.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_clr_convid.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_getnxt_cd.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to obtain remote domain info from shared memory
|
| |
|
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to obtain snadom info from rdom
|
| |
|
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot realloc sna structures
|
| |
|
An internal error has been detected, gw_nw_AllocNwCtx was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory allocation failure
|
| |
|
An internal error has been detected, gw_nw_empty_sndbuf was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
SECURITY: Unable to get remote username from shared memory using local principal name <text>
|
| |
|
A security error has occurred, the user is not authorized to access the remote host.
|
| |
|
Contact your local security administrator.
|
|
|
SECURITY: Unable to get local principal name from shared memory using appkey
|
| |
|
A security error has occurred, the user is not authorized to access the remote host.
|
| |
|
Contact your local security administrator.
|
|
|
SECURITY: Unable to extract password from shared memory
|
| |
|
A security error has occurred, the user is not authorized to access the remote host.
|
| |
|
Contact your local security administrator.
|
|
|
SECURITY: Unable to get security schedule
|
| |
|
A security error has occurred, the user is not authorized to access the remote host.
|
| |
|
Contact your local security administrator.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_mk_error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Context data incorrect - null context index for action <number>
|
| |
|
An internal error has been detected in gw_nw_mk_error.
|
| |
|
Contact BEA Customer Support.
|
|
|
SECURITY: Unable to get remote user from shared memory
|
| |
|
A security error has occurred, the remote user is not authorized to access the local Tuxedo host.
|
| |
|
Contact your local security administrator.
|
|
|
Too many unrecoverable errors occurred - deleting action
|
| |
|
An error has occurred in gw_nw_mk_error.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
SECURITY: Unable to get appkey for this outbound request
|
| |
|
A security error has occurred, the user is not authorized to access the remote host.
|
| |
|
Contact your local security administrator.
|
|
|
Deleting the action with the invalid context, <number>
|
| |
|
An internal error has been detected in gw_nw_snd failure.
|
| |
|
Contact BEA Customer Support.
|
|
|
Can't find transaction node for Network TMS event!
|
| |
|
An internal error has been detected in gw_nw_TranCommon.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
A severe error such as a protocol error or memory corruption has occurred and has already been logged. The GWSNAX process will shutdown.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unknown input transactional event(<number>)!
|
| |
|
An internal error has been detected in gw_nw_TranCvtMsgEvt2TranEvt.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input object pointer!
|
| |
|
An internal error has been detected in gw_nw_BindStateObject.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input object initial state!
|
| |
|
An internal error has been detected in gw_nw_BindStateObject.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input object type!
|
| |
|
An internal error has been detected in gw_nw_BindStateObject.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input state object event(<text>)!
|
| |
|
An internal error has been detected in gw_nw_StateObjectTestEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Event <text> is not allowed for state <text>!
|
| |
|
An internal error has been detected in gw_nw_StateObjectTestEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid object event test metric with value <number> for <text>!
|
| |
|
An internal error has been detected in gw_nw_StateObjectTestEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input trace object pointer!
|
| |
|
An internal error has been detected in gw_nw_InitEventTrace.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input trace object pointer!
|
| |
|
An internal error has been detected in gw_nw_AddEventTrace.
|
| |
|
Contact BEA Customer Support.
|
|
|
Input event <number> out of range <number>!
|
| |
|
An internal error has been detected in gw_nw_AddEventTrace.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input trace object pointer!
|
| |
|
An internal error has been detected in gw_nw_QueryEventTrace.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input trace object pointer!
|
| |
|
An internal error has been detected in gw_nw_PrintEventTrace.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input event identification(<number>)!
|
| |
|
An internal error has been detected in gw_nw_EventToString.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory allocation failure
|
| |
|
An internal error has been detected in gw_nw_CreateNodeTable.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transaction table already exists!
|
| |
|
An attempt has been made to create the node table and it already exists.
|
| |
|
No action needs to be taken.
|
|
|
Invalid input parameters!
|
| |
|
An internal error has been detected in gw_nw_AssociateTranByTXID.
|
| |
|
Contact BEA Customer Support.
|
|
|
Requires CRM id to create transaction!
|
| |
|
An internal error has been detected in gw_nw_AssociateTranByTXID.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot associate with network transaction!
|
| |
|
An internal error has been detected in gw_nw_AssociateTranByTXID.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction context!
|
| |
|
An internal error has been detected in gw_nw_AssociateTranByTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction event(<number>)!
|
| |
|
An internal error has been detected in gw_nw_AssociateTranByTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction context pointer!
|
| |
|
An internal error has been detected in gw_nw_TranCreateTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
Exceeded local transaction limit(<number>)!
|
| |
|
Number of concurrent transactions using this domain gateway exceeded the configured limit.
|
| |
|
Examine the DMCONFIG file for the MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then examine the ubbconfig file for the MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary.
|
|
|
Can not create shared memory nettxid!
|
| |
|
An internal error has been detected in gw_nw_TranCreateTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
Create transaction tree node failed!
|
| |
|
gw_nw_TranCreateTCTXT failed to create the transaction tree node object. This can be caused by reaching the configured transaction limit or by a memory allocation failure.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. If the cause is the limit being reached, update the configuration. If the cause is a memory allocation failure, update the system and/or the system configuration.
|
|
|
Invalid input transaction handle!
|
| |
|
An internal error has been detected in gw_nw_TranGetTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction handle!
|
| |
|
An internal error has been detected in gw_nw_TranGetTXID.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_TranProcessEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to calculate transaction handle!
|
| |
|
An internal error has been detected in gw_nw_TranProcessEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Input Gateway event not transactional!
|
| |
|
The service request inbound from a remote host is transactional but the Tuxedo Mainframe Adapter for SNA Gateway is not configured as a transactional gateway.
|
| |
|
The MAXSYNCLVL specified in the DMCONFIG must be 2 if transactional requests are to be processed.
|
|
|
Transaction does not exist!
|
| |
|
An internal error has been detected in gw_nw_TranProcessEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction handle!
|
| |
|
An internal error has been detected in gw_nw_TranProcessEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action identification!
|
| |
|
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Decoding input transaction message failed!
|
| |
|
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
CRM verb <number> is not for TMS event!
|
| |
|
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid input transaction context!
|
| |
|
An internal error has been detected in gw_nw_TranRelease.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transaction for context(<number>) not found!
|
| |
|
The specified context for the transaction to be released could not be found by gw_nw_TranRelease.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Cannot disassociate with network transaction!
|
| |
|
An error has been returned by gw_tx_end.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Cannot set remote domain for transaction!
|
| |
|
An error has been returned by gw_tx_set_rdom. Several possibilities exist for this failure.
- The process is unable to obtain the shared memory lock.
- The configured limit for the number of remote domains that can be involved in the same transaction has been reached. This limit is specified in the MAXRDTRAN in the
DMCONFIG.
|
| |
|
Examine the DMCONFIG and compare with the number of remote domains which might become involved in the same transaction. Update the DMCONFIG if necessary. Also examine the ULOG for more information concerning possible reasons for the failure.
|
|
|
Invalid input transaction handle!
|
| |
|
An internal error has been detected in gw_nw_TranGetNodePtr.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transaction handle not in use!
|
| |
|
An internal error has been detected in gw_nw_TranGetNodePtr.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transaction processing not yet initialize!
|
| |
|
An internal error has been detected in gw_nw_TranGetNodePtr.
|
| |
|
Contact BEA Customer Support.
|
|
|
Defined transaction limit <number> reached!
|
| |
|
The number of concurrent transactions using this domain gateway has exceeded the limit.
|
| |
|
Examine the DMCONFIG file for the MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then examine the ubbconfig file for the MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary.
|
|
|
Allocate CRM branch structure failed!
|
| |
|
An internal error has been detected in gw_nw__gw_nw_AllocateNode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to bind outbound node state object!
|
| |
|
A failure was returned by gw_nw_BindStateObject.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to bind inbound node state object!
|
| |
|
A failure was returned by gw_nw_BindStateObject.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to bind recover node state object!
|
| |
|
A failure was returned by gw_nw_BindStateObject.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Invalid event <text> to create transaction tree node!
|
| |
|
An internal error has been detected in _ gw_nw_AllocateNode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Memory allocation failure!
|
| |
|
An internal error has been detected in gw_nw_AllocBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Event(<text>) is not allowed to create CRM branch!
|
| |
|
An internal error has been detected in gw_nw_AllocBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Free more branch than transaction tree node has!
|
| |
|
An internal error has been detected in gw_nw_FreeBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Protocol violation, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_3.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_4.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_5.
|
| |
|
Contact BEA Customer Support.
|
|
|
Branch in a bad state(<text>) to issue prepare!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_5.
|
| |
|
Contact BEA Customer Support.
|
|
|
Inconsistent branch state for prepare(<number>, <number>)!
|
| |
|
The transaction branch is in an inconsistent state for issuing a prepare. It will be assumed that they are all prepared.
|
| |
|
No action needs to be taken.
|
|
|
Transaction node is deallocated because of ABEND!
|
| |
|
Informational message. Tuxedo Mainframe Adapter for SNA Gateway detected an ABEND condition or received an ABEND event from the CRM which caused the node object to be destroyed.
|
| |
|
No action needs to be taken.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_7.
|
| |
|
Contact BEA Customer Support.
|
|
|
Branch in a bad state(<text>) to issue prepare!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_7.
|
| |
|
Contact BEA Customer Support.
|
|
|
Inconsistent branch state for rollback(<number>, <number>)!
|
| |
|
The transaction branch was in an inconsistent state for issuing a rollback. It will be assumed that they are all rolled back.
|
| |
|
No action needs to be taken.
|
|
|
Inconsistent branch accounting for rollback(<number>, <number>, <number>)!
|
| |
|
The transaction branch accounting was inconsistent while issuing a rollback.
|
| |
|
No action needs to be taken.
|
|
|
Incorrect branch accounting for rollback(<number>)!
|
| |
|
The transaction branch accounting was incorrect while issuing a rollback.
|
| |
|
No action needs to be taken.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_8.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_9.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_10.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_11.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_12.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_13.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_14.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_15.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_Retired.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_16.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_17.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_18.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_19.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_20.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_21.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_22.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_23.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_24.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_25.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_26.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_27.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_28.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_29.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_30.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_31.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_32.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_33.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_39.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_40.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_42.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_43.
|
| |
|
Contact BEA Customer Support.
|
|
|
Encoding transaction message for verb(<number>) failed!
|
| |
|
A failure was returned by CRM_tx_msg.
|
| |
|
Contact BEA Customer Support.
|
|
|
CRM(<number>) in bad state(<text>) to issue verb(<number>)!
|
| |
|
An internal error has been detected in gw_nw_NodeSendToBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Send verb <number> to CRM failed!
|
| |
|
A failure has been detected while sending the specified verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
Encoding transactional message for verb(<number>) failed!
|
| |
|
A failure was returned by CRM_tx_msg.
|
| |
|
Contact BEA Customer Support.
|
|
|
CRM(<number>) in bad state(<text>) to issue verb(<number>)!
|
| |
|
An internal error has been detected in gw_nw_NodeSendToSubordinate.
|
| |
|
Contact BEA Customer Support.
|
|
|
Send verb(<number>) to CRM failed!
|
| |
|
A failure has been detected while sending the specified verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
Encoding transactional message for verb(<number>) failed!
|
| |
|
A failure was returned by CRM_tx_msg.
|
| |
|
Contact BEA Customer Support.
|
|
|
CRM(<number>) in bad state(<text>) to issue verb(<number>)!
|
| |
|
An internal error has been detected in gw_nw_NodeSendToSubordinate.
|
| |
|
Contact BEA Customer Support.
|
|
|
Send verb(<number>) to CRM failed!
|
| |
|
A failure has been detected while sending the specified verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
Protocol violation, branch id[<number>] at state(<text>) receive event(<text>)!
|
| |
|
An internal error has been detected in gw_nw_BranchMethod_1.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected in gw_nw_TranRestart.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to get shared memory semaphore lock!
|
| |
|
An internal error has been detected in gw_nw_TranRestart.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to find transaction on GTT!
|
| |
|
An internal error has been detected in gw_nw_TranRestart.
|
| |
|
Contact BEA Customer Support.
|
|
|
SNAX group is not participating the transaction!
|
| |
|
An internal error has been detected in gw_nw_TranRestart.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to setup transaction recovery!
|
| |
|
A failure was returned by gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to setup transaction recovery!
|
| |
|
A failure was returned by gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to create recovery action!
|
| |
|
A failure was returned by gw_new_action.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to create recovery action!
|
| |
|
A failure was returned by gw_chld_action.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to setup transaction recovery!
|
| |
|
A failure was returned by gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to create recovery action!
|
| |
|
A failure was returned by gw_new_action.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to create recovery action!
|
| |
|
A failure was returned by gw_chld_action.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to setup transaction recovery!
|
| |
|
A failure was returned by gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to setup transaction recovery!
|
| |
|
A failure was returned by gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to release shared memory lock!
|
| |
|
A failure was returned by _ gw_shmunlock.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to find CRM for superior remote domain(<text>)!
|
| |
|
Failed to find the remote domain definition in the configuration in order to get the CRM identification.
|
| |
|
Examine the DMCONFIG for changes between the boots that would modify or remove the remote definition. If no such change has occurred, contact BEA Customer Support.
|
|
|
Could not find Remote Domain(<text>) to do recovery!
|
| |
|
An internal error has been detected in gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Could not find Remote Domain to do recovery!
|
| |
|
An internal error has been detected in gw_nw_TranRecover.
|
| |
|
Contact BEA Customer Support.
|
|
|
Could not create transaction tree structure!
|
| |
|
Unable to allocate a transaction tree node structure to represent the transaction recovery object.
|
| |
|
Examine the configuration to determine if there has been a change of MAXTRAN in DMCONFIG and/or a change of MAXGTT in UBBCONFIG. This condition may occur if there is a decrease in the number of transactions allowed between boots while many transactions must be recovered. If no changes have been made, contact BEA Customer Support.
|
|
|
Unable to create CRM branch structure!
|
| |
|
A failure was returned by _ gw_nw_AllocBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to create CRM branch structure!
|
| |
|
A failure was returned by _ gw_nw_AllocBranch.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_44.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_45.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Gateway action, receive event(<text>) at state(<text>)!
|
| |
|
An internal error has been detected in gw_nw_NodeMethod_46.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid transaction context(<number>) from CRM!
|
| |
|
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Undefined instrumentation register <number> specification, ignored!
|
| |
|
An internal error has been detected in gw_nw_SetUpInstrumentation.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
The Tuxedo Mainframe Adapter for SNA Gateway process has successfully started the Gateway connection to the CRM process.
|
| |
|
No action needs to be taken.
|
|
|
CRM Link <text> Inoperable
|
| |
|
The specified link did not start up correctly.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
INVALID STARTTYPE (<text>) - calling shutdown
|
| |
|
The STARTTYPE specified in the DMCONFIG must be AUTO or COLD.
|
| |
|
Correct the value specified in the DMCONFIG and restart.
|
|
|
Unable to find remote service definition link
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to find local service definition link
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Buffer type (<text>,<text>) not defined in the buffer type switch!
|
| |
|
The buffer type associated with the inbound message is not specified in the type switch.
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. Tuxedo Mainframe Adapter for SNA Gateway only supports standard Tuxedo buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEW32DIR, or VIEW32FILES.
|
|
|
Failed to tpalloc() STRING buffer of size <number>
|
| |
|
No buffer of type STRING was returned by tpalloc for the size specified.
|
| |
|
If the size specified is 1, then a length of zero was received. Check the application to determine if it has an error, otherwise contact BEA Customer Support.
|
|
|
Failed to tpalloc() CARRAY/X_OCTET buffer of size <number>
|
| |
|
No buffer of type CARRAY or X_OCTET was returned by tpalloc for the size specified.
|
| |
|
If the size specified is 1, then a length of zero was received. Check the application to determine if it has an error, otherwise contact BEA Customer Support.
|
|
|
Input buffer too big (<number>)!
|
| |
|
The buffer received of the size specified, exceeded the maximum allowed of 32767.
|
| |
|
Check the application to determine if it has an error, otherwise contact BEA Customer Support.
|
|
|
Missing subtype specification for <text>
|
| |
|
The buffer type specified of VIEW, VIEW32, X_C_TYPE, or X_COMMON requires that a subtype be specified.
|
| |
|
Examine the application and the DMCONFIG and correct the problem.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert buffer type(<text>,<text>) failed, convert failure!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Convert buffer type(<text>,<text>) failed, length too big!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful due to the resulting size exceeding the maximum of 32767.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Failed to tpalloc() buffer (<text>,<text>) of size <number>
|
| |
|
No buffer was returned by tpalloc for the size specified to hold the converted buffer data.
|
| |
|
Examine the application to determine if it has an error, otherwise contact BEA Customer Support.
|
|
|
Missing subtype for FML type buffer!
|
| |
|
The buffer type specified of FML requires that a subtype be specified.
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. Tuxedo Mainframe Adapter for SNA Gateway only supports standard Tuxedo buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEW32DIR, or VIEW32FILES.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Malloc failed, unable to convert!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Failed to malloc temporary buffer of size <number>
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert buffer type(<text>,<text>) failed, convert failure!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any mistakes in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Failed to tpalloc() buffer (<text>,<text>) of size <number>
|
| |
|
No buffer was returned by tpalloc for the size specified to hold the converted buffer data.
|
| |
|
Check the application to determine if it has an error, otherwise contact BEA Customer Support.
|
|
|
Missing subtype definition for FML32 buffer type!
|
| |
|
The buffer type specified of FML32 requires that a subtype be specified.
|
| |
|
Correct the DMCONFIG definition.
|
|
|
Malloc temporary of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML32 buffer type(<text>,<text>) failed, convert failure!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML32 buffer with subtype(<text>) failed!
|
| |
|
The conversion of the buffer received from the remote host was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Failed to tpalloc() FML32 buffer of size <number> for <text>!
|
| |
|
An internal error has been detected in gw_nw_decode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Fail to convert for FML buffer(<text>), exceeding limit!
|
| |
|
Failed to convert the FML buffer; the buffer size required to process the conversion exceeds the limit.
|
| |
|
Examine the application and the view for this buffer for any errors. If no errors are found, contact BEA Customer Support.
|
|
|
Fail to convert for FML32 buffer(<text>), exceeding limit!
|
| |
|
Failed to convert the FML32 buffer; the buffer size required to process the conversion exceeds the limit.
|
| |
|
Examine the application and the view for this buffer for any errors. If no errors are found, contact BEA Customer Support.
|
|
|
Fail to retrieve remote service definition!
|
| |
|
Unable to find the remote service definition in shared memory.
|
| |
|
Examine the DMCONFIG remote service definitions. Correct any errors found. If no error is found, contact BEA Customer Support.
|
|
|
Fail to retrieve local service definition!
|
| |
|
Unable to find the local service definition in shared memory.
|
| |
|
Examine the DMCONFIG local service definitions. Correct any errors found. If no error is found, contact BEA Customer Support.
|
|
|
Must specify subtype for <text>
|
| |
|
The buffer type specified of VIEW, VIEW32, X_C_TYPE, or X_COMMON requires that a subtype be specified.
|
| |
|
Correct any errors in the DMCONFIG buffer type definitions. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert buffer type <text> with subtype <text> failed(rc=<number>)!
|
| |
|
The conversion of the buffer received from Tuxedo was unsuccessful.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Convert buffer type <text> with subtype <text> failed(rc=<number>)!
|
| |
|
The conversion of the buffer received from Tuxedo was unsuccessful due to the resulting size exceeding the maximum of 32767.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
FML buffer type requires subtype to be specified!
|
| |
|
The buffer type specified of FML requires that a subtype be specified.
|
| |
|
Correct the DMCONFIG definition.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML buffer with subtype <text> failed(Ferror=<number>)!
|
| |
|
The conversion of the FML buffer received from Tuxedo was unsuccessfulErrorerror is the return code from the FML conversion routine.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML buffer with subtype <text> failed(Ferror=<number>)!
|
| |
|
The conversion of the FML buffer received from Tuxedo was unsuccessful. Ferror is the return code from the FML conversion routine.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc buffer of size(<number>) failed!
|
| |
|
An internal error has been detected in gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
FML32 buffer type requires subtype to be specified!
|
| |
|
The buffer type specified of FML32 requires that a subtype be specified.
|
| |
|
Correct the DMCONFIG definition.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML32 buffer with subtype <text> failed(Ferror=<number>)!
|
| |
|
The conversion of the FML32 buffer received from Tuxedo was unsuccessful. Ferror is the return code from the FML conversion routine.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
Malloc temporary buffer of size(<number>) failed!
|
| |
|
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Convert FML32 buffer with subtype <text> failed(Ferror=<number>)!
|
| |
|
The conversion of the FML32 buffer received from Tuxedo was unsuccessful. Ferror is the return code from the FML conversion routine.
|
| |
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact BEA Customer Support.
|
|
|
GP_SEND flow controlled for GPND <number>
|
| |
|
An internal error has been detected, gw_nw_proto_flow has detected a flow control callback from gp_send.
|
| |
|
Contact BEA Customer Support.
|
|
|
Maximum number of pointers exceeded
|
| |
|
An internal error has been detected. The maximum number of pointers has exceeded 500.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to format CRM_acall
|
| |
|
An internal error has been detected, CRM_acall has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to send data on sna_conv_idx <number>, gpnd = <number>
|
| |
|
An error has occurred while sending acall data ( gw_nw_acall) to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to format CRM_connect
|
| |
|
An internal error has been detected, CRM_connect has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to send data on sna_conv_idx <number>, gpnd = <number>
|
| |
|
An error has occurred while sending connect data ( gw_nw_connect) to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Unable to format CRM_send_data
|
| |
|
An internal error has been detected, CRM_send has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to format CRM_connect
|
| |
|
An internal error has been detected, CRM_connect_rsp has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Send event for RRCORR(<number>) failed!
|
| |
|
An internal error has been detected, gw_nw_SendEvent has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
Encode ACALL_RSP failed, RRCORR(<number>)!
|
| |
|
An internal error has been detected, CRM_acall_rsp has returned an error.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An error was detected while attempting to encode the reply message data destined for the remote host.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Invalid network descriptor(<number>)!
|
| |
|
The network descriptor this context is invalid.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Could not get transaction
|
| |
|
Failed to associate a transactional ACALL service request to a transaction object. The most likely reasons for this failure are:
- The locally configured limit has been exceeded, or
- Memory allocation has failed to create the transaction object.
|
| |
|
Determine if the application is licensed to do transactions. Examine the DMCONFIG file for the MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then examine the ubbconfig file for the MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary. Verify that the remote domain MAXSYNCLVL is set to 2.
|
|
|
|
| |
|
An internal error has been detected. The API information is invalid.
|
| |
|
Contact BEA Customer Support.
|
|
|
Could not get transaction
|
| |
|
Failed to associate a transactional CONNECT service request to a transaction object. The most likely reasons for this failure are:
- The locally configured limit has been exceeded, or
- Memory allocation has failed to create the transaction object
|
| |
|
Determine if the application is licensed to do transactions. Examine the DMCONFIG file for the MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then examine the ubbconfig file for the MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary. Verify that the remote domain MAXSYNCLVL is set to 2.
|
|
|
|
| |
|
An internal error has been detected. The API information is invalid.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected. The API information is invalid.
|
| |
|
Contact BEA Customer Support.
|
|
|
Protocol violation, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Link status down for remote domain <text>
|
| |
|
The link status returned by the CRM is LINK_DOWN.
|
| |
|
Determine if the stack is active and check that the session between the stack provider and the remote host is active.
|
|
|
Link status pending for remote domain <text>
|
| |
|
The link status returned by the CRM is LINK_PENDING. Transaction recovery for the link is still in progress following a restart. Only non-transactional requests may be sent to this link.
|
| |
|
Wait until recovery is complete before requesting transactional services on this link.
|
|
|
Transaction not allowed, request rejected!
|
| |
|
Failed to send a transactional ACALL request to the remote domain because MAXSYNCLVL is not 2.
|
| |
|
Determine the following things:
- Tuxedo Mainframe Adapter for SNA Gateway is licensed for transactions.
and
- DMCONFIG specifies MAXSYNCLVL=2 for the link.
|
|
|
Transaction not allowed, request rejected!
|
| |
|
Failed to send a transactional CONNECT request to the remote domain because MAXSYNCLVL is not 2.
|
| |
|
Determine the following things:
- Tuxedo Mainframe Adapter for SNA Gateway is licensed for transactions
and
- DMCONFIG specifies MAXSYNCLVL=2 for the link.
|
|
|
Protocol violation, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected. An error was returned by gw_nw_AllocNwCtx.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid conversation identification, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_convsend.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unknown message type, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
LINK_STATUS state error, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Protocol violation, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, an error was returned by gw_nw_getsncrm_idx.
|
| |
|
Contact BEA Customer Support.
|
|
|
Trans Event Error shutdown
|
| |
|
An internal error has been detected, an error was returned by gw_nw_TranSetUpExtTmsEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
SIGNON identify failed, shutdown Gateway!
|
| |
|
CRM returned an error to the SIGNON request by Tuxedo Mainframe Adapter for SNA Gateway.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected. An error was returned by gw_nw_AssociateTranBy.
|
| |
|
Contact BEA Customer Support.
|
|
|
SIGNON state error, shutdown Gateway!
|
| |
|
An internal error has been detected, an error was returned by _ gw_nw_CRM_nextop.
|
| |
|
Contact BEA Customer Support.
|
|
|
STARTUP state error, shutdown Gateway!
|
| |
|
An internal error has been detected, an error was returned by _ gw_nw_CRM_nextop.
|
| |
|
Contact BEA Customer Support.
|
|
|
LINK_STATUS decode error, shutdown Gateway!
|
| |
|
An internal error has been detected. An error was returned by CRM_linkstatus_rcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
LINK_STATUS status error, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
LINK_CONFIG state error, shutdown Gateway!
|
| |
|
An internal error has been detected, an error was returned by _ gw_nw_CRM_nextop.
|
| |
|
Contact BEA Customer Support.
|
|
|
STACK_CONFIG state error, shutdown Gateway!
|
| |
|
An internal error has been detected, an error was returned by _ gw_nw_CRM_nextop.
|
| |
|
Contact BEA Customer Support.
|
|
|
SHUTDOWN message received, shutdown Gateway!
|
| |
|
GWSNAX has received a SHUTDOWN request from the CRM and will shut down immediately.
|
| |
|
Examine the ULOG for more information concerning the reason for the shutdown.
|
|
|
LOG_DATA decode error, shutdown Gateway!
|
| |
|
An internal error has been detected. An error was returned by CRM_log_data_rcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
LOG_DATA state error(<number>), shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Protocol violation, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv. Inbound ACALL request contained SEND_INVITE for function DPL.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_InBoundConnectRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_OutBoundConnectRsp.
|
| |
|
Contact BEA Customer Support.
|
|
|
Protocol violation, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
SEND_DATA decode error, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Cannot create action to send remote disconnect
|
| |
|
An internal error has been detected, an error was returned by gw_new_action.
|
| |
|
Contact BEA Customer Support.
|
|
|
ACALL decode error, shutdown Gateway!
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_InBoundAcallRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_OutBoundAcallRsp.
|
| |
|
Contact BEA Customer Support.
|
|
|
Failed to find local service(<text>) definition!
|
| |
|
Unable to find the local service definition for the inbound request.
|
| |
|
Examine the DMCONFIG local service definitions. Correct any errors found. If no error is found, contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, an error was returned by _gw_nw_set_link_idx.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_QueryProcess.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
A failure has been detected while sending the CRM_QSVC_RSP verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
Encode SEND_DATA failed, RRCORR(<number>)!
|
| |
|
An internal error has been detected by gw_nw_reply.
|
| |
|
Contact BEA Customer Support.
|
|
|
Decode inbound ACALL request failed!
|
| |
|
An error has occurred while decoding an inbound ACALL request in gw_nw_decode.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_acall.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_connect.
|
| |
|
Contact BEA Customer Support.
|
|
|
SECURITY: Failed in security checking for RRCORR(<number>)!
|
| |
|
Security checking failed for the inbound ACALL request. An error was returned by gw_nw_SetSecurity.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
BAD Transaction ID shutdown
|
| |
|
An internal error has been detected by gw_nw_SendData.
|
| |
|
Contact BEA Customer Support.
|
|
|
BAD Transaction ID shutdown
|
| |
|
An internal error has been detected by gw_nw_OutBoundAcallRsp.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_QueryProcess.
|
| |
|
Contact BEA Customer Support.
|
|
|
Decode outbound ACALL response failed, RRCORR(<number>)!
|
| |
|
An error has occurred while decoding the response from the host application to an outbound ACALL.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_QueryProcessError.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid connect_resp index
|
| |
|
An internal error has been detected by gw_nw_ConnectError.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
A failure has been detected while sending the CRM_QSVC_RSP verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
|
| |
|
A failure has been detected while sending the CRM_CONNECT_RSP verb to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Determine if the CRM process is still active.
|
|
|
BAD Transaction ID shutdown
|
| |
|
An internal error has been detected by gw_nw_InBoundAcallRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
Decode inbound connect request failed, RRCORR(<number>)!
|
| |
|
An error has occurred while decoding an inbound connect request in gw_nw_InBoundConnectRqst.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
SECURITY: Inbound connect request security check failed, RRCORR(<number>)!
|
| |
|
Security checking failed for the inbound CONNECT request. An error was returned by gw_nw_SetSecurity.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Decode SEND_DATA failed, RRCORR(<number>)!
|
| |
|
An error has occurred while decoding an outbound send data request in gw_nw_SendData.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Invalid buffer type, encode failed!
|
| |
|
The buffer type specified for the outbound message was invalid. Tuxedo Mainframe Adapter for SNA Gateway only supports standard Tuxedo buffer types over the domain gateway.
|
| |
|
Correct the DMCONFIG definition.
|
|
|
Outbound ACALL encode failed!
|
| |
|
An error has occurred while encoding an outbound ACALL request in gw_nw_encode.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_InBoundAcallRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_InBoundAcallRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid buffer type, decode failed!
|
| |
|
The buffer type specified for the inbound message was invalid. Tuxedo Mainframe Adapter for SNA Gateway only supports standard Tuxedo buffer types over the domain gateway.
|
| |
|
Correct the DMCONFIG definition.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_init_env.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_InBoundConnectRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
Outbound CONNECT encode failed!
|
| |
|
An error has occurred while encoding an outbound CONNECT request in gw_nw_encode.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
Outbound CONVSEND encode failed!
|
| |
|
An error has occurred while encoding an outbound CONVSEND request in gw_nw_encode.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_crmrcv.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to send data on sna_conv_idx <number>, gpnd = <number>
|
| |
|
An error has occurred while sending a connect response to the CRM.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure.
|
|
|
BAD Transaction ID shutdown
|
| |
|
An internal error has been detected by gw_nw_InBoundConnectRqst.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to obtain socket id
|
| |
|
An internal error has been detected by gw_nw_link_gp.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_link_gp.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_link_gp.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected, an error was returned by gw_nw_AllocNwCtx.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to obtain socket id
|
| |
|
An internal error has been detected by gw_nw_init_env.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to find view file for <text> <text>
|
| |
|
Failed to find the view file for the FML buffer type specified in the INBUFTYPE for an inbound request.
|
| |
|
Examine the environment variables VIEWDIR, VIEWFILES, VIEW32DIR, and VIEW32FILES to determine if the requested view is present.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_reply.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_reply.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_QueryProcess.
|
| |
|
Contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_encode.
|
| |
|
Contact BEA Customer Support.
|
|
|
Allocate send buffer failed!
|
| |
|
An internal error has been detected, an error was returned by gw_nw_empty_sndbuf.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to get appkey for this outbound request
|
| |
|
An internal error has been detected, gw_shm_getbylink returned an error while getting the remote domain entry.
|
| |
|
Examine the DMCONFIG remote domain definitions and its security setting. Correct any errors found. If no error is found, contact BEA Customer Support.
|
|
|
|
| |
|
An internal error has been detected by gw_nw_SendEvent.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unable to find view file for <text> <text>
|
| |
|
Failed to find the view file for encoding outbound FML data as specified in the OUTBUFTYPE.
|
| |
|
Examine the environment variables VIEWDIR, VIEWFILES, VIEW32DIR, and VIEW32FILES to determine if the requested view is present.
|
|
|
Unable to find view file for <text> <text>
|
| |
|
Failed to find the view file for encoding outbound FML32 data as specified in the OUTBUFTYPE.
|
| |
|
Examine the environment variables VIEWDIR, VIEWFILES, VIEW32DIR, and VIEW32FILES to determine if the requested view is present.
|
|
|
BAD Context shutdown caused at transaction associate
|
| |
|
An internal error has been detected, an error was returned by gw_nw_AssociateTranByTCTXT.
|
| |
|
Contact BEA Customer Support.
|
|
|
System full, can't create action, Enter shutdown
|
| |
|
Failed to create GWSNAX Gateway internal scheduled event to handle failure ore disconnect.
|
| |
|
Either memory allocation failed or a system limit was reached. Contact BEA Customer Support.
|
|
|
Realloc buffer of size(<number>) failed!
|
| |
|
An internal error has been detected, gw_nw_Realloc was unable to allocate memory needed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid network descriptor(<number>)!
|
| |
|
An internal error has been detected by gw_nw_acall.
|
| |
|
Contact BEA Customer Support.
|
|
|
Encryption setup failed, code <number>
|
| |
|
An error has occurred while establishing link-level encryption with the CRM. -1:The processes are using different encryption types (ex. GPE) 6: The processes are using different versions of the encryption protocol. 7: The negotiation of an encryption level has failed. 8: Asystem error has occurred in the encryption setup
|
| |
|
Verify that the setup of encryption on both sides of the link is correct. Verify that there are common encryption levels in the ranges specified on the process command lines. Verify that the correct encryption libraries are installed.
|
|
|
CRM authentication setup failed
|
| |
|
An error has occurred while authenticating a CRM client.
|
| |
|
Verify that the authentication file(s) for both the CRM and the client are set up correctly, and that both have correct access privileges. Verify that the authentication file is specified correctly on both command lines.
|
|
|
Link encryption established, <text> bits
|
| |
|
The SNAX has established link-level encryption with the CRM..
|
| |
|
No action is required. If the encryption level specidied does not match the desired value, verify the encryption level range specified on the SNAX and CRM command lines. A value of ‘40/56’ indicates that encryption is set at 56, even though the specified range may be as low as 40.
|
|
|
YOUR TUXEDO MAINFRAME ADAPTER FOR SNA LICENSE IS EITHER INVALID OR EXPIRED
|
| |
|
The Tuxedo Mainframe Adapter for SNA license is missing from the lic.txt file in $TUXDIR/udataobj or it has expired.
|
| |
|
Look in the $TUXDIR/udataobj/lic.txt file for a section labeled Tuxedo Mainframe Adapter for SNA and if present, check the expiration date.
|
|
|
< taskname> timed out with failCode < failcode>
|
| |
|
A conversation has timed out in the CRM with the stack return code of <failcode>. A timer event set to watch a conversation has expired.
<taskname> may appear as:
OB-Conversation # nn ( <linkref>) tx # m <tranname>, or
IB-Conversation #nn ( <linkref>) tx # m <tranname>
nn is an internal APPC conversation number and m is the transaction context where -1 signifies non-transactional.
Outbound Conversation nnnn Link (<linkref>) TCTXT (tctxt) Tran(<tranname>), or
Inbound Conversation nnnn Link (<linkref>) TCTXT (tctxt) Tran(<tranname>)
nnnn is the CRM Logical Task Number and tctxt is the transaction context, where FFFFFFFF indicates notn-transactional.
|
| |
|
Examine stderr and the ULOG for additional information concerning the failure.
|
|
|
Unable to create APPC Server for <text>.
|
| |
|
CRM was unable to instantiate the stack object due to an error.
|
| |
|
Check for additional messages in stderr. The shared library for the stack or the stack interface might not have been loaded due to an incorrect library path.
|
|
|
Server Failed (< stackref>), Code = < returncode>
|
| |
|
CRM received a bad return code from the stack start-up.
|
| |
|
The < returncode> is the value returned by the SNA Stack software. Check the status of the stack, the configuration of the stack, and the gateway configuration.
| Note: |
Unless you started the CRM as a Tuxedo server, you must manually kill the CRM process. |
|
|
|
Configuration change on link < linkref> requires cold start
|
| |
|
Attempting to do a warm start after changing the domain configuration.
|
| |
|
Change start type to COLD and restart.
|
|
|
Unrecovered transaction, TCTXT(<text>), blob dropped. Transaction presumed forgotten.
|
| |
|
An attempt was make by Tuxedo to recover the specified transaction that was unknown by the CRM. It is presumed that it was already committed or aborted prior to the recovery attempt.
|
| |
|
None. This message is for information only.
|
|
|
Unable to start the recovery task for link < linkref>
|
| |
|
An error occurred during the warm start of Tuxedo.
|
| |
|
Cold start the Tuxedo application.
|
|
|
Unknown tranid dropped, id=< tctxt>
|
| |
|
Recovery was requested by Tuxedo on a transaction that was already forgotten by the CRM.
|
| |
|
None. This message is for information only.
|
|
|
No blob with recovery request. Transaction dropped, id=< tctxt>
|
| |
|
Attempting to warm start after the CRM's BLOBLOG has been modified.
|
| |
|
Change start type to COLD and restart.
|
|
|
<taskname> failed with failCode < failcode>
|
| |
|
A conversation has failed with the stack return code of < failcode>.
<taskname> may appear as:
Outbound Conversation nnnn Link <linkref> TCTXT (<tctxt>) Tran <tranname>, or
Inbound Conversation nnnn Link <linkref> TCTXT (<tctxt>) Tran <tranname>,
nnnn is the CRM Logical TAsk Number.
tctxt is the transaction context where FFFFFFFF signifies non-transactional.
Possible values for the < failcode> are:
- Communications - unable to create the APPCserver object.
- MemoryAllocation - internal error allocating memory.
- InvalidObject - a CRM object could not be created or has been made invalid by some previous error.
- InputOutput - error occurred during file I/O or an unexpected APPC return code was received.
- Registration - internal task cannot be registered.
|
| |
|
Examine stderr and the ULOG for additional information concerning the failure. For failcode Input/Output, verify that the user starting the CRM process has the proper file permissions for the BLOBLOG and RSTRTLOG. If no apparent error is found, contact BEA Customer Support.
|
|
|
Attempt to connect as second master refused!
|
| |
|
A second GWSNAX is attempting to connect to the CRM as a master gateway. Only one master gateway is allowed.
|
| |
|
Ensure that multiple Tuxedo configurations do not use the same CRM address.
|
|
|
Attempt to connect as master in autonomous mode refused!
|
| |
|
An attempt to connect to the CRM as a master gateway was made when the CRM was running in autonomous mode.
|
| |
|
Ensure that multiple Tuxedo configurations do not use the same CRM address.
|
|
|
Attempt to connect with incorrect group name (< groupname>) refused!
|
| |
|
The group name in the gateway configuration file does not match the group name specified in the CRM command line.
|
| |
|
Correct the group name that is in error and restart.
|
|
|
INTERNAL ERROR: memory allocation failed [for new context/data buffer]
|
| |
|
Internal error allocating memory. No more memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
INTERNAL ERROR: server registration failed
|
| |
|
Internal error registering the APPC server. APPC libraries not found. The stack failed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Link refers to undefined APPC stack (< stackref>)!
|
| |
|
The stackref in the link configuration is incorrect.
|
| |
|
Correct the stackref that is in error, run dmloadcf, and restart.
|
|
|
INTERNAL ERROR: link registration failed
|
| |
|
Internal error registering the link. The stack failed.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Transition <additional information>
|
| |
|
An internal state table failure has occurred. The <additional information> will be one of the following:
- From
<oldstate> to <newstate> for <dir>-bound transaction TCTXT<tid>
- To
<newstate> for inbound transaction TCTXT<tid>
- To
<newstate> for outbound transaction TCTXT<tid>
|
| |
|
Contact BEA Customer Support.
|
|
|
Unknown Service Correlator = < correlator>, message dropped
|
| |
|
Internal error assigning service correlator values. Message context lost.
|
| |
|
Contact BEA Customer Support.
|
|
|
Duplicate Service Correlator = < correlator>
|
| |
|
Internal error assigning service correlator values.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Remote Link Name < linkref>
|
| |
|
The remote link name in a request does not match any defined link name.
|
| |
|
Correct the gateway configuration and restart.
|
|
|
Invalid transaction context = < tctxt>
|
| |
|
Internal error assigning transaction context values. Bad transaction.
|
| |
|
Contact BEA Customer Support.
|
|
|
Unknown Service Correlator = < correlator>, message dropped
|
| |
|
Internal error assigning service correlator values. Message context lost.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid initial syncpoint received from subordinate, TCTXT(<text>)
|
| |
|
Syncpoint processing protocol violation. Subordinate member of conversation attempted to initiate a syncpoint. XA does not support syncpoints from subordinate members.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid Input Message Discarded
|
| |
|
Internal error, bad message sent between GWSNAX and CRM. Possibly incompatible Tuxedo Mainframe Adapter for SNA Gateway and CRM.
|
| |
|
Contact BEA Customer Support.
|
|
|
CNOS Notification Received for unknown partner < partnerLU>
|
| |
|
Multiple instances of the CRM may be using the same local LU.
|
| |
|
Ensure that multiple Tuxedo configurations do not use the same local LU.
|
|
|
Remote Stop Received for < linkref>
|
| |
|
The remote host has issued a stop for the specified link.
|
| |
|
None. This message for information only.
|
|
|
Remote Start Received for < linkref>
|
| |
|
The remote host has issued a start for the specified link.
|
| |
|
None. This message for information only.
|
|
|
Undefined Remote LU on link < linkref>
|
| |
|
The remote LU does not exist as defined.
|
| |
|
Check the gateway configuration file and the stack configuration and correct the mis-match.
|
|
|
Unable to start session on link < linkref>. Reason=< reason>
|
| |
|
Link activation failure due to SNA error.
|
| |
|
< reason> is the description of the stack return code. Determine the cause and correct.
|
|
|
Unable to initialize link < linkref>. Reason=< reason>
|
| |
|
Link initialization failure due to SNA error.
|
| |
|
< reason> is the description of the stack return code. Determine the cause and correct.
|
|
|
No Available Session on link < linkref> for context < correlator>
|
| |
|
Max sessions has been exceeded.
|
| |
|
Check session limits in gateway configuration, stack configuration, CICS or VTAM. Increase if necessary.
|
|
|
Requested Synclevel not supported by link < linkref> for context < correlator> (synclevel < level>)
|
| |
|
Attempted to issue a request at sync level < level> on a link that does not support that level.
|
| |
|
Correct application or gateway configuration.
|
|
|
Service Request at SyncLevel=2 Rejected on PENDING link < linkref> for context < correlator>
|
| |
|
An attempt to start a new sync level 2 request has been received and the Link is currently processing recovery information.
|
| |
|
Wait until recovery is complete to request sync level 2 services.
|
|
|
Inbound Request Transform Failed (< status>) for context < correlator>
|
| |
|
An error has occurred while processing the CICS transform for an inbound DPL request. This normally occurs when the API entry in the gateway configuration for the local service specifies CICS instead of ATMI.
|
| |
|
Check gateway configuration for incorrect specification of local service API entry.
|
|
|
Inbound Response Transform Failed (< status>) for context < correlator>
|
| |
|
An error has occurred while processing the CICS transform for an inbound DPL response. This normally occurs when the API entry in the gateway configuration for the local service specifies CICS instead of ATMI.
|
| |
|
Check gateway configuration for incorrect specification of local service API entry.
|
|
|
Outbound Request Transform Failed (< status>) for context < correlator>
|
| |
|
An error has occurred while processing the CICS transform for an outbound DPL request. This normally occurs when the API entry in the gateway configuration for the remote service specifies CICS instead of ATMI.
|
| |
|
Check gateway configuration for incorrect specification of local service API entry.
|
|
|
Outbound Response Transform Failed (< status>) for context < correlator>
|
| |
|
An error has occurred while processing the CICS transform for an outbound DPL response. This normally occurs when the API entry in the gateway configuration for the remote service specifies CICS instead of ATMI.
|
| |
|
Check gateway configuration for incorrect specification of local service API entry.
|
|
|
Conversation terminated without confirm for context < correlator>
|
| |
|
Sync level 2 conversation was terminated with out confirm.
|
| |
|
Check application program and correct.
|
|
|
Inbound Confirm not supported
|
| |
|
Host application is requesting an inbound confirm. This is not supported.
|
| |
|
Check host application program and correct.
|
|
|
Inbound Confirm for multi-ISRT not supported
|
| |
|
Host IMS application is requesting an inbound confirm and using multiple ISRT commands. This is not supported.
|
| |
|
Check host application program and correct.
|
|
|
Missing send last from host (ATMI request/response) for context < correlator>
|
| |
|
Host application did not issue send last during an outbound request/response service. The host application may have abended.
|
| |
|
Check application program and correct.
|
|
|
DPL program abended with CICS code < abendcode>, program=< progname>
|
| |
|
The specified host DPL program has abended with the code specified.
|
| |
|
None. This message is for information only.
|
|
|
DPL program failed with CICS rcode < eibrcode>, program=< progname>
|
| |
|
The specified host DPL program has failed with the eibrcode specified.
|
| |
|
None. This message is for information only.
|
|
|
Invalid combination for Service Context < correlator>, < combination>
|
| |
|
The specified <combination> is invalid. It will be one of the following:
- Sync-Level, function, and API
- Function and API
|
| |
|
Examine the gateway configuration and make corrections.
|
|
|
Sequence number error for Service Context < correlator>, seqno < seqno>
|
| |
|
There has been a sequence number failure for the specified context. Context is out of sequence.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid conversation task for Service Context < correlator>, task=< task>
|
| |
|
The conversation has already been terminated.
|
| |
|
Contact BEA Customer Support.
|
|
|
Invalid task switch for Service Context < correlator>, from < task1> to < task2>
|
| |
|
An internal protocol violation has occurred.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transformer creation failed for inbound transaction < trancode>
|
| |
|
An internal error has occurred. Possibly out of memory.
|
| |
|
Contact BEA Customer Support.
|
|
|
Transformer failed for inbound transaction < trancode>
|
| |
|
An internal error has occurred. Resource name is not present. Mainframe compatibility problem.
|
| |
|
Contact BEA Customer Support.
|
|
|
Inter-task Message dropped (< verbname>), parm=< parm> From: < task1> to < task2>
|
| |
|
An internal message between two tasks has been dropped.
|
| |
|
None. This message is for information only.
|
|
|
Attempt to send < nnnnn> bytes (> 32767)
|
| |
|
The length of a send request exceeded 32767 (including overhead).
|
| |
|
Check application program and correct.
|
|
|
Allocation Failure for < trancode> on < remotesysid>: < error>
|
| |
|
An Allocation error occurred.
|
| |
|
The reason for the failure is described by <error>. Correct problem with configuration or application.
|
|
|
Invalid Exchange Logs GDS variable received from < remotesysid>
|
| |
|
The log files for the CRM have been incorrectly modified.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Invalid cold start received from < remotesysid>. Unrecovered local transactions are pending.
|
| |
|
Attempting to cold start host while warm starting Tuxedo.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Invalid warm start received from < remotesysid>. Unknown log name.
|
| |
|
The log files for the CRM have been incorrectly modified.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Invalid Compare States GDS variable received from < remotesysid>
|
| |
|
The log files for the CRM have been incorrectly modified.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Mixed Heuristic on link < linkref> for < unitofwork> Correlator [< correlator>]
|
| |
|
One side has reported committed while the other side has reported aborted.
|
| |
|
Check the ULOG for any additional messages.
|
|
|
Inbound Exchange Logs Rejected for < remotesysid>
|
| |
|
Link not configured for sync level 2.
|
| |
|
None. This message is for information only.
|
|
|
Link < linkref> not configured for sync level 2
|
| |
|
Link specified by < linkref> is not configured for sync level 2.
|
| |
|
None. This message is for information only.
|
|
|
Exchange Logs Rejected for < remotesysid>, Restart Type or Log Name Mismatch
|
| |
|
The log files for the CRM have been incorrectly modified.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Exchange Logs failed with < linkref>
|
| |
|
An error occurred during the exchange logs process.
|
| |
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
Invalid initial syncpoint received from subordinate, <text>
|
| |
|
An internal error has occurred during the commit process. XA does not support syncpoints originating from subordinate members.
|
| |
|
Contact BEA Customer Support
|
|
|
CRM encryption setup failed
|
| |
|
An error has occurred while establishing link-level encryption with the CRM.
|
| |
|
Verify that the setup of encryption on both sides of the link is correct. Verify that there are common encryption levels in the ranges specified on the process command lines. Verify that the correct encryption libraries are installed
|
|
|
Attempted access by unauthorized CRM client
|
| |
|
A client has attempted to access the CRM without the proper authentication or encryption setup.
|
| |
|
Verify that the client should have access to the CRM. Verify that encryption is set up correctly in both the CRM and the client, and that the correct security add-on packages are installed. Verify that the authentication file is set up correctly, and that both the CRM and the client have correct access privileges.
|
|
|
CRM authentication setup failed
|
| |
|
An error has occurred while authenticating a CRM client.
|
| |
|
Verify that the authentication file(s) for both the CRM and the client are set up correctly, and that both have correct access privileges. Verify that the authentication file is specified correctly on both command lines.
|
|
|
CRM Logical Unit %s is probably inactive or unconfigured
|
| |
|
An error has occurred while connecting to the APPC stack.
|
| |
|
Verify that the CRM Logical Unit name is correct and is defined and active in both the stack and VTAM configuration.
|
|
|
WARN: Synclevl on link %s
|
| |
|
The configured Synclevel could not be negotiated.
|
| |
|
Verify that the Remote LU is configured for the correct synclevel.
|
|
|
CRM Logical Unit %s is probably the wrong type
|
| |
|
An error has occurred while connecting to the APPC stack.
|
| |
|
Verify that the CRM Logical Unit is correctly configured.
|
|
|
CRM Logical Unit %s is already in use
|
| |
|
An error has occurred while connecting to the APPC stack.
|
| |
|
Verify that the CRM Logical Unit is not in use by another application.
|
|
|
CRM client message rejected -- incompatible software/protocol version (CRMAPI RC=%s)
|
| |
|
A CRM client has attempted to communicate with the CRM, but the client is at a software version level that is incompatible with and unsupported by the CRM.
|
| |
|
The CRM rejects the message and terminates the connection. Check the version levels of the CRM and the client to ensure compatiblity.
|
|
|
Gateway Signon request rejected -- CRM disconnect in progress
|
| |
|
The CRM is in the process of stopping all links and de-configuring, and is not able to accept a new Signon request at this time.
|
| |
|
The Signon request is rejected. When the CRM has completed disconnect processing and returned to the reset state, retry the Signon request.
|
|
|
Failure occured during Rollback of %s, remote resources may not be backed out
|
| |
|
An Error occurred while performing BACKEDOUT processing. Remote resources may not be backed out.
|
| |
|
Check mainframe application transaction logs to determine the cause and take the appropriate action.
|
|
|
Unable to determine if the transaction was committed on the partner side, possible heuristic situation
|
| |
|
Failed to determine the state of the global transaction due to a partial resynchronization.
|
| |
|
Examine the CRM traces for more information concerning the reason for the failure. Check the CICS logs to see the transaction status.
|
