IBM Support

Fix list for IBM Financial Transaction Manager for Immediate Payments 3.2.11 Multiplatforms

Fix Readme


Abstract

Fix list for IBM Financial Transaction Manager for Immediate Payments 3.2.11 Multiplatforms

Content

Note:
V.R.M.FDownloadBuild datePrerequisites
3.2.11.2 (Fix pack 2)Available for download at Fix Central20251016-1735None
3.2.11.1 (Fix pack 1)Available for download at Fix Central20230428-0654None
3.2.11.0
Available from Passport Advantage
20230126-1528None



Back to top3.2.11.2 (Fix pack 2) 
  
Fix numberTypeComponentDescription
TS018419312
APAR
TCHPayment before sign off was rejected (19432)
 
 

Back to top3.2.11.1 (Fix pack 1) 
  
Fix numberTypeComponentDescription
145015
Defect
 
Problem: When MAX_REPEAT_VALUE / IP_FROM_DBTR_INSTR = 2 is set, repeated messages are sent, but after that, Timeout Waiting For CSM Payment Acknowledgement are constantly created
Solution: the action that updates the timeout now includes a check for max repeats and if reached/exceeded sets the timeout to NULL
 
 

Back to top3.2.11.0 
  
Fix numberTypeComponentDescription
141195Defect Problem: An incoming RFP that was accepted cannot be canceled or expired by an incoming camt.056 message from TCH RTP. 
Solution: The process model was updated to allow this function.
142574DefectReal Time PaymentsProblem: The Initiate Credit Transfer v2 and Request for Payment v2 APIs that use the <Invcr> and <Invcee> elements, which are new to TCH 3.0, fail when their <Id> is specified under LEI. 
Solution: The new to TCH 3.0 elements <Invcr> and <Invcee> must specify their <Id> under <RmtInf><Strd><Invcr><Id><OrgId><Othr><Id> and <RmtInf><Strd><Invcee><Id><OrgId><Othr><Id>. 
Limitation: When you are moving from TCH 2.9, which allows only a single <RmtInf><Strd><RfrdDocInf> element, to TCH 3.0, which allows multiple <RmtInf><Strd><RfrdDocInf> elements, still use a single <RfrdDocInf> element. Support for multiple <RmtInf><Strd><RfrdDocInf> elements will be added in future releases.
143041Defect Problem: The module that validates operator-initiated requests to return funds does not enumerate UPAY as a valid code even though it is offered in the model or OAC and is otherwise supported in the code modules. 
Solution: UPAY was added to the validation list.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9GGC","label":"IBM Financial Transaction Manager for Immediate Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]

Document Information

Modified date:
25 October 2025

UID

ibm16839187