Prognosis 10.3 can't find all transactions sent from ATM in TRANDET records

[Abdelaziz_AMAMR]

Hi,
in the lase days we have a problm to find all the transactions sent by the ATM.
when we display the transaction détails (TARNDET) we do not find all ATM transactions. we loose some ones ( a round 20 transaction in 1 hour).

we use "irepstlr" as log reader and IRTSVCOL without EXCEPTIONS RULE and the parameter "NUMBER-OF-TRANSACTIONS = 54000".

problem of buffer ?????? I don't no !!!
I think to increase the NUMBER-OF-TRANSACTIONS to 72000 but I am not sur to get a results.

can you help me please.
Thank you from advance.

Best regards

[ChristopherS]

Hi,
Off the top of my head... being you are on Prognosis 10.3 an important question is how many rows are in a typical interval of the TRANDET record? Does it ever exceed or get near 32,000 per interval?

If so increasing the Number-of-Transactions further (you currently have it set 3x the out of box setting) will not help.

If your exception rules are commented out or removed in IREPSTLR it shouldn't be interfering with the transaction record collection. I don't off the top of my head
believe you would see any IRTSVCOL caching / delays causes by this as well. So I would initially rule that out.

If you are hitting anywhere near 32,000 rows in any interval, even only a couple intervals an hour, this might account for the 20 or so lost transactions. If this is the case the next thing to consider is probably consider an upgrade to Prognosis 11.1 which can have more rows per interval on most platforms.

Christopher

[GeraldC]

Hi,

A good point, with buffer at 54000 you're limited to the 32K limit, but note that this 32K limit is Per Interval in Prognosis - just make the interval shorter if your display/database with Where ALL is full at 32767 rows in some intervals, you could use your highest TPS rate to calculate an appropriate time interval to avoid losses from that limit.

Otherwise, there are no known causes/fixes for losses at the collector level (IREPSTLR / IRTSVCOL ) in your version 10.3 or later so make sure you open a case with IR Support if you need further assistance and we can get more details and diagnostics and investigate further.

HTH

P.S. more details about that buffer NUMBER-OF-TRANSACTIONS in Help here:
Prognosis for Payments > ACI BASE24 and BASE24-eps > Transaction Surveillance > Configuration > TRANSACTION-DETAILS

[Abdelaziz_AMAMR]

Hi,
Thank you for your explanation, Christopher and Gerald,
OK, I understand that I am limited to 32000 Transactions. Gerald, how can I change the interval time to avoid losses.

Thank you.

[Abdelaziz_AMAMR]

Hi
it's OK ,
I found the collection interval and I changed it,
but the problem remains.
and some transactions detail don't collected by prognosis but I can see them on Base24 by other tools.
regards

[Anon]

Hi Abdelaziz,

There are a number of configuration items that control what transactions are collected and displayed in Prognosis. Assuming that you have reviewed these already it's probably best to log a call with support as Gerald suggested; they are in the best position to collect and review the appropriate information and advise you on the best way to resolve the problem.

Cheers,
Mick