|
View previous topic :: View next topic
|
| Author |
Message |
Jim Stout
New User
Joined: 11 May 2013
Posts: 4
Location: USA
|
|
|
|
Good day everyone!
I'm working on a project to determine the amount of allocated DASD space using a DCOLLECT as input to an assembler program. I'm using DCDALLSP from the D records and am comparing the result obtained by using the DCVALLOC from the V records. I would expect them to be equal but so far, the numbers are very far apart. I'm hoping that someone has some advice for getting accurate space allocation information from a DCOLLECT. Thanks in advance! |
|
| Back to top |
|
 |
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2154
Location: USA
|
|
|
|
Examples of code, and input/output data, please.
Do not forget to enclose all samples into Code tags. |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1348
Location: Bamberg, Germany
|
|
|
|
| Basically when comparing DCVALLOC with all DSNs DCDALLSP on a volume, you should get the size of the VTOC. Consider EAV bits where needed. Also some SORT product might be the better option for processing DCOLLECT output. |
|
| Back to top |
|
|
Jim Stout
New User
Joined: 11 May 2013
Posts: 4
Location: USA
|
|
|
|
| Thanks for the responses! It turns out that the DCOLLECT I was using was "incomplete" which caused the discrepancy between the V record allocation and the D record allocation values. I've sampled a dozen other DCOLLECTs and the difference is minor (< 1%). The goal of this exercise was to see how much data is being compressed vs. data that is not compressed. |
|
| Back to top |
|
|
|
|
