Table of Contents Previous Next PDF


Error Messages

Error Messages
The following messages are logged to the USERLOG file from an Oracle Tuxedo Mainframe Adapter for SNA Gateway (GWSNAX) and the Communications Resource Manager (CRM).
 
An internal error has been detected, gw_nw_acall has returned a failure.
An internal error has been detected, gw_nw_connect has returned a failure.
An internal error has been detected, gw_nw_convsend has returned a failure.
An internal error has been detected, gw_nw_decode has returned a failure.
An internal error has been detected, gw_nw_encode has returned a failure.
An internal error has been detected, gw_nw_decode has returned a failure.
An internal error has been detected, gw_nw_encode has returned a failure.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to create a listener.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
2.
The //host:port parameters as specified in the DMCONFIG and the CRM command line parameters in the UBBCONFIG do not agree
GWSNAX is unable to send the SHUTDOWN command to CRM.
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
An internal error has been detected, gw_nw_getnxt_cd has returned a failure.
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
An internal error has been detected, gw_nw_AllocNwCtx was unable to allocate memory needed.
An internal error has been detected, gw_nw_empty_sndbuf was unable to allocate memory needed.
An internal error has been detected in gw_nw_TranCvtMsgEvt2TranEvt.
An internal error has been detected in gw_nw_StateObjectTestEvent.
An internal error has been detected in gw_nw_StateObjectTestEvent.
An internal error has been detected in gw_nw_StateObjectTestEvent.
An internal error has been detected in gw_nw_AssociateTranByTXID.
An internal error has been detected in gw_nw_AssociateTranByTXID.
An internal error has been detected in gw_nw_AssociateTranByTXID.
An internal error has been detected in gw_nw_AssociateTranByTCTXT.
An internal error has been detected in gw_nw_AssociateTranByTCTXT.
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.
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
An error has been returned by gw_tx_set_rdom. Several possibilities exist for this failure.
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.
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.
An internal error has been detected in gw_nw__gw_nw_AllocateNode.
A failure was returned by gw_nw_BindStateObject.
A failure was returned by gw_nw_BindStateObject.
A failure was returned by gw_nw_BindStateObject.
An internal error has been detected in gw_nw_NodeSendToSubordinate.
An internal error has been detected in gw_nw_NodeSendToSubordinate.
A failure was returned by gw_nw_TranRecover.
A failure was returned by gw_nw_TranRecover.
A failure was returned by gw_nw_TranRecover.
A failure was returned by gw_nw_TranRecover.
A failure was returned by gw_nw_TranRecover.
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 Oracle Customer Support.
A failure was returned by _gw_nw_AllocBranch.
A failure was returned by _gw_nw_AllocBranch.
An internal error has been detected in gw_nw_TranSetUpExtTmsEvent.
An internal error has been detected in gw_nw_SetUpInstrumentation.
The STARTTYPE specified in the DMCONFIG must be AUTO or COLD.
No buffer of type STRING was returned by tpalloc for the size specified.
Examine the application and the DMCONFIG and correct the problem.
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 Oracle Customer Support.
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 Oracle Customer Support.
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
An internal error has been detected, gw_nw_proto_flow has detected a flow control callback from gp_send.
An internal error has been detected, gw_nw_SendEvent has returned an error.
GWSNAX has received a SHUTDOWN request from the CRM and will shut down immediately.
An internal error has been detected by gw_nw_crmrcv. Inbound ACALL request contained SEND_INVITE for function DPL.
An internal error has been detected, gw_shm_getbylink returned an error while getting the remote domain entry.
An internal error has been detected, gw_nw_Realloc was unable to allocate memory needed.
<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.
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>
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.
Configuration change on link <linkref> requires cold start
<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.
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 Oracle Customer Support.
A second GWSNAX is attempting to connect to the CRM as a master gateway. Only one master gateway is allowed.
The stackref in the link configuration is incorrect.
Correct the stackref that is in error, run dmloadcf, and restart.
An internal state table failure has occurred. The <additional information> will be one of the following:
1.
From <oldstate> to <newstate> for <dir>-bound transaction TCTXT<tid>
2.
To <newstate> for inbound transaction TCTXT<tid>
3.
To <newstate> for outbound transaction TCTXT<tid>
Unknown Service Correlator = <correlator>, message dropped
Unknown Service Correlator = <correlator>, message dropped
Unable to start session on link <linkref>. Reason=<reason>
<reason> is the description of the stack return code. Determine the cause and correct.
Unable to initialize link <linkref>. Reason=<reason>
<reason> is the description of the stack return code. Determine the cause and correct.
No Available Session on link <linkref> for context <correlator>
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.
Inbound Request Transform Failed (<status>) for context <correlator>
Inbound Response Transform Failed (<status>) for context <correlator>
Outbound Request Transform Failed (<status>) for context <correlator>
Outbound Response Transform Failed (<status>) for context <correlator>
DPL program abended with CICS code <abendcode>, program=<progname>
DPL program failed with CICS rcode <eibrcode>, program=<progname>
The specified <combination> is invalid. It will be one of the following:
Invalid task switch for Service Context <correlator>, from <task1> to <task2>
Inter-task Message dropped (<verbname>), parm=<parm> From: <task1> to <task2>
Attempt to send <nnnnn> bytes (> 32767)
Allocation Failure for <trancode> on <remotesysid>: <error>
Invalid cold start received from <remotesysid>. Unrecovered local transactions are pending.
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
Invalid warm start received from <remotesysid>. Unknown log name.
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
Mixed Heuristic on link <linkref> for <unitofwork> Correlator [<correlator>]
Check the ULOG for any additional messages.
Link <linkref> not configured for sync level 2
Link specified by <linkref> is not configured for sync level 2.
Exchange Logs Rejected for <remotesysid>, Restart Type or Log Name Mismatch
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
 

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.