Error Messages

9001:ERROR	<text>
	DESCRIPTION	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: Outbound Conversation nnnn Link(<linkref>) TCTXT(<tctxt>) Tran(<tranname>) or Inbound Conversation nnnn Link(<linkref>) TCTXT(<tctxt>) Tran(<tranname>) or where nnnn is the CRM Logical Task Number and tctxt is the transaction context, where FFFFFFFF indicates non-transactional.
	ACTION	Examine stderr and the ULOG for additional information concerning the failure.
9002:ERROR	Unable to create APPC Server for <text>
	DESCRIPTION	The CRM was unable to instantiate the APPC Server object due to the indicated reason.
	ACTION	Check for additional messages in stderr. Common causes of this problem include a mismatch between the Stack Type and the APPC Stack Library module name, or an incorrectly specified library path.
9003:ERROR	Server Failed <text>
	DESCRIPTION	CRM received a bad return code from the stack start-up.
	ACTION	The <returncode> is the value returned by the SNA Stack software. Check the status of the stack and the configuration of the stack and the gateway configuration.
9004:ERROR	Configuration change on link <text> requires a cold start
	DESCRIPTION	Attempting to do a warm start after changing the domain configuration.
	ACTION	Change start type to "COLD" and restart.
9005:WARN	Unrecovered transaction, TCTXT(<text>), blob dropped. Transaction presumed forgotten.
	DESCRIPTION	An attempt was make by a gateway to recover the specified transaction which was unknown by the CRM. It is presumed that it was already committed or aborted prior to the recovery attempt.
	ACTION	None. This message for information only.
9006:ERROR	Unable to start the recovery task for link <text>
	DESCRIPTION	An error occurred during the warm start of a gateway.
	ACTION	Perform a cold start.
9008:WARN	Unknown transaction dropped, TCTXT(<text>)
	DESCRIPTION	Recovery was requested by a gateway on a transaction that was already forgotten by the CRM.
	ACTION	None. This message for information only.
9009:ERROR	No blob with recovery request. Transaction dropped, TCTXT(<text>)
	DESCRIPTION	Attempting to warm start after the CRM's BLOBLOG has been modified.
	ACTION	Change start type to "COLD" and restart.
9010:ERROR	<text>
	DESCRIPTION	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>) where nnnn is the CRM Logical Task Number and tctxt is the transaction context where FFFFFFFF indicates non-transactional.
	ACTION	Examine stderr and the ULOG for additional information concerning the failure. For failcode InputOutput, 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.
9013:ERROR	Attempt to connect with incorrect CRM name (<text>) refused!
	DESCRIPTION	The group name in the gateway configuration does not match the CRM name specified in the CRM command line.
	ACTION	Correct the CRM name that is in error and restart.
9014:ERROR	INTERNAL ERROR: memory allocation failed <text>
	DESCRIPTION	Internal error allocating memory.
	ACTION	Contact BEA Customer Support.
9015:ERROR	INTERNAL ERROR: server registration failed
	DESCRIPTION	Internal error registering the APPC server.
	ACTION	Contact BEA Customer Support.
9016:ERROR	Link refers to undefined APPC stack (<text>)!
	DESCRIPTION	The stackref in the link configuration is incorrect.
	ACTION	Correct the stackref that is in error, run dmloadcf, and restart.
9017:ERROR	INTERNAL ERROR: link registration failed
	DESCRIPTION	Internal error registering the link.
	ACTION	Contact BEA Customer Support.
9018:ERROR	Invalid Transition <text>
	DESCRIPTION	An internal state table failure has occurred. The <additional information> will be one of the following:
	ACTION	Contact BEA Customer Support.
9019:ERROR	Unknown Service Correlator = <text>, message dropped
	DESCRIPTION	Internal error assigning service correlator values.
	ACTION	Contact BEA Customer Support.
9020:ERROR	Duplicate Service Correlator = <text>
	DESCRIPTION	Internal error assigning service correlator values.
	ACTION	Contact BEA Customer Support.
9021:ERROR	Invalid Remote Link Name <text>
	DESCRIPTION	The remote link name in a request does not match any defined link name.
	ACTION	Correct the gateway configuration and restart.
9022:ERROR	Invalid transaction context = <text>
	DESCRIPTION	Internal error assigning transaction context values.
	ACTION	Contact BEA Customer Support.
9023:ERROR	Unknown Service Correlator = <text>, message dropped
	DESCRIPTION	Internal error assigning service correlator values.
	ACTION	Contact BEA Customer Support.
9024:ERROR	Invalid initial syncpoint received from subordinate, TCTXT(<text>)
	DESCRIPTION	Syncpoint processing protocol violation. Subordinate member of conversation attempted to initiate a syncpoint.
	ACTION	Contact BEA Customer Support.
9025:ERROR	<text>
	DESCRIPTION	The CRM has incurred an error attempting to process a received CRMAPI message. The error may be due to an improperly formatted CRMAPI message, or an error encountered during functional processing associated with the message. In any case, the CRM responds by terminating the session with the partner that sent the message.
	ACTION	Contact BEA Customer Support.
