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

IMSConversationalHelper

Limitations and known problems with IMS Connector Update

TCP/IP and Local Option Connections

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

WebSphere Application Server for z/OS servant restarts may restart if executionTimeout property is "wait forever"

Properties purgeAsyncOutput and reRoute ignored for dedicated persistent socket connections

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

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.

Cumulative Fix 009 - Code and Documentation Fixes

Process Editor

The Fault Variable field sometimes failed to appear after a Fault Handler and Catch entry were created. The field now appears.
A correction has been made to allow a flow diagram to be printed properly.
Saving a BPEL file after it had been deployed could generate errors. The problem has been fixed. (APAR JR21940)
On a Japanese version, BPEL files could sometimes not be saved after creating a Java snippet. The problem has been addressed. (APAR JR21919)
Unexpected Java snippet code displayed when copying is no longer a problem. (APAR JR22261)
A correction has been made so that extra line control characters no longer appear in a Java snippet.
Incorrect code generation of BPEL processes with JMS bindings sometimes occurred. The problem has been addressed. (APAR JR22106)
In the implementation tab of a staff activity, sometimes a WSDL file name, which described an operation, failed to appear. This error has been fixed. (APAR JR22247)
Dragging and dropping activities into a while activity occasionally produced linking errors. The problem has been addressed. (APAR JR22091)
In the regeneration of a Java bean from a BPEL process, sometimes errors occurred if changes had been made to a complex type used in the WSDL files. A correction has been made. (APAR JR22192)
A correction has been made so that dragging and dropping an activity into the process editor while align flow contents automatically was selected behaves properly. (APAR JR22258)
After editing the client properties of a staff activity, the regenerated deploy code of the process would sometimes fail. The error has been corrected. (APAR JR22238)
The generation of a BPEL process could fail with a naming collision if a complex type had a suffix "Element" and there was another complex type with the same name but without this suffix. The problem has been addressed.

General Fixes

After creating a service project, compilation errors could occur if folders were nested beneath the src folder. This problem has been addressed. (APAR JR21889)
An incorrect Java security error could be caused when using a CICS ECI resource adapter. The error has been fixed. (APAR JR22255)
Message-driven beans (MDBs) created by WebSphere Studio Application Developer Integration Edition could under certain conditions issue an exception on a database used internally by the product. The problem has been corrected. (APAR JR22246)

Documentation

In a previous WSAD technote, it was not clear to WebSphere Studio Developer Integration Edition customers that the integration test environment must be selected. This has been corrected. (APAR JR21937)
The Format Handling section has added an explanation of how generated input and output beans extend the com.ibm.wsif.format.jca.WSIFFormatPartImpl class and may be coupled with a FormatHandler.

WebSphere Studio Application Developer Updates

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

In addition, you should update the run time with the APAR PK08581.

WebSphere Business Integration Server Foundation Updates

This cumulative fix supports WebSphere Business Integration Server Foundation Cumulative Fix 2. 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.

Additional APARs in WebSphere Business Integration Server Foundation that this cumulative supports are: IY75617, IY75320, IY75325, IY75078, IY71565, IY73737, IY70548. Like WebSphere Studio Application Developer Integration Edition, these APARs are cumulative fixes, so one to the left of another such as IY75617 contains those after it.

Cumulative Fix 010 - Code Fixes

Deploy code with JMS bindings would under some circumstances fail to generate format handlers. The error has been corrected.
An improvement has been made to the initialization of formatHandlers used for JMS text, Transformer, COBOL, and C serialization. The formatHandlers need to be regenerated to take advantage of this improvement. (APAR JR22325)

Cumulative Fix 011 - Code and Documentation Fixes

IMS resource adapter

This update applies maintenance to both IMS resource adapters included in WebSphere Studio Application Developer Integrated Edition. After applying the update

IMS Connector for Java Version 9.1.0.1.2 will become IMS Connector for Java Version 9.1.0.1.3
IMS Connector for Java Version 2.2.4 will become IMS Connector for Java Version 2.2.5

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

