IBM Support

V3.2.7 Fix List for Financial Transaction Manager for Digital Payments

Fix Readme


Abstract

This document contains V3.2.7 fix list information for Financial Transaction Manager for Digital Payments for Multiplatforms.

Content

V3.2.7 Fix List for Financial Transaction Manager for Digital Payments (DP)

This document contains fix list information for:

V3.2.7 Financial Transaction Manager for Digital Payments for Multiplatforms


The following is a complete listing of available FTM for Digital Payments fixes on all platforms. Multiplatforms fixes are available on Fix Central.




Note:


V.R.M.F Fix List Links to FixCentral Download
(by Fix ID)
Product Build Date Pre-req
3.2.7.0 interim fix 2 3.2.7.0-FTM-DP-MP-iFix0002 Digital Payments 20220127-1721 3.2.7.0
3.2.7.0 interim fix 1.2 3.2.7.0-FTM-DP-MP-iFix0001.2 Digital Payments 20220106-1651 3.2.7.0
3.2.7.0 interim fix 1.1 3.2.7.0-FTM-DP-MP-iFix0001.1 Digital Payments 20211215-0758 3.2.7.0
3.2.7.0 interim fix 1 3.2.7.0-FTM-DP-MP-iFix0001 Digital Payments 20210625-1447 3.2.7.0
3.2.7.0 Available from Passport Advantage Digital Payments 20210407-1900 None


Note: APAR links for security fixes aren’t active.

Refer to V3.2.7 Release Information for Financial Transaction Manager for Digital Payments (DP) for further details on issues and changes.

Note: The update instructions referred to by interim fixes are located in the install location\component\doc folder, for example:

install location\shared\v327\pfs\Gateway\doc\updates.


Back to top 3.2.7.0 interim fix 2
  
Note: 3.2.7.0 interim fix 2 contains a security fix.
 
Fix Number Type Component(s) Description
DT107360 Defect
Gateway Other
RiskMonitorLimitsViews Service is showing same available monthly and daily credit amount even for participant sent Zelle payments.
DT107461 Defect Core - Other CXCPayment service getting DB2 exception when sending payment to already existing recipient
DT109967 Defect Transaction Server - Console MQ Queue Messages are getting piled up under queue.
126736 Defect Real Time Payments - Other
Problem:  Zelle July Mandates - Enrolled As Solution.
Resolution:  Added sharedDirectoryFirstName and sharedDirectoryLastName to the Outgoing Payment in the CXCParticipantView call.


Back to top 3.2.7.0 interim fix 1.2

Note: 3.2.7.0 interim fix 1.2 contains a security fix.
 


Back to top 3.2.7.0 interim fix 1.1

Note: 3.2.7.0 interim fix 1.1 contains a security fix.
 
Fix Number Type Component(s) Description
DT107360 Defect Gateway - Other RiskMonitorLimitsViews Service is showing same (original customer limits amount) available monthly and daily credit amount even for participant sent Zelle payments.
DT107898 Defect Real Time Payments - Other Shared Directory First Name and Shared Directory Last Name were not populating in database correctly.
125915 Defect Real Time Payments - Other
Transaction Server - Console
Problem:  Making a Zelle payment against a Zelle Payment Request throwing SQL error.
Resolution: Addressed issue where the responder name  was not updated correctly when completing a payment request.  
125974 Defect Real Time Payments - Other
Problem: CXCPayment service is not updating send payment count value when CXC recipient last name is null.   
Resolution: Addressed issue where Send Payment Count was not being updated properly with Recipients with no last name.  
126575 Defect Core - Other
Real Time Payments - Other
 
Problem:  Zelle : Issue with deleting a participant.
Resolution:   When deleting a participant, all recipients are updated to inactive at once.


Back to top 3.2.7.0 interim fix 1
  