9026:ERROR	CNOS Notification Received for unknown partner <text>
	DESCRIPTION	Multiple instances of the CRM may be using the same CRM Logical Unit.
	ACTION	Ensure that each CRM in the gateway configuration has a unique Logical Unit.
9027:INFO	Remote Stop Received for <text>
	DESCRIPTION	The remote host has issued a stop for the specified link.
	ACTION	None. This message for information only.
9028:INFO	Remote Start Received for <text>
	DESCRIPTION	The remote host has issued a start for the specified link.
	ACTION	None. This message for information only.
9029:ERROR	Undefined Remote LU on link <text>
	DESCRIPTION	The remote Logical Unit does not exist as defined.
	ACTION	Check the gateway configuration file and the stack configuration and correct the mismatch.
9030:ERROR	Unable to start session on link <text>
	DESCRIPTION	Link activation failure due to SNA error.
	ACTION	<reason> is the description of the stack return code. Determine the cause and correct.
9031:ERROR	Unable to initialize link <text>
	DESCRIPTION	Link initialization failure due to SNA error.
	ACTION	<reason> is the description of the stack return code. Determine the cause and correct.
9032:ERROR	No Available Session on link <text>
	DESCRIPTION	Max sessions has been exceeded.
	ACTION	Check session limits in gateway configuration, stack configuration, CICS or VTAM. Increase if necessary.
9033:ERROR	Requested Synclevel not supported by link <text>
	DESCRIPTION	Attempted to issues a request at sync level <level> on a link that does not support that level.
	ACTION	Correct application or gateway configuration.
9034:ERROR	Service Request at SyncLevel=2 Rejected on PENDING link <text>
	DESCRIPTION	An attempt to start a new sync level 2 request has been received and the Link is currently processing recovery information.
	ACTION	Wait until recovery is complete to request sync level 2 services.
9035:ERROR	Inbound Request Transform Failed <text>
	DESCRIPTION	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.
	ACTION	Check gateway configuration for incorrect specification of local service API entry.
9036:ERROR	Inbound Response Transform Failed <text>
	DESCRIPTION	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.
	ACTION	Check gateway configuration for incorrect specification of local service API entry.
9037:ERROR	Outbound Request Transform Failed <text>
	DESCRIPTION	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.
	ACTION	Check gateway configuration for incorrect specification of local service API entry.
9038:ERROR	Outbound Response Transform Failed <text>
	DESCRIPTION	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.
	ACTION	Check gateway configuration for incorrect specification of local service API entry.
9039:ERROR	Conversation terminated without confirm for context <text>
	DESCRIPTION	Sync level 2 conversation was terminated with out confirm.
	ACTION	Check application program and correct.
9040:ERROR	Inbound Confirm not supported
	DESCRIPTION	Host application is requesting an inbound confirm. This is not supported.
	ACTION	Check host application program and correct.
9041:ERROR	Inbound Confirm for multi-ISRT not supported
	DESCRIPTION	Host IMS application is requesting an inbound confirm and using multiple ISRT commands. This is not supported.
	ACTION	Check host application program and correct.
9043:ERROR	Missing send last from host (ATMI request/response) for context <text>
	DESCRIPTION	Host application did not issue send last during an out-bound request/ response service. The host application may have abended.
	ACTION	Check application program and correct.
9044:ERROR	DPL program abended with CICS code <text>
	DESCRIPTION	The specified host DPL program has abended with the code specified.
	ACTION	None. This message is for information only.
9045:ERROR	DPL program failed with CICS rcode = <text>
	DESCRIPTION	The specified host DPL program has failed with the eibrcode specified.
	ACTION	None. This message is for information only.
9046:ERROR	Invalid combination for Service Context <text>
	DESCRIPTION	The specified <combination> is invalid. It will be one of the following: 1) SyncLevel, function, and api; 2) function and api
	ACTION	Examine the gateway configuration and make corrections.
9047:ERROR	Sequence number error for Service Context <text>
	DESCRIPTION	There has been a sequence number failure for the specified context.
	ACTION	Contact BEA Customer Support.
9048:ERROR	Invalid conversation task for Service Context <text>
	DESCRIPTION	The conversation has already been terminated.
	ACTION	Contact BEA Customer Support.
9049:ERROR	Invalid task switch for Service Context <text>
	DESCRIPTION	An internal protocol violation has occurred.
	ACTION	Contact BEA Customer Support.
9050:ERROR	Transformer creation failed for in-bound transaction <text>
	DESCRIPTION	An internal error has occurred.
	ACTION	Contact BEA Customer Support.
9051:ERROR	Transformer failed for in-bound transaction <text>
	DESCRIPTION	An internal error has occurred. Resource name is not present.
	ACTION	Contact BEA Customer Support.
