The BDP process generates review and completion code attributes and other output that identifies the conditions that were found for each parsed row.
- Ways to review the parser results...
-
- Review Codes. The BDP generates review codes in the bp_misc_review_codes attribute to identify any problems or conditions which occur for each parsed row. You may need to analyze the output entity to determine the values for this attribute.
- Completion (Return) Codes. BDPcompletion codes are written to the output attribute bp_completion_code. Each code corresponds with a parser or file path error. A code of 0 (zero) indicates no errors were generated.
- Miscellaneous Attribute. The output attribute bp_misc_data stores data that is not recognized by the parser. Review this output to determine if you need to add more word definitions, or create more categories or substring patterns.
- Output Entity and Attributes. Open the BDP output entity in List View to view the original and recoded output attribute data. You can compare data, verify standardizations, see miscellaneous (undefined) data, determine if you need to define more words, and assign or create different categories.
Note: All user-defined attributes appended by DISPLAY (for example, BP_USER5_DISPLAY) contain original data. All non-DISPLAY user-defined attributes (for example, BP_USER5) contain the standardized data, such as recoded words and phrases. If there are no recodes, the original data is displayed. Depending on how they are defined, synonyms may also be contained in DISPLAY attributes. For more information, see Synonyms and Adding Word and Phrase Definitions.-
Results Files. Open the following files for information about the
Parser process:
- The statistics, error, and log files include information indicating whether the process ran successfully, number of records processed, bypassed, and written to the output. Open these files from the Summary Data or Project View. The BDP statistics file differs from that of the CDP; it does not include Review Groups.
- Debug files are available when you enable this Output Setting option.
- The Parser Tuner exceptions file contains information about bad patterns.
- The control (.TSD) file contains read-only BDP process settings.
Note: For information about output attribute codes, see Parser Review Codes and Parser Completion Codes.
To open result files from the Navigation View
- Select the Projects tab and expand the project that contains the BDP results.
- Expand Processes and right-click the BDP process.
- Select View > and one of the following file types:
- Control File (.TSD/.STX)
- Log File
- Error File
- Graphic Stats File
- Text Stats File
- Parser Customization Stats File
The file opens.
- Scroll through the file to find the information you need to review.
To open result files from the Summary Data View
What To Do Next
If necessary, perform the following corrective action and run the BDP process
again:
- In the Schema Editor, add, redefine, or delete attributes as needed; for example, delete output attributes that you are not using to reduce record length, increase performance, and make the output easier to work with. For information, see Editing Attributes.
- Review and correct any bad patterns (patterns that the parser cannot identify) in the Parser Tuner. For more information, see Correcting Pattern Problems.
- Modify word definitions, masks, and patterns contained in the Customized Definitions word and pattern table in the Parser Tuner. For more information, see Adding a Definition.
- Adjust other BDP configurations, options, and advanced rules.