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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

Record 2: a track header record. This consists of data that describes the set<br />

of blocks that follow (such as block numbers <strong>and</strong> the number of tape records<br />

required to hold these FB-512 blocks). Following the control data are the<br />

actual FB-512 blocks filling out the tape record. When possible, DDR will use<br />

a 480K data buffer to store the FBA data (959 FBA blocks maximum). If<br />

storage for this buffer cannot be obtained or if the OLDFORM option was<br />

specified, then a smaller, 64K buffer will be used (127 FBA blocks maximum).<br />

Record 3: FB-512 data records. These contain the rest of the blocks making<br />

up the set. The record lengths of records 2 <strong>and</strong> 3 are 4K when FTR is not<br />

specified. When FTR is specified, these tape records are 8K, 12K, or 48K<br />

depending on the recording format of the tape.<br />

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

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 ID field<br />

contains EOJ.<br />

DDR<br />

Note: When dumping with FTR to a 3490E or subsequent tape device, tape<br />

records may vary in length (depending on the size of each track header<br />

record) up to a maximum record length of 64K–1.<br />

FTR32k<br />

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

size of 32654 bytes. Using this option instead of FTR will possibly result in<br />

more I/O to the output device <strong>and</strong> is generally recommended only when an<br />

output tape will be read by applications that cannot h<strong>and</strong>le larger blocks.<br />

Generally FTR (which is the default for many devices) is a better choice. See<br />

FTR for a complete description of this option.<br />

OLDFORM<br />

indicates that the FBA data should be dumped using the smaller buffer (64K)<br />

rather than the larger buffer (480K) to remain compatible with older versions of<br />

DDR. The large buffer was implemented to enhance the performance of<br />

dumping FBA data to a streaming tape drive in a virtual machine environment.<br />

Using the OLDFORM option in this situation may degrade performance. This<br />

option is ignored when dumping from a CKD/ECKD DASD.<br />

COpy<br />

requests that the utility copy data from one device to another device of the<br />

same or equivalent type. Data may be recorded on a cylinder basis from input<br />

device to output device. A tape-to-tape copy can be accomplished only with<br />

data dumped by this program. A tape in compact format may be used as input.<br />

For a tape-to-tape copy, the output is in the same format (compact, LZcompact,<br />

or st<strong>and</strong>ard) as the input tape. The COMPACT or LZCOMPACT option on the<br />

OUTPUT control statement is not valid for the COPY function. If it is specified,<br />

a message stating COMPACT OPTION IGNORED FOR COPY OPERATIONS<br />

is displayed.<br />

REstore<br />

requests that the utility return data that has been dumped by this program. Data<br />

can be restored only to a DASD volume of the same or equivalent device type<br />

from which it was dumped. It is possible to dump from a real disk <strong>and</strong> restore to<br />

a minidisk as long as the device types are the same. A tape in a compact<br />

format may be used as input. DDR checks to see if the input is in compact<br />

format, <strong>and</strong> exp<strong>and</strong>s the data back to st<strong>and</strong>ard format, if needed. You do not<br />

Chapter 3. <strong>CP</strong> <strong>Utilities</strong> 1805

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

Saved successfully!

Ooh no, something went wrong!