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


OAM configuration database

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

The OAM configuration database (CBROAM) contains configuration information related to the target destinations for objects including tape volumes, optical libraries, drives, slots, and volumes. CBROAM also identifies objects to be ultimately deleted by OAM from optical volumes and the file system. It is a DB2 database and consists of the following tables:
Library
Contains one row for each optical library. The DB2 name of this table is OLIBRARY. There is a unique index on the library name.
Drive
Contains one row for each optical drive, whether operator-accessible or library-resident. The DB2 name of this table is DRIVE. There are two indexes defined on the table; one is unique and one is not.
Slot
Contains one row for each of the slots in a 9246 optical library. The DB2 name of this table is SLOT. There is a unique index defined on the slot name in combination with the library name.
Note: The 9246 optical library is no longer supported.
Volume
Contains one row for each optical disk volume. The DB2 name of this table is VOLUME. There is a unique index on the volume serial number.
Deleted-Objects
Contains one row for each object waiting to be deleted from 3995 rewritable optical media. The DB2 name of this table is DELOBJT. There are two indexes defined on the table; one is unique and one is not.
Tape Volume
Contains one row for each tape volume used by OAM for object storage. The DB2 name of this table is TAPEVOL. There is a unique index on the volume serial number.
File System Delete
Contains one row for each object waiting to be deleted from the file system. The DB2 name of this table is FSDELETE.

Table 1 provides DASD space recommendations for storage of the CBROAM tables.

Table 1. CBROAM space recommendations
Description DB2 name Primary space 3390 tracks Secondary space 3390 tracks

Library Table
 

OCLIBTSP LNAMINDX

  1
  1

1
1

Drive Table
 
 

OCDRVTSP DNAMINDX DRIDINDX

  5
  1
  1

1
1
1

Slot Table
 

OCSLTTSP SLIBINDX

  1
  1

1
1

Volume Table
 

OCVOLTSP VSERINDX

20
  2

10
1

Deleted-Objects Table
 
 

OCDELTSP DVOLINDX DELOINDX

100
10
100

10
5
10

Tape Volume Table
 

OCTVLTSP TVOLINDX

10
  2

1
1

File System Delete Table
 

OCFSDTSP FSDTINDX

100
10

10
5

These recommendations allow:
  • 216 optical library definitions
  • 1␠320 drive definitions
  • 1␠404 slot definitions for as many as twenty-two 9246 library definitions
  • 5␠040 volume definitions
  • 39␠600 objects waiting for deletion from rewritable optical media
  • 5␠280 tape volumes to be used for storing objects
  • 34␠900 objects waiting for deletion from the file system

If you do not use a particular level or sublevel of the OAM storage hierarchy, then you can use minimal space values for the tables related to that level or sublevel. For example, if the file system sublevel is not implemented in your installation, then use 1 for the primary and secondary space values for the File System Delete Table and the associated index.

If your installation requires more entry space or if you are using DASD storage that allows fewer than twelve pages per track, the above space recommendations might need to be increased.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014