Dataloader/MP Reference Manual

DataLoader/MP Reference Manual—424148-003
6-1
6 DataLoader/MP Examples
This section provides examples to demonstrate DataLoader/MP. These examples
represent the four basic loading scenarios from which nearly all real loading scenarios
are derived, as well as use with FTP.
The examples here cover:
•
Single Source Parallel Loading
•
Single Source Parallel Maintenance
•
Multiple Source Parallel Loading
•
Multiple Source Parallel Maintenance
•
Combined Usage With FTP
Single Source Parallel Loading
This highly parallel load scenario was created by writing only two simple user exits:
one to build the key from a raw record (the BUILDKEY exit in the initial DataLoader/MP
process) and one to convert a raw record to a suitable format (the CONVERTIT exit in
downstream DataLoader/MP processes).
Figure 6-1 shows a single input stream. Suppose you are replacing all of the data in a
partitioned database.
LOAD requirements involve the following:
•
You must start with one initial DataLoader/MP process because there is one data
source.
•
You must have one SQLCI LOAD process for each partition and one
DataLoader/MP process that is the input to each LOAD process.
In this example, you know the key partition boundaries and give them to the initial
DataLoader/MP process in a simple edit file. You would include a user exit in each
downstream DataLoader/MP process. The user exit converts incoming records to the
format expected by SQLCI (SQLUTIL) LOAD and performs any other processing that
might be necessary. You can use any number of routines to do this conversion.
The steps that DataLoader/MP performs are as follows:
1. The initial DataLoader/MP 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/MP process.
2. The DataLoader/MP 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.