Release Notes
Abstract
Release Notes for IBM Financial Transaction Manager V3.2.0
Content
Before installation
System requirements
Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For more information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
Downloading the product:
If you are downloading IBM Financial Transaction Manager from Passport Advantage, see Downloading IBM Financial Transaction Manager.
Product documentation
For more information about any tasks you must complete before you install FTM, see the FTM online documentation. The online product documentation is in IBM Documentation.
IBM Financial Transaction Manager for Multiplatforms documentation.
Support
Defects:
These release notes might contain references to defect numbers. These numbers refer to internal IBM problem numbers that you might find useful when you are discussing problems with your IBM service representative.
Technotes:
For more information about available fixes, see the IBM support web page.
To find the information, go to Downloads and then enter the product name. This web page provides links to the latest available maintenance for the in-service IBM Financial Transaction Manager family of products.
Feature updates
To learn about the new features in IBM Financial Transaction Manager, see the following topic in the FTM online documentation: What's new in FTM
Known issues
This section outlines the known issues and their workarounds (if any).
Issue 1
Users Affected: Customers that use IBM WebSphere Transformation Extender version 8.4.1.2.
Summary:
Customers that use IBM WebSphere Transformation Extender version 8.4.1.2 who use native schema and choice sequence iterations are unable to access iterations of a particular sequence group.
Resolution:
The fix for this issue (APAR PI31636) is available in WebSphere Transformation Extender version 8.4.1.3.
Issue 2
Users Affected: Customers that use IBM Integration Bus version 9.0.0.x.
Summary:
Customers that use IBM Integration Bus version 9.0.0.x might experience the following BIP2930E error when the broker is deployed or restarted.
RecoverableException BIP2930E: A function or procedure was called but the value supplied for the ''cAppVer'' parameter was of type ''BOOLEAN'' but the function/procedure expects value of type ''CHARACTER'' Functions and procedures require an exact matching between the data type of values supplied as parameters and the data type in its definition.
Resolution:
The fix for this issue (Integration Bus APAR IT06286) is available in IBM Integration Bus maintenance level 9.0.0.4.
Issue 3
Users Affected: Customers that use IBM Integration Bus version 9.0.0.3.
Summary:
Customers that use IBM Integration Bus version 9.0.0.3 might experience the following BIP2503E error when they run customer flows if the flow propagates from a node after exiting a FOR loop acting on a shared variable.
RecoverableException BIP2503E: Propagate with a SHARED variable lock held by FOR statement.
Resolution:
The fix for this issue (Integration Bus APAR IT07974) is available in IBM Integration Bus maintenance level 9.0.0.4.
Issue 4
Users Affected: Customers that use IBM Integration Bus version 9.0.0.5.
Summary:
Customers that use IBM Integration Bus version 9.0.0.5 might experience the following issue:
If a user has a REFERENCE variable declared at the module or schema level that points at either OutputRoot, OutputLocalEnvironment, or OutputExceptionList and does a PROPAGATE without specifying DELETE NONE in a compute node, it is not defined what the REFERENCE variable is left pointing at. After the PROPAGATE, the output trees are deleted and the REFERENCE variables should be reset to point at the root of the newly created trees. The module and schema level reference variables are not being reset and are left to point at the original syntax element that they were pointing at. The original syntax element will now have been reset, which can lead to unexpected results.
Resolution:
The fix for this issue (Integration Bus APAR IT14426) is available in IBM Integration Bus maintenance level 9.0.0.6.
Issue 5
Users Affected: Customers that use any broker level beginning with version 7.x.
Summary:
Customers that use any broker level version 7.x or later might experience inconsistent validation results when FTM Channel based validation, Integration Bus in ESQL parser validation, or both, are used.
Resolution:
The fix for this issue (Integration Bus APAR IT14075) is available in IBM Integration Bus maintenance levels 8.0.0.8, 9.0.0.6 and 10.0.0.5
Issue 6
Users Affected: Customers that use Oracle Database version 11.x and later.
Summary:
FTM (with Oracle) users might experience the following issues when they use the Multi Row Insert(MRI) function: "ORA-00932 inconsistent datatypes: expected NUMBER got TIMESTAMP" "ORA-01400 cannot insert NULL into ()" This issue is a known Oracle issue - reference Oracle bug # 9648430.
Resolution:
Apply the Oracle fix. If an Oracle fix is not available for your version of Oracle, a workaround is to disable MRI in FTM by using the configuration values that are shown in the following table:
| Category | Key | Value |
|---|---|---|
| CORE | MRI_EM2_ENABLED | N |
For more information about the Database Persistence API configuration, see the following section in the Financial Transaction Manager online documentation, Version 3.2.0: Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration
Issue 7
Users Affected: Customers that use FTM SWIFT WebSphere Transformation Extender maps.
Summary:
FTM SWIFT SR2016 WebSphere Transformation Extender maps do not work with FTM SWIFT SR2015 WebSphere Transformation Extender maps at a single broker instance together at the same time.
The reason is that IBM Transformation Extender changed the JVCWrapper code with the new Financial Payments Pack for SWIFT 9.0.1 release and it is not compatible with the earlier Financial Payments Pack for SWIFT releases.
Resolution:
Using multiple versions of the Financial Payments Pack for SWIFT at the same time in a specific instance of a program is not supported.
Issue 8
Users Affected: Customers that use IBM Integration Bus version 10
Summary:
BIP4633E: An error occurred whilst performing an MQGet node operation.
BIP4630E: An MQGET operation was unsuccessful. Completion Code 2; Reason Code 2046.
An MQGet node in a message flow might fail when you use the LocalEnvironment to override some of the MQGET message options but not the 'Options' specific field.
Resolution:
Request the fixes for IBM Integration Bus APAR IT24438 from IBM Support.
Issue 9
Users Affected: Customers that use IBM Integration Bus version 10, fix pack 10 (10.0.0.10)
Summary:
From IBM Integration Bus V10, fix pack 10 and later, it was observed that when a usertrace/service trace is enabled, the log inserts were incorrectly populated for certain BIP messages that correspond to ESQL processing.
For example , a comparison of the traces between FP09 and FP10 shows following differences for the BIP2539I message.
- For fix pack 9: BIP2539I: Node '': Evaluating expression ''J'' at ('.testflow_Compute.CopyMessageHeaders', '5.13'). This resolved to ''J''. The result was ''3''.
- For fix pack 10: BIP2539I: Node '{5}': Evaluating expression '{4}' at ('J','3'). This resolved to ''J''. The result was ''.
Resolution:
Request the fixes for IBM Integration Bus APAR IT24909 from IBM Support.
Issue 10
Users Affected: Customers that use IBM Integration Bus version 10 on z/OS.
Summary:
The following SQLERROR can be seen on z/OS when a flow does some non-coordinated database work in an ESQL node before it does any IBM MQ work in the flow:
+BIP2322E MQXXBRK EG1 44 DATABASE ERROR: SQL STATE '2D521';NATIVE ERROR CODE '-926'; ERROR TEXT '{DB2 FOR OS/390}{ODBC DRIVER}
{DSN10015} DSNT408I SQLCODE = -926, ERROR: ROLLBACK NOT VALID IN IMS, CICS OR RRSAF ENVIRONMENT
Resolution:
Request the fixes for IBM Integration Bus APAR PI83720 from IBM Support.
Issue 11
Users Affected: Customers that use IBM Integration Bus version 10 and ODBC XA.
Summary:
IBM MQ connections that are used by message flow threads are released when they are idle (unused) for longer than the timeout period, which is 60 seconds by default.
Also, the ODBC connections are released after a database failure or failover.
Resolution:
Request the fixes for IBM Integration Bus APAR IT22302 from IBM Support.
Was this topic helpful?
Document Information
Modified date:
28 March 2022
UID
swg27051134