ADSM-L

[ADSM-L] contents of a .bfs empty but q vol says different

2015-05-01 14:47:00
Subject: [ADSM-L] contents of a .bfs empty but q vol says different
From: Jeanne Bruno <JBruno AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 1 May 2015 18:45:23 +0000
Hello.
TSM server v 6.2.3.0

Has anyone seen this?
When I do a Q VOL on a .bfs file, I get this info:

            Estimated Capacity: 2.0 G
       Scaled Capacity Applied:
                      Pct Util: 100.0
                 Volume Status: Full
                        Access: Read/Write
        Pct. Reclaimable Space: 91.4
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 4
             Write Pass Number: 1
     Approx. Date Last Written: 03/27/2015 04:27:20
        Approx. Date Last Read: 03/29/2015 20:34:42
           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: 03/27/2015 04:16:15
          Begin Reclaim Period:
            End Reclaim Period:
  Drive Encryption Key Manager:
       Logical Block Protected: No

But when I do a Q CONTENT on the same .bfs, I get:
ANR2034E QUERY CONTENT: No match found using this criteria.
ANS8001I Return code 11.

(I know my typing is correct as I'm using the 'up arrow' on the console and 
only changing the word 'vol' to 'content')

The ReUse on the storage pool is 2 days.
And the RETO is set to 19 days.
So I'm assuming the contents have actually been deleted, but why does the .bfs 
files show up at all when I do:  Q VOL * STGPOOL=xxxx_prim ?

____________________
Jeannie Bruno
Senior Systems Analyst
jbruno AT cenhud DOT com<mailto:jbruno AT cenhud DOT com>
Central Hudson Gas & Electric
(845) 486-5780