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 />

FT<br />

GAINED SPACE<br />

This is a decoded value derived from the file type indicator bytes in the VTOC<br />

<strong>for</strong>mat-1 record. Generally, the codes are the same as those used on a DLBL,<br />

but VSAM is abbreviated as VS; -- is displayed if the bits as set do not<br />

correspond to one of the known file types (VS, SD, IS, or DA), which can occur<br />

with initialized but never-opened utility files or in general <strong>for</strong> PIOCS files.<br />

Reported in units appropriate to the device in question (tracks <strong>for</strong> CKD devices<br />

and blocks <strong>for</strong> FBA). First, the number of logical records <strong>for</strong> that file is<br />

ascertained, and then the number of optimal blocks required. From that, the<br />

number of units is computed and subtracted from the actual number of units<br />

used, to arrive at the number that can be gained.<br />

This figure is correct <strong>for</strong> a file whose extents are partly outside the pool space<br />

being reported on, but the potential gain shown applies to the whole amount<br />

of space reported as TRACKS/BLOCKS ACTUAL (see below) even if that is not<br />

all in the pool space.<br />

Note that <strong>for</strong> sorting on the REBLOCK report the savings are converted into<br />

bytes to make figures <strong>for</strong> different device types comparable. This can result in<br />

some unexpected figures in this column, but the sort order is nonetheless<br />

correct.<br />

PERCENT HI/LO<br />

This figure can be computed in the following ways:<br />

• For under-allocated files it is shown as the percentage of the original<br />

request by which the actual amount used exceeds the original request, and<br />

has a minus sign (-) appended.<br />

• For over-allocated files it is shown as the percentage of the actual amount<br />

used by which the original request exceeds the actual amount, and has a<br />

plus sign (+) appended.<br />

On the REALLOC report the sort variable is the absolute value of whichever of<br />

the percentages mentioned above has been calculated, so that over- and<br />

under-allocated files are presented together in the output.<br />

REBLOCKING GAIN INFO<br />

The fields in this section are filled only if the file is type SD with record <strong>for</strong>mat<br />

F or FB, <strong>for</strong> which the record length and blocksize have been recorded in the<br />

<strong>for</strong>mat-1 record. For all other files these fields are left blank.<br />

RF<br />

TRACKS/BLOCKS<br />

ACTUAL<br />

This is a decoded value derived from the record <strong>for</strong>mat byte in the VTOC<br />

<strong>for</strong>mat-1 record. The <strong>for</strong>mats F, FB, V, VB, S, SB, and UN are decoded. If the<br />

bits as set do not correspond to one of these codes then -- is shown. This<br />

often occurs with PIOCS files and also with continuations of files beyond the<br />

first real volume.<br />

This is reported <strong>for</strong> all files or portions of a file, It shows the total amount of<br />

space used on the real volume in question, regardless of whether it is in the<br />

defined pool space.<br />

5–46 <strong>User</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!