ISErrorRefiner
Use the ISErrorRefiner activity to modify error lines (also called DTL lines) in an Instream results file.
For more details on ISErrorRefiner, refer to the ISErrorRefiner PDF document.
Example
An example use of ISError Refiner is as follows.
The following data is encountered during validation:
DTL 30 2330AN4 1343 27 4 1 1 7 41652 2 14482 8 7024 X7 21
The ISErrorRefiner configuration file specified in the input field "config_file" contains the following modification instructions:
The modified Instream detail file (saved as specified in the input field "output_file") contains the changed severity and element position rather than the default settings.
The modified data appears as follows:
DTL 30 2330AN4 1343 27 2 1 1 7 41652 3 14482 8 7024 X7 21
Input
The Input tab contains the following fields.
| Field | Literal Value/Module Property/Process Property? | Description |
|---|---|---|
| instream_result |
Specifies the file path and name of the Instream detail file to be modified. (Required) |
|
| config_file |
Specifies the file path and name of the ISErrorRefiner configuration file containing the modification instructions that ISErrorRefiner is to use. (Required) It should not be the same as the Input, Output, or Log files. (See the ISErrorRefiner PDF document, Configuration File Layout section for more information about the ISErrorRefiner Configuration File.) |
|
| output_file |
Specifies the file path and name for the output modified Instream detail file. (Required) It should not be the same as the Input file. |
Output
The Output tab contains the following fields.
| Field | Literal Value/Module Property/Process Property? | Description |
|---|---|---|
| instream_result_out |
File path and name for the output modified Instream detail file. |
|
| return_code |
Specifies the return code. For example, 0 means the program ran successfully, 2 means a specified file could not be found, and so on. Return codes are listed in Chapter 4 of the ISErrorRefiner PDF document |