DASD 0305 LINKED R/O; R/W BY RACFVM at ITSOZVM4 Ready; T=0.01/0.01 15:38:12  ipl 490 RACFVM CMS XA Rel. 27 2011-10-18 Ready; T=0.01/0.01 15:38:50 acc 305 l DMSACP723I L (305) R/O Ready; T=0.01/0.01 15:39:28 acc 190 t DMSACP723I T (190) R/O Ready; T=0.01/0.01 11:42:47 def t3390 200 100 DASD 0200 DEFINED Ready; T=0.01/0.01 10:27:41  def t3390 300 100 DASD 0300 DEFINED Ready; T=0.01/0.01 10:27:45  link racfvm 200 f200 rr DASD F200 LINKED R/O; R/W BY RACFVM at ITSOZVM4 Ready; T=0.01/0.01 10:29:06 link racfvm 300 f300 rr DASD F300 LINKED R/O; R/W BY RACFVM at ITSOZVM4 Ready; T=0.01/0.01 10:29:13 ddr z/VM DASD DUMP/RESTORE PROGRAM  ENTER: in f200 dasd ENTER: out 200 dasd ENTER: sys cons ENTER: copy 0 99 HCPDDR711D VOLID READ IS RACF DO YOU WISH TO CONTINUE? RESPOND YES, NO OR REREAD: yes ENTER NEXT EXTENT OR NULL LINE GLYPH<SM590000> In the example environment, no temp disk was available that was large enough to hold the  same disk size of the RACF database. The environment was created with four SSI  members, which means you must allocate a full pack DASD for the RACF database.  To overcome this situation, and knowing that the size that the RACF database uses is less  than the full pack disk, create a smaller copy of the RACF database on a temporary disk  by using DDR. Example 5-32 shows the output of this process. During the example tests, the exec ran with some problems: Example 5-32 Creating a smaller copy of the RACF database Chapter 5. Security policy management on IBM z/VM  139