do not run into this problem - not even with the new tape
that it wrote to. :0)
-Original Message-
From: Matthew Glanville [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 6:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Volume delete problem...
From: Matthew Glanville
I have ran into th
----
>> From: Richard Sims <[EMAIL PROTECTED]>
>> To: <[EMAIL PROTECTED]>
>> Sent: Friday, August 04, 2000 5:22 PM
>> Subject: Re: Volume delete problem...
>>
>> > > adsm> del vol ofsex1 discardd=yes
>> > > ...
>> > > ANS8001I Return code 13.
>> >
>> > Take a look at that pesky "Access: Unavailable" thingie in the
>> > volume info report.
>> >Richard Sims, BU
> - Original Message -
> From: Richard Sims <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, August 04, 2000 5:22 PM
> Subject: Re: Volume delete problem...
>
> > > adsm> del vol ofsex1 discardd=yes
> > > ...
> > > ANS8001
Sims,
this process doesen4t work with any acess status!
thanks,
Roberto Godoy
Service IT Solutions
- Original Message -
From: Richard Sims <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 04, 2000 5:22 PM
Subject: Re: Volume delete problem...
> > ad
> adsm> del vol ofsex1 discardd=yes
> ...
> ANS8001I Return code 13.
Take a look at that pesky "Access: Unavailable" thingie in the
volume info report.
Richard Sims, BU
Hi *SMers,
I have one tape called OFSEX1 that is defined in the tsm volumes with the
following parameters:
Volume Name: OFSEX1
Storage Pool Name: SAP_DLT_POOL_OFFLINE
Device Class Name: DLTCLASS
Estimated Capacity (MB): 35,840.0
Pct Util: 0.0
Volume Status: Filling
Access: Unavailable
Pct. Recla
