Calculating DASD storage for an object storage database

The following example calculates the DASD storage needed for one object storage database. These calculations would be repeated for each object storage database within OAM. The specific values for the example calculations are based on the following conditions:

• During each workday 10,000 objects, each 3000 bytes long, are stored in database GROUP00. A second case is also shown in the example calculation for objects averaging 1500 bytes long.
• During each workday 10,000 objects, each 64,000 bytes long, are stored in database GROUP00. A second case is also shown in the example calculation for objects averaging 9000 bytes long.
• The 3000-byte objects that have been in the database for 30 calendar days are deleted from the database.
• The 64,000-byte objects that have been in the database for seven calendar days are moved from the database to optical storage, where they will remain for five years (1825 calendar days) before being deleted.
• New objects are stored in the database before any existing objects are deleted or moved.
• To allow for new objects exceeding the predicted maximum number, an extra 10% space contingency is added.
• The database for object storage resides on a 3390-type, DASD device.