The loaddata command creates an entity by importing data from a data
source and storing it in a repository.
createentity command.The required syntax for the loaddata command depends on the data source
type you choose for the entity. The command syntax is different if you are importing
data from a Trillium file as compared to importing data that uses a COBOL copybook file.
The command returns the job identifier for the loader job.
The command supports five data source types, which are listed in the following table.
|
Data Source Type |
Description |
|---|---|
|
Delimited data file |
Data stored in a delimited flat file database that separates records by rows, and fields by fixed length with padding or delimited by whitespace, tabs, commas (CSV) or other characters; for example, a basic name and address list in spreadsheet format. Supports ASCII, extended ASCII or hexadecimal delimiters. Delimited files with multiple global character encodings are not supported. |
|
COBOL copybook |
Data stored in flat, fixed length files that have a companion COBOL copybook (schema) file. Supports multiple character encoding, including EBCDIC, ASCII, and Unicode; Big Endian and Little Endian byte orders, and one or two byte data alignment. |
|
ODBC-compliant relational database source |
Databases supported using an ODBC-compliant RDBMS connection. See Relational Data Sources for a list of supported sources. Data imports do not support analysis of duplicate row ID (checksum) calculation, sparse row counting, or row length statistics. NATIONAL data type is not supported. |
|
Direct connection to Relational Database Management System (RDBMS) |
Direct connections to IBM DB2 and ORACLE relational database systems. See Relational Data Sources for a list of supported sources.
|
|
Trillium file |
Output files created by the Trillium Quality application. Data imports do not support analysis of duplicate row ID (checksum) calculation, sparse row counting, or row length statistics. |
loaddata command syntax for
delimited data sources.