Previous Fixes

The following list of problems have been addressed with previously-released fixes. These previously-released fixes are included in this cumulative fix.

Interim Fix 001 - General Fixes

• IMS Connector for Java v9.1.0.1- IMS Connector for Java v9.1.0.1 repackages IMS Connector for Java v2.2.2 into IMS v9.1.  IMS Connector for Java v2.2.2 is a Data Management tool offering shipped as a component of IMS Connect v2.2.  IMS Connector for Java v9.1.0.1 is functionally equivalent to IMS Connector for Java v2.2.2.
• IMS Connector for Java Limitations - IMS Connector for Java (also known as the IMS resource adapter) has the following limitations, which have been added to the Limitations section of the help:
  • Currently the SSL support only supports TLSV1.0 protocol, X.509 certificates, and JKS keystores.
  • Limitations of the MFS support can be found in the HowTo.html file that is installed with the run-time component of IMS Connector for Java.
  • IMS Connector for Java attempts to reconnect a socket after IMS Connect fails and is restarted. This means that most interactions will execute successfully following the restarting of IMS Connect. However, in some cases, a SYNC_SEND (send only) interaction will appear to execute successfully, but the message will not be received by IMS. This occurs when a SYNC_SEND interaction is the first interaction that attempts to use a socket after IMS Connect fails and is restarted.
• Process editor updates:
  • A correction to the transformer service support addresses incorrect generation of aggregate messages.
  • A process using a resource adapter and complex business objects occasionally would take a very long time to generate and issue an error at run time. This error has been corrected.
  • Occasionally, generation of a BPEL process using the SOAP/HTTP for IBM Web Service deployment options would fail. This interim fix corrects the problem.
  • Occasionally, if a sub process had more than one partner link type of a "my role" kind, the generate deploy code wizard would request an endpoint. This behavior has been corrected.
  • A process created with a correlation set would fail to deploy in the previous version. The problem has been corrected.
  • A message would sometimes fail to completely expand in a tree view in the editor. The problem has been corrected. 
  • Improvements have been made to syntactical error checking.
  • A null pointer exception that was thrown when generating a WSDL interface has been corrected.
  • Sometimes at the point of generating a new process, a message would be returned telling you to replace the WSDL interface. This error has been fixed.
• A correction was made to prevent an exception being occasionally thrown when code was generated by a wizard.
• When generating deploy code after building a service from a service, occasionally an error was issued. This problem has been corrected.
• An EJB deployment descriptor occasionally was generated incorrectly with an empty message selector element. This problem has been corrected.
• Several limitations have been added to the help. They include:
  • Hyphens are not supported in XSD names when a service is deployed as a SOAP service.
  • For deployment with a SOAP binding, only IBM Web Service or Apache SOAP deployment versions are supported. Apache Axis is not supported.
  • XML Schema anyType data type is not supported. The XML Schema anyType data type is not supported by the Business Integration tools. It cannot appear in the schema types which are
    to be used within the tools. Should you use anyType, this problem surfaces itself as the compilation error "Unable to resolve the class org.w3.www._2001.XMLSchema.WSIFFormatPartImpl". A workaround for this is to use the IBM Web Services tools to provide the access to the web service.
  • In a synchronous process, the Web Services Invocation Framework (WSIF) Java provider does not support Duration or Timeout expressions for EJB or Java WSDL bindings. You can work around this in one of the two following ways:
    1. Use an asynchronous process.
    2. Specify the timeout as a WSIF property.
• Generated message driven beans sometimes had some irregularities caused by invoked methods. The problem has been resolved.
• A failure sometimes occurred while importing files needed to create a service. A correction has been made.
• The Client Web Services wizard has been corrected to allow users to select any client type. Previously, you could only select a web client for WebSphere Application Server v5.1 Enterprise Edition UTE.
• Helper classes that were generated for a SOAP service occasionally appeared to handle dateTime formats incorrectly. This error has been corrected.

Cumulative Fix 002 - General Fixes

