Delete volume VT0164L3

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Leonard, Matthew
Sent: Wednesday, April 16, 2014 8:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Relabel/checkin Tapes marked as "empty"

I have about 100 volumes that are defined in my storage pool as "Empty" (See 
Below).  How would I change the status to scratch?  I've tried running "update 
libvol xdcvtl VT0164L3 status=scratch" however I receive the following error:
ANR8443E UPDATE LIBVOLUME: Volume VT0164L3 in library XDCVTL cannot be assigned
a status of SCRATCH.
ANS8001I Return code 12.


tsm: SXDCTSM01>q vol VT0164L3 f=d

                   Volume Name: VT0164L3
             Storage Pool Name: VTLPOOL
             Device Class Name: VTL
            Estimated Capacity: 0.0 M
       Scaled Capacity Applied:
                      Pct Util: 0.0
                 Volume Status: Empty
                        Access: Read/Write
        Pct. Reclaimable Space: 0.0
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 4
             Write Pass Number: 0
     Approx. Date Last Written:
        Approx. Date Last Read:
           Date Became Pending:
        Number of Write Errors: 0
         Number of Read Errors: 0
               Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator):
         Last Update Date/Time: 04/16/2014 06:13:13
          Begin Reclaim Period:
            End Reclaim Period:
  Drive Encryption Key Manager: None

Regards,

Matthew J. Leonard
Network Infrastructure Administrator
IT Network Operations
AtlasAir, Inc.
Matthew.Leonard AT AtlasAir DOT com
914-701-8042


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
bjoern.nachtwey AT gwdg DOT de
Sent: Wednesday, April 16, 2014 2:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Question about "Storage hierarchy"

Dear all,

switching to an new employer allows me to read all^H^H^H some of IBM's 
documentation about TSM ;-)

inside the server documentation there's a short description on "Example: 
How the server determines where to store files in a hierarchy" [1]. 
within this there's written:

"If the DISKPOOL storage pool has no maximum file size specified, the server 
checks for enough space in the pool to store the physical file. 
If there is not enough space for the physical file, the server uses the next 
storage pool in the storage hierarchy to store the file."

=> does this really mean, that when one client is flooding my staging pools the 
migration processes becme concurrent to new data that is written directly to 
the NEXTSTGPool, because the first pool is full? if the next pool has a limited 
number of mount points (e.g. tape drives) this will cause the next, eben bigger 
problem.

if so, what's the best practise to empty the staging pool?
- setting a max filesize does not solve the problem, especially if there are 
many files
- perhaps "DISABLE SESSIONS CLIENT" -- this seems to be no really good answer 
:-(

Thanks & best regards,
Bjørn

[1]
http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/index.jsp?topic=%2Fcom.ibm.itsm.srv.doc%2Ft_volume_seq_define.html
[1] http://tinyurl.com/p23j5eo

-- 

Bjørn Nachtwey                    <mailto:bjoern.nachtwey AT gwdg DOT de>
Arbeitsgruppe IT-Infrastruktur               Tel. +49 551 201-2181
----------------------------------------------------- G W D G ---- Gesellschaft 
für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 
Göttingen
E-Mail: gwdg AT gwdg DOT de                   Tel.:   +49 (0)551 201-1510
URL:    http://www.gwdg.de             Fax:    +49 (0)551 201-2150
Geschäftsführer:            Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender:  Dipl.-Kfm. Markus Hoppe
Sitz der Gesellschaft:      Göttingen
Registergericht:            Göttingen  Handelsregister-Nr. B 598