IMS TM resource adapter messages and exceptions

Explanations and user actions for IMS™ TM resource adapter messages and exceptions

While you develop Java™ programs that use IMS TM resource adapter (also known as IMS Connector for Java), you might encounter situations in which your program throws exceptions. Some of these exceptions are thrown by the IMS TM resource adapter, while others are thrown by class libraries used by the IMS TM resource adapter (such as the Java class libraries). This topic provides information on exceptions generated by the IMS TM resource adapter J2C applications.

The following terms, in italics in the message descriptions that follow, are replaced by specific values at runtime.

hostname
The TCP/IP host name of the machine that is running IMS Connect.
innermethodname
The name of the method that originally throws this exception. This exception has been caught by IMS Connector for Java and is being re-thrown to another exception, according to the Common Connector Framework specification.
length
The length of the data.
libraryFileName
The Local Option native library file name.
llvalue
The value of LL.
maxlength
The maximum valid length of the data.
methodname
The name of the method that is throwing this exception.
mode
The type of interaction between the IMS TM resource adapter and the IMS Connect component on the host (as defined in the interactionSpec).
nativeMethodName
The Local Option native method name.
portnumber
The port number that is assigned to IMS Connect.
propertyname
The name of the property.
propertyvalue
The value of the property.
reasoncode
The reason code that is returned by IMS Connect.
rectype
The type of the record.
returncode
The return code, formatted in decimal, that is returned by IMS Connect.
sensecode
The sense code, formatted in decimal, that is returned from IMS OTMA
socketexception
The socket exception.
source_exception
The exception thrown when the error first occurred in an internal method.
source_methodname
The internal method in which the error first occurred.
state
The internal state of IMS Connector for Java.

Related Reading

Exceptions generated by IMS Connector for Java J2C applications

The following exception messages are produced by applications built with the Java 2 Platform, Enterprise Edition (J2EE) Connector Architecture (J2C) class libraries when an error condition is detected.

ICO0001E
javax.resource.spi.EISSystemException:
ICO0001E: methodname error.
IMS Connect returned error:
RETCODE=[returncode], REASONCODE=[reasoncode].
reasoncode_string.

Explanation: IMS Connect returned an error. The connection in error will not be reused. reasoncode_string provides a brief description of the reasoncode , if available.

User Action: Check the MVS™ console for associated IMS Connect error messages. IMS Connect error messages begin with the characters " HWS". For diagnostic information on the return code (returncode) and reason code (reasoncode) values, as well as IMS Connect error messages, see the IMS Connect Guide and Reference.

ICO0002E
javax.resource.spi.EISSystemException:
ICO0002E:methodname error.
IMS OTMA returned error:
SENSECODE=[sensecode], REASONCODE=[otmareasoncode].
[source_methodname:source_exception]

Explanation: IMS OTMA returned a NAK error.

User Action: For diagnostic information on the sense code (sensecode) and OTMA reason code (otmareasoncode) values of the NAK error, see the IMS OTMA Guide and Reference. Note that IMS Connector for Java displays sensecode and otmareasoncode in decimal. If the application is running with two-phase commit, you may receive the following sense code values with the NAK error:
  • Sense code = 17 (decimal, 23 Hex)

    Your IMS is not enabled with RRS processing. Ensure your IMS has Protected Conversation processing with RRS enabled. See Two-phase commit prerequisites for more information.

  • Sense code = 46 (decimal, 2E Hex)

    RRS and two-phase commit processing is not supported by IMS Connect and IMS Connector for Java. Make sure that both your IMS Connect and IMS Connector for Java is at least version 2.1.0 or above.

ICO0003E
javax.resource.spi.CommException:
ICO0003E:methodname error.
Failed to connect to host [hostname], 
port [portnumber].
[java_exception]

Explanation: IMS Connector for Java was unable to connect to the host and port combination. java_exception indicates the reason for the failure to connect. For additional information see the User Action section below.

User Action: Examine java_exception to determine the reason for the failure to connect to the host. Some values for java_exception are:
  • java.net.UnknownHostException: hostname

    The host name you specified when configuring the Connection Factory used by your application is invalid or your application specified an invalid host name. Check the spelling of the host name. You may have to use the fully qualified path for host name or the IP address.

  • java.net.ConnectException: Connection refused
    Some possible reasons for the exception are:
    • The port number is invalid. Ensure that you are using a valid port number for the IMS Connect indicated by hostname.
    • The specified port is stopped. This can be determined using the IMS Connect command VIEWHWS. If the port is stopped its status will be NOT ACTIVE. Use the IMS Connect command, OPENPORT dddd, where dddd is the specified port number, to start the port.
    • IMS Connect on the specified host is not running. Start IMS Connect on the host machine.
    • TCP/IP was restarted without canceling and restarting IMS Connect or issuing STOPPORT followed by OPENPORT on the host.
  • java.net.SocketException: connect (code=10051)
    Some possible reasons for the exception are:
    • The machine with the specified host name is unreachable on the TCP/IP network. Ensure that the host machine is accessible from the TCP/IP network. Verify by issuing the ping command to the specified host machine. Enter the ping command on the machine on which IMS Connector for Java is running. Start TCPIP on the host, if it is not started.
    • TCP/IP was restarted but the status of the port used by the application was NOT ACTIVE. To correct this situation you can do one of the following:
      • Use the IMS Connect command OPENPORT dddd, where dddd is the port number, to activate the port
      • Restart IMS Connect
ICO0005E
javax.resource.spi.CommException:
ICO0005E:methodname error.
A communication error occurred while sending or receiving the IMS message.
[java_exception]

Explanation: IMS Connector for Java was unable to successfully complete a send and receive interaction with the target IMS Connect. java_exception indicates the reason for the failure to complete the interaction. For additional information see the User Action section below.

User Action: Examine java_exception to determine the reason for the failure. Some values for java_exception are:

ICO0006E
javax.resource.ResourceException:
ICO0006E:methodname error.
The value provided for DataStoreName is null or an empty string.

Explanation: The method indicated in methodname was invoked using an empty DatastoreName parameter. This error message will appear in the trace log when a connection factory with an empty DatastoreName parameter is started. This message will be followed by a J2EE Connector warning,

J2CA0007W: An exception occurred while invoking method setDataStoreName on 
com.ibm.connector2.ims.ico.IMSManagedConnectionFactory used by resource 
Connection_Factory_JNDI_name.
Processing will then continue leading to other error messages after IMS Connect sends a response indicating that a datastore with a null name cannot be found. The underlying message which triggers the other messages is:
javax.resource.spi.EISSystemException: ICO0001E: 
com.ibm.connector2.ims.ico.IMSTCPIPManagedConnection@.processOutputOTMAMsg(byte[],
InteractionSpec, Record) error. IMS Connect returned error: RETCODE=[4], 
REASONCODE=[NFNDDST ]. Datastore not found.
When this error occurs, a corresponding HWSS0742W warning message is displayed on the MVS console of the host machine where IMS Connect is running. This HWSS0742W message will include a field showing the datastore name that it attempted to find, in this case all blanks:
DESTID=        ;

