The database load utility reads user-provided data and stores it in a table. This is called data loading. The figure below provides an overview of data loading.
Figure 5-1 Overview of data loading
An input data file contains user-provided data. The database load utility supports four different formats of files. Basically, one of the following two formats is used:
Jones,36,1958-10-15,Chicago
.
.
928691ba814081408140000000243f8000000008796f6b6f68616d61 |
Additionally, you can use a format in which fixed-size data is specified on each line, or a format that is output by pdrorg, shown as follows:
A control information file contains the pdload control statements.
These control statements specify an input data file, index information, LOB column information, file output destination directory, and other information. If you do not specify a file output destination directory in the control statements, files are output to the directory noted in 5.12(5) Directory to be used when no file output destination directory is specified in the control statements.
You need to define a table before you can perform data loading.
You can create an index at the same time as data loading. Or, you can output only the index information during data loading and use pdrorg to create the index later.
You can execute data loading in units of tables or RDAREAs.
If you use the security audit facility, you can load an audit trail from the audit trail files into an audit trail table.
You use the srcuoc statement in the control information file to specify whether data loading is to be performed on a regular table (table defined by the user) or on an audit trail table. For details about the srcuoc statement, see 5.4.11 srcuoc statement (specification of UOC storage library information).