Creating a Global Copy relationship using DS CLI

Complete this task to create a Global Copy relationship between a source volume and target volume.

Before you begin, ensure that you have met the following conditions:

The remote mirror and copy license key is installed and enabled to allow operations to be performed. If you are using a Model 2105 ESS as part of the configuration, ensure that you have PPRC Version 2 license enabled.
The I/O ports are configured for paths between source and target LSSs.
The fibre-channel paths are created between all Metro Mirror source and target LSSs. The paths are needed for communication between the volume pairs and to copy data from the source volumes to the target volumes. Otherwise, this task fails.

You can create a Global Copy relationship between a source and target volume. Global Copy functions run on the DS6000™ storage units and are supported on many operating systems. For example, if you set up and configure your DS6000 to use i5/OS^®, you can use Global Copy to create a copy of a System i™ disk pool on a separate DS6000, typically in a remote location.

Perform the following steps to create Global Copy relationships between the source volumes and target volumes.

Issue the lsfbvol command (for fixed blocked (FB) volumes) or the lsckdvol command (for count key data (CKD) volumes) to display which volumes are available for Global Copy relationships on the source and target LSSs. A report is displayed that shows the availability of the volumes.
Issue the mkpprc command to create a Global Copy relationship between a source volume and a target volume. Enter the mkpprc command at the dscli command prompt with the following parameters and variables:
dscli>mkpprc -dev storage_image_ID -remotedev storage_image_ID
-type gcp -mode full SourceVolumeID:TargetVolumeID
Notes:
1. The -remotedev parameter specifies the ID of the secondary storage unit.
2. The -type gcp parameter specifies that one or more Metro Mirror volume relationships be established. Global Copy creates the remote mirror and copy relationship in an asynchronous manner.
3. The shortened version of the SourceVolumeID:TargetVolumeID parameter is shown (value = 0100:0100) because the example uses the fully qualified -dev storage_image_ID and -remotedev storage_image_ID parameters. If the fully qualified -dev and -remotedev parameters were not used, you must use the fully qualified SourceVolumeID:TargetVolumeID value. For example: IBM.1750-68FA120/0100:IBM.1750-68FA150/0100 . This value must be placed at the end of your command line.
Example
```
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 
-type gcp -mode full 0100:0100
```
A confirmation message is issued for each successful Global Copy volume association that is created.
Issue the lspprc command to view the status information of each Metro Mirror relationship in the list. Enter the lspprc command at the dscli command prompt with the following parameters and variables:
dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -s SourceVolumeID:TargetVolumeID.
```
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 
-s 0100:0100 0101:0101  
```