Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Configuring the Database Layout >

About the Siebel Storage Control File Templates

The storage control file is unique to the DB2 UDB for z/OS and OS/390 platform for Siebel eBusiness Applications. The storage control file contains storage information (for example, partitioning indexes, table spaces, and storage groups) that is used as the basis for the storage layout of your Siebel database. Even if you are using a preconfigured storage layout, make sure that the layout is valid for your Siebel schema.

Starting with release 7.7, the Siebel Schema layout consists of one table per table space and one table space per database. This layout reduces logging, removes concurrency issues, and allows for more databases to be used to achieve high database parallelism.

The Siebel application installation process installs three storage control file templates in the DBSRVR_ROOT\DB2390 directory for Windows and the $DBSRVR_ROOT/db2390 directory for UNIX. Select one of the templates that follow based on your partitioning needs and your encoding scheme (if you are using partitioning):

• storage_np.ctl. This template contains database storage layout for Siebel Schema with one table per table space, and one table space per database. No partitioned table spaces are provided in this storage control file.
• storage_p.ctl. This template is the database storage layout for Siebel Schema with partitioning for ASCII encoding. Every nonpartitioned table resides in its own segmented table space. Each table space resides in its own database.
• storage_p_e.ctl. This template is the database storage layout for Siebel Schema with partitioning for EBCDIC encoding. Every nonpartitioned table resides in its own segmented table space. Each table space resides in its own database.

The layouts of the storage control file templates are generic, and they require customization by your DBA to suit the needs of your enterprise, for example, to change the default space allocation for Siebel objects, seed data, and views.

While Siebel-provided templates might be sufficient for your development environment without any changes, your DBA needs to review and modify the database storage layout to best fit the needs of your deployment in a production environment.

The storage control file templates are the starting point for your customization process. Before you select a Siebel storage control file template, you should understand the logic behind how objects are grouped, and you should understand the object naming conventions. Knowledge of these concepts will help you when you perform customizations and will help you understand how your operations affect the underlying data sets.