I THINK (ducks low and waits for bucket loads of correcting messages)
that you can quite safely simply run the delete volhist command for
all types providing your todate parameter value is older than your
latest dbbackup.  All the necessary information regarding the current
status of each volume is stored in the database, the volume history
file is used as part of the recovery process when you restore an ADSM
database from backup then roll forward.

The following paragraphs were extracted from the ADSM (MVS) Admin
Guide under the "Delete Volhistory" command section:

2.  Do not delete sequential volume history information until you are
sure
        that you no longer need it.  For example, do not delete dump
volume
        information or storage volume reuse information unless you
have backed
        up or dumped the database at a later time than that specified
for the
        delete operation.

    3.  Do not delete the volume history information for database
dump,
        database backup, or export volumes that reside in automated
libraries
        unless you want to return the volumes to scratch status.  When
the
        DELETE VOLHISTORY command removes volume information for
database
        dump, database backup, or export volumes, the volumes are
        automatically returned to scratch status if they reside in
automated
        libraries.  The result is that these volumes are available for
reuse
        by the server and the information stored on them may be
overwritten
        when the server reuses the volume for some other purpose, such
as
        storage pool volumes or other database backups.


Murray Nicholas
IT Systems Consultant
Galeforce Information Services Pty Ltd
email:  murray AT galeforce.bu.aust DOT com