Shannon,
The trimming of the physical volume history file should have no bearing on
the return of tapes back to scratch. TSM maintains volume history
information in the database; the physical file is merely a backup copy
that can be used for restoring the TSM server database, and for your own
reference.
The volume history (in the database) is "trimmed" via the DELETE
VOLHISTORY command. Regular storage pool tapes should be returned to
scratch after they go empty and the reusedelay has transpired, regardless
of whether you've run DELETE VOLHISTORY. Database backup volumes and
export volumes are returned to scratch when records for those volumes are
deleted.via DELETE VOLHISTORY.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Shannon Bach <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/17/2003 05:33
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: APAR IC36566 for MVS Server 5.1.7???
Thanks, I'll check into the physical size/allocation of the file but I do
have an automatic script that trims the volhist file weekly. I have to do
this in order to get scratch tapes back into the fold. CA-1 will not
recognize TSM tapes as scratch until they are deleted from the volhist
file.
Shannon
