z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Understanding object databases

z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
SC23-6866-00

NOT programming interface information

This segment documents information that is provided to help you diagnose OAM problems.

OAM allows multiple DB2 databases to be used for object storage. Each object storage database has an object directory table space, a 4 KB Object Storage Table space, and a 32 KB Object Storage Table space. Within each table space is one table (an object directory table, a 4 KB Object Storage Table, and a 32 KB Object Storage Table, respectively). Each database has three indexes into the object directory table and one index into each of the object storage tables. The high-level qualifier on the object storage database must match the high-level qualifier on the object storage definition in the SCDS that was created using ISMF and the high-level qualifier and package name in PBIND.

LOB support adds the LOB storage database structure to the 4 KB and 32 KB object storage table hierarchy. This structure consists of a LOB base table and a LOB auxiliary table. The LOB base table resembles a 32 KB table with the addition of a ROWID column and changing the OTOBJ column datatype from 'long varchar' to BLOB. The LOB auxiliary table contains the actual BLOB object represented by the OTOBJ column in the LOB base table. The LOB auxiliary table is managed exclusively by DB2 and is transparent to OAM.
Note: Reference to the LOB storage structure refers to both the LOB base table and the LOB auxiliary table.

Object storage administration uses one additional database. The object storage administration database name is OAMADMIN. This database contains a management class table space, a storage class table space, and a collection name table space. Within each table space is one table (a management class table, a storage class table, and a collection name table, respectively). The management class table and the storage class table each have one index, and the collection name table has three indexes.

Each OAM DB2 object storage database has its own separately defined set of VSAM data sets. There is one VSAM data set for each table space, and one VSAM data set for each index within the database.

Attention: The information from the OAMADMIN tables is crucial to the operation of OSMC. IBM strongly advises against altering these tables.
End of NOT programming interface information

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014