User Action: Provide a valid name for the DatastoreName parameter. In a managed environment, the DatastoreName is specified when you are configuring a Connection Factory to be used by WebSphere Application Server. In a non-managed environment, the DatastoreName is specified in your Java application.

ICO0007E
javax.resource.NotSupportedException:
ICO0007E:methodname error.
The [propertyName] property value [propertyValue] is not supported.

Explanation: The value propertyValue specified for the property propertyName is not supported.

User Action: Provide a supported value for the named property. For example, certain values of the InteractionVerb property of the InteractionSpec class that are defined in the J2C architecture are not supported by the IMSInteractionSpec class in this release of IMS Connector for Java. Also the ReRoute value TRUE is not supported on dedicated persistent socket connections.

ICO0008E
javax.resource.ResourceException:
ICO0008E:methodname error. The value [propertyValue] of the [propertyName] 
property exceeds the maximum allowable length 
of [maxPropertyLength].

Explanation: The length of the value propertyValue supplied for property propertyName exceeds maxPropertyLength, the maximum length allowed for values of property propertyName.

User Action: Provide a value for the named property which does not exceed maxPropertyLength.

ICO0009E
javax.resource.ResourceException:
ICO0009E:methodname error.
The [propertyName] property value [propertyValue] is invalid.

Explanation: The value propertyValue specified for the property propertyName is not valid.

User Action: Provide a value which is valid for the named property. For example, valid values for the InteractionVerb property of the InteractionSpec class of IMS TM resource adapter are listed in the Javadoc documentation for the IMSInteractionSpec class.

ICO0010E
javax.resource.spi.IllegalStateException:
ICO0010E:methodname error.
Method invoked on invalid IMSConnection instance.

Explanation: The method indicated in methodname was invoked on an invalid IMSConnection instance. If the methodname is lazyEnlist, an attempt was made to enlist a connection in the current transaction that could not be enlisted.

User Action: The named method was most likely issued on an IMSConnection instance that was already closed.

  • If the methodname is not lazyEnlist, ensure that the IMSConnection instance is not already closed before you attempt to use it or close it.
  • If the methodname is lazyEnlist, ensure that your application is not using non-managed connections in a managed environment, as only managed connections are eligible for Lazy Transaction Enlistment Optimization. For more information please refer to the Deferred Enlistment topic found in the WebSphere Application Server 6.0 online information center.
ICO0011E
javax.resource.spi.IllegalStateException:
ICO0011E:methodname error.
Method invoked on invalid IMSInteraction instance.

Explanation: The method indicated in methodname was invoked on an invalid IMSInteraction instance.

User Action: The named method was most likely issued on an IMSInteraction instance that was already closed. Ensure that the IMSInteraction instance is not already closed before you attempt to use it or close it.

ICO0012E
javax.resource.ResourceException:
ICO0012E:methodname error.
The value provided for HostName is null or an empty string.

Explanation: The method indicated in methodname was invoked using a null or empty HostName parameter.

User Action: Provide a valid HostName parameter. In a managed environment, the property value is specified when you are configuring a Connection Factory to be used by WebSphere Application Server. In a non-managed environment, the property value is specified in your Java application.

ICO0013E
javax.resource.ResourceException:
ICO0013E:methodname error.
ConnectionManager is null.

Explanation: The method indicated in methodname was invoked. The application server invoked the createConnectionFactory method of the IMSManagedConnectionFactory class with a null ConnectionManager object.

User Action: Provide a valid HostName parameter. This form of the createConnectionFactory method is used in a managed environment. It is not typically invoked by a client program. Contact the service personnel for your application server.

ICO0014E
javax.resource.ResourceException:
ICO0014E:methodname error.
Input record contains no data.

Explanation: The method indicated in methodname was invoked with an input record that contained no data.

User Action: Verify that the input record that you provide is not empty.

ICO0015E
ResourceAdapterInternalException
ICO0015E:methodname error.
Unexpected error encountered while processing the OTMA message.
[java_exception]

Explanation: An unexpected internal error was encountered while processing the OTMA message.

User Action: Contact your IBM® service representative.

ICO0016E
javax.resource.ResourceException:
ICO0016E:methodname error.
The value provided for DataStoreName is null or an empty string.

Explanation: The method indicated in methodname was invoked using an empty DatastoreName parameter. This error message will appear in the trace log when a connection factory with an empty DatastoreName parameter is started. This message will be followed by a J2EE Connector warning,

J2CA0007W: An exception occurred while invoking method setDataStoreName on 
com.ibm.connector2.ims.ico.IMSManagedConnectionFactory used by resource 
Connection_Factory_JNDI_name.
Processing will then continue leading to other error messages after IMS Connect sends a response indicating that a datastore with a null name cannot be found. The underlying message which triggers the other messages is:
javax.resource.spi.EISSystemException: ICO0001E: 
com.ibm.connector2.ims.ico.IMSTCPIPManagedConnection@.processOutputOTMAMsg(byte [],
 InteractionSpec, Record) error. IMS Connect returned error: RETCODE=[4], 
REASONCODE=[NFNDDST ].  Datastore not found.
When this error occurs, a corresponding HWSS0742W warning message is displayed on the MVS console of the host machine where IMS Connect is running. This HWSS0742W message will include a field showing the datastore name that it attempted to find, in this case all blanks:
DESTID=        ;

User Action: Provide a valid name for the DatastoreName parameter. In a managed environment, the DatastoreName is specified when you are configuring a Connection Factory to be used by WebSphere Application Server. In a non-managed environment, the DatastoreName is specified in your Java application.

ICO0017E
ResourceAdapterInternalException
ICO0017E:methodname error.
Invalid value provided for TraceLevel.

Explanation: An invalid trace level was specified.

User Action: Specify a valid trace level. Optionally, this exception can be ignored due to the fact that the default trace level will be used for this connection factory. In this case, the connection factory is still usable but the trace level will be the default trace level.

ICO0018E
javax.resource.ResourceException:
ICO0018E:methodname error.
The value provided for PortNumber is null.

Explanation: The method indicated in methodname was invoked using a null PortNumber.

User Action: Provide a valid PortNumber parameter. In a managed environment, the property value is specified when you are configuring a Connection Factory to be used by WebSphere Application Server. In a non-managed environment, the property value is specified in your Java application.

ICO0020E
javax.resource.ResourceException:
ICO0020E:methodname error.
Alternate ClientID is not supported for Interaction Verb [Interaction Verb]. 
Alternate ClientID can only be specified for Interaction Verbs SYNC_RECEIVE_ASYNCOUTPUT, 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT, and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT.

Explanation: The Interaction Verb value specified with the alternate clientID retrieve asynchronous output interaction is not valid.

User Action: Provide a valid Interaction Verb value. The Alternate ClientID can only be specified for Interaction Verbs SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT, and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT.

ICO0024E
javax.resource.ResourceException:
ICO0024E:methodname error.
Invalid segment length (LL) of [llvalue] in input object.[java_exception]

