DataLoader/MX Reference Manual (G06.24+)

DataLoader/MX Reference Manual—525872-002
6-1
6 DataLoader/MX Examples
This section provides examples to demonstrate DataLoader/MX. These examples
represent the four basic loading scenarios, from which nearly all real loading scenarios
are derived, as well as use with the file transfer protocol (FTP).
Examples cover:
•
Single Source Parallel Loading on page 6-1
•
Single Source Parallel Maintenance on page 6-4
•
Multiple Source Parallel Loading on page 6-6
•
Multiple Source Parallel Maintenance on page 6-9
•
Combined Usage With FTP on page 6-12
Single Source Parallel Loading
This highly parallel load scenario is the result of writing only two simple user exits: one
to build the key from a raw record (the BUILDKEY exit in the initial DataLoader/MX
process) and one to convert a raw record to a suitable format (the CONVERTIT exit in
downstream DataLoader/MX processes).
Figure 6-1 shows a single input stream. Suppose that you are replacing all the data in
a partitioned database.
Load requirements involve:
•
Starting with one initial DataLoader/MX process because there is one data source
•
Using one import process for each partition and one DataLoader/MX process that
is the input to each import process
In this example, you know the key partition boundaries and give them to the initial
DataLoader/MX process in a simple text file. You would include a user exit in each
downstream DataLoader/MX process. The user exit converts incoming records to the
format expected by import and performs any other processing that might be
necessary. You can use any number of routines to do this conversion.
The steps are:
1. The initial DataLoader/MX process for all records reads a block of records from the
input stream, looks at each record’s key, and sends it to the correct downstream
DataLoader/MX process.
2. The DataLoader/MX process for keyrange 1 reads a block of records from its
$RECEIVE file, does any necessary data conversions, and waits for a read from its
$RECEIVE file.
3. The import process for keyrange 1 reads a block of records from its
DataLoader/MX process then loads the partition with keyrange 1.