DataLoader/MX Reference Manual (G06.24+)

DataLoader/MX Examples
DataLoader/MX Reference Manual525872-002
6-5
Single Source Parallel Maintenance
The following commands and their descriptions describe one way to accomplish the
scenario in Figure 6-2.
This command executes the initial DataLoader/MX process. It is an unmodified version
of DataLoader/MX that uses the default user exits.
1$ run -name=/G/dbl0 dataload -E=err0 -I=infile -O=\$RECEIVE -S=100000 &
The preceding command uses these parameters:
-E directs the process to write execution time errors to file err0.
-I directs the process to read its input from infile.
-O indicates the process should write the output (blocks of the unmodified input
records) to $RECEIVE. The DataLoader/MX process put them in a buffer pool and
waits for a read from another process.
-S asks for a status display every 100,000 records.
Command lines 2 through 5 start the downstream DataLoader/MX processes, which
are customized versions with user exits CONVERTIT (to do the conversion), INSERTIT
(to attempt to insert the converted record), and UPDATEIT (to attempt to update the
row corresponding to the converted record). Each of these command lines give the
downstream DataLoader/MX processes their own file (err1, err2, ...) in which to record
execution time errors through the -E parameter.
These commands use these parameters:
Figure 6-2. Single Source Parallel Maintenance
Note. gpri and cpu parameters are omitted from the example. The initial DataLoader/MX
process should run at high priority, and the downstream DataLoader/MX processes should be
distributed across processors.
Data Source
Part 1
Part 2
Part 3
$dbl0
Initial
DataLoader/MX
DBL1
DataLoader/MX
1
DBL1
DataLoader/MX
2
DBL1
DataLoader/MX
N
VST011.vsd