Fix Number Type Component(s) Description
DT091133 Defect
Business Rules Other
Core Other
Gateway Other
Transaction Server Console
Transaction Server Other 
Remove Business Rules Tactical Activation when creating or modifying Zelle or TCH participants using the UI or API.
DT094451 Defect Distribution Engine Nullpointer exception when creating outbound presentment for null file for activated ZELLE business day and Payments "Not Getting Mapped" and Distributed
DT094687 Defect Gateway - Engine Multiple transactions with the same ITEM.CAPTURE_SEQ_NUM causes Return matching problems
DT099153 Defect Gateway Other Extra transmissions created in NACHA outbound transmission window and incorrect transmission definition.
DT099183 Defect Gateway Other Returns transaction are sent to older business day on outbound transmission.
DT099481 Defect Real Time Payments Other Payment Request to Out of Network is timing out.
DT099846 Defect Core Other
Gateway Other
Realtime Payments Other
CXC_ParticipantView returns no participant message even though participant is in the database
DT102598 Defect Risk Management Engine Calling the RiskMonitorLimitsViews web service or viewing the Exposure Limit Monitoring page periodically causes a Null Pointer Exception.
DT103132 Defect Real Time Payments Console During the create payment process, the EJB rolled back.
DT103409 Defect Core Other
Web Services Engine
Participant ID not found error is generated during Create Schedule Model for newly created participants.
DT105481 Defect
Business Rules Other
Core Other
Distribution Other
Gateway Other
Realtime Payments Other
Risk Management Other
Transaction Server Console
Transaction Server Other
JDBCLogHandler has potential to leave uncommitted work if/when retrying during J2SE logging.
91370 Defect Gateway - Other
Problem: Zelle Debit Card Reconciliation Task not allowed to run concurrently which doesn't align with EWS.
Resolution: Added methods to check if during task processing, another method instance failed because it was locked out.  The task will trigger the failed task to re-launch.
118013 Defect Services Framework Console SECURITY: CVE-2020-5000
117116 Defect Transaction Server Console SECURITY: CVE-2020-5002
120609 Defect Distribution - Engine Problem: For null file endpoints, Distribution is failing to map a payment which has a different mapping criteria than existing payments which have already been mapped to a null file.
Resolution: In Distribution engine, during mapping of an inbound batch, when reading unmapped payments from the database, the SAME_DAY, GOVERNMENT_INDICATOR, and SETTLEMENT_DEFERRED fields are set as either 'Y' or 'N' (or 'C'/'G' for GOVERNMENT_INDICATOR).  If the database value is not 'Y', 'N' (or 'G' for GOVERNMENT_INDICATOR), the value is interpreted as 'N' (or 'C' for GOVERNMENT_INDICATOR).
121076 Defect Transaction Server Console SECURITY: CVE-2021-20531
121355 Defect Realtime Payments Console Problem: Performance issue with CXCParticipantView Read service while reading incoming payment requests.
Resolution: Improved performance of various queries in Payment Request processing that use selects to OBJ_VALUE table.
121687 Defect Distribution Engine Problem:  Distribution - Unable to remake business day in complete status.
Resolution: Changed remake code path in Distribution engine to support remake of an outbound transmission for which the business day is in complete status.
122220 Defect
Distribution Engine
Distribution Other
Problem:   Distribution is creating multiple batches for single EndPoint.
Resolution: In Distribution engine, modified the logic which determines when to request build/release of file-to-file outbound transmission.
122702 Defect
Framework Console
Real Time Payments Other
Problem:  NullPointerException is occurring in 10x framework.
Resolution: Code Fix for NullPointerException in third party 10x framework when invalidating browser sessions.
122951 Defect
Real Time Payments Console
Transaction Server Other
Problem: Transaction Server console is not creating new processing batch when passing payment insert bean.
Resolution: Code change includes Payment Scheme when invoking internal classes.
123005 Defect Transaction Server Console
Problem: Inbound Transmissions > Force Filer message is set to True but Transaction Server > User Interface has it set to False.
Resolution: Moved a condition in the code to the correct spot.
123122 Defect
Services Framework Console
Services Framework Engine
Problem: Usage Purge Task where deleting entries could cause an error with SQLSTATE 23001
Resolution: Resolved an issue with the Usage Purge Task where deleting entries could cause an error with SQLSTATE 23001.
124094 Defect Distribution Engine
Problem: Issue with the outbound distribution for MLP Payments - Delay hierarchy retry.
Resolution: In Distribution engine, during mapping, if Db2 unique constraint error is encountered when creating new outbound_presentment/outbound_pres_group record, delay 5 seconds before retrying the operation.
124895 Defect Risk Management  Engine Problem:   Risk is not applying payments to daily or monthly limits.
Resolution: Code change made so that the presentments are cleaned up after applying payments to the limits.
125176 Defect Distribution Engine
Distribution Other
Problem: Changing log message severity to information.
Resolution: The message severity changed for IZLBW026S and IZLBW031I to information level.
125240 Defect Services Framework Engine
Problem: Zelle debit card reconciliation task fails when more than one debit card file is ingested at same time.
Resolution: Code fix with Zelle debit card reconciliation task not re-firing on failure due to a concurrent instance executing.


 
Back to top                   3.2.7.0 Release                                                                                   
  
