After running, the CDP process returns a set of attributes called the Parser Repository (PREPOS). It also generates completion codes and review codes that identify the conditions that were found for each parsed row.
- Parser Repository. The Parser passes a comprehensive data block called the Parser Repository (PREPOS). The PREPOS contains parsed data including error codes, identification indicators and name information. The output schema determines which of these attributes are returned to the output.
- Return Codes and Status Codes. The Parser generates Return Codes and Status Codes to indicate specific problems and conditions which occurred for each row being parsed.
- Process Report Files. You can also review the Debug file, exceptions file and statistics for information about the Parser process. See Viewing Process Report Files.
Note: The Parser exceptions file includes the final masks for all records (pr_mask_final). A
Parsing Exception file is generated in the entity folder in the repository directory (for
example, C:/Program Files/Trillium Software/MBSW/17/.../metabase/repository_name/entity_id/entity_id_parse_exceptions.txt).
Note: You can also analyze review
codes and review
groups. However, since Trillium cannot
effectively parse the Asian name and address data until the address is validated, review
codes and review groups for CDP are generated when the Postal Matcher is run.