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.

v Flagged tracks are treated just as any other track for all 2314 <strong>and</strong> 2319<br />

devices—that is, no attempt is made to substitute the alternate track data when a<br />

defective primary track is read. In addition, tracks are not inspected to determine<br />

whether they were previously flagged when written. Therefore, volumes<br />

containing flagged tracks should be restored to the same cylinders of the volume<br />

from which they were dumped. The message H<strong>CP</strong>715E occurs each time a<br />

defective track is dumped, copied, or restored, <strong>and</strong> the operation continues.<br />

v A minidisk that has extended into the alternate track cylinder must be moved<br />

either to another area of the disk, or to another disk entirely. Use the REORDER<br />

option to copy or restore a minidisk to another area.<br />

v The FTR option can be used with the COMPACT option; however, DDR ignores<br />

the FTR option. This happens because when data compaction is requested, DDR<br />

defaults to using full-track-read if possible, <strong>and</strong> the tape record formats for the<br />

default are the same as those generated by FTR.<br />

v For DASDs other than the 3380 <strong>and</strong> 3390 that support the full track read (FTR)<br />

processing, the option must be specified. Otherwise, the tape is produced in the<br />

current DDR format of 4096 blocks.<br />

v Tapes created by the DDR DUMP function in compact or LZcompact format<br />

cannot be used as input to earlier levels of DDR that do not support the same<br />

format.<br />

v If performing a DDR COPY from a device with a cylinder-based allocation record<br />

to a device with an extent-based allocation record, or vice versa, <strong>and</strong> if you plan<br />

on attaching the output DASD to the system as a <strong>CP</strong> volume, the output DASD<br />

should be reallocated by issuing the ICKDSF <strong>CP</strong>VOLUME ALLOCATE comm<strong>and</strong>.<br />

If the output DASD contains a cylinder-based allocation map when it should<br />

contain an extent-based allocation map, ICKDSF will convert the cylinder-based<br />

map into an extent-based map during the reallocation. Likewise, if the output<br />

DASD contains an extent-based allocation map when it should have a<br />

cylinder-based allocation map, ICKDSF will convert the extent-based map into a<br />

cylinder-based map during the reallocation.<br />

Example 1<br />

input 191 3390 sysres<br />

output 180 3490 181<br />

dump all<br />

input 130 3390 mini01<br />

dump 1 to 50 reorder 51<br />

dump 60 70 101<br />

This example dumps all data from the volume labeled SYSRES onto the tape<br />

mounted on unit 180. If the program runs out of space on the first tape, it continues<br />

dumping onto the alternate device (181). A map of the dumped cylinders is printed<br />

on unit 00E while the program is dumping. When the first function is complete, the<br />

volume labeled MINI01 is dumped onto a new tape. Its cylinder header records are<br />

labeled 51 to 100. A map of the dumped cylinders is printed on unit 00E. Next,<br />

cylinders 60 to 70 are dumped <strong>and</strong> labeled 101 to 111. This extent is added to the<br />

cylinder map on unit 00E. When the DDR processing is complete, the tapes are<br />

unloaded, <strong>and</strong> the program stops.<br />

Example 2<br />

input 182 3490<br />

output 250 fb-512 systst<br />

restore 10 to 20 reorder 30<br />

DDR<br />

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

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

Saved successfully!

Ooh no, something went wrong!