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.
|
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:
|
|
C |
Invalid Service Call Type. Must be either:
|
|
D |
Statistics File Error |
|
F |
Parser not successfully initialized. Settings file may not be correctly defined. Check path and file name. |