• Documentation updates have been made to the samples, tutorials, limitations and information center, including some updates based on previous tech notes.
• Corrections have been made to the process editor including correcting errors on code generation at deployment affecting Web services, SOAP and JMS bindings and applications using resource adapters. Also, there have been corrections to the activities, partner links, and staffing functions in the process editor. The transformer editor has had some improvements to ensure it generates the expected code.
• The anyType datatype is supported in complex XSD schemas.
• An error caused by a maxOccurs attribute in a sequence element has been addressed.
• Corrections have been made in the wizards responsible for code generation from Java to Web Services Description Language (WSDL) and vice-versa.
• Generated message classes conform to the JavaBeans specification so that they are compatible with frameworks like JavaServer Faces (JSF).
• This cumulative fix contains WebSphere Studio Application Developer v5.1.2 interim fix 006. This fix includes interim fixes 002, 003 and 005 for WebSphere Studio Application Developer v5.1.2.

Cumulative Fix 003 - General Fixes

• Process editor improvements:
  • A correction has been made to better handle complex types.
  • The transformer service has been updated to correct a possible error when transforming structures containing multi-dimensional arrays.
  • Occasionally importing a message into the transformer service failed. This problem has been resolved. 
• Code generation would sometimes fail to create necessary helper classes. This error has been corrected.
• A correction has been made to the code generation of a CICS service to correct a possible code page error.

Cumulative Fix 004 - Process Editor and Runtime Fixes

• Process editor improvements:
  • Periodic code generation failures linked to SOAP and JMS interfaces have been corrected by this cumulative fix.
  • Occasionally when transforming a service with multi-dimensional arrays, the service would appear incorrectly formed in the editor. This problem has been fixed.
  • A clarification has been made to the documentation to specify how the start time property of a process is determined. A limitation has been made on using nested fault handlers.
• Runtime corrections:
  • An enterprise service running over Apache SOAP would sometimes fail when invoked because of incorrect code generation at development time and an incorrect interpretation of the dot ('.') character in the schema name. These errors have been corrected. After this cumulative fix has been applied, you will need to regenerate the helper classes of your enterprise service. Also, see the Prerequisite section for a runtime fix that must be applied.
  • Multiple Web Services Invocation Framework (WSIF) exceptions were on occasion thrown while invoking the same Transformer service through a Java proxy, in a threaded environment. This error has been corrected. You will need to regenerate the proxy class of the transformer service after applying this cumulative fix. Also, see the Prerequisite section for a runtime fix that must be applied.
  • The invocation of a Transformer service would not transform any data, if a message and its part name in the WSDL file were identical. The generation of incorrect helper classes by the Transformer service has been addressed. After this cumulative fix has been applied, you will need to regenerate the helper classes of your Transformer service. Also, see the Prerequisite section for a runtime fix that must be applied.
• A documentation update to the WebSphere Business Integration Server Foundation help has been made.
• Services created with Container Managed Persistence (CMP) beans would sometimes find missing methods in the generated CMP bean. This error has been fixed.

Note: This cumulative fix supports WebSphere Business Integration Server Foundation Cumulative Fix 1. If you have not done so, it is recommended you update your application server to this level, as your newly developed applications on this cumulative fix will be based on this runtime level.

Several fixes require runtime fix PQ99981. It can be found by searching APARs on the WebSphere Application Server Support page.

Cumulative Fix 005 - Code Fixes

• Several corrections to WebSphere Studio Application Developer, which is included in WebSphere Studio Application Developer Integration Edition, have been added to this cumulative fix. Specifically, APARs: JR21184, JR21185 and JR21186. 
• Process editor improvements:
  • When a transformer service was created from within the process editor, the location URI of the Web Services Description Language (WSDL) file import statement was incorrect, if its location in the file system was different than that of the transformer service WSDL file. This error would cause the execution of the transformer service to fail at run time. The incorrect location URI started with "/resource/...". This problem has been corrected. After this cumulative fix has been applied, you will need to either manually correct the import statement, or recreate the transformer service from scratch. This problem did not exist if the transformer service was created from the 'New > Business Integration > Transformer Service' wizard.
  • An extra closing bracket '}' at the end of a Java snippet led to the loss of Java code upon invoking the save function. A correction has been made to this behavior. APAR JR20890. 
  • When a fault was added to the interface WSDL file of a long running Business Process Execution Language (BPEL) process and the deployment code regenerated, the regenerated code was missing some binding information. This problem has been corrected.  
• Editing a BPE Deployment Descriptor file led to the generation of an incorrect .project file. The problem has been fixed.

Cumulative Fix 006 - Code and Documentation Fixes

IMS Connector Update

