This scenario is closely related to the one above. But the difference is that, the addresses that cannot be assigned are written into a separate file for manual checking. Additionally, to write ambiguous addresses in a separate file, the procedure is the same as described here.
Create a job as described in the previous scenario.
Drag the following additional components from the Palette into the design workspace: tMap and tFileOutputDelimited.
Double-click tUniservRTPost to open its Basic settings view.
Select the Use rejects check box and enter "5" in the field if result class greater or equals to. This is the result class from the check of postal codes in addresses, which contain too few or unfeasible data.
Connect tUniservRTPost with tMap_5 via Row > Rejects.
Connect tMap with tFileOutputDelimited via Row > Main.
Define the fields for the output file in the mapping window.