Standard Attributes - trillium_discovery - trillium_quality - 17.1

Trillium Input/Output Attributes Reference Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Trillium > Trillium Quality
Version
17.1
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Input/Output Attributes Reference Guide
Topic type
How Do I
Administration
Installation
Overview
Reference
Configuration
First publish date
2008
ft:lastEdition
2024-02-22
ft:lastPublication
2024-02-22T07:11:30.316879

The table given below lists the standard attributes for the Business Data Parser (BDP).

Table 1. BDP Standard Attributes

Attribute Name

Length

Description

bp_category

100

Attribute used to store category codes assigned to word definitions in the Word and Pattern tables.

bp_completion_code

2

Receives the Business Data Parser return codes:

0—No error

1—Insufficient Storage. When using attribute sub-segments (line_01a, line_01b, etc.) and the sum of the data in these attributes exceeds the redefine attribute 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.

Note: Errors 2, 3, 4, 5, 8, and D are caused by inaccuracies in the file path.

bp_data_present_user1

2

If Y, indicates data is present in the bp_user1 attribute. If blank, indicates data is NOT present in the bp_user1 attribute. Repeated 50 times.

bp_filler_01

8

Reserved for future use.

bp_filler_02

26

Reserved for future use.

bp_filler_03

620

Reserved for future use.

bp_filler_04

202

Reserved for future use.

bp_line_rules

40

Line type identification rule.

Note: You can ignore this attribute as it is mainly used for the Customer Data Parser.

bp_misc_data

2000

Stores any data not identified by pattern processing.

bp_misc_review_codes

300

Review code for MISC.

082—Unidentified pattern

083—Unknown token

086—Output line too long

087—Miscellaneous line too long

088—Too many categories found

090—No data found

000—No targeted conditions found

bp_orig_linepat

2

Original line pattern of input line. The original line pattern for the BDP is an 'M' (miscellaneous line pattern).

bp_pattern

600

Attribute used to store a pattern for debugging and tuning. A pattern contains a maximum of 60 tokens.

bp_stand_orig_data

2000

Label line standardized in original sequence.

bp_user1

200

User-defined business data attribute, containing the standardized data. This attribute is repeated a maximum of 50 times.

Note:  The maximum number of characters is 500 (1000 bytes). If the word/phrase exceeds 100 characters, you must increase the size of this attributes in the Schema Editor.

bp_user1_display

200

User-defined business data attribute, containing the original data. This attribute is repeated a maximum of 50 times.

Note: The maximum number of characters is 500 (1000 bytes). If the word/phrase exceeds 100 characters, you must increase the size of this attributes in the Schema Editor.

bp_user1_original

200

User-defined business data attribute, containing the original data in mixed case used in the input. This attribute is repeated a maximum of 50 times.

Note: The maximum number of characters is 500 (1000 bytes). If the word/phrase exceeds 100 characters, you must increase the size of this attributes in the Schema Editor.
Note: If you use this attribute, it must be specified in BPREPOS for all 50 output attributes (default maximum, bp_user1 through bp_user50). For example, even if you use only bp_user1 through bp_user5, you must specify bp_user1_original through bp_user50_original.