Release Notes for IBM Financial Transaction Manager for Multiplatforms V3.2.10

---

• Before installation
• Product documentation
• Support
• Features and Fix updates
• Known issues

 

---

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:

For IBM Financial Transaction Manager for Multiplatforms: Passport Advantage instructions.  

---

Product 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 Download - Fixes, updates and drivers, and then enter the name of the product. This web page provides links to the latest available maintenance for the in-service IBM Financial Transaction Manager family of products.
   

---

Features and Fix updates

For a list of the features and fixes that are included in this release, see Features and Fix list.

To learn more about the new features in IBM Financial Transaction Manager, see the following section in the FTM documentation in IBM Documentation:

Financial Transaction Manager->What's new in FTM->What's new in FTM Version 3.2.10

 

---

Known issues

This section outlines the known issues and their workarounds (if any).
 

Issue 1

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.

Issue 2

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:

1. If the Record Detection property is promoted and Delimiter is not, the Delimiter property can no longer be edited.
2. If the Delimiter property is promoted and its value is changed to a nondefault value, the message flow can no longer be deployed. The following error is observed on deployment: BIP3310E: 'FileInput' node 'File Input' in message flow 'FileInputNodePropertyPromotion' property name 'null' is supplied with an invalid value 'customDelimiter'.
3. Renaming the Delimiter property after it was promoted causes the values to display incorrectly.

Resolution:

The fix for this issue (APAR IT30075) is available in IBM Integration Bus Toolkit 10.0.0 Fix Pack 19

Issue 3

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.

Issue 4

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.

Issue 5

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

Issue 6

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 trace:  BIP2539I: Node '': Evaluating expression ''J'' at ('.testflow_Compute.CopyMessageHeaders', '5.13'). This resolved to ''J''. The result was ''3''.
Fix Pack 10 trace:  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

Issue 7

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 noncoordinated 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

Issue 8

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

Issue 9

Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 11

Summary:

The BAR file 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

• Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0 Fix Pack 10
• Building BAR files by using mqsipackagebar on the command line.

Issue 10

Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 Fix Pack 12

Summary:

The BAR file 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

• Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0, Fix Pack 10
• Building BAR files by using mqsipackagebar on the command line.

Issue 11

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 N

For more information about the database persistence API configuration, see the following section in the Financial Transaction Manager Version 3.2.8 documentation in IBM Documentation:
Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration

Issue 12

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.

Issue 13

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 models are models that are included in the main model by using package import relationships.

Resolution:

Validate each of the referenced models separately.

Issue 14

Users affected: OAC users

Summary:

The text for a date validation message in the search tab is not being displayed correctly.

Resolution:

On the preferences page, select a locale entry other than the default blank entry to display the full message text.

---