| This table lists the fixes in Fix Pack version 7.0.0.4 |
| Fixes |
| 1 | 102877 | JR38713 | The adapter throws exception when user uses array of structures inside a nested structure
|
| Symptom: When the user uses array of structures inside a nested structure and runs a simple outbound operation, the adapter fails. |
| Resolution: Now the user can use an array of structures inside a nested structure with the adapter for an outbound operation. |
|
| 2 | 102592 | JR38393 | The adapter throws exception when user uses array of simple data types inside structures.
|
| Symptom: When the user uses array of simple data types inside structures and runs a simple outbound operation, the adapter fails. |
| Resolution: Now the user can use an array of simple data types inside structures with the adapter for an outbound operation. |
|
| 3 | 102062 | FITS:MR0906105628 | Support for CCSID in the parameters for execution of RPG and COBOL programs. And also support for DBCS characters in adapter
|
| Symptom: Currently the adapter does not support encoding for the parameters. |
| Resolution: Now the adapter supports Encoding for the parameters of RPG and COBOL programs. The adapter takes the CCSID from the data tag attribute of the PCML. For DBCS graphic-only field, the user need to provide the pure DBCS CCSID in the EMD for the Data CCSID field |
|
| 4 | 101456 | Internal | Detecting illegal XML characters in SDO DESPI of Adapters.
|
| Symptom: A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters. |
| Resolution: Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log. |
|
| 5 | 101936 | JR37522 | In the inbound operation, if BOPrefix is used adapter fails with exception
|
| Symptom: When the user uses BOPrefix and runs a simple Inbound operation, the adapter fails with exception com.ibm.websphere.sca.ServiceRuntimeException: Did not find method for native method 'emit(DataQueueName)'. |
| Resolution: Now the user can use a BOPrefix with the adapter for an inbound operation. |
|
| 6 | 102606 | JR38285 | The adapter throws exception when user uses relative reference of varaibles inside structures.
|
| Symptom: When the user uses relative reference of varaibles inside structures and runs a simple outbound operation, the adapter fails exception. |
| Resolution: Now the user can use a relative reference of varaibles inside structures with the adapter for an outbound operation. |
|
| 7 | 102564 | JR37664 | The adapter throws exception when user uses dynamic variable length array.
|
| Symptom: When the user uses dynamic variable length array and runs a simple outbound operation, the adapter fails exception. |
| Resolution: Now the user can use a dynamic variable length array with the adapter for an outbound operation. |
|
| 8 | 103446 | JR39653 | In some cases,the adapter throws exception when user uses the structure inside array of nested structures.
|
| Symptom: When the user uses the structure inside array of nested structures and runs a simple outbound operation, the adapter fails. |
| Resolution: Now the user can use the structure inside array of nested structures with the adapter for an outbound operation. |
|
| 9 | 103414 | Internal | Selecting two objects in EMD with same name, will result in NPE
|
| Symptom: When the user selects two objects with same name in the EMD, the discovery cannot be completed and will result in NPE. |
| Resolution: Now EMD validates the objects selected by the user. |
|
| 10 | 103415 | Internal | BOPrefix for RPG, COBOL and service programs does not work.
|
| Symptom: When the user selects a BOPrefix value for RPG,COBOL,Service Program, the BO name is not prefixed with that BOPrefix. |
| Resolution: Now the user can select BOPrefix, and the BO are prefixed with the BOPrefix |
|
| 11 | 103417 | Internal | If "getQueue" operation is invoked with no data present in data queue, then an exception is thrown.
|
| Symptom: When the user does an "getQueue" operation and no data is present in the Data queue, then an excepion is thrown. |
| Resolution: The adapter will let the user know that no data is present in the Data queue and exception is not thrown |
|
| 12 | 103418 | Internal | The user has to explicitly add elements to the structure to get it to work.
|
| Symptom: The user has to add elements to the structure explicitly otherwise the adapter throws an exception |
| Resolution: Now the user can run the outbound without explicitly adding elements to the structure containing simple data types. |
|
| 13 | 103419 | Internal | The adapter throws exception when the user unset the values inside structures or arrays.
|
| Symptom: When the user unset the attributes inside the structures or arrays and calls pgm operation then adapters throws exception. |
| Resolution: Now the user can unset the attributes, and the adapter works fine with out exception. |
|
| 14 | 103421 | Internal | Dynamic reference for length does not work.
|
| Symptom: When the user selects the pcml having the attribute(length) of the variable is referring to the other variable in the same structure or different structure, then its throwing the exception. |
| Resolution: Now the user can select pcml having the Dynamic reference for length, and the adapter works fine. |
|
| 15 | 102613 | JR38019 | Enable JCA timer capability for inbound polling |
| Symptom: Adapter uses a polling thread in the runtime, which will poll as per the pollperiod. The polling thread will be only submitted once and always being in the runtime environment. When there are no events for a longer duration, the polling thread will be hung and throws a warning message from the JCA container. |
| Resolution: Use JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the thread hang issue. |
|
| 16 | 103162 | JR39129 | Duplicate messages are created in the event table due to unexpected database outage. |
| Symptom: During Adapter Inbound operation, after several unplanned database outages during event processing duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. |
| Resolution: If the event is already delivered to the downstream components but the overall transaction is marked failure due to issues in downstream component, the event is deleted if no rollback is issued. |
|