Explanation: The input message provided by the Java program for the IMS application program contains a value for its segment length which is either negative, 0, or greater than the number of bytes of data in the message segment.

User Action: Provide the correct value for the segment length of the input message.

ICO0025E
javax.resource.IllegalArgumentException:
ICO0025E:methodname error.
Invalid segment length (LL) of [llvalue] in OTMA message.

Explanation: The output message provided by the IMS application program contains a value for its segment length which is either negative, 0, or greater than the number of bytes of data in the message segment. The output message provided by the IMS application program is contained in the OTMA message.

User Action: Ensure that your IMS application program provides valid lengths for the segments of its output message.

ICO0026E
javax.resource.ResourceException:
ICO0026E:methodname error.
An error was encountered while processing the IMS message.
[source_methodname:source_exception]

Explanation: An error occurred while processing the IMS transaction input or output message. source_exception provides additional information regarding the cause of the error.

User Action: Examine source_exception for additional information regarding the cause of the error. Some suggested actions to take, based on the value of source_exception are:
  • java.io.IOException

    Error preparing input or output record. Ensure that the objects you are providing to IMS Connector for Java for use as the IMS transaction input and output are defined properly for the J2C architecture. For example, ensure that they implement the interfaces javax.resource.cci.Record and javax.resource.cci.Streamable.

  • com.ibm.ims.ico.IMSConnResourceException

    The OTMA message containing the IMS transaction output message contained an invalid length field (i.e., LLLL was <= 0). If this error continues to occur after verifying that your IMS application program is returning a valid output message, contact your IBM service representative.

  • java.lang.IllegalArgumentException

    The output message returned from IMS Connect is invalid. Ensure that the release levels of IMS Connector for Java and IMS Connect are compatible. For example, if you built a transactional required EJB application to perform a two phase commit transaction via TCP/IP by using IMS Connector for Java version 2.1, but at runtime, you are using IMS Connect version 1.2 instead of version 2.1, you will receive this error message. Hereby, either you update to IMS Connect version 2.1 or create a none global transactional EJB application.

ICO0027E
javax.resource.ResourceException: 
ICO0027E:methodname error. 
The OTMA header of the IMS output message did not contain a segment_name segment. 

Explanation: The OTMA header in the IMS transaction output message was not built properly. It did not contain the segment identified by segment_name.

User Action: Correct the problem with the way that the message header is built. An example of an situation in which this error could occur would be executing a SYNC_RETRIEVE_ASYNCHOUTPUT_WAIT (or _NOWAIT) interaction which retrieves a message which had been queued by a non-IMS Connector for Java client (e.g., a 3270 terminal interaction.) Messages queued by non-IMS Connector for Java clients will typically not have the OTMA headers required by IMS Connector for Java. To remedy this situation, ensure that IMS Connector for Java and non-IMS Connector for Java clients use separate queues for their respective asynchronous output.

ICO0028E
javax.resource.ResourceException: 
ICO0028E:methodname error. 
The Prefix flag in the OTMA header Message-Control Information segment of the 
IMS output message is not valid.

Explanation: The OTMA header fn the IMS transaction output message was not built properly. The Prefix flag in the OTMA header specified which segments are included in the OTMA header of the message, but the total length of the message (which should include both the headers and the message data) is less than the sum of the lengths of the specified headers. The total message length should be equal to or greater than the total length of the headers depending on whether or not the message contains any data, but never less than the total length of the headers.

User Action:Correct the problem with the way that the message header is built. This situation would typically be a result of either a user message incorrectly modifying the message header or an internal error in either IMS Connect or IMS Connector for Java. If your user exits are being used as shipped, without modification, or you are unable to to determine why the headers are not being built correctly, contact your IBM service representative.

ICO0030E
javax.resource.spi.ApplicationServerInternalException:
ICO0030E:methodname error.
[source_methodname:source_exception]

Explanation:A runtime error or exception was detected in methodname during the interaction. source_methodname:source_exception indicates where the error or exception that was detected in methodname originally occurred and may provide additional information regarding the cause of the error.

User Action: Examine source_exception for additional information regarding the cause of the error. The action(s) to be taken depend on the value of source_methodname:source_exception. Some suggested actions to take, based on the value of source_methodname:source_exception are:
  • java.lang.OutOfMemoryError

    This error is thrown when the Java Virtual Machine cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector. Increase the amount of memory available to the virtual machine used by WAS.

  • java.io.InterruptedIOException

    An InterruptedIOException is thrown to indicate that an input or output transfer has been terminated because the thread performing it was terminated. Investigate reasons why the thread may have been terminated.

ICO0031E
javax.resource.spi.IllegalStateException:
ICO0031E:methodname error.
Protocol violation. The Interaction Verb [interactionverb] is not allowed for 
the current state [state].
[java_exception]

Explanation: The interaction attempted by the application resulted in a protocol violation. [interactionverb] is the value of the interactionVerb property of the IMSInteractionSpec object that was used for the interaction. [state] is the current state of the protocol used for the interactions between IMS Connector for Java and IMS Connect.

For example, a protocol violation would occur if your Java program is not in conversation with IMS, but attempted an interaction with IMS using the SYNC_END_CONVERSATION value for the interactionVerb property.

User Action: Ensure that you are using an appropriate value for the interactionVerb property of IMSInteractionSpec. Check the IMS Connector for Java documentation for values of the interactionVerb property that are supported by IMS Connector for Java. A particular release of IMS Connector for Java may not support all the values defined by the J2EE Connector Architecture.

ICO0034E
javax.resource.NotSupportedException:
ICO0034E:methodname error.
Auto-commit not supported.

Explanation: Auto-commit is currently not supported by IMS Connector for Java.

User Action: Ensure that your Java application uses classes and methods that are appropriate for the level of support currently provided by IMS Connector for Java.

ICO0035E
javax.resource.NotSupportedException:
ICO0035E:methodname error.
Local Transaction not supported.

Explanation: Local Transactions are not currently supported by IMS Connector for Java.

User Action: Ensure that your Java application uses classes and methods that are appropriate for the level of support currently provided by IMS Connector for Java.

ICO0037E
javax.resource.NotSupportedException:
ICO0037E:methodname error.
ResultSet not supported.

Explanation: ResultSets are currently not supported by IMS Connector for Java.

User Action: Ensure that your Java application uses classes and methods that are appropriate for the level of support currently provided by IMS Connector for Java.

ICO0039E
javax.resource.spi.IllegalStateException:
ICO0039E:methodname error.
Not in CONNECT state.

Explanation: The sequence of interactions between IMS Connector for Java and IMS Connect is invalid. The current state of the protocol used for the interactions between IMS Connector for Java and IMS Connect is not CONNECT as it needs to be at this point in the interactions.

User Action:This is most likely an error in IMS Connector for Java or IMS Connect. Contact your IBM service representative.

ICO0040E
javax.resource.NotSupportedException:
ICO0040E:methodname error.
IMSConnector does not support this version of execute method.

Explanation: IMS Connector for Java does not support the form of the execute method that takes two input parameters and returns an object of type javax.resource.cci.Record.

