At 4:20 PM -0600 2/6/03, Julian Armendariz wrote:

You will have to specify which copypool to get the files from.

restore v 000345 copy=name_of_copypool p=y

According to the manual, copypool is optional, and if not specified, "files
are restored from any copy pool in which copies can be located."
But, since the manual is occasionally wrong, I tried specifiying
copypool. It didn't help.

Someone else suggested maybe the access on the original tape needed
to be changed to "destroyed".  I tried that. It didn't help.

At 5:35 PM -0500 2/6/03, Prather, Wanda wrote:

 could be there was a problem reading the 2 bad files
at the time it was trying to create the copy pool copy.

That's what I was thinking.

if you purge the DB entries for the bad files, TSM will
back them up on the next go around, assuming they still exist on the client.

And if they don't still exist on the client, I'll just hope that the
user doesn't change his mind and decide he needs them back.  I'll do
the audit and let it delete the entries.  Thanks for the advice.


--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.