Provides enhancements to reroute support:
- Allows the secondary output messages from a program-to-program switch that was spawned by a commit mode 0, SYNC_SEND_RECEIVE interaction to be queued on the TPIPE associated with the reroute destination.
- Allows the secondary output messages from a commit mode 0 interaction with multiple output messages to be queued on the TPIPE associated with the reroute destination.
- Allows undelivered messages from OTMA to IMS Connect to be queued on the TPIPE associated with the reroute destination.
Provides enhancements to Socket Timeout support:
- Ensures the socket is always disconnected when Socket Timeout occurs.
- Enhances trace with Socket Timeout listed among interactionSpec properties for analysis.
Ensures that leading and trailing blanks of the value specified for reRouteName property are removed by IMS Connector for Java internally, so that an error message ICO0009E exception will no longer be thrown when reRouteName field contains one or more blanks in front or at the end of a valid value, or when the reRouteName field contains one or more blanks without a valid value.
Eliminates a NullPointerException when an interaction on a shareable persistent socket (with no clientID value specified) was run after a successful interaction on a dedicated persistent socket (with clientID value specified).
Updates the default values of InteractionSpec properties: reRouteName, ltermName and mapName to null string instead of 8 blanks.
Eliminates a ClassNotFoundException for class com.ibm.ejs.j2c.ThreadIdentitySecurityHelper when the user attempts to use a Local Option connection when running on a distributed platform. This situation can occur if the user inadvertently provides a value for the IMSManagedConnectionFactory IMSConnectName property.
Eliminates ICO0085E exception when an interaction on a shareable persistent socket without clientID value specified was run after an interaction with clientID value specified.

Note: In many cases updates to the IMS resource adapter may require prerequisite APARs for IMS Connect and IMS. For information about prerequisite APARs, see the IMS Family Web site.

Process editor

Dragging and dropping a transformer service onto the canvas of the process editor could under some conditions lead to problems with the aggregation function. A fix corrects this problem.
When specifying a variable for a catch block in a fault handler, the result was a variable with an incorrect type. A correction has been made to provide the right type. (APAR JR22777)

Code generation

If you applied cumulative fix 010 for an improvement to the initialization of formatHandlers, the format handler generation for multiple possible output services was incorrect, and the code would not compile. This error has been addressed. The formatHandlers need to be regenerated to remove the compilation error. (APAR JR22902)
An array in C with exactly one element would cause the format handler generation to fail. The problem has been fixed.
Format handlers generated for SOAP services were not handling the lexical values for a boolean data type correctly. Specifically the lexical values '0' and '1' were not being recognized. This error has been fixed. The formatHandlers need to be regenerated in order to take advantage of this fix.

Deployment

A WSDL file containing more than one service could, on generating deploy code, overwrite part of the EJB deployment descriptor file. The error has been addressed. (APAR JR22546)

Documentation

In the human task editor documentation, the starter role has been clarified. (APAR JR21530)
In the limitations section for deploying business integration applications, a clarification has been made about deploying BPEL long running processes to a running test server.

WebSphere Business Integration Server Foundation Updates

This cumulative fix supports WebSphere Business Integration Server Foundation Cumulative Fix 3. 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.

Cumulative Fix 012 - Code and Documentation Fixes

This update applies an enhancement to MFS Web Services plugins included in WebSphere Studio Application Developer Integrated Edition. This enhancement provides additional MFS attributes fields and extended attributes fields in the Web service schema definition. A client application can now access the display information for each application data field. The supported attribute fields are modified, protected, intensity, and numeric. The supported extended attribute fields are color, underline highlighting, and outlining.
The CICS CTG RAR files have been updated to address these APARs.
- PK17700 - CICS TG GETCREDENTIALS() CALL POLICES PASSWORD PREVENTING USE OF ATTACHSEC=IDENTIFY - When a connection is specified in CICS with ATTACHSEC=Identify, a bug in the CICS TG does not allow the use of a null password. Since a 'null' password is a valid password as we only require the userid, this APAR has fixed the bug.
- PK18268 - ERROR IN CICSFRAME.JAR CAN CAUSE APPLICATION TO REQUEST TOO MANY CONNECTIONS - When specifying an ECIConnectionSpec of the format new ECIConnectionSpec(a, b) where a and b are variables, each individual call made will be in its own separate Unit of Work - these calls should be made under one unit of work. When a and b are set to be explicit strings (ie new ConnectionSpec("stringa", "stringb") ) the calls work as expected and all calls occur under one Unit of Work. This APAR provides a fix that allows either an explicit String or a variable to be used in the ConnectionSpec constructor.
- PK18552 - ECI RESOURCE ADAPTER NEEDS TO RUN WITH WRITE PERMISSION, WHICH CAN BE A SECURITY ISSUE - Running with Java2 Security enabled, the CICS TG requires read and write permissions for the "PropertyPermission". This was felt to be unnecessary since the CICS TG does not write out to the system properties. This APAR removes the need for the 'write' security permission, only 'read' is required.
When a server project was included in the workspace a rebuild of the project in WebSphere Integration Developer led to performance degradation. The problem has been addressed (APAR JR22971).
Format handlers were not correctly handling the case of a null array element. The problem has been addressed. The format handlers need to be regenerated in order to take advantage of this fix (APAR JR23345).
The Java snippet editor could sometimes hang when editing a Java snippet. This problem has been fixed.
An update has been made to the process editor documentation to correctly define the meaning of the "Continue on Error" property used in activities.
A WebSphere Studio Application Developer v5.1.2 interim fix to correct the logging utility has been added.