User Action: Use the supported form of the execute method in class IMSInteraction. The supported form of the execute method has the following signature:

boolean execute(InteractionSpec, Record input, Record output)
ICO0041E
javax.resource.ResourceException:
ICO0041E:methodname error.
Invalid interactionSpec specified [interactionSpec].

Explanation: An invalid InteractionSpec object was passed to the execute method of class com.ibm.connector2.ims.ico.IMSInteraction.

User Action: Ensure that the InteractionSpec object that you pass to the execute method of class com.ibm.connector2.ims.ico.IMSInteraction is of type com.ibm.connector2.ims.ico.IMSInteractionSpec.

ICO0042E
javax.resource.ResourceException:
ICO0042E:  methodname error.
Input is not of type Streamable.

Explanation: The input object provided to the execute method of com.ibm.connector2.ims.ico.IMSInteraction for the "input" parameter was either null or did not implement the interface javax.resource.cci.Streamable. This exception most likely occurs when an application is written to use the J2EE Connector Architecture Common Client Interface (CCI). This exception should not occur if Rational® Application Developer is used to build the input message.

The execute method allows null input objects for some types of interactions. For example, interactions with interactionVerb values of SYNC_END_CONVERSATION and SYNC_RECEIVE_ASYNCOUTPUT allow null input objects.

User Action: Ensure that you are providing a valid javax.resource.cci.Record object for the "input" parameter to the execute method. For example, ensure that this object implements the interfaces javax.resource.cci.Record and javax.resource.cci.Streamable.

ICO0043E
javax.resource.ResourceException:
ICO0043E:  methodname error. 
Output is not of type Streamable. 

Explanation: The output object provided to the execute method of com.ibm.connector2.ims.ico.IMSInteraction was either null or did not implement the interface javax.resource.cci.Streamable. This exception most likely occurs when an application is written to use the J2EE Connector Architecture Common Client Interface (CCI). This exception should not occur if Rational Application Developer is used to build the output message.

User Action: Ensure that you are providing a valid output object to the execute method.

ICO0044E
javax.resource.NotSupportedException:
ICO0044E:methodname error.
RecordFactory is not supported by IMS Connector for Java.

Explanation: RecordFactory is currently not supported by IMS Connector for Java.

User Action: Ensure that your Java application uses classes and methods that are appropriate for the level of support currently provided by IMS Connector for Java.

ICO0045E
javax.resource.NotSupportedException:
ICO0045E:  methodname error.
Invalid type of ConnectionRequestInfo.

Explanation: An invalid ConnectionRequestInfo object was passed to an IMS Connector for Java method.

User Action: This is most likely an error in IMS Connector for Java. Contact your IBM service representative.

ICO0049E
javax.resource.NotSupportedException:
ICO0049E:methodname error.
The security credentials passed to getConnection do not match existing 
security credentials.

Explanation: The security credentials in the request do not match the security credentials of the IMSManagedConnection instance that was being used to process the request.

User Action: Contact your IBM service representative.

ICO0053E
javax.resource.ResourceException:
ICO0053E: methodname error.
Invalid clientID value. Prefix HWS is reserved by IMS Connector for Java.

Explanation: The value specified for the property clientID is invalid. The prefix 'HWS' is reserved by IMS Connector for Java.

User Action: Provide a valid value for clientID property. A valid value should follow the following rules:
  • is not a null string;
  • does not start with a blank field;
  • does not start with IMS Connector for Java reserved prefix 'HWS';
  • is 8 characters long;
  • uses valid characters A - Z, 0 - 9, and @, #, $.
ICO0054E
javax.resource.ResourceException:
ICO0054E:methodname error.
Invalid ConnectionSpec.

Explanation: IMS Connector for Java was unable to cast the connectionSpec provided for this connection to type IMSConnectionSpec. While the Common Client Interface will accept a connectionSpec object for any supported connector, IMS Connector for Java will only work with an IMSConnectionSpec or a derivative of IMSConnectionSpec as its connectionSpec.

User Action: Ensure that the connectionSpec used by your application is an IMSConnectionSpec or inherits from IMSConnectionSpec.

ICO0055E
javax.resource.ResourceException:
ICO0055E:methodname error.
Failed to cast the connection object to IMSConnection.

Explanation: IMS Connector for Java was unable to cast the connection object allocated by the ConnectionManager for this connection to type IMSConnection. IMS Connector for Java will only work with an IMSConnection or a derivative of IMSConnection as its connection object. This error might be the result of a problem with the ConnectionManager.

User Action: Please contact your IBM service representative.

ICO0056E
javax.resource.ResourceException:
ICO0056E:methodname error.
IMSConnectName is only valid for Local Option connections 
which can only be used in z/OS or OS/390.

Explanation: Setting the IMSConnectName property of an IMSManagedConnectionFactory instance is mandatory for managed connection factory to be used for Local Option connections. Furthermore, you can only use Local Option to communicate with IMS Connect if your application using IMS Connector for Java is running on the z/OS® or OS/390® platform. This exception indicates that you have a specified a value for the IMSConnectName property but your application is not running on neither the z/OS nor OS/390 platforms.

User Action: Ensure that your application using IMS Connector for Java is running on the z/OS or OS/390. Note that it is also required that your application (or more precisely, the Web server where your application is running) must be running in the same MVS image as IMS Connect. If this is not the case, for example, if you plan to run your application on a workstation platform or if the Web server where you plan to run your application is on z/OS but in a different MVS image than IMS Connect, ensure that the connection factory used by your application is set up to use TCP/IP communication.

ICO0057E
javax.resource.spi.IllegalStateException:
ICO0057E:methodname error.
Invoked with invalid connection handle.

Explanation: The application is in an illegal state: the connection handle (IMSConnection instance) used for this interaction is not valid. This could occur if the application attempted to use a connection handle for a previously used connection or the handle for the wrong connection if the application has more than one connection open.

User Action: Ensure that the application is using the currently valid IMSConnection instance for that connection.

ICO0058E
javax.resource.ResourceException:
ICO0058E:methodname error.
Interactions SYNC_SEND_RECEIVE, SYNC_SEND, SYNC_RECEIVE_ASYNCOUTPUT, 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions with Commit Mode 0 
are not supported with Local Option.

Explanation: You can use Local Option to communicate with IMS Connect only if your application using IMS Connector for Java with the selection of Commit Mode 1.

User Action: Ensure that your application using IMS Connector for Java is selected with Commit Mode 1. If you plan to run your application with Commit Mode 0, correct your application to use TCP/IP communication.

ICO0059E
javax.resource.ResourceException:
ICO0059E: methodname error.
SYNC_END_CONVERSATION interation with Commit Mode 0 is not supported.

Explanation: Interaction SYNC_END_CONVERSATION with Commit Mode0 is not supported.

User Action: IMS Connector for Java supports the interaction combination SYNC_END_CONVERSATION with Commit Mode 1, SYNC_SEND_RECEIVE with Commit Mode 0, and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAITwith Commit Mode 0.

ICO0060E
java.lang.UnsatisfiedLinkError:
ICO0060E:methodname error.
Error loading Local Option native library: libname=libraryFileName. 
[source_exception].

