Fix readme

Abstract

Readme file for IBM Financial Transaction Manager for Multiplatforms v3.2.2.0_iFix0002
Product/Component Release: 3.2.2
Fix ID: 3.2.2.0-FTM-MP-iFix0002

Contents:


Download location

Download IBM(R) Financial Transaction Manager for Multiplatforms Version 3.2.2.0_iFix0002
from Fix Central
Search for the Fix ID: 3.2.2.0-FTM-MP-iFix0002

See the "Installation information" section below for install instructions.


Prerequisites and co-requisites


Before downloading FTM V3.2.2.0_iFix0002, perform the following steps:

- Ensure that your system meets all of the system requirements: http://www.ibm.com/software/industry/financial-transaction-manager/requirements
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 Web site: http://www.ibm.com/software/industry/financial-transaction-manager/support
Open APARs describe defects that are not yet addressed in a fix, and they might contain workarounds that will impact your use of FTM V3.2.2.0_iFix0002

- Read the "Known issues" section of this readme.

- You need to have a file system with 400MB of free space to contain the fix files.
Ensure that you have the free space required to install the fix.

- If you already have an FTM product installed and have obtained special fixes, contact IBM(R) support to determine whether you need an updated version of the fixes before you install.
This helps to ensure that your system is in a consistent state and that no special fixes are lost.
Back to Contents

What's new in FTM V3.2.2.0, iFix0002

  • OAC Preference properties added to control the max. number of audit log records to retrieve and display.(Ref: 92193).

    See the "Financial Transaction Manager -> Financial Transaction Manager overview -> What's new in FTM" section of the "FTM for Multiplatforms v3.2.2 Knowledge Center" available at
    IBM Financial Transaction Manager for Multiplatforms v3.2.2 documentation

List of fixes

Fixes included in FTM for V3.2.2
http://www.ibm.com/support/docview.wss?uid=ibm10883832
Back to Contents

Known issues

Issue 1

Users Affected : Customers using FTM Base v3.2.2

Summary :

When using the A_EmailOp Action, the email Subject will be null.
If the $AuditLog macro is used in the Value of the EMAIL_SUBJECT category, it will not be resolved.

Resolution :

Avoid using the $AuditLog macro.

Issue 2

Users Affected : Customers using IBM Integration Bus v10

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 may fail if the user has used 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 IIB v10.0.0.13

Issue 3

Users Affected : Customers using IBM Integration Bus v10 fixpack 10(v10.0.0.10)

Summary :

From IIB v10 FP10 onwards, 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 : Comparison of the traces between FP09 and FP10 shows following difference for BIP2539I message.
FP09 :- BIP2539I: Node '': Evaluating expression ''J'' at ('.testflow_Compute.CopyMessageHeaders', '5.13'). This resolved to ''J''. The result was ''3''.
FP10 :- 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 IIB v10.0.0.13

Issue 4

Users Affected : Customers using IBM Integration Bus v10 on z/OS.

Summary :

The following SQLERROR may be seen on zOS when a flow performs some non-coordinated database work in an ESQL node before performing any 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 IIB v10.0.0.13

Issue 5

Users Affected : Customers using IBM Integration Bus v10 using ODBC XA.

Summary :

MQ connections used by message flow threads are released if they have been idle (unused) for longer than the timeout period, default 60 seconds.
Additionally, after a database failure/failover, the ODBC connections are released.

Resolution :

The fix for this issue(APAR IT22302) is available in IIB v10.0.0.12

Issue 6

Users Affected : Customers using IBM Integration Bus toolkit v10.0.0.11

Summary :

Bar build fails with java.lang.ArrayIndexOutOfBoundsException in the details.

Resolution :

The fix for this issue(APAR IT23841) is available in IIB v10.0.0.12

Other workarounds include

  • Building Bar files in IIB 9 or IIB 10 up to and including 10.0.0.10
  • Building Bar files using mqsipackagebar on the command line.

Issue 7

Users Affected : Customers using IBM Integration Bus toolkit v10.0.0.12

Summary :

Bar build fails with java.lang.IllegalStateException in the details.

Resolution :

The fix for this issue(APAR IT24755) is available in IIB v10.0.0.14

Other workarounds include

  • Building Bar files in IIB 9 or IIB 10 up to and including 10.0.0.10
  • Building Bar files using mqsipackagebar on the command line.

Issue 8

Users Affected : Customers using Oracle Database v11.x and above.

Summary :

FTM(with Oracle) users may experience the following issues when using 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 then a workaround is to disable MRI in FTM as follows:

Category  Key             Value
CORE      MRI_EM2_ENABLED N
For additional details about the Database Persistence API configuration, see the following section in the Knowledge Center for Financial Transaction Manager, Version 3.2.2 :
Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration

Issue 9

Users Affected : Customers using FTM SWIFT WTX maps with Financial Payments Pack for SWIFT v9.0.1.

Summary :

FTM SWIFT SR2016 WTX maps will not work with FTM SWIFT SR2015 WTX maps at a single broker instance together at the same time.

The reason is that IBM Transformation Extender has changed the JVCWrapper code with the new Financial Payments Pack for SWIFT 9.0.1 release and it is not compatible with the earlier Pack for SWIFT releases.

Resolution :

Therefore using multiple Pack for SWIFT versions at the same time in a specific instance of a program is not supported.

Back to Contents

Installation information

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

Installing FTM V3.2.2.0_iFix0002 to create a new runtime installation

Follow the instructions in the "Financial Transaction Manager -> Installing" section of the "FTM for Multiplatforms v3.2.2 Knowledge Center" available at
IBM Financial Transaction Manager for Multiplatforms V3.2.2 documentation

To update an existing V3.2.2 runtime installation

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.2 documentation

Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for Multiplatforms v3.2.2 Knowledge Center" available at
IBM Financial Transaction Manager for Multiplatforms V3.2.2 documentation

FTM for zOS Developer Edition

Installing FTM V3.2.2.0_iFix0002 to create a new runtime installation

Follow the instructions in the "Financial Transaction Manager -> Installing -> FTM Developer Edition installation" section of the "FTM for zOS V3.2.2 Knowledge Center" available at
IBM Financial Transaction Manager for zOS V3.2.2 documentation

To update an existing V3.2.2 runtime installation

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.2 documentation

Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the "FTM for zOS v3.2.2 Knowledge Center" available at
IBM Financial Transaction Manager for zOS V3.2.2 documentation

Back to Contents

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 Tooling:

Use Installation manager to re-install the previous version of the 'FTM Model Tools'.
Back to Contents