DataLoader/MX Reference Manual (G06.24+)

DataLoader/MX Reference Manual—525872-002
5-1
5
Creating a Customized Version of
DataLoader/MX
Although DataLoader/MX default functions might be enough for any loading scenario,
you might want to create a customized version of DataLoader/MX. You can do this by
combining user exits and utility routines. Utility routines are provided for such tasks as
data conversion, communication with the user, error checking, and generating test
data. User exits can perform such tasks as building or retrieving record keys;
converting, deleting or inserting records; and any other tasks you need to code. Finally,
use the build.sh script to generate the customized version of the DataLoader/MX
process.
This section describes:
•
User Exits on page 5-1
•
User Exit Descriptions on page 5-3
•
Default User Exits on page 5-12
•
DataLoader/MX Library on page 5-14
•
Building a Customized Version of DataLoader/MX on page 5-40
See Appendix B, Processing Flowcharts, for another look at the conditions that cause
a user exit to be called.
User Exits
DataLoader/MX can call user-supplied procedures at many points during its
processing. Each of these procedures are passed arguments appropriate to their
function. Some procedures might return a value indicating the outcome of their
processing. DataLoader/MX is delivered with a set of bound-in default user exits.
This subsection explains how to use user-supplied procedures to control custom
processing in DataLoader/MX.
While user exits are called under different conditions, these exits are always called by
DataLoader/MX:
•
EXITSDESCRIPTION
•
INITIALIZE1
•
INITIALIZE2
•
TERMINATING
•
TERMINATING2
Table 5-1 lists exits called only if you specify a parameter that requires them to be
called.