Parser Completion Codes (CDP/BDP) - trillium_discovery - trillium_quality - Latest

Trillium Control Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
Latest
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
Copyright
2024
First publish date
2008
Last updated
2024-10-18
Published on
2024-10-18T15:02:04.502478

The following table shows the return codes that appear in the pr_completion_code or bp_completion_code attribute, in output from the Customer Data Parser or Business Data Parser (not all codes in the table are relevant to the BDP). You view this code by drilling down on the Values metadata in the attribute.

Note: Several errors (2, 3, 4, 5, 8, D) are caused by inaccuracies in the file path.

Value

Description

0

No error

1

Insufficient Storage. When using DDL field sub-segments (line_01a, line_01b, etc.) and the sum of the data in these fields exceeds the redefine field length, the data is truncated and a value of ‘1’ is returned. Processing continues normally for all other lines.

2

Table Error – Pattern, Word and/or City tables not found

3

Log File Error

4

Detail File Error

5

Pattern-Word-City Tab Error – Pattern, Word and/or City tables not readable.

6

Too Many Tokens

7

Line Definition Error

8

Display File Error

9

Invalid Parser Handle

A

Invalid Parm File Entry

B

Invalid Interface Call Type. Must be either:

  • O—Open
  • P—Process
  • C—Close

C

Invalid Service Call Type. Must be either:

  • D—Send to Display File
  • E—Supply Error Text

D

Statistics File Error

F

Parser not successfully initialized. Settings file may not be correctly defined. Check path and file name.