Dataloader/MP Reference Manual

DataLoader/MP Examples
DataLoader/MP Reference Manual—424148-003
6-8
Multiple Source Parallel Loading
The following commands and their descriptions describe one way to implement the
scenario in Figure 6-3.
Command lines 1 through 3 execute a version of the DataLoader/MP process called
“db10” (created with the MAKE routine). In db10, the default user exit BUILDKEY has
been replaced by one that, given an input record, returns its key. This result is
necessary because the DataLoader/MP process uses this key to determine which
downstream DataLoader/MP process receives the record.
1>dbl0 /NOWAIT/ -E=err0a -I=infile1 -O=kr(keyrange) -S=100000
2>dbl0 /NOWAIT/ -E=err0b -I=infile2 -O=kr(keyrange) -S=100000
3>dbl0 /NOWAIT/ -E=err0c -I=infile3 -O=kr(keyrange) -S=100000
The preceding commands use these parameters:
•
-E specifies that any execution time errors are recorded in the appropriate error
listing file.
•
-I directs the DataLoader/MP process to read the input from the appropriate input
file.
•
-O specifies that the output is written to the file kr (which is interpreted as a
keyrange file).
•
-S directs the DataLoader/MP process to generate a status message every
100,000 records.
Figure 6-3. Multiple Source Parallel Loading
Note. PRI and CPU parameters have been omitted from the example. The initial
DataLoader/MP process should run at high priority, and the downstream DataLoader/MP
process and SQLCI pairs should run in the CPU where the primary disk process for the
corresponding partition is running.
VST012
Data
Source N
Data
Source 2
Data
Source 1
Part 1
Part 2
Part N
$dbl2
SQLCI Load
Keyrange2
$dbl3
SQLCI Load
KeyrangeN
$dbl1
SQLCI Load
Keyrange1
DB10 - Initial
DataLoader/MP
1
DB10 - Initial
DataLoader/MP
2
DB10 - Initial
DataLoader/MP
N
$dbl3
DataLoader/MP
Key RangeN
$dbl2
DataLoader/MP
Key Range2
$dbl1
DataLoader/MP
Key Range1