DataLoader/MX Reference Manual (G06.24+)

DataLoader/MX Examples
DataLoader/MX Reference Manual—525872-002
6-2
Single Source Parallel Loading
4. At the same time, the second DataLoader/MX process for keyrange 2 reads a
block of records, does any necessary data conversions, and waits for a read from
its $RECEIVE file.
5. The import process for keyrange 2 reads a block of records from its
DataLoader/MX process and then loads the partition with keyrange 2.
Figure 6-1 illustrates this process.
The following commands and their descriptions describe one way to accomplish the
scenario in Figure 6-1.
This command executes a version of the DataLoader/MX process called dbl0
(created with the build.sh script). In dbl0, the default user exit BUILDKEY is
replaced by one that, given an input record, returns its key. This strategy is necessary
because the DataLoader/MX process uses this key to determine which downstream
DataLoader/MX process receives the record. The default BUILDKEY interprets that the
key of the record is the first 255 bytes of the record, which is not the case with this
data:
$ run dbl0 -E=err0 -I=infile "-O=kr(keyrange)" -S=100000 &
The preceding command uses these parameters:
•
-E specifies that execution time errors are recorded in the file named err0.
Figure 6-1. Single Source Parallel Loading
Note. gpri and cpu parameters have been omitted from the example. The initial
DataLoader/MX process should run at high priority, and the downstream DataLoader/MX
process and import pairs should run in the CPU where the primary disk process for the
corresponding partition is running.
import
Keyrange 1
import
Keyrange 2
import
Keyrange N
Data Source
Part 1
Part 2
Part 3
Initial
DataLoader/
MX Process
DataLoader/MX
Keyrange 1
DataLoader/MX
Keyrange 2
DataLoader/MX
Keyrange N
VST010.vsd