Another strange thing is that when I use the volumelabel instead of the
wildcard it works normally.


On Thu, Oct 18, 2012 at 10:27 AM, Stefan Folkerts <stefan.folkerts AT gmail DOT 
com
> wrote:

> I can't wrap my head around what is happing here, maybe you guy's can help
> me little. :-)
>
> I want to move two volumes from courier to vault, this is what happens.
>
> ===================================================
>
> tsm: TSMSRV>q drmedia source=dbs
>
> Volume Name          State                 Last Update
> Automated
>                                            Date/Time               LibName
> ----------------     -----------------     -------------------
> ----------------
> *000002L3*             Courier               10/15/12   10:42:34
> *000003L3 *            Courier               10/15/12   10:42:34
> 000536L3             Mountable             10/18/12   05:06:07     LTOLIB
> 000535L3             Courier               10/15/12   10:45:10
>
> tsm: TSMSRV>
>
>
> MOVE DRMEDIA * wherestate=courier tostate=vault source=dbs
>
> ANR6696I MOVE DRMEDIA: *CHECKOUT LIBVOLUME* for volume *000002L3* in
> library LTOLIB starting.
> ANR6696I MOVE DRMEDIA: *CHECKOUT LIBVOLUME* for volume *000003L3* in
> library LTOLIB starting.
> ===================================================
>
> Why does he want to do a checkout library volume, the volumes are listed
> as offsite;
>
> ===================================================
>
>                   Volume Name: 000002L3
>              Storage Pool Name: COPYPOOL
>              Device Class Name: LTOCLASS
>             Estimated Capacity: 0.0 M
>        Scaled Capacity Applied:
>                       Pct Util: 0.0
>                  Volume Status: Empty
>                         Access: *Offsite*
>         Pct. Reclaimable Space: 0.0
>                Scratch Volume?: Yes
>                In Error State?: No
>       Number of Writable Sides: 1
>        Number of Times Mounted: 34
>              Write Pass Number: 1
>      Approx. Date Last Written: 10/15/12   05:04:11
>         Approx. Date Last Read: 08/28/12   07:05:52
>            Date Became Pending:
>         Number of Write Errors: 0
>          Number of Read Errors: 0
>                Volume Location: COURIER
> Volume is MVS Lanfree Capable : No
> Last Update by (administrator): admin
>          Last Update Date/Time: 10/15/12   10:42:34
>           Begin Reclaim Period:
>             End Reclaim Period:
>   Drive Encryption Key Manager: None
>        Logical Block Protected: No
>
>
>
>                  Volume Name: 000003L3
>              Storage Pool Name: COPYPOOL
>              Device Class Name: LTOCLASS
>             Estimated Capacity: 0.0 M
>        Scaled Capacity Applied:
>                       Pct Util: 0.0
>                  Volume Status: Empty
>                         Access: *Offsite*
>         Pct. Reclaimable Space: 0.0
>                Scratch Volume?: Yes
>                In Error State?: No
>       Number of Writable Sides: 1
>        Number of Times Mounted: 1
>              Write Pass Number: 1
>      Approx. Date Last Written: 08/28/12   08:14:12
>         Approx. Date Last Read: 08/28/12   07:06:38
>            Date Became Pending:
>         Number of Write Errors: 0
>          Number of Read Errors: 0
>                Volume Location: COURIER
> Volume is MVS Lanfree Capable : No
> Last Update by (administrator): admin
>          Last Update Date/Time: 10/15/12   10:42:34
>           Begin Reclaim Period:
>             End Reclaim Period:
>   Drive Encryption Key Manager: None
>        Logical Block Protected: No
> ===================================================
>
> So what happens is that the move drmedia proces fails with this error;
>
> ===================================================
> ANR0985I Process 11 for MOVE DRMEDIA running in the BACKGROUND completed
> with completion state FAILURE at 10:07:35 AM.
> ANR1893E Process 11 for MOVE DRMEDIA completed with a completion state of
> FAILURE.
> ===================================================
>
> q libv / show slots, nothing shows these volumes as being in the library.
> Running TSM 6.3.2.0 and before today 6.3.1.0 on Linux, same "issue" on
> that level.
> I might very well be missing something but I am not seeing it at the
> moment, any help is welcome. :-)
>
> Regards,
>   Stefan
>
>