27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

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.

DDR<br />

If you know the density of the output tape, you can use the value for “BYTES<br />

OUT” to calculate the approximate number of feet of tape used. The density is<br />

dependent on the tape device <strong>and</strong> may be modified with the value for MODE on<br />

the OUTPUT control statement.<br />

The format of the tape depends on the type of the direct access volume.<br />

Once the dump is complete, DDR writes a tape mark.<br />

FTr<br />

requests an output tape format of variable unblocked records with a maximum<br />

size of 65535. Specifying FTR will reduce the number of read I/O operations<br />

initiated on the device by reading many records (a full-track) for each operation.<br />

In addition, the tape record format (variable length <strong>and</strong> unblocked) will result in<br />

less tape used. The size of the records <strong>and</strong> the number of records on each<br />

track written to the tape depends on the density of the tape. The option can be<br />

used for those devices supporting the full-track-read feature (FTR): 3380, 3390<br />

<strong>and</strong> for FBA devices. FTR is the default for the 3380 <strong>and</strong> 3390 <strong>and</strong> therefore<br />

need not be specified.<br />

If FTR is specified on the DUMP control statement for a count-key-data (CKD)<br />

DASD but the control unit does not support the feature, a message is written,<br />

<strong>and</strong> the operation proceeds with data written, in the old format.<br />

For a count-key-data DASD, the data is moved cylinder by cylinder. Any number<br />

of cylinders can be moved. The format of the resulting tape is:<br />

v Non-FTR <strong>and</strong> Non-Compact Format:<br />

Record 1: a volume header record, consisting of data describing the<br />

volumes.<br />

Record 2: a track header record, consisting of a list of count fields to restore<br />

the track, <strong>and</strong> the number of data records written on tape. After the last count<br />

field, the record contains key <strong>and</strong> data records to fill the 4 KB buffer.<br />

Record 3: track data records, consisting of key <strong>and</strong> data records packed into<br />

4 KB blocks, with the last record truncated.<br />

Record 4: either the end-of-volume (EOV) or end-of-job (EOJ) trailer label.<br />

The end-of-volume label contains the same information as the next volume<br />

header record, except that the ID field contains EOV. The end-of-job trailer<br />

label contains the same information as record 1, except that the cylinder<br />

number field contains the disk address of the last record on tape <strong>and</strong> the ID<br />

field contains EOJ.<br />

v FTR or Compact Format:<br />

Record 1 <strong>and</strong> Record 4 are the same as described for the non-FTR format.<br />

Record 2: a track header record, consisting of fields containing the length of<br />

the track, the density of the tape, <strong>and</strong> the number of count fields in the track<br />

followed by the track contents.<br />

Record 3: track data records, consisting of count-key-data records in 8 KB,<br />

12 KB, or 48 KB blocks for 800, 1600, or 6250 BPI respectively. The last<br />

block in all cases is a short block.<br />

For FBA devices, the data is moved in sets of blocks. Each set is arbitrarily<br />

called a track (there is no relation to device geometry in this terminology). Any<br />

number of blocks can be moved with one DUMP statement. The format of the<br />

resulting tape depends on whether the FTR option is used or not, <strong>and</strong> also on<br />

the recording format of the tape.<br />

v FBA Tape Format:<br />

1804 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong>

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

Saved successfully!

Ooh no, something went wrong!