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
Recovery Strategies
DataLoader/MP Reference Manual—424148-003
7-9
Parallel Considerations
In order for a loading job to be restarted using restarting from a known state and the -T
parameter, each DataLoader/MP process must receive the same records and in the
same order as were read in the first run. By using the scenario in which downstream
DataLoader/MP processes read from the upstream DataLoader/MP as fast as they are
able to read, the records that a given downstream DataLoader/MP receives are
controlled by the system’s load, and their order cannot be repeated exactly during a
rerun.
If you are using restarting from an unknown state and are not using -T, the records that
a given downstream DataLoader/MP receives are not important. It is a plus for the
restarting from an unknown state method that a self-balancing parallel configuration
can be used.