Shows the files in the current directory. Click a file in the list to add it to the File or Path entry field.
Specifies a directory or path. You can either type the path, or you can use the directory list box and drive combination box (OS/2 and Windows 32-bit operating systems only) to build the path. If you type a UNC name, such as \\localhost\e$\test the path browser ignores the drive and directory selection.
Shows the directories in the current directory.
Lists the valid drives on the system. Specify a drive by typing it, or by selecting a drive letter from the list. The amount of free space in MB on the current drive is displayed beside the drive letter. All the drives on the system on which the database resides are listed, including drives on local and remote systems. If the Control Center could not connect to the remote system, the drive list will be empty. In this case, enter the drive letter manually by typing it.
Note that selecting \\ from the drives list clears the file and directory fields, and allows you to type the rest of the name in the path entry field.
Shows the containers that are currently being used to store the table space. For SMS containers, the list shows the path of the container. For DMS containers, the list shows the full path, the type, and the size of the container.
Use the buttons to add more containers, change an existing container, or remove a container.
Shows the extent and prefetch for the user table space.
Use the Change push button to change the extent and prefetch for the table space.
Shows the performance parameters for the drives where any containers will be stored. The overhead and transfer rates are used by DB2 to optimize database performance.
Use the Change push button to change the overhead and transfer rates for the selected drive.
Type a description of your command script in this field (for example, Backup of payroll database). The description cannot be longer than 99 characters.
Contains the number of pages that are read from the table space when data prefetching is being performed. Initially, it displays the default value of the dft_prefetch_sz configuration parameter.
To change the prefetch size, use one of these methods:
Contains the time, in milliseconds, to use as the I/O controller overhead, and the disk seek and latency time during query optimization.
If this time is not the same for all containers in the table space, the value used should be an average of the overhead time for all containers.
To change the overhead time, use one of these methods:
Overhead is calculated using the following formula:
OVERHEAD = average seek time in milliseconds + (0.5 * rotational latency)
where:
where you:
Contains the time, in milliseconds, required to read one 4 KB page into memory. It is used to determine the cost of I/O during query optimization.
If this time is not the same for all containers in the table space, the value used should be an average of the transfer time for all containers.
To change the time, use one of these methods:
Transfer is calculated using the following formula:
transfer = ( 1 / transfer rate in MB per second ) * 1000 / 102400
0 * 4096
Specifies the name of the buffer pool the table space will use to cache table data. If you do not specify a name, the table space will use the default buffer pool.
To select a buffer pool, click the arrow keys to scroll through a list of existing names and select one.
Answer these questions to get recommended average seek time, rotation speed, and transfer rate in the Recommended specifications group. The recommended specifications are used to calculate settings for overhead and transfer.
Specify the size of the physical drive, not a logical partition of the drive.
The recommended specifications are based on the fact that hard drives of similar sizes have similar specifications.
Select 1995 or newer if the drive was new in or after 1995. If you are not sure, guess based on the age of the computer.
Selecting 1995 or newer recommends faster specifications.
The recommendation is based on the fact that newer drives of a given size tend to have faster specifications.
Contain the recommended average seek time, rotation speed, and transfer rate based on the answers you specify in the Questions for recommended specifications. However, if you can get the exact specifications from the drive manufacturer, you can modify the fields directly.
The overhead and transfer values in these fields are calculated from the values in the Average seek time, Rotation speed, and Transfer rate fields in the Recommended specifications which in turn are recommended based on the answers you specify in the Questions for recommended specifications.
However, you calculated the settings manually, you can modify the fields directly.
overhead = avg seek time + ( ( ( 1 / rotation speed ) * 60 * 1000 ) / 2 )
transfer = ( 1 / transfer rate ) * 1000 / 1024000 * 4096
Answer these questions to get recommended extent and prefetch sizes in the Recommended settings group (in the wizard).
You can calculate the size of a table by multiplying the byte count of a single row by the number of rows in the table. A rough estimate is all you need.
The extent recommendation is based on the fact that smaller tables are more efficiently stored in smaller extent blocks.
Type a number in this field or use the arrows to spin to the number you want.
The number in this field multiplied by the extent size is the recommended prefetch size.
The prefetch recommendation is based on the fact that if you have containers on separate physical drives, the database can prefetch from all of those drives at the same time.
Contain recommended settings based on the answers you specify in the Questions for recommended settings. You can also modify the Extent size and Prefetch size fields directly.
Type the name of the directory from which the script will run. Specify the full path. If you do not specify a full path, the default value is the operating system-dependent directory. Note: You cannot use a network mapped drive in this field. This will generate an error message and the action cannot be completed.
The name of the DB2 instance that you want to associate with the command script. Select an instance name from the group box.
Type a valid user ID in this field.
Type a valid password in this field.
Select this push button to view a summary of pending jobs: that is, the next instance of recurring jobs that are scheduled to run in the future. You can select a specific job from this view, and then use the associated pop-up menu to open other views that are filtered for it.
Select this push button to view all jobs that are currently running. You can select a specific job from this view, and then use the associated pop-up menu to open other views that are filtered for it.
Select this button to view all jobs that have completed. You can select a specific job from this view, and then use the associated pop-up menu to open other views that are filtered for it.
Specifies the system on which to store and run command scripts. The default value is Local.
Click this push button to change the name of the container you selected in the Containers list. The Change Container window opens.
This push button is available only when a container is selected in the Containers list.
Specifies the location of the instance to which you want to attach.
Shows the database partitions that you have not selected.