We see files that fail, for whatever reason - Usually due to inconsistent data being sent by our business partners.
ARS1127E Row 1: The string "12345" has a length of 5 and the field has a maximum length of 4
ARS1129E Row 3: The string "" could not be converted to a date from the format of %m/%d/%Y %H:%M:%S
ARS4309E Indexing failed
ARS1112E Unable to open the file >/files/dropoff/ondemand/CS01.SHARE.BANKING.BANKING.20221201.003834.ARD.out<
We need to report these failures back to our business partners just so they can handle them.
Does anyone have a systematic way of handling large amounts of file failures, easily determining what they are? I cant figure out an easy way - Since these '88' messages are essentialy stored as documents.
Perhaps an enhancement request - an additional folder field in the system log to log any error codes - for easy searching.
Example - ARS1129E correlates, to invalid date.
Thanks all.
Consider using arslog to write load failures to a specific directory, and process them hourly/daily?
-JD.
Quote from: Justin Derrick on December 14, 2022, 01:39:32 PM
Consider using arslog to write load failures to a specific directory, and process them hourly/daily?
-JD.
I've tinkered with no success, any samples?