Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

From the window DB2/390 Storage Attributes: Table, choose Attributes →
DisplayChange. Under Target Tablespace, choose Partitioned; see
Figure 7-8.
Figure 7-8 DB2/390 Storage Attributes: Table
At this point, you can choose whether to use LIMITKEY data for the partitioning.
For this example, we chose not to use it since we are creating a table-controlled
partitioned table. For more information about using LIMITKEY data, see “Using
the LimitKey function” on page 122.
The next decision is to either choose table-controlled partitioning or an index for
the partitioning. Choose table-controlled and then specify a partitioning key, the
number of partitions, and for each partition, the limitkey value. Press Enter to get
to the additional partition fields to fill in the limitkey. For this example, we
arbitrarily chose six partitions and we chose limitkeys to create evenly sized
partitions. Refer to Figure 7-9 on page 118.
Note: Keep in mind that this is just a test DataStore object, and does not
represent real data. The goal of this section is to show the mechanics of
partitioning a DataStore object. Other sections of this book discuss the
considerations for designing a partitioning scheme.
When you are finished, choose Attributes → Save. SAP will use these saved
storage parameters the next time it creates this table, which it will do in the next
step.
Chapter 7. Best practices for DataStore 117