8.3.2 Cross-reference by purpose

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 subsection 8.9.2.

Organization of this subsection
(1) Required items
(2) Information to be specified depending on the attribute of the table being unloaded
(3) Information to be specified depending on the type of unload data file or LOB data unload file
(4) Information to be specified depending on the unloading method

(1) Required items

ItemReference
OptionControl 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 statementscontrol-information-filename(19)----
Information about an unload data file----unload statement8.9.4

--: Not applicable

(2) Information to be specified depending on the attribute of the table being unloaded

ItemReference location
OptionControl statement
There are LOB columns-j(9)lobunld statement8.9.9
There are columns of abstract data type provided by a plug-in (LOB attribute)-j(9)unld_func statement8.9.13
There are repetition columns-W(7)array statement8.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.

(3) Information to be specified depending on the type of unload data file or LOB data unload file

ItemReference location
OptionControl statement
Using unload data as pdload's input data file or with a UAP-W(7)fixtext_option statement8.9.18
Integrating data into a single file-g(8)----
Using EasyMT-f(12)mtguide statement8.9.3
emtdef statement8.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

(4) Information to be specified depending on the unloading method

ItemReference location
OptionControl 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 PDUSER#1-u(10)----
Unloading in batch input/output mode using local buffer instead of global buffer#2-n(11)----
Changing an unloading status message output interval to a value other than 100,000 lines-m(16)----
Suppressing output of information messages
Monitoring the response time for server-to-server communication-X(17)----
Monitoring the execution time of pdrorg----option statement8.9.16
Using the same space character in the entire table data----option statement8.9.16
Setting data in the unload data file to UTF-8 or UTF-16 and then unloading----option statement8.9.16
Unloading a column of abstract data type with BLOB attribute as VARCHAR type----blobtovarchar statement8.9.17
Executing one of the following:
  • Deleting unneeded data and then outputting the unload data file
  • Updating data to use as pdload's input data file
  • Outputting data in a desired format for applications
----unlduoc statement8.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.