Cumulative Fix 013 - Code Fixes

New IMS RAR files (imsico225a.rar and imsico91013a.rar) have been added and the wizards to support them updated.
Updates to the IMS TM resource adapter have been made:
- It has been determined that the current retry function in IMS Connector for Java, which was implemented at the interaction level, could lead to duplicate interactions in cases where a request was submitted to IMS and executed, but the output was prevented from being delivered to IMS Connector for Java. If in this situation, IMS Connector for Java received a connection error while waiting for the response, IMS Connector for Java would retry the interaction. This could lead to duplicate interactions being processed in IMS. To eliminate this possibility, the current interaction-based retry function has been disabled in this maintenance release.
- If IMS Connector for Java receives a response and is notified that there is additional (secondary) output available to be received, since IMS Connector for Java is only able to return one output message per interaction, IMS Connector for Java will NAK all secondary output causing it to be placed on the OTMA hold queue before returning the first response that it received. If an error occurs while IMS Connector for Java is NAKing the secondary output, IMS Connector for Java will currently discard the original output and return an exception to the client containing that error. As a result, the original output will be lost and is not recoverable. This problem has been fixed in this maintenance release by changing IMS Connector for Java's behavior in this situation such that IMS Connector for Java will now return the original output message and ignore the error that occurred while NAKing the secondary output. The undelivered secondary output will continue to be routed to the OTMA hold queue.
- If an application tries to retrieve an output message using the SYNC_RECEIVE_ASYNCOUTPUT interaction and that message originated from a non-OTMA client (e.g., a 3270 terminal rather than an IMS Connector for Java-based client application,) it will instead receive an "ICO0026E: com.ibm.ims.ico.IMSOutputOTMAMsg@2637e2ea.setMsg(byte[]) error." instead of the message. This could happen if a non-OTMA client starts an IMS application that in turn does an ISRT to an ALTPCB. When the IMS Connector for Java-based client application tries to retrieve the message, OTMA adds the "Control", "State", and "Security" segments to the message header. Then, the DFSYDRU0 exit is supposed to add the "User Data" segment to the message header. If it does not, IMS Connector for Java will throw the above exception since IMS Connector for Java depends on the User Data segment being present. With this fix, IMS Connector for Java will now throw a more meaningful exception: "ICO0027E: com.ibm.ims.ico.IMSOutputOTMAMsg@xxxxxxxx.setMsg(byte[]) error. The OTMA header of the IMS output message did not contain a USER DATA segment."
- If you are executing a two-phase commit transaction using a shareable IMS connection, the proper security credentials may not be used. If you pass "UserA" in the IMSConnectionSpec when first getting a connection, that ID is used as expected. If in your CCI application, you do not close ConnectionA, but then get a new connection with "UserB" specified in the IMSConnectionSpec, ConnectionB will correctly use the security credentials of "UserB". However, if your CCI application then goes back and uses ConnnectionA again (since it was not closed,) ConnectionA will now be using the credentials of "UserB". To fix this problem, the IMSConnectionRequestInfo.equals() method has changed so that it checks that the username and password of a candidate IMSConnectionRequestInfo to check if they match the values needed for the current interaction. This ensures that, when an application requests a connection with "UserB" in the IMSConnectionSpec as described in the example in the previous paragraph, a connection handle to a new IMSManagedConnection object will be returned, and there will be no sharing since the existing connection in the pool has "UserA" in the IMSConnectionSpec. The new IMSManagedConnection object will correctly carry the credentials of "UserB". If the application then goes back and tries to re-use the connection which has "UserA" in the IMSConnectionSpec, it will get the original connection with the correct security credentials for "UserA."
- The execute method (of the IMSInteraction class) which takes two parameters, an IMSInteractionSpec and an input Record, has been deprecated in this maintenance release. The execute method which takes an IMSInteractionSpec and both an input Record and an output record as parameters has not been deprecated. This was done to prevent CCI applications from inadvertently using the execute method which does not have an output record for interactions that return output.
A SOAP exception could be thrown by WebSphere Application Server v6 at run time, which was caused by a change in cumulative fix 004 to correct the incorrect interpretation of the dot ('.') character in the schema name. A correction has been made. After this cumulative fix has been applied, you will need to regenerate the helper classes of your enterprise service.
WebSphere Studio Application Developer, included with WebSphere Studio Application Developer Integration Edition, released interim fix 009. This interim fix has been added to the cumulative fix.