Readme file for IBM Financial Transaction Manager for Multiplatforms V3.2.0, Fix Pack 3
Product/Component Release: 3.2.0
Fixpack number: V3.2.0.3
Fix ID: 3.2.0-FTM-MP-fp0003
Download IBM(R) Financial Transaction Manager for Multiplatforms Version 3.2.0, Fix Pack 3
from
Fix Central
Search for the Fix ID: 3.2.0-FTM-MP-fp0003
Note: the downloaded zip file(3.2.0-FTM-MP-fp0003.zip) contains the following two FTM Installation Manager repository files:
- Financial Transaction Manager for Multiplatforms V3.2.0.3.zip
- Financial Transaction Manager for zOS Developer Edition V3.2.0.3.zip
See the "Installation information" section below for information on installing the fixpack for your offering.
Before you download FTM V3.2.0, Fix Pack 3, do the following steps:
- Ensure that your system meets all of the system requirements:
Detailed hardware and software requirements for IBM Financial Transaction Manager offerings
This action prevents technical problems that might occur after the installation and configuration of the fix.
- Review the Flashes and open Authorized Problem Analysis Reports (APARs) on the
Financial Transaction Manager product support website
Open APARs describe defects that are not yet addressed in a fix, and they might contain workarounds that impact your use of FTM.
- Read the "Known issues" section of this readme file.
- You need to have a file system with 400MB of free space to contain the fix files.
Ensure that the free space required to install the fix is available.
- If you already installed an FTM product and obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you continue with this installation.
This step helps to ensure that your system is in a consistent state and that no special fixes are lost.
- Support for SWIFT Standards Release 2019.
See the "Financial Transaction Manager -> Financial Transaction Manager overview -> What's new in FTM" section of the "FTM for z/OS v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for z/OS V3.2.0 documentation
Issue 1
Users Affected: Customers that use IBM WebSphere Transformation Extender(WTX) version 8.4.1.2.
Summary:
Customers that use IBM WebSphere Transformation Extender (WTX) version 8.4.1.2 and
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 WTX V8.4.1.3.
Issue 2
Users Affected: Customers that use any Broker version 7 releases.
Summary:
Customers that use any Broker version 7 releases might experience inconsistent validation results when using FTM channel-based validation, Integration Bus in ESQL parser validation, or both.
Resolution:
The fix for this issue (IBM Integration Bus APAR IT14075) is available in IBM Integration Bus Maintenance Level 10.0.0.5.
Issue 3
Users Affected: Customers that use Oracle database V11 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 (<USER.TABLE.COLUMN>)"
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 as follows:
Category Key Value
CORE MRI_EM2_ENABLED N
For more information about the database persistence API configuration, see the following section in the FTM Version 3.2.0 documentation in IBM Knowledge Center:
Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration
Issue 4
Users Affected: Customers that use FTM SWIFT WTX maps.
Summary:
FTM SWIFT SR2016 WTX maps don't work with FTM SWIFT SR2015 WTX 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 V9.0.1 release and it is not compatible with the earlier Financial Payments for SWIFT releases.
Resolution:
Using multiple Financial Payments Pack for SWIFT versions at the same time in a specific instance of a program is not supported.
Issue 5
Users Affected: Customers that use IBM Integration Bus V10.0.
Summary:
Payments not completing correctly due to incorrect IBM MQ rollback processing.
Resolution:
The fix for this issue(APAR IT25600) is targeted for delivery in the following PTFs:
| Version | Maintenance Level |
| V10.0 | 10.0.0.14 |
Note: If the maintenance level is not yet available, information on its planned availability can be found
here.
Issue 6
Users Affected: Customers that use IBM Integration Bus V10.0.
Summary:
BIP2329E: An unexpected NULL value was encountered.
Resolution:
Patches for this issue are available on request from IBM Support.
Put the APAR number (IT25754) in the request and provide full details of the IBM Integration Bus V10 levels that you are using.
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.
FTM for Multiplatforms
Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for Multiplatforms v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.0 documentation
To update an existing V3.2.0.x runtime installation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for Multiplatforms v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for Multiplatforms V3.2.0 documentation
FTM for zOS Developer Edition
Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for zOS V3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.0 documentation
To update an existing V3.2.0.x runtime installation
Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for zOS v3.2.0 Knowledge Center"
available at
IBM Financial Transaction Manager for zOS V3.2.0 documentation
Uninstalling if necessary
To rollback to the previous version of FTM:
- Start Installation manager
- Click Roll Back.
- Select the Package Group name where FTM is installed.
Database:
Restore the backup taken during the Database migration step.
Application Migration:
Revert to the WebSphere Message Broker Toolkit workspace taken during the installation steps.
Re-deploy the application bar files.
OAC Migration:
Re-deploy the OAC ear from the previous version.
RSA Model Tools:
Use Installation manager to re-install the previous version of the 'FTM Model Tools'.
Fixes included in FTM for V3.2.0, Fix Pack 3
http://www.ibm.com/support/docview.wss?uid=ibm10729307