Explanation: The Local Option native library cannot be found in any of the directories listed in the libpath.

User Action: Ensure that the Local Option native library exists in one of the directories in the LIBPATH environment variable. If you are running IMS Connector for Java in WebSphere Application Server for z/OS and OS/390, ensure that the full name of the directory that contains the Local Option native library file is defined in the LIBPATH environment variable for your J2EE server. For more information, see "Preparing the base operating system" in the WebSphere Application Server Version 6.0 Information Center .

ICO0061E
javax.resource.ResourceException:
ICO0061E:methodname error.
Local Option runs only in z/OS and OS/390.

Explanation: You can use Local Option to communicate with IMS Connect only if your application using IMS Connector for Java is running on the z/OS or OS/390 platform.

User Action: Ensure that your application using IMS Connector for Java is running on the z/OS or OS/390. Note that it is also required that your application (or more precisely, the Web server where your application is running) must be running in the same MVS image as IMS Connect. If this is not the case, for example, if you plan to run your application on a workstation platform or if the Web server where you plan to run your application is on z/OS but in a different MVS image than IMS Connect, ensure that the connection factory used by your application is set up to use TCP/IP communication.

ICO0062E
javax.resource.ResourceException:
ICO0062E:methodname error.
Error loading Local Option native method: libfilename=libraryFileName,
methodname=nativeMethodName. [source_exception].

Explanation: The Local Option native method cannot be found.

User Action: Verify that you have the correct level of IMS Connector for Java resource adapter and Local Option native library installed on your system. Always use the version of the Local Option native library that shipped with the IMS TM resource adapter that you installed in your WebSphere Application Server for z/OS and OS/390 system. See "Prerequisites for using IMS Connector for Java" for more information.

ICO0063E
javax.resource.spi.ResourceAdapterInternalException:
ICO0063E:methodname error.
Exception thrown in native method. [source_exception].

Explanation: An internal error occurred in the Local Option native method.

User Action: Contact your IBM service representative.

ICO0064E
javax.resource.spi.SecurityException:
ICO0064E:methodname error.
Invalid security credential.

Explanation: The subject provided by WebSphere Application Server did not contain a security credential available that is supported by IMS Connector for Java.

User Action: Ensure that you have the correct level of WebSphere Application Server for z/OS and OS/390 installed. See the " Prerequisites for using IMS TM resource adapter" section for details. Configure WebSphere Application Server for z/OS and OS/390 to provide a security credential that is supported by IMS TM resource adapter. IMS TM resource adapter supports the PasswordCredential for TCP/IP connections and the UToken GenericCredential for Local Option connections.

ICO0065E
javax.resource.spi.SecurityException:
ICO0065E:methodname error.
Error obtaining credential data from the security credential.[source_exception].

Explanation: There was a security related error in obtaining the credential data from the security credential provided by the application server.

User Action: Ensure that you have correctly set up security for your application server so that the user associated with the calling program is authorized to extract the data from a security credential.

ICO0066E
javax.resource.ResourceException:
ICO0066E:methodname error. Error loading WebSphere Application Server 
Transaction Manager. [source_exception].

Explanation: An error occurred when accessing the Transaction Manager of the WebSphere Application Server for processing the transaction request.

User Action: Ensure that you have the correct level of WebSphere Application Server for z/OS and OS/390 installed. See the " Prerequisites for using IMS Connector for Java" section for details.

ICO0068E
javax.resource.ResourceException:
ICO0068E:methodname error.
Error obtaining the transaction object.  [java_exception]

Explanation: An error occurred while attempting to determine if a transaction has been started using the WebSphere Application Server Transaction Manager.

User Action: Ensure that you have the correct level of WebSphere Application Server for z/OS and OS/390 installed. See the "Prerequisites for using IMS Connector for Java" section for details.

ICO0069E
javax.resource.spi.ResourceAllocationException
ICO0069E:methodname error.
Error obtaining RRS transaction context token. 
IMSConnResourceException: RRS retcode=[rrs_routinecode].

Explanation: An unexpected internal error occurred while obtaining an RRS transaction context token for processing the global transaction.

User Action: Check the RRS job log for associated RRS error messages. For diagnostic information on the RRS return code (rrs_routinecode) see the MVS Programming: Resource Recovery manual for your release of z/OS or OS/390.

ICO0070E
javax.resource.spi.EISSystemException
ICO0070E:methodname error.
IMS Connect reported an RRS error: IMS Connect Return Code=[returncode], 
RRS Routine name=[rrs_routine], RRS Return code=[rrs_routinecode]."

Explanation: IMS Connect returned an error resulting from an RRS failure.

User Action: Check the MVS console for associated IMS Connect and RRS error messages. For diagnostic information on the return code (returncode) value, as well as IMS Connect error messages, see the IMS Connect Guide and Reference. For diagnostic information on the RRS return code (rrs_routinecode) locate the RRS routine name (rrs_routine) within the MVS Programming: Resource Recovery manual for your release of z/OS or OS/390.

ICO0071E
javax.transaction.xa.xAException
ICO0071E:methodname error.
A communication error occurred when processing the XA 
commandtype operation. [java_exception]

Explanation: There are numerous reasons why a communication failure could have occurred during the processing of a global transaction. A TCP/IP or socket failure could have taken place or IMS Connect could have been brought down. The connection in error will not be reused.

User Action: Examine the java_exception to determine the reason for the failure to connect to the host. Also check the MVS console for associated IMS Connect or TCP/IP error messages. Validate that machine can be reached through TCP/IP and that IMS Connect has not been brought down. The command type (commandtype_string) displayed in the error message refers to the stage at which this communication failure occurred during the global transaction: prepare, commit, rollback, recover, or forget.

ICO0072E
javax.transaction.xa.xAException:
ICO0072E:methodname error.
The associated UR for the Xid is not found.

Explanation: During transaction processing a UR that was tied to a specific Xid was eliminated by manual intervention or an error in IMS Connect or RRS.

User Action: Refer to the WebSphere Application Server InfoCenter Reference Library for steps on how to acquire transaction information and Xids within the WebSphere Application Server logs. Refer to the IMS Connect Guide and Reference for IMS Connect commands that will list out the Xid and their associated UR. Verify that a UR is listed for that Xid. Verify that the global transaction was not left in a heuristic state.

ICO0073E
javax.transaction.xa.xAException:
ICO0073E:methodname error.
RRS is not available.

Explanation: RRS has been brought down or communication between RRS and IMS Connect has ended.

User Action: Check the MVS console for associated IMS Connect and RRS error messages. Ensure that RRS has not been brought down on your z/OS or OS/390 system. Refer to the IMS Connect Guide and Reference for IMS Connect commands that can be used to verify that it is RRS enabled.

ICO0074E
javax.transaction.xa.xAException:
ICO0074E: The RRS rrs_routine call returns with a return code [rrs_routinecode].

Explanation: During the processing of your global transaction the following RRS error message was passed in by IMS Connect.

