Dataloader/MP Reference Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to DataLoader/MP
- 2 DataLoader/MP Components
- 3 Running DataLoader/MP
- 4 Specifying File-Related Options for DataLoader/MP
- 5 Creating a Customized Version of DataLoader/MP
- User Exits
- User Exit Descriptions
- BUILDKEY
- CHECKARG
- CONVERTIT
- DELETEIT
- DONEWITHTRANSACTION
- EXITSDESCRIPTION
- GETNEXTRECORD
- INITIALIZE1
- INITIALIZE2
- INSERTIT
- INSTRUCTIONS
- MISC1, MISC2, MISC3, and MISC4
- NEWTRANSACTION
- NEXTINDIRECTFILE
- SKIPPING
- STATISTICSTIME
- TERMINATING
- T0330U00_DEFAULTEXITS_C
- T0330U00-DEFAULTEXITS-COBOL
- T7900D41_DEFAULTEXITS_C
- T7900V00-DEFAULTEXITS-COBOL
- UPDATEIT
- Default User Exits
- DataLoader/MP Library
- The MAKE Routine for NM DataLoader/MP
- The MAKE Routine for Nonnative Mode DataLoader/MP
- 6 DataLoader/MP Examples
- 7 Recovery Strategies
- A Error and Warning Messages
- B Processing Flowcharts
- C C-Only Error Functions
- Index

Creating a Customized Version of DataLoader/MP
DataLoader/MP Reference Manual—424148-003
5-3
User Exits
In the case of “Continue with next exit,” if this is the last exit, the record is passed to
the post process step. The post process step includes partition boundary estimation (if
-P is specified), and may include writing the record to the output file (if -O= is
specified).
In the case of “Read next record” (0 return status from any of these exits, or negative
return status from exits 1, 2, 3, 4, or C), processing of the current record is stopped
immediately. Any remaining user exits are skipped and the post process step is
skipped. If any of the user exits that have already run wrote to the -O file (user call to
DTLWrite with -2 as the file number) that data remains in the -O file.
User Code “H” for Heuristic
It is not unusual for tables to start out empty or, at various stages, have rows added to
them or to have their rows updated. DataLoader/MP can accommodate these
scenarios, if you run it with the parameter -X=IU, which will always try an insert first, or
-X=UI, which will always try an update first. However, when the table is mostly empty, it
is most efficient to attempt an insert first, and when the table is mostly full it is most
efficient to attempt an update first.
While it would be possible to run DataLoader/MP with -X=IU during the first part of the
table’s life and -X=UI during the last part, a better solution is available: -X=H. The letter
H stands for heuristic and it is a combination of I and U. It directs DataLoader/MP to
monitor whether an insert or update was successful for the last 100 records. (100 is the
default but can be overridden by specifying the new value following the letter H, as in
-X=H300.) When DataLoader/MP processes the next record, it first attempts the action
(either insert or update) that has been most successful for those records.
3 MISC3 Continue with next
exit.
Dump record to -E
file. Read next record.
Read next record.
4 MISC4 Continue with next
exit.
Dump record to -E
file. Read next record.
Read next record.
C CONVERTIT Continue with next
exit.
Dump record to -E
file. Read next record.
Read next record.
D DELETEIT Go to post-processing. Continue with next
exit.
Read next record.
I INSERTIT Go to post-processing. Continue with next
exit.
Read next record.
U UPDATEIT Go to post-processing. Continue with next
exit.
Read next record.
Hnnn INSERTIT/
UPDATEIT
Go to post-processing. Continue with next
exit.
Read next record.
Table 5-2. Parameter -X Exit Codes (page2of2)