en@frrom
9th March 2011, 16:20
In Exchange only conditions rejected and error rejected records create log file messages. But "record skipped" does not create a log message. Further more, a condition rejected record, will appear in the log file, but the reason the record is rejected is not mentioned.

For end-users this is not very practical, for they do not see which records are skipped and don't know either why records that are rejected by condition, are skipped.

Is it possible to use a (standard?) command or function to add a message to the log file? If so, how?

Also, on the Exchange Schemes session form 2, there is a field 'add extra logging' (tuxch001.logs). Does anyone know what this field does?

Thanks a lot in advance!


Kind regards,
Eli Nager

en@frrom
9th March 2011, 16:38
Figured it out already. I can use function log.mess() in Exchange conditions. Only don't know yet what the "add extra logging" option does...

mark_h
9th March 2011, 17:56
The help on my system says it has to do with exporting based on audit transactions and then importing. They have to be done in the correct sequence.

I was going to say that we actually have a validate exchange scheme session that gives a somewhat more useful message that a consultant developed. This would allow you to see how many would fail, etc. Then again only IT people run exchange schemes here so we really just run it to see if 0 errors, if errors then we know to fix the data file.

RobertP
15th April 2019, 13:27
Its been a long time, but for anyone interested:

Do additional logging will cause exchange to create an additional logfile for records that are skipped. Very useful.