Load output files
Log Master
enables you to create load files that support a wide range of migration requirements.
Load files can be processed by Db2 Load utilities, including the IBM Load Utility or the BMC LOADPLUS for DB2 product. Each load data file has an associated load control file that contains Db2 Load utility control statements to define the load data file, including:
- Identifying the tables into which data is loaded
- Describing fields in the input (columns in the tables)
- Describing the overall format of the load data file
Although a load file that Log Master creates uses the Db2 Load utility format, the content is not the same as a load file created by a Db2 Unload utility. The load data file created by Log Master reflects activity over a period of time, and can contain multiple records that affect the same row in a table space. A load file created by a Db2 Unload utility reflects a given point in time, and contains only one load record for each row in a table space.
You access the Load Output panel shown in the following figure from the Output Options panel. For descriptions of the options on this panel, press F1 to access the online Help.
Command ===>
SSID : DJV
More: +
Load File . . . . . . . . . . . . . (E=Edit)
FILE: &SYSUID..D&DATE..T&TIME..LOAD.DATA
Load Control File . . . . . . . . . (E=Edit)
FILE: &SYSUID..D&DATE..T&TIME..LOAD.CNTL
Record Format . . . . . . . . . . . V (V=VB, S=VBS)
Spanned . . . . . . . . . . . . . . N (N=No, Y=Yes LOB/XML for LOADPLUS)
Format of Load File Output. . . . . L (L=Log Master, U=Unload Plus,
C=CSV, S=Standard Format, E=EDIT CSV)
Separate Dataset per Table . . . . N (Y=Yes, N=No)
Generate Empty Files . . . . . . . N (Y=Yes, N=No)
Expand VARCHAR columns . . . . . . Y (Y=Yes, N=No)
Include INFO Columns with Data. . . N (A=All, U=Urid Only, N=Urid None,
E=Edit, S=User Prev Specified)
Separate Unit of Recovery Info . . N (Y=Yes, N=No)
Update Record Options . . . . . . . S (A=After Image Only,B=Before Image Only,
S=Both Separately, T=Both Together)
Create Include/Exclude Columns . . (E=Edit)
Sort . . . . . . . . . . . . . . . Y (Y=Yes, N=No)
Include Rollback. . . . . . . . . . N (Y=Yes, O=Only, N=No)
Include XML . . . . . . . . . . . . Y (Y=Yes, N=No, T=Template, E=Edit)
Include LOBS. . . . . . . . . . . . N (Y=Yes, N=No, I=Inline, T=Template, E=Edit)
PeriodOverride . . N IgnoreFields . N (Y=Yes, N=No)
Delimit Column Name . . . . . . . . O (O=Only, N=None, A=ALL)
Creation of tables to receive load data
When Log Master creates an output load file, it adds additional columns to give context to each load record. If you intend to use a load file to migrate data, you must take one of the following actions:
- Define additional columns in the receiving table, to match the columns added by Log Master, if, on the Load Output panel, you
- Set the Separate Unit of Recovery Info field to Y
- Set the Include INFO Columns with Data field to U (URID only), or A (All)
Edit the load control file to remove the definition of the additional columns
This action causes any subsequent Load utility to ignore the additional columns as it loads the data.
For more information about the topics in this section, see the following references:
Topic | Reference |
---|---|
Overview of how to use the interface to define an output load file | |
Determining which additional columns you must define when creating tables to receive load data |
Related topic