9052:WARN	Inter-task Message dropped <text>
	DESCRIPTION	An internal message between two tasks has been dropped.
	ACTION	None. This message is for information only.
9053:ERROR	Attempt to send <text> bytes (> 32767)
	DESCRIPTION	The length of a send request exceeded 32767 (including overhead).
	ACTION	Check application program and correct.
9054:ERROR	Allocation Failure for <text>
	DESCRIPTION	An Allocation error occurred.
	ACTION	The reason for the failure is described by <error>. Correct problem with configuration or application.
9055:ERROR	Invalid Exchange Logs GDS variable received from <text>
	DESCRIPTION	The log files for the CRM have been incorrectly modified.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9056:ERROR	Invalid cold start received from <text>. Unrecovered local transactions are pending.
	DESCRIPTION	Attempting to cold start host while warm starting a gateway.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9057:ERROR	Invalid warm start received from <text>. Unknown log name.
	DESCRIPTION	The log files for the CRM have been incorrectly modified.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9058:ERROR	Invalid Compare States GDS variable received from <text>
	DESCRIPTION	The log files for the CRM have been incorrectly modified.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9059:ERROR	Mixed Heuristic on link <text>
	DESCRIPTION	One side has reported committed while the other side has reported aborted.
	ACTION	Check the ULOG for any additional messages.
9060:WARN	Inbound Exchange Logs Rejected for <text>
	DESCRIPTION	Link not configured for sync level 2.
	ACTION	None. This message is for information only.
9061:WARN	Link <text> not configured for synclevel 2
	DESCRIPTION	Link specified by <linkref> is not configured for sync level 2.
	ACTION	None. This message is for information only.
9062:ERROR	Exchange Logs Rejected for <text>, Restart Type or Log Name Mismatch
	DESCRIPTION	The log files for the CRM have been incorrectly modified.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9063:ERROR	Exchange Logs failed with <text>
	DESCRIPTION	An error occurred during the exchange logs process.
	ACTION	Run CRMLOGS to examine the CRM log file. Perform a cold start.
9064:ERROR	Invalid initial syncpoint received from subordinate, <text>
	DESCRIPTION	An internal error has occurred during the commit process.
	ACTION	Contact BEA Customer Support.
9069:ERROR	CRM encryption setup failed
	DESCRIPTION	An error has occurred while establishing link-level encryption with the CRM.
	ACTION	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.
9072:ERROR	Attempted access by unauthorized CRM client
	DESCRIPTION	A client has attempted to access the CRM without the proper authentication or encryption setup.
	ACTION	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.
9073:ERROR	CRM authentication setup failed
	DESCRIPTION	An error has occurred while authenticating a CRM client.
	ACTION	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.
9074:ERROR	CRM Logical Unit <text> is probably inactive or unconfigured.
	DESCRIPTION	An error has occurred while connecting to the APPC Stack.
	ACTION	Verify that the CRM Logical Unit name is correct and is defined and active in both stack and VTAM configuration.
9075:WARN	Synclevl on link <text>
	DESCRIPTION	The configured Synclevel could not be negotiated.
	ACTION	Verify that the Remote Logical Unit is configured for the correct synclevel.
9076:ERROR	CRM Logical Unit <text> is probably the wrong type.
	DESCRIPTION	An error has occurred while connecting to the APPC Stack.
	ACTION	Verify that the CRM Logical Unit is correctly configured.
9077:ERROR	CRM Logical Unit <text> is already in use.
	DESCRIPTION	An error has occurred while connecting to the APPC Stack.
	ACTION	Verify that the CRM Logical Unit is not in use by another application.
9078:ERROR	Domain Name <text>
	DESCRIPTION	All WebLogic JAM Gateways concurrently connected to a CRM must be members of the same WebLogic Server Domain. The Domain Name for the current CRM configuration is established by the first WebLogic JAM Gateway to connect.
	ACTION	Verify the WebLogic Server/WebLogic JAM configurations and ensure that all WebLogic JAM Gateways to be concurrently connected to a CRM are members of the same WebLogic Server Domain.
9079:ERROR	CRM client message rejected -- incompatible software/protocol version (CRMAPI RC=<text>)
	DESCRIPTION	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.
	ACTION	The CRM rejects the message and terminates the connection. Check the version levels of the CRM and the client to ensure compatiblity.
9080:ERROR	Gateway Signon request rejected -- CRM disconnect in progress
	DESCRIPTION	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.
	ACTION	The Signon request is rejected. When the CRM has completed disconnect processing and returned to the reset state, retry the signon request.
9081:ERROR	Failure occured during Rollback of <text>, remote resources may not be backed out
	DESCRIPTION	An error occurred while performing BACKEDOUT processing. Remote resources may not be backed out.
	ACTION	Check mainframe application transaction logs to determine the cause and take the appropriate action.


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Search \| Download Documentation \| Contact \| Glossary

WebLogic Java Adapter for Mainframe Documentation \| BEA WebLogic Java Adapter for Mainframe Error Messages \| Previous Topic \|