Manage Db2 tablespaces easily without having to remember object names, options, and DDL syntax.
You can alter, create (new or template), or drop any type of DB2 tablespace (segmented, partitioned, and universal) that is supported by the version of DB2 on which you are running or for which DDL is to be generated and subsequently executed. A tablespace is a DB2 object that is used to hold one or more stored tables. As the amount of data in those tables grows, storage is acquired from the appropriate storage group or VSAM data set. The tablespace consists of VSAM ESDS data sets that contain one or more DB2 tables. When the tablespace is created, you designate it is database and storage group.
The following DB2 tablespace types are supported:
  • Universal (UTS) tablespaces (range-partitioned and partition-by-growth)
  • EA-enabled tablespaces and indexspaces
  • Large object tablespaces
  • XML tablespaces
  • Simple tablespaces
  • Segmented (non-UTS tablespaces)
  • Partitioned (non-UTS tablespaces)
Simple tablespaces and non-UTS segmented and partitioned tablespaces have been deprecated by IBM.
From the alter and create panels, you can:
  • Enter selection criteria in many fields to bring up lists of objects to choose from.
  • Create and alter partition-by-growth, partition-by-range, and LOB tablespaces easily.
  • Create an explicit VSAM data set for the tablespace instead of a storage group using the VSAM definition facility.
  • Estimate the space that is required by a tablespace using the space calculation feature. If the tablespace is partitioned, you can also make space calculations on each partition.
  • Browse the LISTC report and view space amounts for user-defined data sets (tablespace alter and template only) using the LC line command.
  • Use primary commands to:
    • Apply user defaults to the tablespace definition using the APPLY DEF command
    • Display the original and current definitions of an object using the COMPARE command
    • Switch the header area on the product panels on and off using the HEADER command
    • Reset all fields to their original values
    • Set all new fields to source or target field values (applies only for compares in
      CA RC/Migrator™ for DB2 for z/OS