Starting the DASD space management cycle for an individual storage group

Use DASD space management to do the following:

Select objects that require processing.
Determine if they have expired by examining the objects’ explicit expiration date or examining the objects’ management class information.
Physically delete data for expired objects on DASD and on rewritable optical disks.
Remove the object directory entry (indicating volume serial number and sector location and other object information) for the expired object.

To start DASD space management:

Enter the following command:
```
F OAM,START,DASDSM,storage-group-name
```
_______________________________________________________

The system issues the following messages:

CBR9300I DASD Space Management starting for storage group storage-group-name.
 
CBR9301I DASD Space Management completed for storage group storage-group-name.

_______________________________________________________

The following message appears if OAM is having some major problems and cannot perform DASD space management on a storage group. This message would be preceded by other CBRxxxxI messages:
```
CBR9043I DASD Space Manager not started for storage-group-name.
```
_______________________________________________________

If any errors occur during the DASD space management cycle, additional messages might be issued identifying the error, and message CBR9043I is not issued.

Note: If OAM detects that an object storage table or an object directory is unable to extend its storage during normal processing of objects using the OSREQ application interface, DASD space management is automatically started for that storage group. If the table that runs out of extents is the object directory, all object stores to that storage group fail until more space is made available to the object directory for the storage group. DASD space management is started automatically in this instance so that subsequent stores to the storage group might have improved chances of storing successfully.

For more information on these messages, see MVS System Messages.