Readme file for IBM Financial Transaction Manager for Multiplatforms V3.2.6 Fix Pack 1 Product/Component Release: 3.2.6 Fix ID: 3.2.6-FTM-MP-fp0001
Download IBM(R) Financial Transaction Manager for Multiplatforms Version 3.2.6 Fix Pack 1
from
Fix Central
Search for the Fix ID: 3.2.6-FTM-MP-fp0001
See the "Installation information" section below for install instructions.
Users affected: Customers that use IBM Integration Bus Toolkit 10.0.0 Fix Pack 19
Summary:
When this version of the toolkit is used for development, the developed artifacts cannot be deployed on previous versions of the IBM Integration Bus.
Resolution:
None currently available.
Users affected: Customers that use IBM Integration Bus Toolkit 10.0.0 Fix Pack 17 and Fix Pack 18
Summary:
When properties that have an enum type (for example, the Record Detection or Delimiter properties on the FileInput Node) are promoted, the following erroneous behavior is observed:
Resolution:
The fix for this issue (APAR IT30075) is available in IBM Integration Bus Toolkit 10.0.0 Fix Pack 19
Users affected: Customers that use IBM Integration Bus Toolkit 10.0.0 Fix Pack 16
Summary:
When the JAR files for user-defined nodes are copied to the drop-ins folder of the toolkit, they are not displayed in the palette in the Message Flow editor.
Resolution:
None currently available.
Users affected: Customers that use FTM Base 3.2.6
Summary:
When the A_EmailOp action is used, the email subject is null.
If the $AuditLog macro is used in the value of the EMAIL_SUBJECT category, it is not resolved.
Resolution:
Avoid the use of the $AuditLog macro.
Users affected: Customers that use IBM Integration Bus 10.0
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:
The fix for this issue (APAR IT24438) is available in IBM Integration Bus 10.0.0 Fix Pack 13
Users affected: Customers that use IBM Integration Bus 10.0.0 Fix Pack 10
Summary:
From IBM Integration Bus 10.0.0 Fix Pack 10 and later, it was observed that when a user or 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 fix pack 09 and fix pack 10 shows the following difference for the BIP2539I message.
Fix Pack 09 :- BIP2539I: Node '': Evaluating expression ''J'' at ('.testflow_Compute.CopyMessageHeaders', '5.13'). This resolved to ''J''. The result was ''3''.
Fix Pack 10 :- BIP2539I: Node '{5}': Evaluating expression '{4}' at ('J','3'). This resolved to ''J''. The result was ''.
Resolution:
The fix for this issue (APAR IT24909) is available in IBM Integration Bus 10.0.0 Fix Pack 13
Users affected: Customers that use IBM Integration Bus 10.0 on z/OS.
Summary:
The following SQLERROR is 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:
The fix for this issue (APAR PI83720) is available in IBM Integration Bus 10.0.0 Fix Pack 13
Users affected: Customers that use IBM Integration Bus 10.0 and ODBC XA.
Summary:
IBM MQ connections used by message flow threads are released when they are idle (unused) for longer than the timeout period, default 60 seconds.
Additionally, after a database failure or failover, the ODBC connections are released.
Resolution:
The fix for this issue (APAR IT22302) is available in IBM Integration Bus 10.0.0 Fix Pack 12
Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 11
Summary:
BAR build fails with java.lang.ArrayIndexOutOfBoundsException in the details.
Resolution:
The fix for this issue (APAR IT23841) is available in IBM Integration Bus 10.0.0 Fix Pack 12
Other workarounds include
Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 12
Summary:
BAR build fails with java.lang.IllegalStateException in the details.
Resolution:
The fix for this issue (APAR IT24755) is available in IBM Integration Bus 10.0.0 Fix Pack 14
Other workarounds include
Users affected: Customers that use Oracle Database 11.x and later.
Summary:
FTM (with Oracle) users might experience the following issues when they use the multiple row insert (MRI) function:
"ORA-00932 inconsistent datatypes: expected NUMBER got TIMESTAMP"
"ORA-01400 cannot insert NULL into (<user.table.column>)"
This issue is a known Oracle issue - refer to 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 as follows:
Category Key Value CORE MRI_EM2_ENABLED NFor more information about the database persistence API configuration, see the following section in the Financial Transaction Manager Version 3.2.6 documentation in IBM Knowledge Center:
Users affected: Customers that use FTM SWIFT WebSphere Transformation Extender maps with Financial Payments Pack for SWIFT 9.0.1.
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.
Users affected: Customers that use Rational Software Architect or Rational Software Architect Designer to develop FTM Models.
Summary:
The model validation function, which is used from the graphical user interface or called during the FTM script generation functions, does not fully validate referenced models. Referenced model are models that are included in the main model by using package import relationships.
Resolution:
Validate each referenced model separately.
Before proceeding with the installation process, view the online version of this readme file to check if information has changed since the
readme file was downloaded.
Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for Multiplatforms v3.2.6 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.6 documentation
First install using the Install function in Installation Manager to install into a new Package Group.
(Note: The Update function in Installation Manager is not supported.)
For more details, see IBM Financial Transaction Manager for Multiplatforms V3.2.6 documentation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for Multiplatforms v3.2.6 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.6 documentation
Follow the instructions in the "Financial Transaction Manager -> Installing -> FTM Developer Edition installation" section of the "FTM for zOS V3.2.6 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.6 documentation
First install using the Install function in Installation Manager to install into a new Package Group.
(Note: The Update function in Installation Manager is not supported.)
For more details, see IBM Financial Transaction Manager for Multiplatforms V3.2.6 documentation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for zOS v3.2.6 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.6 documentation