Thank you for the details/info.

However, I don't see this situation. When TSM releases a tape, CA-1 kicks
in and the tape is put into scratch status and then scratched, nightly.

As you using the appropriate EXIT to manage the tapes ?





Shannon Bach <SBach AT MGE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/20/2003 02:06 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Cleaning up "lost" tapes....



I run a schedule with the following command for our MVS OS/390 TSM Server
once a day (weekdays) defined to run after my daily (weekday)morning
processes are finished;
DELETE VOLHISTORY TODATE=TODAY TYPE=STGDELETE
This gets rid of any volumes that are no longer being used by TSM.  If you
do not delete the STGDELETE volumes, CA-1 will not ever scratch them to be
reused by TSM or any other application.  They still will not be released
to your scratch pool until after you run your batch tape cleanup job, in
our case we have a program in TMS that does the batch tape cleanup.
I also run a schedule with the command;
DELETE VOLHISTORY TODATE=TODAY-1  TYPE=DBBACKUP once a week after a new
DBBackup sequence(type=full -followed by 6 days of incrementals) is
started and the first(full) is OFFSITE in order to release the old TSM
DBBackups to the scratch pool.
Unless you have something else built-in, I don't see how you have ever
gotten any tapes used by ADSM/TSM/ITSM back to the scratch pool.


Shannon Bach
Madison Gas & Electric Co.
Operations Analyst - Data Center Services
Office 608-252-7260
Fax 608-252-7098
e-mail sbach AT mge DOT com