Setting share-level change options
These steps are part of the larger task of
reorganizing a table space or an index. When
you complete the steps for setting the change
options, return to the main task.
With the change option, reorganization operates
by unloading from the area being reorganized
(while applications can read and write to
the area), reloading into a shadow copy of
that area (while applications have read/write
access to the original copy of the area),
applying the log of the original copy to
the shadow copy (while applications can read
and usually write to the original copy),
switching the applications' future access
from the original copy to the shadow copy
by exchanging the names of the data sets,
and then allowing read/write access again.

To set the share-level change options:
- Specify an owner of the mapping table. Either
type the name or click on the
push button to open a window to search for
a List of USER ID's. Not used when reorganizing
an index.
- Specify the mapping table name that the table
space reorganization utility uses to map
between the record identifiers (RIDs) of
data records in the original copy of the
area and the corresponding RIDs in the shadow
copy. This table must already exist and include
an index. Type the table name or click on
the
push button to open a window to search a
List of table names. The table space that
contains the mapping table must be segmented
and cannot be the table space to be reorganized.
Not used when reorganizing an index.
- Specify the None radio button so that no deadline is set
on the reorganization. The reorganization
will run until it terminates with a successful
completion, or until it terminates with informational
or error messages.
- Specify the Point in time radio button to establish a reorganization
deadline by date or time.
- In the Date field, click the
push button to open a calendar and choose
a date. To exit the calendar, click the
again.
- In the Time field, specify a time in the form of HH:MM:SS, where HH is hours, MM is minutes, and SS is seconds. You can also select the up or
down arrows to spin through the available
choices for each time element.
- Specify the Elapsed time radio button to establish an amount of time
before reorganization should stop, regardless
of when you start the reorganization. Reorganization
starts when you click the OK push button on the main Reorganization window,
and stops after the amount of time specified
in the following fields.
- In the Days field, type a number of days that you want
to elapse before the reorganization of a
table space or index should stop.
- In the Hours field, type a number of hours that you want
to elapse before the reorganization of a
table space or index should stop. You can
also select the up or down arrows to spin
through the available choices for hours.
- In the Minutes field, type a number of minutes that you
want to elapse before the reorganization
of a table space or index should stop. You
can also select the up or down arrows to
spin through the available choices for minutes.
- Specify the Time in seconds radio button to determine the maximum amount
of time for the last iteration of log processing.
During that iteration, applications have
read-only access. The default is 300 seconds.
Specifying a small positive value reduces
the length of the period of read-only access,
but it might increase the elapsed time for
the reorganization to complete.
- Specify the Defer final iteration radio button to defer the final iteration
of log processing and the read-only phase
. This option allows the iterations of log
processing to continue indefinitely. If you
specify this option, you should also select
Continue until the JOB time expires radio button below.
- In the Drain parameter used when MAXRO threshold
is reached group of radio buttons, specify the drain
behavior at the end of the log phase after
the MAXRO threshold is reached and when the
last iteration of the log is to be applied.
- The WRITERS radio button specifies the current default
action, in which DB2 drains just writers
during the log phase after the MAXRO threshold
is reached and subsequently issues DRAIN
ALL upon entering the switch phase.
- The ALL radio button specifies that DB2 drain all
readers and writers during the log phase,
after the MAXRO threshold is reached.
- In the Timeout action during object drain group of radio buttons, specify how you
want DB2 to handle timeouts.
- Specify the Leave objects in UTRO or UTUT state (ABEND) radio button to tell DB2 to leave the object
in a read only condition and end reorganization.
- Specify the Leave objects in RW state (TERM) radio button to tell DB2 to terminate the
reorganization process, issue some informational
messages and leave the objects in a read
or write state.
- In the If the LONGLOG message is sent group of radio buttons, you specify the
actions that DB2 performs when applications
are writing changes to the log faster than
the reorganization can process them. You
can select:
- Continue until the JOB time expires. This
is the default. This means that DB2 continues
performing reorganization, including iterations
of log processing, until the time ends on
the job statement.
- Terminate after the delay interval
- Force the final iteration after the delay
interval. This action forces the final iteration
of log processing to occur.
- If you terminate or force the final iteration,
you can specify the delay interval in seconds.
The value must be an integer. The default
is 1200.
- Click OK to define the share level change option.
[Return to reorganization of a table space
in DB2 for OS/390 Version 6]
[Return to reorganization of an index in
DB2 for OS/390 Version 6]