12.01.2013 Views

z/OS V1R8 DFSMS Technical Update - IBM Redbooks

z/OS V1R8 DFSMS Technical Update - IBM Redbooks

z/OS V1R8 DFSMS Technical Update - IBM Redbooks

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.

If you recover a data set from a fast replication dump copy you could find the information in a<br />

VTOCCOPY data set that was created under control of <strong>DFSMS</strong>hsm (see Figure 7-53).<br />

If you want to recover from a DASD fast replication copy a VTOCCOPY data set is not<br />

available.<br />

You will find all this information in DCOLLECT output (see Figure 7-55 on page 241) of the<br />

volumes that are being backed up by using fast replication.<br />

BROWSE HSM.DUMPVTOC.T450116.VMHL0A0.D07071 Line 00000000 Col 001 080<br />

Command ===> Scroll ===> CSR<br />

********************************* Top of Data **********************************<br />

SYS1.VTOCIX.MHL0A0 ..Å......... ...h....{..............<br />

TESTFR.DCOLLECT.D997 ..,.....,... ..Ø{....Ø..............<br />

SYS1.VVDS.VMHL0A0 ..Å...........Ø.Ø....Ø..............<br />

TESTFR.DCOLLECT.D999 ..,.....,... ..Ø{....Ø..............<br />

TESTFR.DCOLLECT.ESDS0.DATA ..,.....,.....Ø.{....Ø..............<br />

TESTFR.CNTL.JCL ..,.....,......ØØ....μ..............<br />

TESTFR.DCOLLECT.ESDS01.DATA ..,.....,.....Ø.{....Ø..............<br />

TESTFR.SRCHFOR.LIST ..,.....,... ..Ø&..À.Ø..............<br />

TESTFR.MHLRES2.MVOL.DATA ..,.....,... ..ØØ..À.Ø..............<br />

UCAT.TESTFR ..,.....,.å...{.{....Ø..............<br />

UCAT.TESTFR.CATINDEX ..,...........{.h....Ø..............<br />

******************************** Bottom of Data ********************************<br />

Figure 7-53 Dump VTOCCOPY data set created by <strong>DFSMS</strong>hsm based on dump class setting<br />

When you run a job (Figure 7-54) right before you start a fast replication for a copy pool, you<br />

can preserve the volume pointers as well as the information of the type of VSAM for future<br />

use.<br />

//STEP1 EXEC PGM=IDCAMS<br />

//*<br />

//*<br />

//SYSPRINT DD SYSOUT=*<br />

//DCOUT DD DSN=MHLRES2.DCOLLECT.SG1,DISP=(MOD,CATLG),<br />

// SPACE=(CYL,(1,1),RLSE),RECFM=VB,LRECL=644,<br />

// STORCLAS=HSMFR<br />

//SYSIN DD *<br />

DCOLLECT -<br />

OUTFILE(DCOUT) -<br />

STORAGEGROUP( -<br />

SG1 -<br />

) -<br />

/* END OF DCOLLECT COMMAND<br />

Figure 7-54 Example JCL for execution of a DCOLLECT run<br />

We recommend reusing a data set for output that is allocated on one of the copy pool<br />

volumes. This makes sure that you never become confused about which data set provides<br />

accurate information for a particular fast replication backup version that you intend to use for<br />

recovery.<br />

You must be prepared to not be able to open a copy of this data set from one of the target<br />

volumes. So, if you need to access more than the current content of such a data set, start<br />

240 z/<strong>OS</strong> <strong>V1R8</strong> <strong>DFSMS</strong> <strong>Technical</strong> <strong>Update</strong>

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

Saved successfully!

Ooh no, something went wrong!