Re: How to determine the amount of available space on tape?

[rob@xxxxxxxxx]

Here's a sample:
Volume ---Temporary Errors--- --------M Bytes--------
ID           Read       Write       Read      Written
HDTGL1          0           0          1      1103725
HDTGL2          0           0          1       524278
HDTGL3          0           0          1       287209
From, basically, a full system save.

SAVSYS
The save operation ended on volume HDTGL1.

SAVLIB *NONSYS
The save operation ended on volume HDTGL1.

SAVDLO
CPI6705-3036 blocks were processed for file label QDOC, sequence 879 for 
volume HDTGL1 loaded on device TAPMLB02. The maximum block size is 262144. 
The tape file was opened at 02/10/07 07:36:31 and closed at 02/10/07 
07:36:55. The total time the file was open was 24 seconds.
The save request ended on volume HDTGL1

SAV (ifs stuff)  (a vast majority of our data is here.  We have more free 
space than what is used by *NONSYS.)
started  02/10/07  07:36:58.918520
02/10/07  08:48 - CPI6705-1621973 blocks were processed for file label 
SAV20070210, sequence 880 for volume HDTGL1 loaded on device TAPMLB02. The 
maximum block size is 262144. The tape file was opened at 02/10/07 
07:37:07 and closed at 02/10/07 08:48:18. The total time the file was open 
was 4271 seconds.
02/10/07  08:51 - The next volume that is inserted on device TAPMLB02 has 
volume identifier HDTGL2.
02/10/07  10:29 - CPI6705-2080471 blocks were processed for file label 
SAV20070210, sequence 880 for volume HDTGL2 loaded on device TAPMLB02. The 
maximum block size is 262144. The tape file was opened at 02/10/07 
08:51:21 and closed at 02/10/07 10:28:55. The total time the file was open 
was 5854 seconds.
02/10/07  10:31 - The next volume that is inserted on device TAPMLB02 has 
volume identifier HDTGL3.
02/10/07  11:17 - CPI6705-1139719 blocks were processed for file label 
SAV20070210, sequence 880 for volume HDTGL3 loaded on device TAPMLB02. The 
maximum block size is 262144. The tape file was opened at 02/10/07 
10:31:58 and closed at 02/10/07 11:17:47. The total time the file was open 
was 2749 seconds.
02/10/07  11:17 - 130528 objects were saved on volumes HDTGL1 HDTGL2 
HDTGL3 sequence number 880 at 02/10/07 07:37:01.  The save operation ended 
on volume HDTGL3.

Ok, so it didn't fill the 3rd tape.  However I refuse to believe that the 
difference between the first two is the manufacturing anomaly.  Doing all 
of the ifs save to one file number (880) may be a factor.  Maybe our IFS 
data is more compressed than DB2 data?
Funny thing is that it only took the IFS save 1 hour and 40 minutes to 
fill the second tape.  And the IFS used the first tape for 1 hour and 15 
minutes.  So, does that mean that (75 minutes)/(100 minutes) of tape 1 is 
also IFS data?

Would adding up all of the CPI6705 messages mean anything?  Note:  There 
are a LOT of CPI6705 messages for the *NONSYS.  Really starts to clutter 
up the joblog.


Rob Berendt