snip of response from Mike Schwab
ML2 is relying on tape drive hardware compress and shows the full size
of the data set.
Thank You Mike for your response. It clarifies what I am seeing.
Sincerely;
Ken Kripke
kkri...@mindspring.com
If it is any consolation: I am using the output from dcollect migratedata for
accounting. I am using the field umallsp. Our 'accounting' is done in 'number
of tapes', so I have the (dis)pleasure of trying to compute the number of tapes
a dataset (single file, single-file-multi-volume,
Problem Statement: We are attempting to estimate the number of compressed ML1
and ML2 data sets that will fit on EAV volumes.
For ML1 data sets, field UMDSIZE from IDCAMS DCOLLECT layout appears to be
reporting with reasonable numbers.
For ML2 the number does not seem close at all.
Test
ML2 is relying on tape drive hardware compress and shows the full size
of the data set.
On Tue, Jul 19, 2011 at 5:50 PM, Kenneth J. Kripke
kkri...@mindspring.com wrote:
deleted
For ML2 the number does not seem close at all.
Test Case.
2 data sets were allocated at 75 tracks each.
One version
4 matches
Mail list logo
