Fix Readme
Abstract
Fix list for IBM Financial Transaction Manager 3.2.11 Multiplatforms
Content
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
| V.R.M.F | Download | Build date | Prerequisites |
| 3.2.11.3 (Fix pack 3) | Available for download from Fix Central | 20250929-0448 | None |
| 3.2.11.2 (Fix pack 2) | Available for download from Fix Central | 20231109-1647 | None |
| 3.2.11.1 (Fix pack 1) | Available for download from Fix Central | 20230426-1543 | None |
| 3.2.11.0 | Available from Passport Advantage | 20230120-1838 | None |
| Back to top | 3.2.11.3 (Fix pack 3) release |
| Fix number | Type | Component | Description |
| 152359 | DT417625 TS016587319 | FTM Generic Model | Product FSM - Outbound Physical Transmission. Incorrect transition - E_PTOutMapAborted |
| Back to top | 3.2.11.2 (Fix pack 2) release |
| Fix number | Type | Component | Description |
| 148881 | Task | SR2023 Support | Add SR2023 support to FTM for 3.2.11 level |
| 142048 | PMR | Purge Tool | FTM purge does not purge H_SCHEDULER_TASK_BASE records |
| 148992 | Defect | OAC | Resolve does not work from Alert screen with multiselect |
| 148738 | PMR | OAC | TS013889959- FTM's file Resend functionality not working as expected |
| 148092 | Defect | UnexpectedError Events raised during FTM Base Sample App performance test | |
| 146960 | PMR | TS013578166 - FTM 3.2.11.1 Throttler getting stuck in the IT2 | |
| 145727 | PMR | TS012919706 - ISFToPacs002 Mapper needs memory management changes | |
| 145724 | PMR | TS012919706 - Batch Status Action can parse lots of ISF into the environment | |
| 147683 | PMR | TS013889959 - FTM's file Resend functionality not working as expected | |
| Back to top | 3.2.11.1 (Fix pack 1) release |
| Fix number | Type | Component | Description |
145301 | Defect | Db2 on z/OS | Support for Db2 on z/OS migration steps is now available for the following: - migration from 3.2.5 to 3.2.6 - migration from 3.2.6 to 3.2.7 - migration from 3.2.7 to 3.2.11.1 (Fix pack 1) |
| 144767 | Defect | Problem: The application-wide Value Table configuration that enables PTW IBM MQ latency to be monitored is not being applied correctly during Cache Load. Category: CORE_PERFORMANCE Solution: Apply the value directly to the channel parameter field PTW_LATENCY_WARN_THRESHOLD, for example, set PTW_LATENCY_WARN_THRESHOLD=1000 | |
| Back to top | 3.2.11.0 release |
| Fix number | Type | Component | Description |
| 140788 | Problem: A defect was found in Config Update Triggers T_SCHED_TASK_UT and T_SCHED_TASK_U. The issue was related to the comparison of NULL values for RESOURCE_REF and RESOURCE_REF2, which can never be true or false and result in incorrect updates of the config history. This problem can lead to frequent cache reloads by the IBM App Connect Enterprise processes of FTM. Solution: To avoid unexpected config history updates, the two triggers were corrected to handle NULL values when these two columns are compared. This problem is fixed by running the FTM database migration scripts that are supplied with 3.2.11. | ||
| 142060 | Defect | Problem: A custom FTM application cannot control or set the OWNER_ID of an outbound transmission when a transaction is sent "inline" by using the outbound transmission handler module. Solution: OWNER_ID was added as a supported property to the transmission properties that can be supplied to the mapper, handler, or both. |
Was this topic helpful?
Document Information
Modified date:
25 October 2025
UID
ibm16839185