Fix Number Type Component(s) Description
108337
defect Transaction Server Console
Problem: The outbound raw data on the hierarchy screen for an outbound pain.013 does not show the outbound version of the message but instead shows a copy of what is in the inbound raw data
Resolution: The raw data for pain.013 outbound will now display the message that is different than the one used for inbound raw data. The outbound raw data is isf format.
108355 defect Transaction Server Console
Problem: Outbound response to request for payment pain.014 shows wrong data in Outbound box of Raw Data on hierarchy screen
Resolution: The reason pain.014 outbound was copy from the inbound was due to the configuration in the property to display FTM raw data was incorrect. The default installation will now contain the default configuration so that pain.014 raw data is displayed.
116954 defect Notification of Change Console, Transaction Server Console 
Problem: Unable to see a NOC UI grid showing up as expected which says what record (or records) will have a NOC
Resolution: The NOCdialog had invalid data mapping caused the grid not to get populated. Such has all been corrected.
118019 defect Settlement Engine
Problem: When canceling a transaction, settlement engine creates inbound balancing transmission with 0 dollar amount
Resolution: Logic in settlement engine has been corrected so that correct balancing transmission is created.
118037 defect Settlement Engine
Problem: When canceling a transmission, settlement engine creates inbound balancing transmission with 0 dollar amount.
Resolution: Logic in settlement engine has been corrected so that correct balancing transmission is created.
118190 defect Settlement Engine Problem: When canceling a batch, settlement engine creates invalid inbound balancing transmissions Resolution: Logic in settlement engine has been corrected so that correct balancing transmissions are created.
119579 defect Transaction Server Console
Problem: Additional IDs for the read inbound transaction should be added.
Resolution: The Read inbound transactions web services now include FTM batch ID and FTM transmission ID in is response. In addition, such value can be filtered to retrieve the associated transactions. e.g. if the filter is based on FTM transmission ID, all associated inbound transactions with such FTM base transmission ID will be returned.
119625 defect Transaction Server Other
Problem: In a high load environment some TCH RTP transaction are missing answer from DP
Resolution: For the IP - Digital Payments complete event in the scheduler the <PARAMETER name="outboundReady">!2</PARAMETER> test has been removed. It was found in some condition this field could be set to 2 before the event was tested causing the message not to be sent to FTM for IP.
120054 defect Core Console
Problem: Delete button causes System Error on uneditable Participant Limit Monitor screen.
Resolution: The delete button on the Participant Limit Monitor should appear only when Participant is activated so that view mode is EDIT.
120234 defect ACH Other
Problem: The FTM IP TCH Application version changed to 3.2.7
Resolution: Spreadsheets for DSU were updated to be for FTM Immediate Payments TCH Application version 3.2.7
120619 defect Web Services Engine
Problem: WebService: CreatedScheduledPamentModel is not successful as an error in immediate payment.
Resolution: If birth date is populated then birth country and birth city are required fields. The new edit has been added to prevent an error in Immediate payment.
120677 defect Core Console
Problem: Recipients 'Create' shows an incorrect Header value
Resolution: The title for create dialog for the recipient should say Create Recipient. The latest add of Unknown type incorrectly populated the title.
120934 defect Web Services Engine
Problem: CreateRecipient web service is returning invalid values for the recipient ID
Resolution: When reformatting the response from the create, the ID was not reset. The fix included the recipient ID in its response.
121311 defect Web Services Engine Problem: Read Inbound Transaction Webservice, company name filter is mapped to receiving FI name Resolution: The company name mapping was recipient FI name instead of the company name. Such incorrect mapping has been corrected.
121836 defect Framework Console
Problem: Need check on user ID string length longer than 32 (source = 60 bytes). No validation existed so sometimes, null pointer exception is logged in enterprise logging system.
Resolution: The audit source contained a string variable with length more than 60 bytes. Such was being ingested to the audit record and caused the 302 error. The remedy is to block more than 60 bytes user ID in the source at any case.
122001 defect ACH Other
Problem: OnUs scenario with pain.013, then pacs.008. This resulted in NPE in Distribution.
Resolution: When responding to pain.013 (request for payment). the pacs.008 must be be associated with the transmission ID. This is done by finding the associated related transactions and its parent transmission IDs in turn. In this case, the multiple related transaction ID can be found. All of them must be tried to attempt to find the right transmission ID.

[{"Type":"SW","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.2.7"}]

Document Information

Modified date:
01 March 2022

UID

ibm16439973