Use the Tablespace editor to specify parameters for a DB2 z/OS tablespace.
To define a DB2 z/OS tablespace
The DB2 for z/OS Tablespace Editor opens.
Note: Click New on the toolbar to create a tablespace. Use the Enter filter text text box to filter a large list of tablespaces to locate the one you want to work with.
Specifies the name of the tablespace.
Specifies the tablespace storage type. Valid Values are: Large or LOB. Your choice affects the display of the parameters below.
Specifies the database in which to store the tablespace.
Specifies whether or not to generate DDL for this object during Forward Engineering.
Specifies that the data sets are created when the tablespace is created. Clear the check box to indicate DEFINE NO.
Indicates that changes to a LOB column in the tablespace are written to the log. Clear the check box to not write changes to the log.
Indicates the value, in gigabytes, for the maximum size for data sets. Select a data set size from the drop-down list.
Indicates the bufferpool to be used for the tablespace. Select a bufferpool name from the drop-down list.
Indicates that, when the limit on the number of open data sets is reached, the tablespace is eligible for closing before CLOSE NO data sets. Clear the check box to indicate CLOSE NO.
Specifies the maximum number of page, row, or LOB locks an application process can hold simultaneously in the tablespace.
Specifies the size of locks used within the tablespace. Select a lock size from the drop-down list. Valid Values are: Any, Table, TableSpace, Page, Row, LOB.
Indicates that modified pages in the space map pages are tracked for the partition. Clear the check box to indicate TRACKMOD NO.
Specifies the encoding scheme for table stored in the tablespace. Select a value from the drop-down list. Valid values are: ASCII, EBCDIC, or UNICODE.
Indicates that data compression applies to the rows of the tablespace or partition. Clear the check box to indicate COMPRESS NO.
Specifies the maximum number of rows (indicated as an integer) to place on each data page.
Specifies how many pages (indicated as an integer) are to be assigned to each segment.
Indicates the maximum number of partitions to which the tablespace can grow. Enter an integer in the text box.
Indicates that data is not clustered. Clear the check box to allow DB2 to locate the data in the tablespace based on available space.
Specifies the number of partitions in the tablespace.
Specifies a name for the partition.
Note: Click New to create a partition element.
Specifies the partition element number. Click the Partition Element Editor icon to define a new partition and its properties.
Specifies that the first data set of the index is managed by the user. Catalog Name identifies the linear VSAM data sets that are cataloged in an integrated catalog facility catalog.
Specifies that DB2 manages the data set.
Specifies the minimum primary space allocated to a DB2-managed data set. If you do not specify any value, DB2 uses a default value.
Specifies the minimum secondary space allocated to a DB2-managed data set. If you do not specify any value, DB2 uses a formula to calculate the value. For more information, refer to IBM DB2 for z/OS documentation.
Specifies whether or not to delete the DB2-managed data sets when the index is dropped while executing a utility or an SQL statement.
Specifies the frequency at which you want to leave a page of free space when you create index entries while executing a DB2 utility or when you create an index for a table with existing rows.
Specifies the percentage of free space you want to leave in each nonleaf page and leaf page when you add entries to an index or index partition while executing a DB2 utility or when you create an index for a table with existing rows.
Specifies the index pages that are written to the group buffer pool and applies to the data sharing environment. Select from the drop-down list; valid values are: Changed, All, None, and System.
The DB2 for z/OS Tablespace Editor closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |