IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Not under consideration
Workspace Financial Transaction Manager
Components TCH RTP
Created by Guest
Created on May 25, 2023

RELATED IDEAS

TCH admn.008 (response to partrep msg) need to stored in database and should be able see from OAC

TCH admn.008 (response to partrep msg) need to stored in database and should be able see from OAC

The issue is When the connectors were started, they all sent an participant report request to TCH. The two TCH sites, however, do not report the same data.

If we track these messages, we will know exactly what has been received incase of issues can do any action item, as this data is not stored or cannot be looked from OAC  simillar to 960 or 982 status messages, incase if issues its difficult to track what went wrong or what is the current status, we always to get the cache dump and verify if this is having any issues, US bank has so many time this issue due to a defect from TCH but we could not track the issue and ended up rejecting transactions.

Here is one of example scenario: TS013030709

From the logs we can see that TCH site PRTPA00 (associated with connector1 and connector2) reported connection ID FNTHPRD as unavailable, while TCH site PRTPA10 (connector3 and connector4) did not include FNTHPRD in the report, indicating that it was available


ricklp (IBM)

May 18, 2023, 13:14

 

Answer from FTM L3--

This is the same issue we have seen previously. When the connectors were started, they all sent an participant report request to TCH. The two TCH sites, however, do not report the same data.

So TCH should be asked to see why their sites ore not in sync.

 

From the logs we can see that TCH site PRTPA00 (associated with connector1 and connector2) reported connection ID FNTHPRD as unavailable, while TCH site PRTPA10 (connector3 and connector4) did not include FNTHPRD in the report, indicating that it was available:

 

connector1:

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - TCoRspFromRtp - DBAvlbtyRptResponse received from: PRTPA00, Status: ACTC, CreDtTm: 2023-05-14T02:25:00

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> CITI

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FISPCM

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> REG

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FNTHPRD

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> HNB

2023-05-14T01:25:00:375 - FTMHA1P - FTMHA1P1.NODE - TCH.Connector1 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> WELLS

 

connector2:

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - TCoRspFromRtp - DBAvlbtyRptResponse received from: PRTPA00, Status: ACTC, CreDtTm: 2023-05-14T02:24:43

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> CITI

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FISPCM

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> REG

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FNTHPRD

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> HNB

2023-05-14T01:24:43:516 - FTMHA2P - FTMHA1P2.NODE - TCH.Connector2 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> WELLS

 

connector3:

2023-05-14T01:24:32:638 - FTMHA2P - FTMHA2P2.NODE - TCH.Connector3 - Online:TRUE - SignedOn:TRUE - TCoRspFromRtp - DBAvlbtyRptResponse received from: PRTPA10, Status: ACTC, CreDtTm: 2023-05-14T02:24:32

2023-05-14T01:24:32:638 - FTMHA2P - FTMHA2P2.NODE - TCH.Connector3 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> CITI

2023-05-14T01:24:32:638 - FTMHA2P - FTMHA2P2.NODE - TCH.Connector3 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FISPCM

2023-05-14T01:24:32:638 - FTMHA2P - FTMHA2P2.NODE - TCH.Connector3 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> REG

2023-05-14T01:24:32:638 - FTMHA2P - FTMHA2P2.NODE - TCH.Connector3 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> HNB

 

connector4:

2023-05-14T01:25:02:062 - FTMHA1P - FTMHA2P1.NODE - TCH.Connector4 - Online:TRUE - SignedOn:TRUE - TCoRspFromRtp - DBAvlbtyRptResponse received from: PRTPA10, Status: ACTC, CreDtTm: 2023-05-14T02:25:02

2023-05-14T01:25:02:062 - FTMHA1P - FTMHA2P1.NODE - TCH.Connector4 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> CITI

2023-05-14T01:25:02:062 - FTMHA1P - FTMHA2P1.NODE - TCH.Connector4 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> FISPCM

2023-05-14T01:25:02:062 - FTMHA1P - FTMHA2P1.NODE - TCH.Connector4 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> REG

2023-05-14T01:25:02:062 - FTMHA1P - FTMHA2P1.NODE - TCH.Connector4 - Online:TRUE - SignedOn:TRUE - AvlbtyRpt - Not Connected->CnnctnId-> HNB

 

Needed By Not sure -- Just thought it was cool

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.