This update applies maintenance to both IMS resource adapters included in WebSphere Studio Application Developer Integration Edition. After applying the update, the IMS resource adapters included in WebSphere Studio Application Developer Integration Edition will be:

• IMS Connector for Java Version 2.2.3
• IMS Connector for Java Version 9.1.0.1.1

This update adds the following new function to both IMS resource adapters:

• Control of whether undelivered output for commit mode 0 interactions on shareable persistent socket connections is queued or discarded. This function is controlled by the purgeAsyncOutput property of IMSInteractionSpec.
• Support for the retrieval of undelivered output on shareable persistent socket connections, as long as the SYNC_RECEIVE_ASYNCOUTPUT interaction is in the same application as the interaction that queued the output.
• The option to provide the name of a destination for undelivered output for commit mode 0 interactions on shareable persistent socket connections. This function is controlled by the reRoute and reRouteName properties of IMSInteractionSpec.
• Enhanced control of the retrieval of undelivered output with the introduction of two new interaction verbs: SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT.
• Support for the use of RACF keyrings as SSL keystores and truststores.

In addition, the following classes are deprecated in IMS Connector for Java Version 2.2.3 and IMS Connector for Java Version 9.1.0.1.1:

• IMSCCIRecord

The functions provided by this class are now available in the development environments, WebSphere Studio Application Developer Integration Edition and Rational Application Developer. For more information, see "How to build a Java application that uses the J2EE Connector Architecture Common Client Interface" in the "IMS Examples Exchange" on the IMS web site: http://www.ibm.com/ims and "Using IMS data bindings in a CCI application" in the online help for the IMS resource adapter in Rational Application Developer.
 
• IMSConversationalHelper

In the future this class will only be available as a sample class. It is recommended that you obtain it from the "IMS Examples Exchange" on the IMS web site: http://www.ibm.com/ims.  Additional versions, using other types of input and output messages, will be made available over time.

Limitations and known problems with IMS Connector Update

• TCP/IP and Local Option Connections

The new function added by this update is supported for TCP/IP connections between IMS Connector for Java and IMS Connect.  However, it is not available until the dependent APARs are available for IMS Connect and IMS.  They are PK03622 and PK03623 for IMS Connect versions 2.2 and 9.1 respectively. For IMS version 8 they are PK00894 and PK00376. For IMS version 9 they are PK00895 and PK03377. See the IMS web site, http://www.ibm.com/ims, for more information about these APARs.

The new function added by this update is not available for Local Option connections between IMS Connector for Java and IMS Connect.
 

• Output cannot be retrieved using IMS Connector for Java application

In order to allow retrieval of undelivered output on shareable persistent socket connections using   SYNC_RECEIVE_ASYNCOUTPUT interactions in the same application, IMS Connector for Java allows a value of FALSE for both the purgeAsyncOutput property and the reRoute property of IMSInteractionSpec. If, however, the SYNC_RECEIVE_ASYNCOUTPUT interaction does not successfully retrieve the output in the application that queued the output, the undelivered output will remain queued on the OTMA TPIPE whose name is that of the shareable persistent socket connection.  This output cannot be retrieved using an IMS Connector for Java application, hence care must be used when setting both purgeAsyncOutput and reRoute to FALSE.
 
• WebSphere Application Server for z/OS servant restarts may restart if executionTimeout property is "wait forever"

In WebSphere Application Server for z/OS application work is dispatched into servants, which is, by default, timed.  In general, when an application in dispatch reaches its timeout, the servant where it is dispatched is abended and then restarted.  For this reason, it is strongly recommended that you do not use the value -1 ("wait forever") for executionTimeout when your application is running in WebSphere Application Server for z/OS.
 
• Properties purgeAsyncOutput and reRoute ignored for dedicated persistent socket connections

The IMSInteractionSpec properties purgeAsyncOutput and reRoute are not applicable for interactions on dedicated persistent socket connections. You cannot purge or reroute undelivered output messages on a dedicated persistent socket connection. If, however, you perform an interaction on a dedicated persistent socket connection and provide values for purgeAsyncOutput and reRoute, the values will be ignored by IMS Connector for Java. Your Java application will not receive an exception.

Process Editor

