1. Implementing Siebel Business Applications on DB2 for z/OS
  2. Table Objects in Storage Control Files

Table Objects in Storage Control Files

The following example illustrates what the Table object looks like in the storage control file: 

[Object 8005]
Type       = Table
Name       = S_ORG_EXT
Database   = SIDB1465
Tablespace = H1465000
Clobs    = No

The Table object illustrated in this topic translates into the following DDL output: 

CREATE TABLE SIEBTO.S_ORG_EXT (
ROW_ID VARCHAR(15) NOT NULL, 
CREATED TIMESTAMP DEFAULT  NOT NULL, 
CREATED_BY VARCHAR(15) NOT NULL, 
... 

VAT_REGN_NUM VARCHAR(30), 
DIRECTIONS LONG VARCHAR) IN SIEBTO.H1465000 /

Siebel CRM includes one template for each encoding scheme when partitioning is used and one template for each encoding scheme for nonpartitioning.

Most tables use page-level locking by default, but a few use row-level locking. The following tables use row-level locking:

  • S_ESCL_ACTN_REQ

  • S_ESCL_LOG

  • S_ESCL_REQ

  • S_DOCK_TXN_LOG

  • S_DOCK_TXN_LOGT

  • S_DOCK_TXN_SET

  • S_DOCK_TXN_SETT

The following tables use table-level locking:

  • S_DOCK_INIT_ITEM

  • S_DOCK_INITM_XX

Note: LockSize is not defined on the table level but for the corresponding table space.