Hi,
A) Check this APAR http://www-01.ibm.com/support/docview.wss?uid=swg1IT15117 
<http://www-01.ibm.com/support/docview.wss?uid=swg1IT15117>
A) http://www-01.ibm.com/support/docview.wss?uid=swg21114873 
<http://www-01.ibm.com/support/docview.wss?uid=swg21114873>

Efim


> 13 янв. 2017 г., в 17:16, Rhodes, Richard L. <rrhodes AT FIRSTENERGYCORP DOT 
> COM> написал(а):
> 
> Hi,
> 
> Last night a DBA tried to do a restore of some files.  He get returned
> 
>  01/12/17   22:01:07 ANS4035W File 'xxxxxxx' currently unavailable on server.
> 
> The client data is on tape.
> The tape drives and library are handled by a separate dedicated library 
> manager instance.
> 
> I see:
>  on tsm server
>     the client restore session
>     the sessions to the library mgr instance (I think)
>  on lib mgr
>     the session which I believe would be for the mount (I think)
> on tsm server
>     ANS4025 errors for all files for the restore
> 
> Nowhere is there any indication of WHY the files are unavailable.
> Nowhere is there any indication of what volume(s) were trying to be used.
> 
> I checked:
>  there were tape drives free in the library
>  all tape volumes are read/write or read-only
>  no tape errors or hdwr errors
> 
> 
> Q)  Any thoughts on why the files would be unavailable?
> Q)  How can you tell specific volumes are needed for a client restore?
> 
> The only thing I can think of is that the volumes are unavailable, but I 
> can't figure out what volumes it wanted to use.
> 
> Rick
> 
> 
> 
> -----------------------------------------
> The information contained in this message is intended only for the personal 
> and confidential use of the recipient(s) named above. If the reader of this 
> message is not the intended recipient or an agent responsible for delivering 
> it to the intended recipient, you are hereby notified that you have received 
> this document in error and that any review, dissemination, distribution, or 
> copying of this message is strictly prohibited. If you have received this 
> communication in error, please notify us immediately, and delete the original 
> message.