Implementing Siebel Business Applications on DB2 for z/OS > Customizing a Development Environment >

About Creating Custom Extensions to the Siebel Schema

There are several different possible scenarios for creating Siebel Schema custom extensions:

• Creating a small extension column, so the table fits into its existing table space
• Creating a large extension column, so the table has to be redefined to a larger page size and therefore a larger table space
• Creating an extension table

If planning custom extensions to the Siebel Schema on the z/OS platform, consider the following:

• If a LONG column is defined for a table, attempting to add an extension column to the table causes an error. This is because a LONG column uses all the space in a table space that is not used by the non-LONG columns, leaving no space available for an extension column. In this case, use an extension table instead. For further information, see About Siebel LONG Columns on DB2 for z/OS.
• You can create a new extension column of type CLOB for a table by typing the value CLOB in the Physical Type field of the column in Siebel Tools, although this option is not available in the drop-down list.
• Creating tables with Identity type columns or extension columns of Identity type is not supported.
• The process of creating a small extension column is the same on z/OS as on other platforms and is documented in Using Siebel Tools. To create a large extension column or an extension table on the z/OS platform, you must specify a 16-KB or 32-KB table space:
  • If you are developing on DB2 for Windows or UNIX, you must enter a 16-KB or 32-KB table space in the Apply Schema screen (see Step 4.)
  • If you are developing on DB2 for z/OS, you must edit the storage control file to specify the database and table space in which the new extension column or table is to reside.

For further information on creating custom extensions to the Siebel Schema, see Roadmap for Creating Custom Extensions to the Siebel Schema. For information on estimating storage needs, see Preparing for Implementation on the DB2 Host.