IBM Support

IBM Financial Transaction Manager for z/OS V3.2.2, Fix Pack 2 readme file

Fix Readme


Abstract

Readme file for IBM Financial Transaction Manager for z/OS Version 3.2.2, Fix Pack 2
Product/Component Release: V3.2.2

Content

 

Download location


Download IBM(R) Financial Transaction Manager for z/OS Version 3.2.2, Fix Pack 2 from IBM Shopz.
 

Prerequisites and corequisites


Before you download FTM V3.2.2, Fix Pack 2, do the following steps:

- Ensure that your system meets all of the system requirements: https://www.ibm.com/support/pages/node/712995
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: https://www.ibm.com/mysupport/s/topic/0TO50000000IVqQGAW/financial-transaction-manager
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 400 MB 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.  

What's new in FTM V3.2.2, Fix Pack 2

  • Support for SWIFT Standards Release 2019.
  • Add execution environment information to exception events
    This information is added to the <cbe:reporterComponentId> node of exception events that conform to the Common Base Event specification. These exception events include the ones that are shown in the following list:
    • E_UnexpectedError
    • E_MpInMappingAborted
    • E_OutPTSendFailed

See the "Financial Transaction Manager -> Financial Transaction Manager overview -> What's new in FTM" section in the Financial Transaction Manager for z/OS Version 3.2.2 documentation in IBM Knowledge Center. It is available at the following link:
IBM Financial Transaction Manager for z/OS V3.2.2 documentation

 

Known issues

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

Issue 1

Users affected: Customers that use 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 usage of the $AuditLog macro.

Issue 2

Users affected: Customers that use 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 can fail if you 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 that use IBM Integration Bus V10, Fix Pack 10 (V10.0.0.10)

Summary:

From IBM Integration Bus V10 Fix Pack 10 and later, when a user trace or service trace is enabled, the log inserts are 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 IBM Integration Bus V10.0.0, Fix Pack 13.

Issue 4

Users affected: Customers that use IBM Integration Bus V10 on z/OS.

Summary:

The following SQLERROR can be seen on z/OS when a flow performs some non-coordinated database work in an ESQL node before any IBM MQ work is done 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 that use IBM Integration Bus V10 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 V10.0.0, Fix Pack 12.

Issue 6

Users affected: Customers that use 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 Integration Bus V9 or IBM Integration Bus V10 up to and including V10.0.0, Fix Pack 10.
  • Building BAR files by using mqsipackagebar on the command line.

Issue 7

Users affected: Customers that use 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 Integration Bus V9 or IBM Integration Bus 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 that use Oracle database V11.x and later.

Summary:

FTM (with Oracle) users might experience the following issues when the multiple row insert (MRI) function is used:

"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, 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 for z/OS Version 3.2.2 documentation in IBM Knowledge Center:
Financial Transaction Manager -> Application programming -> Actions -> Database Persistence -> API configuration

Issue 9

Users affected: Customers that use FTM SWIFT WTX maps with Financial Payments Pack for SWIFT V9.0.1.

Summary:

FTM SWIFT SR2016 WTX maps do not work with FTM SWIFT SR2015 WTX maps in 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 Pack 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.

 

Installation information


Before you proceed with the installation process, view the online version of this readme file to check whether any information changed since the readme file was downloaded: https://www.ibm.com/support/pages/node/1088590

Use the normal SMP/E process to install this PTF.
 

Installing FTM V3.2.2, Fix Pack 2 to create a new runtime installation


Follow the instructions in the "Financial Transaction Manager -> Installing" section of the Financial Transaction Manager for z/OS Version 3.2.2 documentation in IBM Knowledge Center. It is available at the following link:
IBM Financial Transaction Manager for z/OS V3.2.2 documentation

To update an existing V3.2.2.x runtime installation


Follow the instructions in the "Financial Transaction Manager -> Planning -> Migration" section of the Financial Transaction Manager for z/OS Version 3.2.2 documentation in IBM Knowledge Center. It is available at the following link:
IBM Financial Transaction Manager for z/OS V3.2.2 documentation  

Uninstalling if necessary


To roll back to the previous version of FTM:
Use the normal SMP/E process to revert to a previous version.

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.

Redeploy the application BAR files.

OAC Migration:

Redeploy the OAC EAR from the previous version.

RSA Model Tools:

Use Installation Manager to reinstall the previous version of the FTM Model Tools.  

List of fixes


Fixes included in FTM for V3.2.2, Fix Pack 2
https://www.ibm.com/support/pages/node/883832

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Component":"IBM Financial Transaction Manager base product","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"3.2.2.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
23 October 2019

UID

ibm11088590

Page Feedback