A Dump Path is used to pre-define a sequence for depositing material into dump records. They function in a similar way to Input Paths, which define a sequence for extracting material from records. Note that dump records must be created before they can be assigned to a Dump Path.

You may store a sequence for each dump in a separate Dump Path. Alternatively, you can use a single Dump Path to define a dumping sequence to multiple dumps. The approach that you adopt will depend on the resources that you are scheduling and the nature of the interrelationships between the dumps (eg. "it is not possible to dump into DumpB/Level9 until all of DumpA/Level8 is full").

Following is an example of a Dump Path.