Fix Readme
Abstract
This document contains the fix list information for Financial Transaction Manager for Digital Payments for Multiplatforms 3.2.9.
Content
Fix List for Financial Transaction Manager for Digital Payments 3.2.9
This document contains fix list information for:
Financial Transaction Manager for Digital Payments for Multiplatforms 3.2.9
The following tables provide a complete listing of the available FTM for Digital Payments fixes on all platforms. Multiplatforms fixes are available on Fix Central.
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
- To avoid a loss of functionality when you migrate from one release to another, check the Compatibility Matrix for the release being migrated to. The Compatibility Matrix is located in the V3.2.9 Release Information for Financial Transaction Manager for Digital Payments.
| V.R.M.F fix list | Links to Fix Central download (by Fix ID) |
Product | Build Date | Pre-requisites |
| 3.2.9.1 interim fix 1 | 3.2.9.1-FTM-DP-MP-iFix0001 | Digital Payments | 20220405-0859 | 3.2.9.1 |
| 3.2.9.1 | 3.2.9.1-FTM-DP-MP-fp0001 | Digital Payments | 20220207-2026 | None |
| 3.2.9.0 interim fix 9 | 3.2.9.0-FTM-DP-MP-iFix0009 | Digital Payments | 20230105-0755 | 3.2.9.0 |
| 3.2.9.0 interim fix 8 | 3.2.9.0-FTM-DP-MP-iFix0008 | Digital Payments | 20221129-1200 | 3.2.9.0 |
| 3.2.9.0 interim fix 7 | 3.2.9.0-FTM-DP-MP-iFix0007 | Digital Payments | 20221017-1423 | 3.2.9.0 |
| 3.2.9.0 interim fix 6 | 3.2.9.0-FTM-DP-MP-iFix0006 | Digital Payments | 20220816-1905 | 3.2.9.0 |
| 3.2.9.0 interim fix 5 | 3.2.9.0-FTM-DP-MP-iFix0005 | Digital Payments | 20220705-1105 | 3.2.9.0 |
| 3.2.9.0 interim fix 4.1 | 3.2.9.1-FTM-DP-MP-iFix0004.1 | Digital Payments | 20220524-1050 | 3.2.9.0 |
| 3.2.9.0 interim fix 4 | 3.2.9.0-FTM-DP-MP-iFix0004 | Digital Payments | 20220502-1600 | 3.2.9.0 |
| 3.2.9.0 interim fix 3 | 3.2.9.0-FTM-DP-MP-iFix0003 | Digital Payments | 20220308-1115 | 3.2.9.0 |
| 3.2.9.0 interim fix 2 | 3.2.9.0-FTM-DP-MP-iFix0002 | Digital Payments | 20220219-1517 | 3.2.9.0 |
| 3.2.9.0 interim fix 1 | 3.2.9.0-FTM-DP-MP-iFix0001 | Digital Payments | 20220110-2329 | 3.2.9.0 |
| 3.2.9.0 | Available from Passport Advantage | Digital Payments | 20211213-1035 | None |
Note: APAR links for security fixes aren’t active.
Refer to V3.2.9 Release Information for Financial Transaction Manager for Digital Payments for further details on issues and changes.
Note: The update instructions referred to by interim fixes are located in the installation location\component\doc folder, for example:
installation location\shared\v329\pfs\Gateway\doc\updates.
| Back to top | 3.2.9.1 interim fix 1 |
| Fix Number | Type | Component | Description |
| DT121679 | Defect |
Real-Time Payments - Other
Real-Time Payments - Engine
|
Zelle: EWS responded with an invalid failure reason code. |
| DT124223 | Defect |
Real-Time Payments - Other
Real-Time Payments - Engine
|
Financial Transaction Manager has a potential null pointer when a Recipient does not have a stored parent ID. |
| DT124225 | Defect | Real-Time Payments - Engine | Zelle Received payments are getting stuck in Pending Processing. |
| DT124858 | Defect | Real-Time Payments - Engine | Financial Transaction Manager is not handling the valid scenario when an actor ID can be null, which causes a validation error. |
| DT125226 | Defect | Core Real-Time Payments - Engine |
Financial Transaction Manager is occasionally retrieving incorrect Recipient data before sending data to Fraud Detection. |
| DT126191 | Defect | Core Real-Time Payments - Engine |
Financial Transaction Manager does not allow customer types of 2 characters to be used when created CXCParticipants. |
| DT126203 | Defect | Real-Time Payments - Engine | During processing of large NACHA files, FTM is getting many timeouts during processing. |
| DT127251 | Defect | Real-Time Payments - Engine | Financial Transaction Manager is not properly creating previously existing Recipients. |
| 133201 | Defect | Real-Time Payments - Engine | Problem: Zelle Ready Contacts API does not log enough for customers to debug on their own. Resolution: Added the necessary trace strings to log request, response, and endpoint URL. |
| 133559 | Defect | Settlement - Engine | Problem: Settlement engine is getting many errors and does not seem to be processing messages off the queue. Resolution: Financial Transaction Manager is now properly closing connections when Settlement messages are processed. |
| 135112 | Defect | Core Real-Time Payments - Engine |
Problem: Financial Transaction Manager is making unnecessary calls to EWS to update the organizations during payment creation. Resolution: The unnecessary calls to update the organizations were removed from the payment creation process. |
| 135130 | Defect | Real-Time Payments - Engine | Problem: Financial Transaction Manager is not properly handling the scenario where a previously deleted Recipient is being reactivated with a different name. Resolution: Financial Transaction Manager is now getting the correct data from the deleted Recipient to update the correct fields to allow the creation of the Recipient with a different name. |
| 135175 | Defect | Gateway - Other | Problem: During IBM MQ failover, Gateway is logging an excessive number of records in the database. Resolution: Addressed issue when IBM MQ is down, Gateway was logging too many errors. |
| 135204 | Defect | Core | Problem: Financial Transaction Manager has queries that include unnecessary joins and they could be removed to improve performance. Resolution: Where available, joins that were no longer necessary, were removed from certain queries to improve performance. |
| Back to top | 3.2.9.1 Release |
No changes other than what is mentioned in the Release Information.
| Back to top | 3.2.9.0 interim fix 9 |
| Fix Number | Type | Component | Description |
| DT180541 | Defect | Core Transaction Server - Console |
Liberty Initiate Credit Transfer can not be run in asynchronous mode when using ref_transaction_id. |
| Back to top | 3.2.9.0 interim fix 8 |
| Fix Number | Type | Component | Description |
| 141700 | Defect | Core Transaction Server - Console |
Problem: Request for Payment API requests are failing to validate properly.
Resolution: Added missing fields to pain.013.xsd to properly validate all message types for Request for Payment API requests. |
| Back to top | 3.2.9.0 interim fix 7 |
| Fix Number | Type | Component | Description |
| 140025 | Defect | Core Transaction Server - Console |
Problem: API generated payment is missing Creditor Account Proxy Id, required for Zelle over TCH.
Resolution: Added ISF mapping for IdentificationToken to ProxyIdentification. |
| Back to top | 3.2.9.0 interim fix 6 |
| Fix Number | Type | Component | Description |
| 138849 | Defect | Core Transaction Server - Console |
Problem: Cancel Request for Payment is not correlating correctly to the original payment.
Resolution: FTM for Digital Payments is updated to pass the correct ID to Immediate Payments, so correlation to the correct transaction can be done during the cancellation process. |
| 138956 | Defect | Digital Payments |
Problem: The Liberty Web Services APIs might experience the following error: MQJCA1011 exception due to connection pool allocation failure.
Resolution: The global variables representing the jmsConnection, jmsSession, and jmsProducer are localized and the connections are closed. |
| 139158 | Defect | Digital Payments |
Problem: When approval is enabled and asynchronous mode is used, the Liberty Web Services APIs might cause the following error: JMSCC0014 exception due to invalid commit action on the nontransacted session.
Resolution: The invalid commit is removed. In addition, Liberty Web Services API should not use approval and it is also removed. |
| Back to top | 3.2.9.0 interim fix 5 |
| Fix Number | Type | Component | Description |
| 136114 | Defect | Core Transaction Server - Console |
Problem: ReturnPayment Web Service does not work on credits.
Resolution: Added instruction ID to the return payment Web Service. |
| Back to top | 3.2.9.0 interim fix 4.1 |
No changes other than what is mentioned in the Release Information.
| Back to top | 3.2.9.0 interim fix 4 |
| Fix Number | Type | Component | Description |
| 134752 | Defect | Framework - Console |
Problem: FTM is not showing the TCH RTP page on the Participant Directory details page even when the correct roles are assigned. An extra fix is required.
Resolution: Addressed a missing screen group ID when looking for the correct role to populate the Participant Directory details page. Note:
See V3.2.9 Release Information for Financial Transaction Manager for Digital Payments for more steps for this fix. |
| Back to top | 3.2.9.0 interim fix 3 |
| Fix Number | Type | Component | Description |
| DT124863 | Defect | Transaction Server - Console | The Reason code drop-down list is not populating correctly on the Request for Return of Funds pop-up window. |
| DT124976 | Defect |
Core
Real-Time Payments - Engine
Transaction Server - Console
|
Financial Transaction Manager is not showing the TCH RTP page on the Participant Directory details page even when the correct roles are assigned. |
| 133323 | Defect | Transaction Server - Console | Problem: Severe errors are shown in Transaction Server when the user tries to do the end of day action for the business day Resolution: Fixed to not return a severe exception in logs. Also set back the end of day state since Transaction Server could honor the request. In most cases, the error was logged when there was end of day in progress already. |
| 133732 | Defect |
Transaction Server - Console
Web Services - Engine
|
Problem: When a Response to Request for Payment for the transit scenario (not on-us) is processed, Digital Payments retrieves routing information from the transmission. However, the on-us scenario might not have the transmission, which prevents correct processing of the Response to Request for Payment. Resolution: Digital Payments, for the on-us scenario, now retrieves the routing information such as Sender or Receiver from the transaction level instead of the transmission. The transit scenario continues to follow the existing process. |
| 133917 | Defect |
Transaction Server - Console
Web Services - Engine
|
Problem: The customer reference ID that is used in the on-us and transit scenarios are different, which causes a reference failure when Initiate Credit Transfer is the response to the on-us Request for Payment. Resolution: Digital Payments, for the on-us scenario, now retrieves the customer reference ID from the alternate transaction ID. The transit scenario continues to follow the existing process. |
| Back to top | 3.2.9.0 interim fix 2 |
| Fix Number | Type | Component | Description |
| DT112361 | Defect |
Real-Time Payments Engine
Transaction Server Console
|
Batch Process - FTM silently fails for valid transaction. |
| Back to top | 3.2.9.0 Release |
| Fix Number | Type | Component | Description |
|
125122
|
Defect | Web Services Engine |
Problem: Add participant web service was experiencing a delay due to the participant detail creation process. The process was retrieving every detail of the roles of the new participants.
Resolution: Since a new participant does not all have roles, only the available initial roles details are retrieved instead of querying for all different types of role details. |
| 125129 | Defect | Web Services Engine |
Problem: Unnecessary HTTP methods such as OPTIONS were being accepted. Only supported methods are to be accepted for all RESTful services.
Resolution: The web service's deployment descriptor was updated to block the unnecessary OPTIONS HTTP method.
|
| 129003 | Defect | Transaction Server Console |
Problem: The Settlement Window and Distribution Window's filter and sort were using the incorrect database attribute name hence causing the DB2 SQL error.
Resolution: The invalid column names are properly translated leaving all other functionality as is, including the user preferences. The filtering and sorting are now functioning properly.
|
| 130018 | Defect | Web Services Engine |
Problem: The JAXB transformation was not enabled to validate the Create initiate credit transfer and Create request for payment web services API.
Resolution: The new validateSchema (Traditional WebSphere Application Server hosted) and validate_schema (WebSphere Application Server Liberty hosted) request parameters are added for both Initiate Credit Transfer and Initiate Request for Payment web services API. If the new parameter is not used, the APIs ignore the schema validation so compatibility with an earlier version is still supported.
|
| 130286 | Defect | Web Services Engine |
Problem: HTTP header was set to default 200 regardless of whether the timeout occurred for the Initiate Credit Transfer v2 and Request for Payment v2 web services.
Resolution: If a timeout occurred, the Initiate Credit Transfer v2 and Request for Payment v2 web services return a 408 HTTP status code with the transaction status available when the timeout occurred.
|
| 130366 | Defect | Transaction Server Console |
Problem: The participant alias management page was missing the forgery protection.
Resolution: The forgery token is enabled so that it does not fail while the calendar dialog box is loaded.
|
| 130905 | Defect | Transaction Server Console |
Problem: The ibmEntryDate is set to current date by default instead of the requested execution date.
Resolution: The requested execution date is set as an ibmEntryDate, which allows the entry date and business date to be different in the inbound batch records. |
| 130911 | Defect | Risk Management Console |
Problem: The exposed limit monitor detail page turns to read only if the current system time's UTC version is turned to next business day.
Resolution: The current system time is converted to the operational time zone. If such time is within the current business day, then the detail page is still editable. In addition, the limit check update is not allowed if the business day is completed.
|
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9JGN","label":"IBM Financial Transaction Manager for Digital Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"3.2.9"}]
Was this topic helpful?
Document Information
Modified date:
24 February 2023
UID
ibm16517456