Metadata conversion is automatically handled by the Arbutus Data Definition Wizard during the table definition process. Most language or system constructs are automatically converted from the host environment directly into metadata compatible with Arbutus. This includes:
COBOL
- Copybook is directly read from host, or may be downloaded and read locally
- Fixed length or variable length file definitions
- All supported data types and data formats
- Level 88 fields, including single or multi-valued fields
- REDFINES of entire record, group of fields or individual field
- OCCURS including nested OCCURS
- Multiple copybooks may be concatenated, and treated as:
- Separate record definitions
- A single record definition
PL/1
- Copybook is directly read from host, or may be downloaded and read locally
- Fixed length or variable length file definitions
- All supported data types and data formats
- Supports both F-format and V-format input record formats
- Structures
- Arrays
- Multiple copybooks may be concatenated, and treated as:
- Separate record definitions
- A single record definition
DB2
- Table names
- All column attributes are automatically converted, including:
- Name
- Length
- Type
- Decimals
IMS
- Automatic DBD processing to determine and convert:
- Segment names
- Hierarchical paths
- Field information, including:
- Keys
- Name
- Type
- Length
- Decimals
Easytrieve
- Reads field information from source, including:
- Name
- Type
- Start
- Length
- Decimals
Where your data definitions are stored in an unsupported format, or are not available electronically, the Data Definition Wizard supports a graphically assisted field definition process.
While not fully automated, virtually any metadata that is available in electronic form can be converted to Arbutus compatible metadata. This includes data dictionary reports, metadata stored in PC files such as a Word document, or documentation pages printed to a file, like SMF record layouts from IBM documentation.
For any metadata, whether created manually or automatically, the administrator may:
- delete any definitions never to be used
- add any definitions as required
- rename any definitions, to support ease of use
- temporarily hide any definitions, which may be required in the future