unauthorized Transaction over an account

Dear all

I need to know the unauthorized transaction affecting an account is due to which module (MM,TT,FT,etc..) & the ID of this transaction

What i actually do now is taking the account number & go search in unauthorized transaction under each module which really sucks

If any one have a solution , please let me know

Thanks in advance

There is a file named FXXX.ENTRY.HOLD. This will help you to get the unauthorized entries for all transactions.

Do you also face the problem that records exist in ENTRY.HOLD / FWD.ENTRY.HOLD which have been delete from the respective application ? Have you ever reported this to the HD ??

What problem? I can't get you.
The records exist in ENTRY.HOLD / FWD.ENTRY.HOLD is of unauthorized transaction entries. During EOD in job UNAUTH.PROCESSING these records will get deleted if .UNP is set for the respective applications in PGM.FILE.

And what is the intention of the fields ENTRY.HOLD / FWD.ENTRY.HOLD in ACCOUNT ? They should point to records in the mentioned files but in our installation there is no ACCOUNT with any value in this fields...

As of I know these fields are not updated right now. But in help text it's mentioned.

Dear Durai

Thanks for your reply , but FXXX.ENTYR.HOLD , contains all unauthorized entries overall the system with @ ID only (transaction reference) , what am asking for i have account number & want to know the unauthorized debits on this account & their IDs

@jpb
"The point is that there are records in ENTRY.HOLD / FWD.ENTRY.HOLD pointing to non existing transactions (neither live nor $NAU) which gives the impression that one can't rely on its content"

If there is any records like you mentioned then we have to raise it with HD ;-)

"And yes, I know the doc - that's why I'm asking. These fields would be the easy solution for johnnyslife's problem, but ...
The fields are there since 2004, so it's taking more that 8 years to implement them? Strange !!"

They might have not implemented because of write on Account file and locking/performance problems. ;-)