We are having an issue regarding to the Prognosis process that read the PTLF file. We added to the BASE24 configuration a new PTLF file which is inactive (no receiving new trx) during great part of the day.
When the new configuration is started when that PTLF is active, the process read the trx and collect the transaction data until the PTLF is inactive again. In that moment the Prognosis process does not read it again although the ptlf has transactions again.
On the other hand, if the BASE24 configuration is started when the PTLF is inactive, the process never read transaction even the ptlf has new transactions.
Is this a Prognosis BUG or is there some kind of parameter to be configured to correct this behavior?
There are two configurations I suggest you look at in IRTSVCOI which might be involved in these systems.
In particular I would look at Trawler-max-idle-time-in-minutes, as if there is no transactions for 5 minutes it may stop reading.
Max-Back-Time as this is how far bar it will read to 'recover' when you start it back up.
MAX-BACK-TIME-IN-MINUTES = <n>
MAX-TPS-ON-RECOVERY = <n>
First of all, thanks for your response.
Following your suggestions, we modified the value TRAWLER-MAX-IDLE-TIME-IN-MINUTES in IRTSVCOI file from 5 minutes to 90 minutes and no changes in the behavior.
On the other hand, we realized that the time the IRTSVCOL process release the "today" ptlf file is 60 seconds aprox. (Since the configuration was applied).
BTW, the process have taken the "tomorrow" ptlf file ever. Just in case, the "tomorrow" ptlf file is generated 24 hours in advance.
Could this issue be related to BASE24 "NEW-FILE-CHECK-DELAY-IN-SECONDS" parameter?
Thank you so much!
Reading a little more, I'm checking that IRTSVCOL is used for "Transaction Surveillance", a process we are not using. So, I guess any parameter modified within IRTSVCOI is not used.
The Process that read the different logs (ptlf) is IRB24TLR. This is the process that release the "inactive" ptlf.
"Inactive" = This ptlf receive a lot of transactions three times in a day, but the rest of the day don't receive any trx.
@Claudio_Osadczu, we are still looking into this but I don't yet have an answer on how to handle this situation.
@Claudio_Osadczu Hi, I have discussed this with someone else internally and the behavior described is not what we would expect IRTXNCOL to act like.. or we are not following the circumstances completely. Can you create a support case and describe the different scenarios in detail, provide an IRFAX, and reference this community thread?
Thank you Chris,
We already created the case #00037490 on January, 25th.
BTW, the IRFAX file was uploaded to that case.
Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...Join Webinar