Have anybody sees the ATM transaction with respond code 74 in their displays. They are not being display or account for in the out of the box product.
Solved! Go to Solution.
In the display window Associate names tab, add "ACQUIRER+RESPOCODE" name to the Selected names field. Do you see Response Code 74 being captured in the display?
There is a Response Code Descriptin file you can modify yourself so it is populated if response codes are coming up without a description.
I admit it is very frustrating to find the name of these file in the 11.6 helps but simply typing "Maintaining Response Codes" in any version of the help will bring this right up previous versions of the help is super easy ( @Chris )
I am not following why @LindaYu would have you add that ASSOCIATE name to the display as generally you don't want more than one ASSOCIATE per display nor what that would buy you as RESPDESC still would just be blank.. other than it might tell you the acquirer the transaction might be coming from to narrow it down.. but in most of our solutions we use the internal normalized ResponseCode and Description vs. the external one. So Linda if you can clarify your thoughts on what you were thinking when you suggested this.
The issue is not related to the Response Description. It is that any transaction with respond code 74 will just not be display at all. In ay total transactions display they also seem to be ommited in the count value dispite that those transactions are register within the ATLF file.
I have seen totals omitted from Approval / Decline / Timeouts counts/metrics when a response code is missing from the same tables and missing the classification of Approval / Decline / Timeout. If it is being classifed as "N" or "U" then it doesn't go into any count/metric.
I am not recally what 74 is off the top of my head.. but if Prognosis is not processing a transaction at all there is almost always a log an error the the WVLOG.
If the response code exists in the tables in my previous reply and no error is logged in the WVLOG then we can trace via a support case exactly what is happening.
The 74 respond code description within the ATLF is "MSG ERR" or "MSG ERR".
Can other classification, apart from Approval / Decline / Timeout, can be added to be included to the metric or counters?
When refereing to the transactions classification, do you mead the transaction code or is it another field?
Does the "N" and "U" clasificaction stands for Non-Applicable and Unknown?
What type of event should I be looking for in the WVLOG? I do not recall seeing an event related to ATM, ATLF, Base24, Transaction nor Respond Code.
I am including you in the case for more details.
I believe it effects all of our metrics I believe beyond A/D/T but still would be counted in in some of them.. I don't have access to the code to tell you which ones it does and does not. .. just all response codes have to exist in those lookup tables. The value I believe varies but its either "N" or "U" and yes that means "Unknown".
If anything is logged it would be "unknown" something.. but looking at another customer running another platform's WVLOG they didn't get any errors when 10% of their transactions were hitting "Unknown". I know I've seen an error before but I am also not seeing it in the Server\Configuration\defserr file but did find it will error for sure if you configure it incorrectly.
ERROR ENG 5644143 "Invalid response type - %1TypeName"
CAUSE: Invalid response type in RESPONSE CODE configuration. The valid type must be
"APPROVED", "DENIED", or "TIMEDOUT".
ACTION: Program continues. No data available.
For others following this issue, we have a case on it. From what we have seen, there is nothing blocking the actual response code. There is some filtering at the record type. Below are the record types as defined by ACI in their "BASE24 Release 6.0 Refresh and Extract Data Structures" docment
Prognosis only captures the "01 = Customer transaction" record type, others will be skipped. Looking at the data will give you more information. Any other record type in the transaction data will be skipped.
Hhhmm late to the party.....
IR support Case 11658 - resulting in an RFE back in 2015
Custom log-reader on NonStop to read more then only tlf.head.rec^typ = "01"