Diagnosing IVP failures

If an error occurs when you run the IMS™ TM resource adapter IVP, first check for information in WebSphere® Application Server logs.

The WebSphere Application Server logs are located under WebSphere_install_directory\AppServer\logs. The trace.log file lists exceptions and provides stack traces that are useful for diagnosing the failure.

The following problems are possible causes for IVP failures:
  • WebSphere Application Server is not started properly.
  • If you receive the following ResourceException error about not finding the RAR reference in the context in a cluster environment, ensure that you have created a copy of the RAR file with the appropriate cluster or server scope, in addition to installing the RAR at the node level.
    Error 500: javax.resource.ResourceException: Context: myCell/clusters/myCluster1, name: myIMSTMRARef: First component in name myIMSTMRARef not found. 
  • The enterprise application for the IVP, IMSICOIVPServiceEAR, is not started. To determine the status of the enterprise application:
    1. In the WebSphere Application Server administrative console, expand Applications in the navigation tree on the left pane of the console.
    2. Click the Enterprise Applications link. The IMSICOIVPServiceEAR EAR file displays as one of the installed applications. A green arrow indicates that the application is started. If the application is not started, follow the instructions for starting the application in the topic on Deploying the IVP EAR file in the Java EE application server.
  • Invalid data was specified when you configured the connection factory. For example:
    • The host name is misspelled or is not sufficiently qualified (for TCP/IP communication).
    • An incorrect port number was specified for the target IMS Connect (for TCP/IP communication).
    • The IMS Connect name was misspelled.
    • The data store name is invalid for the target IMS or was misspelled. The data store name must be in uppercase characters.
  • IMS is not running.
  • IMS Connect is not running.
  • The IMS Connect port is not active. Use the IMS Connect command VIEWHWS to determine if the port is active. Use the IMS Connect command OPENPORT to activate an IMS Connect port.
  • The target IMS data store is not active. Use the IMS Connect command VIEWHWS to determine if the data store is active. Use the IMS Connect command OPENDS to activate a IMS data store.
  • TCP/IP fails. Issue the ping command before you run the IVP to ensure the connection is working.
  • The wrong level of IMS Connect is running on the host. See Prerequisites for running the IVP for the required level of IMS Connect.
  • If you expect the IVP to return the message DFS058I hh:mm:ss START COMMAND COMPLETED, but the message DFS1292E SECURITY VIOLATION is returned instead, check for the conditions:
    • The username and password that you provided in the custom properties of your IVP connection factory are not authorized to run the /STA OTMA command that the IVP issues to IMS.
    • Security is not enabled in IMS Connect (RACF=Y in the VIEWHWS command output).
    • Security is not enabled in IMS OTMA (SECURITY=FULL in the /DIS OTMA command output).
  • If you receive the following exception, you must configure the connection factory that is used by the IVP to set the value of the CM0Dedicated property to false.
    javax.resource.ResourceException: ICO0087E: 
    com.ibm.connector2.ims.ico.IMSTCPIPManagedConnection@28f39301.call(Connection, 
    InteractionSpec, Record, Record) error. Protocol violation. Commit Mode 1 is not 
    allowed for interactions on a dedicated persistent socket