Submits the data and closes the window.
Cancels any unsaved changes that you made and closes the window.
Specify the alias of the server on which you want to create the control tables for the Capture or Apply program.
Opens a window to select a valid choice for this field.
Type the name of the schema for which you want to create Capture control tables.
Select to specify that the source tables for your replication scenario are located in a supported non-DB2 database. When you select this option, a small set of Capture control tables are created on the non-DB2 database only, while nicknames for them are created on the DB2 federated server.
Select the non-DB2 server on which the source tables for your replication scenario reside.
Select to create the control tables for both the
Capture program and the Apply program on the server.
The server will be able to contain source tables for
replication, as well as the information about the
subscription sets.
If you are creating Capture control tables on a non-DB2 server, you cannot select this option.
The Apply control tables cannot reside on a non-DB2 server.
Displays the names of the control tables. You can select each control table to specify particular properties for it.
Specifies that an existing table space be used for the selected control table. You can then type or select the table space name.
Type or select the name of the existing table space that you want to use.
Opens the List Table Spaces window so you can search for a particular table space.
Specifies that you want to use a table space you have already defined but not yet created for another table in this instance.
Select the table space that you want to use.
Specifies that you want a new table space to be created for the selected control table.
Type the name of the new table space.
Lists the specifications for the containers to use for the new table space. In the Container field, choose whether a container will be a file or a device. In the Container name field, type the path and file name to use for a file container, or the device to use for a device container. In the Size field, type the size of the file to use for the file container.
Adds a container to the table.
Removes the selected container from the table.
Select a page size in kilobytes for the table space.
Type an extent size in 4 KB page size increments. This is the amount of storage that will be used if you have exceeded the primary storage allocations. Primary and secondary allocation sizes are the main factors that affect the amount of DASD space that DB2 uses.
Select a prefetch size in 4 KB page size increments for the table space. A prefetch operation brings pages into the virtual buffer pool before they are required and reads several pages with a single I/O operation.
Select the name of a buffer pool to associate with the table space.
Type a schema name to use for the control table index.
Opens a window so that you can search for a particular schema to use.
Type a name to use for the control table index.
Specifies to use a table space that has already been created for the selected control table.
Specifies to use a table space defined within the current session for the selected control table.
Select the table space to use.
Specify a table space name from the list that has been defined within the current session.
Specifies to create a new table space for this control table.
Specify the database name that will contain this table space.
Opens a window listing available database names.
Specify the new table space name.
Specifies to create the table space as a non-partitioned or simple table space. This is a table space that can contain more than one table but the rows of different tables are not kept separate. All tables in a simple table space must be either user defined or in the same storage group.
Specifies to create the table space as a segmented table space. This is a table space that can hold more than one table. The available space is divided into groups of pages called segments, each the same size. Each segment contains rows from only one table. A segmented table space can have between 1 and 32 VSAM linear data sets, all of which are either user defined or in the same storage group. The maximum size of a data set in the segmented table space is 2 gigabytes. And so, the maximum size of a segmented table space is 64 gigabytes (2 gigabytes multiplied by 32 data sets).
Specify the number of pages per segment.
Specify the lock size for the table space. The recommended lock size is page, which means that an entire page can be locked at one time. In DB2 for z/OS, when the number of locks acquired for the table space is greater than the maximum number of locks allowed for a table space (an installation parameter), the page locks are released and locking is set at the next higher level.
Specify the encoding scheme for tables stored in the table space.
Specify the buffer pool to associate with this table space. The buffer pool must have already been activated.
Specify an eight character identifier for a storage group name. When you create table spaces and indexes, you name the storage group from which you want space to be allocated. Try to assign frequently accessed objects (indexes, for example) to fast devices, and assign seldom-used tables to slower devices.
Opens a window listing the available storage group names from which to select.
Specify the minimum primary space allocation. In general, the primary allocation must be large enough to handle the storage needs that you anticipate. DB2 always allocates a primary allocation space on a volume that has space available and is specified in the DB2 storage group. Specifying sufficient primary allocation for frequently used data sets minimizes I/O time, because then the data is not physically located at different places on the disks.
Specify a unit of measurement for the allocation size.
Specify the minimum secondary space allocation. The secondary allocation must be large enough for your applications to continue operating until the data set is reorganized. If the secondary allocation space is too small, the data set might have to be extended more times to satisfy those activities that need a large space.
Specify a unit of measurement for the allocation size.
Type a valid schema name for the index.
Opens the List User IDs window so that you can search for a specific schema.
Type a valid name for the index.
Specify an active buffer pool to use for this index.
Type the name of the storage group to use for this index.
Opens the List Storage Groups window so that you can search for a specific storage group.
Specify the minimum primary space allocation for the index. In general, the primary allocation must be large enough to handle the storage needs that you anticipate. DB2 always allocates a primary allocation space on a volume that has space available and is specified in the DB2 storage group. Specifying sufficient primary allocation for frequently used data sets minimizes I/O time, because then the data is not physically located at different places on the disks.
Specify a unit of measurement for the allocation size.
Specify the minimum secondary space allocation. The secondary allocation must be large enough for your applications to continue operating until the data set is reorganized. If the secondary allocation space is too small, the data set might have to be extended more times to satisfy those activities that need a large space.
Specify a unit of measurement for the allocation size.
Specify a schema name. This is from the three part naming convention.
Specify a name that identifies the wrapper.
Specify a schema name for the index.
Specify an index name.
Opens a window to select a valid choice for this field.
Opens a window to select a valid choice for this field.
Opens a window to select a valid choice for this field.
Opens a window to select a valid choice for this field.