Creating a volume component from an existing z/OS instance that ZD&T or ZVDT runs on Linux

After you configure an existing z/OS instance that ZD&T or ZVDT runs on a host Linux® system, you can create a volume component from the source environment with faster speed.

Before you create a volume component from such a source environment, ensure that the following two requirements are met.
To create a volume component, complete the following steps.
  1. Select a Linux running a ZD&T or ZVDT instance environment that you want to connect to from the drop-down menu in the SOURCE ENVIRONMENT pane.
  2. Click Create components on the home page. Or, click the Components tab on the header, and click Create component.
  3. Enter the credentials of the existing z/OS instance on Linux.
    Note: Contact your administrator if you do not have the information.
  4. Enter a unique name that can be used to recognize the volume component.
  5. Optional: Select if you want the system residence files to be contained in the component.
  6. Optional: Enable the Adjust advanced settings option, and enter an integer in the box of Concurrent extractions to define the number of volumes that you want to copy simultaneously.
    Note: Concurrent extractions can copy multiple volumes in parallel, and improve the efficiency of creating components with multiple volumes. However, if the number is too large, the system might be overloaded, and the overall process might be slow.
  7. Optional: Enter some notes that can help you identify the component.
  8. Select the volumes that are needed to create your component.
  9. Click Show number items selected to verify the volumes that are selected to create the component.
  10. Click Create component directly. Or, click Schedule extraction to specify the date and time that you want to create your component.

    When you create a component, all the volumes that are copied will be stored on the system that you configured for storage.

  11. Enter the credentials to log in the Linux that runs the ZD&T emulator or the ZVDT hypervisor.