z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Performing a virtual export of logical volumes

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

You can use DFSMSrmm subcommands to perform a virtual export for a private logical volume to an existing exported stacked volume container. A virtual export is when you use the DFSMSrmm subcommands rather than VTS export processing to export a volume. This is possible if you have imported a logical volume from a stacked volume, processed the logical volume only for input, and now want to re-associate the logical volume with the previously exported volumes on the original stacked volume container. You use the CHANGEVOLUME subcommand with the CONTAINER operand to do the virtual export. For example:
RMM CHANGEVOLUME V12345 CONTAINER(S26901)

DFSMSrmm changes the status of the logical volume to scratch in the library manager database prior to ejecting the volume. This results in a logical eject which deletes the logical volume from the library manager database. DFSMSrmm then adds the volume logically back into the container.

For the logical eject to work and delete the logical volume from the TCDB and the library manager data base, the scratch categories in the VTS must be defined with the 'Fast Ready' attribute. If you do not use the fast ready attribute for your scratch categories, do not use virtual export. If you do so, you will receive messages CBR3650I and EDG3726I with error code '06' and the volume will not be deleted from the TCDB and the library manager data base.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014