03.03.2015 Views

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Reporting on Disk Files<br />

• If VOL= is given specifying a pool-id, one output detail line is generated<br />

<strong>for</strong> each pool space that is on a real volume on which a file has extents. If<br />

there is more than one pool space defined on one real volume, a detail line<br />

will appear <strong>for</strong> each of them, causing some items to be repeated. The<br />

contribution added into the total space used in the pool, however, is<br />

adjusted to result in correct totals <strong>for</strong> each pool space and <strong>for</strong> the pool as<br />

a whole. Files having no extents that overlap the pool space being<br />

processed, are not reported <strong>for</strong> that pool space.<br />

ALLO<strong>CA</strong>TION INFO<br />

BLOCKSIZE OPT.<br />

EXTENTS: 1ST SQ#<br />

EXTENTS: # on VOL<br />

The computations <strong>for</strong> this group are only attempted <strong>for</strong> files that are complete<br />

on the real volume in question and which have had the original allocation<br />

request in<strong>for</strong>mation recorded in the <strong>for</strong>mat-1 record. (This is true <strong>for</strong> files<br />

created under <strong>CA</strong> <strong>Dynam</strong>/D control.)<br />

This is computed by calculating the largest blocksize that will fit on a track or<br />

control interval <strong>for</strong> the device in question and is consistent with the file's<br />

record length.<br />

This is the extent sequence number <strong>for</strong> the first extent on the real volume<br />

being reported on.<br />

This is the number of extents that are on the real volume <strong>for</strong> the file being<br />

reported on.<br />

FILE IDENTIFI<strong>CA</strong>TION, PREFIX FLAGS<br />

The first flag (#) is displayed <strong>for</strong> any file that has one or more extents that<br />

overlap the pool space in question. Where there are multiple pool spaces<br />

defined on a single volume, this flag should not be trusted, because it can be<br />

raised by extents that are entirely contained in the other pool spaces on the<br />

volume.<br />

The second flag can have the following values:<br />

• - if the <strong>for</strong>mat-1 record doesn't contain the <strong>CA</strong> <strong>Dynam</strong>/D system ID.<br />

Continuations of files beyond the first real volume cannot have this ID set<br />

even though they were created under <strong>CA</strong> <strong>Dynam</strong>/D control, and so can<br />

have the - prefix set.<br />

• < if the extent sequence number of the first extent <strong>for</strong> this volume or pool<br />

space is not 0. This can occur if the first extent was created with an<br />

EXTENT statement containing a nonzero sequence number (allowed by<br />

<strong>VSE</strong>). Otherwise it is a correct indication that the file has prior extents on<br />

another real volume.<br />

• > if the <strong>for</strong>mat-1 record complete on this volume flag is not set. This can<br />

occur if the file was never closed, and also <strong>for</strong> certain system utility or<br />

PIOCS files. Otherwise it is a correct indication that the file has subsequent<br />

extents on another real volume.<br />

• * if the conditions <strong>for</strong> both > and < are satisfied.<br />

Chapter 5: Supporting Disk File Management 5–45

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!