Required options and control statements depend on the type of unload operation executed by the user.
The options listed in (1) and the control statements are mandatory. The items in (2) through (4) are related to the options and control statements presented in the Reference column. For details about the options, see Section 8.9.2.
Item | Reference | |||
---|---|---|---|---|
Option | Control statement | |||
Type of pdrorg processing | -k unld | (1) | ![]() | ![]() |
Reorganization of a user-defined table (can be omitted because the default is -c user) | -c user | (2) | ![]() | ![]() |
Name of the table to be unloaded | -t | (3) | ![]() | ![]() |
File containing the control statements | control-information-filename | (19) | ![]() | ![]() |
Information about an unload data file | ![]() | ![]() | unload statement | 8.9.4 |
: Not applicable
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
There are LOB columns | -j | (9) | lobunld statement | 8.9.9 |
There are columns of abstract data type provided by a plug-in (LOB attribute) | -j | (9) | unld_func statement | 8.9.13 |
There are repetition columns | -W | (7) | array statement | 8.9.12 |
Consecutive trailing spaces are to be removed from a table with suppress option specified* | -S | (14) | ![]() | ![]() |
Inner replica facility is used | -q | (18) | ![]() | ![]() |
: Not applicable
* This option helps you reduce the processing time and the size of the unload data file.
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
Using unload data as pdload's input data file or with a UAP | -W | (7) | fixtext_option statement | 8.9.19 |
Integrating data into a single file | -g | (8) | ![]() | ![]() |
Using EasyMT | -f | (12) | mtguide statement | 8.9.3 |
emtdef statement | 8.9.3 | |||
Using HiRDB files | -f | (12) | ![]() | ![]() |
Specifying the unload data storage sequence (in order of cluster key, index, or data storage) | -b | (13) | ![]() | ![]() |
: Not applicable
Item | Reference location | |||
---|---|---|---|---|
Option | Control statement | |||
Unloading only some of the RDAREAs for a row-partitioned table | -r | (4) | ![]() | ![]() |
Changing the pdrorg executor's user authorization identifier to a value other than the value of environment variable PDUSER1 | -u | (10) | ![]() | ![]() |
Unloading in batch input/output mode using local buffer instead of global buffer2 | -n | (11) | ![]() | ![]() |
Changing an unloading status message output interval to a value other than 100,000 lines | -m | (16) | ![]() | ![]() |
Monitoring the response time for server-to-server communication | -X | (17) | ![]() | ![]() |
Monitoring the execution time of pdrorg | ![]() | ![]() | option statement | 8.9.16 |
Using the same space character in the entire table data | ![]() | ![]() | option statement | 8.9.16 |
Obtaining tuning information during the execution of pdrorg | ![]() | ![]() | report statement | 8.9.17 |
Unloading a column of abstract data type with BLOB attribute as VARCHAR type | ![]() | ![]() | blobtovarchar statement | 8.9.18 |
Executing one of the following:
| ![]() | ![]() | unlduoc statement | 8.9.10 |
: Not applicable
1 If omitted, the system assumes the value of the PDUSER environment variable. If the PDUSER environment variable has not been specified, the system assumes the user name in the login window.
2 By specifying the number of batch input/output pages, you can reduce the number of I/O operations, because data is input/output in units of specified pages in batch mode.