User Action: Check the MVS console for associated IMS Connect and RRS error messages. For diagnostic information on the RRS return code (rrs_routinecode) locate the RRS routine name (rrs_routine) within the MVS Programming: Resource Recovery manual for your release of z/OS or OS/390.

ICO0075E
javax.transaction.xa.xAException:
ICO0075E:methodname error.
The transaction branch may have been heuristically completed. [rrs_exception]

Explanation: An RRS error has been passed in by IMS Connect that indicates that the processing of your transaction may have been affected in such a way as to leave it in a heuristic situation. It reveals a possibility that part of the transaction committed and part of it encountered an error during the commit phase which may have prevented it from committing. The rrs_exception is an ICO0074E error message indicating the RRS routine and return code associated with this issue.

User Action: Refer to the documentation of the ICO0074E error for more information regarding the RRS error message. Refer to the WebSphere Application Server InfoCenter Reference Library for steps on how to acquire transaction information and Xids within the WebSphere Application Server logs. Refer to the IMS Connect Guide and Reference for IMS Connect commands that will list out the Xid and their associated UR. Determine the Xid and URs involved and the result that should have been committed to IMS. Verify values within IMS to ensure that a heuristic state has occurred. A decision must then be made to take actions to rectify the data within IMS so that it matches the result that would have been committed or to rectify the other databases involved to return to a state prior to the execution of that transaction.

ICO0076E
javax.resource.ResourceException:
ICO0076E:methodname error. An internal error occurred. [rrs_exception]

Explanation: An internal error occurred while trying to extract information about an RRS error message passed in by IMS Connect. The rrs_exception is an ICO0074E error message indicating the RRS routine and return code associated with the error.

User Action: Refer to the documentation of the ICO0074E error for more information regarding the RRS failure that has taken place. Please contact your IBM service representative.

ICO0077E
javax.resource.ResourceException:
ICO0077E:methodname error. The transaction has already rolled back. [rrs_exception]

Explanation: An RRS error has been passed in by IMS Connect that indicates the attempt to rollback a transaction has been made a second time upon the same UR. RRS will prevent the second rollback from taking place and throw an error indicating that such an action is being attempted. The rrs_exception is an ICO0074E error message indicating the RRS routine and return code associated with the error.

User Action: No action is needed as the transaction should be rolled back. Refer to the documentation of the ICO0074E error for more information regarding the RRS failure that has taken place. As a precaution, verify that data prior to the execution of the transaction has not been lost or modified.

ICO0078E
javax.resource.ResourceException:
ICO0078E: methodname error.
A valid user-specified clientID is required for interactions on a 
dedicated persistent connection.

Explanation: A valid, user-specified value is required for the clientID property when a value of 0 is specified for the commitMode property, and the interaction is using a dedicated persistent socket connection. This applies to SYNC_SEND_RECEIVE, SYNC_SEND, SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions.

User Action: Provide a valid value for the clientID property. A valid value should follow the following rules:
  • is not a null string
  • does not start with a blank field
  • does not start with IMS Connector for Java reserved prefix 'HWS'
  • is 8 characters long
  • has valid characters A - Z, 0 - 9, and @, #, $
ICO0079E
com.ibm.connector2.ims.ico.IMSDFSMessageException:
ICO0079E:methodname error.
IMS returned DFS message:DFS_message

Explanation: IMS returned the message indicated by DFS_message instead of the output of the IMS transaction. This exception is thrown if the interaction uses the value IMS_REQUEST_TYPE_IMS_TRANSACTION for the imsRequestType property of IMSInteractionSpec.

For example, if the Java application attempts to run an IMS transaction that is stopped, this exception is thrown and the value of DFS_message is
DFS065 hh:mm:ss TRAN/LTERM STOPPED

User Action: Find the explanation and response that corresponds to DFS_message in the IMS Messages and Codes documentation, then address the problem in IMS.

ICO0080E
javax.resource.spi.EISSystemException:
ICO0080E:methodname error.
Execution timeout has occurred for this interaction. The executionTimeout 
was [executionTimeout_value] milliseconds. The IMS Connect 
TIMEOUT was used.
Explanation: The time it took for IMS Connect to send a message to IMS and receive the response was greater than the IMS Connect TIMEOUT value. The IMS Connect TIMEOUT value is:
  • Specified in the IMS Connect configuration member for SYNC_SEND_RECEIVE interactions
  • Two seconds for SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT, and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions
The reason of IMS Connect TIMEOUT value has been used is the executionTimeout property for this interaction was not specified or has been set to zero.

User Action: Ensure your application has set a valid executionTimeout value. To set the executionTimeout values, you can either use WebSphere Studio or use the setExecutionTimeout method. For detail instruction, please refer to the topic of Setting execution timeout values in WebSphere Studio Application Developer Integration Edition 5.0.1 Help.

ICO0081E
javax.resource.spi.EISSystemException:
ICO0081E:methodname error.
Execution timeout has occurred for this interaction. The executionTimeout 
value specified was [executionTimeout_value] milliseconds. 
The value used by IMS Connect was 
[rounded_executionTimeout_value] milliseconds.

Explanation: The time it took for IMS Connect to send a message to IMS and receive the response was greater than the executionTimeout value that was rounded to an appropriate execution timeout interval. Once a valid execution timeout value is set, this value is converted into a value that IMS Connect can use.

User Action: If the rounded execution timeout value is not what you expected, please verify with the follow table of conversion rules:

Range of user-specified values Conversion rule
1 - 250 If the user-specified value is not divisible by 10, it is converted to the next greater increment of 10.
251 - 1000 If the user-specified value is not divisible by 50, it is converted to the next greater increment of 50.
1001 - 60000 The user-specified value is converted to the nearest increment of 1000. Values that are exactly between increments of 1000 are converted to the next greater increment of 1000.
60001 - 3600000 The user-specified value is converted to the nearest increment of 60000. Values that are exactly between increments of 60000 are converted to the next greater increment of 60000.

For more examples, please refer to the topic of Valid execution timeout values in Rational Application Developer 7.0 Help.

ICO0082E
javax.resource.NotSupportedException:
ICO0082E:methodname error.
Execution timeout has occurred for this interaction. The executionTimeout 
value of [{executionTimeout_value}] milliseconds is not supported. 
The valid range is [{executionTimeout_waitforever_flag}, 0 to 
{maximum_executionTimeout_value}] milliseconds. 
The IMS Connect TIMEOUT was used.

Explanation: The execution timeout value specified for the executionTimeout property was above or below the minimum or maximum timeout values respectively.

User Action: Ensure that your application has set a valid value for executionTimeout property. The execution timeout value is represented in milliseconds and must be a decimal integer in the range of 1 to 3600000, inclusively. Also it could be -1 if you want an interaction to run without a time limit.

ICO0083E
javax.resource.ResourceException::
ICO0083E:methodname error.
SYNC_SEND_RECEIVE, SYNC_SEND, SYNC_RECEIVE_ASYNCOUTPUT, 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions with Commit Mode 0 
are not valid within the scope of a global transaction.

