|
midrange.com
Yeah... I wasn't sure about that angle. From what i'm seeing on the DSPTAP
output and from the RTVDSKINF/PRTDSKINF report it's very, very close in
size.
"DeLong, Eric"
<EDeLong@Sallybea
uty.com> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
05/04/2006 01:09 Subject
PM RE: Display Tape Volume Information
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
I would think this would be how to determine the "size on tape", but I
doubt
this would reliably determine the actual "size on DASD"... Device
compression will reduce the actual size of the tape object.
Note that saving to SAVF, you will not see a benefit from device
compression, so the object size in a SAVF could be much larger than what
you
see on tape.
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
ChadB@xxxxxxxxxxxxxxxxxxxx
Sent: Thursday, May 04, 2006 9:44 AM
To: Midrange Systems Technical Discussion
Subject: Display Tape Volume Information
When looking at a Display Tape Volume Information screen, can the size of
the saved item be determined by multiplying the block length by the file
length? Below is an example of a DSPTAP showing a save of our IFS
(excluding QSYS.LIB and QDLS). It seems that the block length x file
length should give the exact size of this saved item:
262144 x 133349 = 34,956,640,256
This seems to jibe very closely with my RTVDSKINF stat for User
Directories, but I want to make sure i'm getting the exact size of the
saved item as it is on the tape (I'm using the info to verify that the
saved item can be saved to a save file rather than a tape). I think i'm on
the right track here...
Device . . . . . . : TAP02 Volume ID . . . . : DOM302
Owner ID . . . . . : Density . . . . . : *ULTRIUM1
Type . . . . . . . : *SL Code . . . . . . . : *EBCDIC
Data file label . . . . . . . . . : SAV20060427
File sequence . . . . . . . . . . : 0000000004
Record format . . . . . . . . . . : U
Block attribute . . . . . . . . . :
Record length . . . . . . . . . . : 00000
Block length . . . . . . . . . . . : 262144
File length . . . . . . . . . . . : 0000133349
Buffer offset . . . . . . . . . . :
Control character . . . . . . . . :
More...
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT0004570E
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