• Modifying a Java snippet would sometimes generate errors.  This problem has been addressed. APAR JR21492, JR21575.
• A WSDL file with a file type of .WSDL, that is, in uppercase, would sometimes generate an error when dragged on to the canvas of the process editor. A correction has been made to allow this type of file.
• A join failure fault would sometimes be issued when an activity type was changed to empty or assign. This error has been addressed.
• Corrections have been made to correct a stack overflow error and a performance problem on deployment of a BPEL process. APAR JR21563, JR21584.  
• Renaming a process would occasionally generate an error. A correction has been made for it. APAR JR21593.

Enterprise Services

• The "Service built from" wizard would occasionally stop in the midst of processing the generation of WSDL files from a Java application. This error has been corrected.

Batch Importer

• When importing COBOL using the batch importer, occasionally there were incorrect namespaces for the generated files. This error has been corrected. APAR JR21587. 
• The Batch Importer sometimes did not generate a necessary WSDL file. This error has been corrected. APAR JR21587.

Documentation Updates

• In the process editor documentation, a limitation has been placed on deployment of an IBM Web Services process, a correction to structured activities has been made and a maximum value has been set on the value of a duration. APAR JR21360, JR21475.  
• A correction has been made to the Batch Importer syntax.
• New IMSInteractionSpec properties have been added.

WebSphere Studio Application Developer Updates

• WebSphere Studio Application Developer, included with WebSphere Studio Application Developer Integration Edition, released interim fix 007. This interim fix has been added to the cumulative fix. 

Runtime Support Updates

• WebSphere Business Integration Server Foundation, which the test environment is based on, has added some fixes to its run time. Tools in WebSphere Studio Application Developer Integration Edition have been updated to support these runtime fixes. To take advantage of these updates to the tools, you will of course also need to update your run time, if you have not done so. To update your run time, add Cumulative Fix 1. 

Cumulative Fix 007 - Code Fix

• An update to WebSphere Studio Application Developer, which was included in WebSphere Studio Application Developer Integration Edition v5.1.1 cumulative fix 006, caused XSD beans to fail on generation. A subsequent correction (APAR JR21735) has been added to this cumulative fix to address the problem.  

Cumulative Fix 008 - Code and Documentation Fixes

Process Editor

• An assign activity would sometimes display its implementation incorrectly. The error has been corrected. (APAR JR21849)
• A missing description of a business process role was added to the documentation. (APAR JR21530)

Limitations 

• Limitations for using complex schemas and schema types in BPEL processes has had some additional restrictions added. (APAR JR21746)
• A limitation has been added specifying the exact location of all imports and includes that are involved in processes deployed as Web services. (APAR JR21824)
• A limitation has been added with respect to a schema making an XSD choice determined at run time. (APAR JR21877)

IMS

This update applies maintenance to both IMS resource adapters included in WebSphere Studio Application Developer Integration Edition. After applying the update, the IMS resource adapters included in WebSphere Studio Application Developer Integration Edition will be:

• IMS Connector for Java Version 2.2.4
• IMS Connector for Java Version 9.1.0.1.2

This update includes the following modifications to both IMS resource adapters:

• Provides support for the execute method with three parameters (IMSInteractionSpec, Input Record, Output Record) for SYNC_SEND interactions.
• Throws an exception containing message ICO0007E when reRoute property is set to TRUE on a dedicated persistent socket connection.
• Ensures that a "DFS" message from IMS is internally acknowledged by IMS Connector for Java so that subsequent interactions, following the "DFS" message, will not receive a java.lang.IllegalArgumentException containing the ICO0026E message. 
• Resets the value of the internal clientID used by IMS Connector for Java following the exception containing the message ICO0085E.  The exception containing message ICO0085E is thrown when an application provides a a user-specified clientID for an interaction on a shareable persistent socket connection.  Prior to this update, the clientID value would persist until the application was restarted.  
• Ensures that the socket connection remains open after an invalid value is detected for the LL field of the input message.
• Corrects a null pointer exception in tracing.
• Throws an exception containing message ICO0056E when a value is specified for the IMSConnectName property but IMS Connector for Java is not running on the 390 platform. If a value is specified for the IMSConnectName property and IMS Connector for Java is running in an OS/390 or z/OS environment, IMS Connector for Java will attempt to create a Local Option connection. If IMS Connector for Java is not running in an OS/390 or z/OS environment, the ICO0056E exception will be logged by the application server but the interaction will continue and IMS Connector for Java will attempt to create a TCP/IP connection using default hostname and port values.