Explanation: SYNC_SEND_RECEIVE, SYNC_SEND, SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions with Commit Mode 0 are not valid within the scope of a global transaction. Because currently the global transaction requires SYNC_LEVEL_SYNCPOINT and SYNC_LEVEL_SYNCPOINT only valid with Commit Mode 1.

User Action:
  • If you want to use Commit Mode 0, ensure that your application is configured as a "non-transactional" application.
  • If you want to run your interactions within the scope of a global transaction, then the commitMode property value must be 1.
ICO0084E
javax.resource.ResourceException:
ICO0084E:methodname error.
An unexpected internal IMS Connector for Java error occurred.
[source_method] [source_exception]

Explanation: A PrivelegedActionException occurred while executing a [source_method] call in methodname. This exception will occur if Java 2 security is enabled and the user associated with the calling program, methodname, or any program in the current call stack is not authorized to execute [source_method].

User Action: Ensure that you have correctly set up security for your application server so that the user associated with the calling program plus any programs in the current call stack at the time of the exception is/are authorized to execute [source_method]. Alternatively, you could turn off Java 2 security checking in the application server.

ICO0085E
javax.resource.ResourceException:
ICO0085E: methodname error.
Protocol violation. A user-specified clientID is not allowed for interactions 
on a shareable persistent socket.

Explanation: The value specified for clientID property is not allowed. Because the connection factory is configured for shareable persistent socket, a user-specified clientID is not allowed within this kind of connection factory.

User Action: For shareable persistent socket connection factory, IMS Connector for Java provides generated clientID. User-specified clientID is not allowed. To determine if you are using a shareable persistent socket, check for a value of FALSE for the CM0Dedicated property of the connection factory used by the interaction.

ICO0086E
javax.resource.ResourceException::
ICO0086E:methodname error.
Invalid value was specified for CommitMode property.

Explanation: The CommitMode value you have specified in the commitMode property field is invalid.

User Action: Ensure that your application has set a valid value for commitMode property. Values supported are:
  • Value 1 (SEND_THEN_COMMIT), indicates that IMS processes the transaction and sends a response back before committing the data.
  • Value 0 (COMMIT_THEN_SEND), indicates that IMS processes the transaction and commits the data before sending a response.
ICO0087E
javax.resource.ResourceException:
ICO0087E: methodname error.
Protocol violation. Commit Mode 1 is not allowed for interactions on a 
dedicated persistent socket.

Explanation: The value 1 specified for Commit Mode property is invalid. Because the connection factory is configured for dedicated persistent socket, Commit Mode 1 is not allowed within this kind of connection factory.

User Action: For dedicated persistent socket connection factory, Commit Mode 0 interactions are valid. To determine if you are using a dedicated persistent socket check for a value of TRUE for the CM0Dedicated property of the connection factory used by the interaction.

ICO0088E
javax.resource.ResourceException:
ICO0088E: methodname error.
Protocol violation. SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAITinteractions 
are not allowed on a shareable persistent sockets.

Explanation: The value SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAITspecified for interactionVerb property is invalid. Because the connection factory is configured for shareable persistent socket, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAITis not allowed within this kind of connection factory.

User Action: SYNC_SEND_RECEIVE, SYNC_SEND, and SYNC_END_CONVERSATION are the valid values for the interactionVerb property for interactions on a shareable persistent connection. To determine if you are using a shareable persistent connection, check for a value of FALSE for the CM0Dedicated property of the connection factory used by the interaction.

ICO0089I
javax.resource.ResourceException::
ICO0089I: methodname.
 Non-persistent socket closed for Commit Mode 0 IMS transaction.

Explanation: Running CommitMode 0 with non-persistent socket (transaction socket), IMS Connector for Java will force removal of managed connection object from Connection Pool.

User Action: This is not an error message, no action required.

ICO0091E
javax.resource.ResourceException:
ICO0091E: methodname
error.SSL client context could not be created. [{1}]
Explanation: An SSL Context could not be created due to one of the following reasons:
  • The algorithm used to check the integrity of the keystore cannot be found
  • The certificates in the keystore could not be loaded
  • The key cannot be recovered (e.g. the given password is wrong).
User Action: Ensure the following:
  • The algorithm used to create certificates must be one that is supported by IBMJSSE.
  • The passwords for the keystore and truststore are correct.
ICO0096I
javax.resource.ResourceException:
ICO0096I: methodname 
Warning. Invalid value provided for SSL parameter.

Explanation:The method indicated in methodname was invoked using a null or empty SSLKeystoreName, SSLKeystorePassword, SSLTruststoreName or SSLTruststorePassword parameter. This is an informational message to let the user know that one of the above-mentioned parameters is a null or an empty string. This will not terminate the program execution.

User Action: Provide valid values for SSLKeystoreName, SSLKeystorePassword, SSLTruststoreName and SSLTruststorePassword parameters. For convenience, private keys and certificates can be stored either in a keystore or a truststore. Therefore only one set of valid values (either SSLKeystoreName and SSLKeystorePassword or SSLTruststoreName and SSLTruststorePassword) are required for proper execution.

ICO0097E
javax.resource.ResourceException:
ICO0097E:methodname error.
{0} error. The given value is invalid for 'SSLEncryptionType'. The value must 
be 'STRONG' for strong encryption, 'WEAK' for weak (export) encryption or 
'ENULL' for null (no) encryption.

Explanation: A value other than STRONG, WEAK, or ENULL was provided for the SSLEncryptionType parameter.

User Action: Provide either STRONG, WEAK, or ENULL for the SSLEncryptionType parameter. The value is not case-sensitive.

ICO0111E
javax.resource.ResourceException:
ICO0111E:methodname error.
 SSLEnabled must be set to FALSE when using Local Option.

Explanation: The property IMSConnectName is set to a non-null value and the property SSLEnabled is set to true. However, SSL is not supported on local option connections (which is indicated by providing a value for IMSConnectName parameter).

User Action: Set SSLEnabled to false.

ICO0113E
javax.resource.spi.CommException:
ICO0113E: methodname error.
Socket Timeout has occurred for this interaction. The Socket Timeout value 
specified was [socket timeout value] milliseconds.
[source_exception:exception_reason]

Explanation: The time for IMS Connector for Java to receive a response from IMS Connect is greater than the time specified for Socket Timeout.

User Action: Ensure that the time value of Socket Timeout is sufficient for IMS Connector for Java to receive a response from IMS Connect. If it is not, increase the value. If the value of Socket Timeout given is sufficient, it is possible that network problems are causing delays. Contact your network administrator.

ICO0114E
javax.resource.ResourceException:
ICO0114E: methodname error.
The Socket Timeout Property value of [socket timeout value] is invalid.
[source_exception:exception_reason]

Explanation: The value [socket timeout value] specified for the Socket Timeout property is not valid.

User Action: Review the exception_reason provided. Ensure a positive numerical value was given for Socket Timeout.

ICO0115E
javax.resource.spi.CommException:
ICO0115E: methodname error.
A TCP Error occurred.

Explanation: This is an error in the underlying protocol.

User Action: Contact your network administrator.

