Release Notes for IBM Financial Transaction Manager for z/OS V3.2.2

---

• Prior to installation
• Product documentation
• Support
• Feature updates
• Known issues

 

---

Prior to 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 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 z/OS: shopZ website.
For IBM Financial Transaction Manager for z/OS Developer Edition: Use the latest z/OS Developer Edition update available on Fix Central - V3.2.2.0_iFix0002.  

---

Product documentation

The online product documentation is in IBM Knowledge Center.
IBM Financial Transaction Manager for z/OS documentation.
   

---

Support

Defects:

These release notes can 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 current information about available fixes, see the IBM support web page.
To find information, see Download - Fixes, updates and drivers, 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 section in the FTM documentation in IBM Knowledge Center:

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

 

---

Known issues

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

Issue 1

Users Affected: Customers using FTM Base V3.2.2

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 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 IBM Integration Bus V10.0.0, Fix Pack 13

Issue 3

Users Affected: Customers using IBM Integration Bus V10, Fix Pack 10 (V10.0.0.10)

Summary:

In IBM Integration Bus V10 Fix Pack 10 or 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, comparing the traces between FP09 and FP10 shows the following difference for the 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 IBM Integration Bus V10.0.0, Fix Pack 13

Issue 4

Users Affected: Customers using IBM Integration Bus V10 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 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 V10.0.0, Fix Pack 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 IBM Integration Bus V10.0.0, Fix Pack 12

Issue 6

Users Affected: Customers using IBM Integration Bus toolkit V10.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 V10.0.0, Fix Pack 12

Other workarounds include

• Building BAR files in IBM IB V9 or IBM IB V10 up to and including V10.0.0, Fix Pack 10
• Building BAR files using mqsipackagebar on the command line.

Issue 7

Users Affected: Customers using IBM Integration Bus toolkit V10.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 V10.0.0, Fix Pack 14

Other workarounds include

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

Issue 8

Users Affected: Customers using Oracle Database V11.x and later.

Summary:

FTM (with Oracle) users might 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 - 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.2 documentation in IBM Knowledge Center:
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 V9.0.1 release and it is not compatible with the earlier Pack for SWIFT releases.

Resolution:

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

 

---