ICO0117E
javax.resource.ResourceException:
ICO0117E: methodname error.
Protocol violation: Commit Mode 1 is not allowed for SYNC_SEND, 
SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT 
and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions.

Explanation: The IMS TM resource adapter currently only supports Commit Mode 0 for SYNC_SEND interactions.

User Action: Commit Mode 0 is required for SYNC_SEND, SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT , SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions. Commit Mode 1 is valid with SYNC_SEND_RECEIVE and SYNC_END_CONVERSATION interactions.

ICO0118E
javax.resource.ResourceException:
ICO0118E: methodname error.
Protocol violation. IMS request type 2(IMS_REQUEST_TYPE_IMS_COMMAND) 
is not allowed for SYNC_SEND, SYNC_END_CONVERSATION, SYNC_RECEIVE_ASYNCOUTPUT, 
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT 
interactions.

Explanation: The value 2(IMS_REQUEST_TYPE_IMS_COMMAND) specified for imsRequestType property is invalid.

User Action: ImsRequestType 2(IMS_REQUEST_TYPE_IMS_COMMAND) only valid with SYNC_SEND_RECEIVE interaction. ImsRequestType 1(IMS_REQUEST_TYPE_IMS_TRANSACTION) is required for SYNC_SEND, SYNC_END_CONVERSATION, SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions.

ICO0119E
javax.resource.ResourceException:
ICO0119E: methodname error.
A supported SSL provider was not found. [caught_exception]

Explanation: When attempting to initialize a Secure Sockets Layer TCP/IP connection with IMS Connect, IMS Connector for Java needs to use one of the two supported providers, com.ibm.jsse.JSSEProvider or sun.security.provider.Sun. This error indicates that neither of these providers is available.

User Action: com.ibm.jsse.JSSEProvider should be added by default in an IBM JVM and sun.security.provider.Sun should be added by default in a Sun JVM. Ensure that you are running IMS Connector for Java in a supported IBM JVM if running in WebSphere Application Server or a Sun JVM in other application servers.

ICO0121E
javax.resource.ResourceException:
ICO0121E: methodname error.
Invalid reRoute name value. Prefix HWS is reserved for use by 
IMS Connector for Java.

Explanation: The value specified for reRouteName property is invalid. The prefix 'HWS' is reserved for use by IMS Connector for Java.

User Action: Provide a valid value for reRouteName property. A valid value should adhere to the following rules:
  • Is not a null string
  • Does not start with a blank field
  • Does not start with the IMS Connector for Java reserved prefix 'HWS'
  • Is 8 characters long
  • Uses the valid characters A - Z, 0 - 9, @, #, and $
ICO0122E
javax.resource.ResourceException:
ICO0122E: methodname error.
Invalid reRoute value. When purgeAsyncOutput value is true, reRoute 
value cannot be true.

Explanation: The value specified for reRoute property is invalid. Because the value specified for purgeAsyncOutput property is TRUE, or the default value (TRUE) is used for purgeAsyncOutput property.

User Action: Ensure to set purgeAsyncOutput property to FALSE, if you want to set reRoute to TRUE.

ICO0123E
 javax.resource.NotSupportedException:
ICO0123E : methodname error . 
A Sync Level value of synclevel is not supported for commit-then-send 
(Commit mode 0) interactions.  

Explanation: The value specified for IMSInteractionSpec.syncLevel is not supported for commit-then-send (Commit mode 0) interactions .  Confirm (1) is the only supported value of IMSInteractionSpec.syncLevel for commit-then-send (Commit mode 0) interactions.

User Action: Specify the value Confirm (1) for the IMSInteractionSpec.syncLevel property, or accept the default Sync Level value of Confirm (1), for commit-then-send (Commit mode 0) interactions.

ICO0124E
javax.resource.ResourceException: 
ICO0124E : methodname error . 
SYNC_SEND_RECEIVE interactions with Sync Level Confirm are not supported 
with Local Option. 

Explanation: Commit-then-send (Commit Mode 0) interactions are not supported with Local Option. Send-then-commit (Commit Mode 1) interactions with Sync Level confirm (1) are not supported with Local Option.

User Action: Do not use Local Option for this functionality.

ICO0125E
javax.resource.EISSystemException: 
ICO0125E : methodname error. 
An internal error occurred. The status of the IMS transaction associated
 with this SYNC_SEND_RECEIVE interaction with Commit Mode 1 and Sync Level 
1 cannot be determined. 

Explanation:As part of the send-then-commit (Commit Mode 1) sync Level confirm (1) protocol, t he IMS TM resource adapter received an output message from the IMS transaction, sent a positive acknowledgement to IMS Connect, but received an error indication instead of the expected indication from IMS Connect that the transaction was committed.  The output message received by the IMS TM resource adapter is not returned to the application component.  The IMS transaction may or may not have been committed.

User Action:Manually determine whether the transaction was committed or aborted and perform reconciliation if necessary.

ICO0126E
javax.resource.ResourceException: 
ICO0126E : methodname error .
IMS Connect reported a Commit Mode 1 Sync Level Confirm error: IMS 
Connect Return Code=[returncode], Reason Code=[reasoncode].  reasoncode_string	

Explanation:IMS Connect returned an error. The connection in error will not be reused. reasoncode_string provides a brief description of the reasoncode, if available.

User Action: Check the MVS™ console for associated IMS Connect error messages. IMS Connect error messages begin with the characters " HWS". For diagnostic information on the return code (returncode) and reason code (reasoncode) values, as well as IMS Connect error messages, see the IMS Connect Guide and Reference.

ICO0127E
com.ibm.ims.ico.IMSIllegalStateException
ICO0127E : methodname error.
Protocol violation. The Mode [mode] is not allowed for the current state 
[state]. [exception]

Explanation: IMS Connector for Java is an illegal state.

User Action: This is most likely an error in IMS Connector for Java or IMS Connect. Contact your IBM service representative.

ICO0128E
javax.resource.NotSupportedException
ICO0128E : methodname error.
The Sync Level property value of [synclevel] given is invalid. Sync Level 
NONE (0) and Sync Level CONFIRM (1) are the only values supported by the 
setSyncLevel(int) method. 

Explanation:A non-zero or non-one value was specified as to input to the setSyncLevel(int) method.

User Action: A non-zero or non-one value was specified as to input to the setSyncLevel(int) method.

User Action: Specify either zero or one as a Sync Level property value input to the setSyncLevel(int) method.

ICO0129E
javax.resource.ResourceException:
ICO0129E:methodname error.
Specifying the Alternate ClientID is not allowed on a dedicated persistent 
connection. The Alternate ClientID value is supported on shareable persistent 
socket connections ONLY.

Explanation: The retrieval of asynchronous output using alternate clientID is supported on shareable persistent socket connections only.

User Action: Use a shareable persistent socket connection to retrieve asynchronous output with an alternate clientID.

Related tasks
Logging and tracing with the IMS TM resource adapter
Related reference
Diagnosing problems when using the IMS TM resource adapter
J2CA0056I, WLTC0017E, HWSP1445E, and HWSSL00E Error Messages

Feedback